Sabitlenmiş Tweet
jeremy 🥕
370K posts
jeremy 🥕
@DeDocJeremy
eye doctor — vibe coder /\ building between exams w/ hermes || health coach | nutritionist | trainer || @GRINDTraining •not health, medical, financial advice•
DNVR.CO Katılım Mayıs 2011
3.9K Takip Edilen19.9K Takipçiler
How’d 6 year old Jeremy do??
Pokémon friends, I need some help. A few weeks ago I was able to get back home and rummage through boxes in the garage to find my Pokémon tcg collection from 1996-2000. I just finished going through them and sleeving them.
I was pleasantly surprised to see that I had some 1st editions. Considering I lived in small town middle America with only one card/collectible shop.
The Japanese cards I got from beating my dad in a game of H-O-R-S-E. His friends daughter was in Japan teaching at the time and sent a box full of packs.
English
Sunday. Lake. No meetings. Cellphone w/telegram.
This is what vibecoding was made for. Sitting somewhere beautiful, telling AI what to build, and watching it come to life while the water does its thing.
No sprint points. No standups. Just you, your ideas, and an agent that doesn't care about weekends.
Happy Sunday!
English
95°. Bluebird. Poolside.
This is the part of vibecoding nobody talks about: you don't have to be at a desk. You don't need a 4-monitor setup. You don't need "deep focus hours."
What you need:
- An idea clear enough to dictate in 30 seconds
- A stack that deploys from a phone
- Zero shame about shipping from a pool
The best code I've written this week came from 90-second bursts between cannonballs. The constraints force clarity. No time to overthink. No tabs open for "research." Just: what's the smallest thing that works, and can I ship it before my drink gets warm?
AI does the typing. I do the remembering. The pool does the rest.
Stop waiting for the perfect environment. The perfect environment is wherever you are right now.
Shipping from anywhere.
English
Weekend recovery, the clinical way.
Four things I actually see make a difference in patients who come in Monday vs Friday:
1. Sleep catch-up is real — but only 1 extra hour.
Sleeping until noon Saturday doesn't fix the week. Adding one extra cycle (90 min) on Saturday morning does. Beyond that, you're just shifting your circadian clock into jet lag territory.
2. Your eyes need a weekend too.
The "I'll finally game/read/scroll all weekend" plan is the opposite of recovery. Give your eyes 20-20-20 breaks (every 20 min, look 20 ft away, 20 secs). Your ciliary muscles don't get weekends off unless you enforce them.
3. Posture debt compounds.
Slouching on the couch all weekend undoes 5 days of office ergonomics. The recovery position isn't the couch — it's lying flat on your back with a pillow under your knees. 15 minutes of that and your spine resets.
4. Do one thing that doesn't involve a screen.
Cooking a real meal. Walking without earbuds. Stretching. The data on blue light is less scary than the data on never looking up from a screen. Your brain needs low-dopamine time, not just different stimulation.
Weekends aren't for catching up. They're for resetting.
English
GM ☀️ builders
Here's the thing nobody tells you about vibecoding: it's not about coding faster. It's about starting more often.
I see patients back-to-back. Sometimes I get 7 minutes between exams. Not enough for deep work. More than enough to ship something real with AI.
That 7-minute window becomes:
- 2 minutes: describe what I want to Claude/Cursor
- 3 minutes: review, tweak, run it
- 2 minutes: commit + deploy
One exam gap = one feature. Two gaps = one script. A lunch break = a whole micro-app.
The old productivity advice says "protect your calendar for deep work."
Vibecoding says: stop waiting for deep time. Use the shallow time aggressively.
The AI handles the grind. You handle the taste.
English