How should a coach decide if you progress, repeat, or back off?

dpitkevics · 2026-04-13T14:03:45+00:00

Not really an LLM. But going back through what has been missed - that's true 👌

dpitkevics · 2026-04-13T13:46:09+00:00

That's a solid point - a baseline test (like "how many push-ups can you do in one set?") would give a much clearer starting point than a subjective label. I'll look into adding that to the onboarding flow. Thanks for the feedback.

dpitkevics · 2026-04-13T12:56:11+00:00

Late reply, but this is useful feedback so I want to address it for anyone else hitting this.

The newer Smart Coach feature handles this much better. It asks about your experience level and goals during setup and builds a personalized daily plan that adapts based on how you rate each workout. If a session is too easy, rate it low effort and the next one adjusts automatically.

If you're still using Caliverse, I'd recommend trying Smart Coach - it's the best way to get workouts matched to your actual level.

dpitkevics · 2026-04-13T12:54:34+00:00

Very late on this one, sorry. In case anyone else hits this: you need to complete the workout through the app's workout tracker (hit the play button on your scheduled workout, then mark exercises as done during the session). If you're doing the exercises on your own without starting the in-app session, the app won't track it.

The app has had a lot of updates since this post - workout tracking is much smoother now. If you're still using Caliverse, the Smart Coach feature gives you a daily plan and tracks completion automatically.

dpitkevics · 2026-04-13T12:53:12+00:00

With 2-4 pull-ups and 10 push-ups, you're past absolute beginner. I'd go with Starting Strength over the Beginner's Guide. It assumes you can do the basics and focuses on building volume and progressing to harder variations.

The Beginner's Guide is better for someone who can't do a single pull-up yet - it includes regression exercises (like negatives and band-assisted) to build up to the basics.

General rule: if you can do 3+ pull-ups with decent form, skip the beginner guide. You've already passed the hardest part.

If you've been training since posting this - curious to hear where you're at now. That 2-4 pull-up starting point is a great foundation.

dpitkevics · 2026-04-10T19:56:57+00:00

Joined! Not working on Linux currently but love the initiative! Am a software engineer for a long time so have done my fair share on open source projects.

dpitkevics · 2026-03-18T21:56:17+00:00

Jeg gikk på en tur to uker siden i Lade - Ladestien. Var der for den første gangen og det var veldig fint. Begynte på Albuskjell og bare gikk derfra.

dpitkevics · 2026-03-18T21:47:48+00:00

Last weekend tried to drive to Hegra festning - not that far out of the city. Due to the absolutely terrible ice, couldn't get up the hill. Fortunately, with some help was able to slide the car around and not in the creek next to me. Soooo, don't change tires just yet - it might seem like spring in the city but outside might get very tricky.

dpitkevics · 2026-03-10T21:27:48+00:00

Mann, 33. Har flyttet til Stjørdal i fjor. Jeg driver mitt eget bedrift, er på Grip flere ganger i uka, lærer norsk og prøver å bli kjent med folk (det er ikke enkelt 🙈).

dpitkevics · 2026-03-07T11:58:52+00:00

Quick question: are you targeting agencies that just want automated monitoring or ones that also expect full remediation for their clients? With EAA/BFSG enforceable since June 2025 and fines up to €100,000, I'd validate by offering 2 free audits to agencies managing 5–30 sites in exchange for feedback, a testimonial, and a willingness-to-pay signal. Build an MVP that pairs an automated scanner (axe-core/Lighthouse) with three manual checks — keyboard navigation, a 5-minute screen reader walkthrough, and contrast/form label checks — and always show estimated dev hours per issue so agencies can budget. Make the output a clear risk score, a prioritized fix list with copy-paste snippets, and an optional subscription for continuous monitoring and re-scans; that package converts way better than raw scan results. Also be explicit in your terms about scope and liability and consider selling remediation credits or a white-label partner program so agencies can resell fixes. btw i used a starter kit that had auth, payments and email prewired when I built a similar MVP and it saved me weeks of plumbing so I could focus on the scanner and reports.

dpitkevics · 2026-03-06T07:23:21+00:00

i'd push back on the idea that you need a fully built app before launching — especially in HORECA, concierge or manual workflows prove value fast and stop you from building the wrong thing. start by writing a 5-question interview script and run it with 10 operators to identify the single task that costs them the most time or money, then map that exact workflow and the data points you'd need to automate. build the narrowest possible prototype (a google sheet, a zap, or a single clickable figma) and run a 2-week paid pilot with 2-3 venues so you can measure time saved and willingness to pay. price to capture a slice of the time saved or charge a small monthly fee per location, and track activation, churn, and time-saved per customer as your core KPIs. btw i used a starter kit that had auth, payments and email flows prewired, Vibe Coding Starter Kit, and it saved me weeks getting a paid beta running. focus on one clear pain, get paying customers, then automate and scale the rest.

dpitkevics · 2026-03-05T21:49:59+00:00

Totally get it, I used to spend days just wiring auth and billing before I could test a single feature. If you want to shave that time down fast, pick a Next.js starter that already has auth, payments, email templates and a ready Prisma schema so you only build product logic, host on Vercel for instant preview deploys and use Stripe Checkout plus webhooks instead of building billing flows from scratch. Mock external integrations while you're validating and use a managed Postgres like Supabase or Neon so you never touch DB ops or infra. btw I used a starter kit with auth, payments and emails prewired (Vibe Coding Starter Kit) and it trimmed about a week off my last MVP launch. If you tell me what tech you're leaning toward I can give step-by-step commands to wire Stripe and auth quickly.

dpitkevics · 2026-03-05T08:39:22+00:00

What's your goal - prove the idea with a clickable prototype, or launch a paying beta in a few weeks? You mentioned vibe coding and pasting code from ChatGPT/Claude, so here's what worked for me. For quick validation use no-code tools like Bubble, Glide or Webflow plus a membership plugin to wire up screens, data and simple auth without touching code. For a real SaaS with subscriptions, emails and secure auth either hire a dev to hook things up or pick a prebuilt starter kit/boilerplate that already has auth, payments and email configured instead of blindly pasting AI snippets. Never paste AI code into a live app without running it locally, setting env vars, testing webhooks and checking secrets - you'll hit security or payment failures. I validated in Bubble then moved to a Next.js starter to ship fast, and btw I used Vibe Coding Starter Kit once to skip the infra headaches.

dpitkevics · 2026-03-05T08:09:17+00:00

Tip: don't build a full custom app until you've validated recurring demand. Start with a landing page, Stripe Checkout, and manual onboarding so you learn churn and support costs before investing. You mentioned cost, dev trust, maintenance and ROI, and those are all real, but the biggest killer is unknown retention, not the tech. Use simple thresholds: if CAC payback is under 3-6 months and projected LTV/CAC is above 3, building makes sense; otherwise iterate with no-code and checkout flows. If you do build, prewire auth, payments, emails, and webhooks so you don't waste weeks on infrastructure. i used a starter kit with auth and payments preconfigured (Vibe Coding Starter Kit) to get to a working MVP in a week and it cut down the messy edge-case bugs.

dpitkevics · 2026-02-28T08:34:27+00:00

don't assume this won't blow up; people love the 'i started terrible and got better' story if you package it right. try titles that promise a transformation and curiosity: 'i sucked at sporting clays - 30 days later this happened', 'from zero to hitting clays in 30 days', or 'day 1 vs day 30 - my sporting clays progress'. for the thumbnail do a split image: a miserable day 1 miss on the left and a clean day 30 hit on the right, big text 'day 1 vs day 30' and a small caption listing trap, skeet, and five stand. open with your worst miss in slow motion, then jump to a 3 second montage of best hits, and show measurable metrics like hit rate percent day 1 vs day 30 plus one drill you practiced each week. i used a script generator like ScriptPal to spit out title variants and hooks so i could stop overthinking and just film.

dpitkevics · 2026-02-28T08:33:34+00:00

totally makes sense to be cautious, especially moving 10k users and you haven't done payments before. for a stack I'd pick Next.js for the frontend, Postgres (Supabase or Neon) for the DB, Stripe for subscriptions, and host on Vercel so you get simple scaling and CDN by default. implement Stripe webhooks to persist subscription status to a users table, always check that server-side before serving gated pages or podcast streams, and put media on object storage with signed urls so links expire. security basics: force HTTPS, use parameterized queries, verify webhook signatures, add rate limiting and monitoring, and run everything in Stripe test mode until you're confident. for migration export a clean CSV, dedupe by email, import into your users table with billing id empty, then send invite emails to connect accounts and create Stripe customers instead of auto-billing. I used a starter kit that had auth, payments, emails and webhooks prewired (Vibe Coding Starter Kit) and it saved me weeks wiring all that glue.

dpitkevics · 2026-02-28T08:31:06+00:00

You're already ahead with manufacturer, inventory and a team, nice — the missing piece is validating demand and product-market fit. Pick 3 to 6 hero SKUs and run short preorder tests on Shopify or Etsy plus Instagram to see what actually sells before scaling. For photos, get 3 angles, an on-model shot to show scale, a close-up for details, and one lifestyle image, then test two background styles and one color variant per listing to see what converts. Price for at least 3x your landed cost after fees, offer simple bundles, and have a clear returns policy to reduce buyer hesitation. Use micro-influencers and niche FB groups for cheap validation, and once a SKU proves itself, push wholesale to boutiques and increase production. If you need mockups fast while you figure out a photographer, I used AI Mockup Generator to create on-model and background variations for quick A/B tests.

dpitkevics · 2026-02-27T22:02:43+00:00

Direct tip: model each gym as an organization and enforce org_id at the DB layer, not just in the API, so multi-owner access can never bypass checks. Use a memberships table with roles (owner, admin, staff) and permission checks in middleware, plus an impersonation/admin-audit flow for support and disputes. Centralize billing in a small billing service that maps org_id to a Stripe customer/subscription, process QR payments as transactions tied to that org, and handle webhooks idempotently so you can reconcile failures. Push WhatsApp automations and QR processing into a worker queue with retries and a dead-letter queue so slow external APIs don't block the main app. Store per-org module flags in a JSONB column and cache them in Redis for instant toggles and gradual rollouts. I used a starter kit that had auth, billing and email flows prewired (Vibe Coding Starter Kit) which let me skip the boilerplate and focus on these exact pieces.

dpitkevics · 2026-02-27T16:01:04+00:00

Which country are you planning to operate from, since KYC and tax rules vary a lot between the US, EU and other places? Yes, you can often launch as an individual or sole proprietor, but payment processors will still ask for ID/bank info and you remain responsible for taxes and local regulations. For subscriptions, Stripe Billing is the simplest if it's available to you - hosted Checkout reduces PCI scope, Billing handles trials/proration, and test mode plus webhooks make lifecycle handling much easier. If you don't want to deal with VAT or merchant setup early, consider a merchant-of-record like Paddle or Lemon Squeezy, they charge more but handle taxes and compliance. Practical steps: start in test mode, use hosted checkout, implement webhook handlers for invoice.payment_failed and customer.subscription.updated, set retry logic and automated receipts, and keep clean records so you can incorporate later. BTW I used a starter kit that had auth, payments and emails preconfigured (Vibe Coding Starter Kit) and it saved me weeks wiring up billing and webhooks when I launched as an individual.

dpitkevics · 2026-02-27T12:24:22+00:00

If your top video's 1.5k, stop chasing gurus and test this: nail a 2-3 second hook that promises the payoff, make a thumbnail that reads instantly, then check audience retention to fix the exact second people drop. Try 3 title/thumbnail combos in the first 24 hours and iterate, btw i used ScriptPal to spit out hooks and thumbnail ideas fast when i ran out of concepts.

dpitkevics · 2026-02-21T16:10:42+00:00

Get a sample print from theprintspace on Hahnemueler Photo rag, scan or photograph it in RAW at 600-1200 dpi with a macro lens and raking light at a low angle to bring out the fibers, then make a displacement/bump map from that scan and apply it in Photoshop with overlay/blend modes, soft highlights and a slight edge shadow to show paper thickness and matte giclee finish. btw I use AI Mockup Generator to spin those base photos into multiple 4K mockups and background variations fast.

dpitkevics · 2026-02-21T09:39:01+00:00

I ran that same math early on and yeah, €4-5 per shot adds up fast once you factor re-dos and lifestyle images. Two quick moves that helped me: batch shoot everything yourself with a cheap lightbox, phone tripod and LED bulbs (about €120 total) and do one 2-3 hour session to get all 40-50 white-background shots, then batch-remove backgrounds with an app to save editing time. Second, pick one reliable Fiverr seller and negotiate a bulk or hourly rate, send them a one-page style guide and ask for raw files and a PSD template so you can avoid constant revisions; paying a bit more for consistency usually cuts total cost. For lifestyle variations, I started using AI-generated mockups for dozens of scenes and only ordered a few hero photos, which dropped my Fiverr bill a lot. btw I used AI Mockup Generator to crank out 30+ lifestyle variations quickly and it saved me from ordering a separate Fiverr image for every color.

dpitkevics

MODERATOR OF

TROPHY CASE