Radek Voltr
16.1K posts












3D printed stencils are the superior stencils, no more being beholden to big stencil. Take a look at how fast and easy it is to apply, no messing around with tape or surrounding it with other boards. It’s only going to get better from here.











This sums up everything nicely. The M1 MacBook Air is as good or better than the Neo and came out 6 years ago. Sure it launched at $1000 compared to $600, but $400 less for a laptop that at best matches a 6 year old base model? I'm not really seeing the value. It's fine, but it's not special. The M1 MacBook Air 8gb did not age all that well due to ram limitations. The Neo won't magically do any better.


25 signs your vibe-coded app is a TICKING BOMB ! 1. API keys hardcoded “for now” 2. No /health endpoint, you just hit the homepage 3. Schema changes live in your head, not migrations 4. Every query is SELECT * and vibes 5. Error handling = console.log(e) and hope 6. No rate limit on auth or writes 7. UTC, local time, and “JS default” all mixed 8. README is empty or wrong 9. No staging env, just “dev” and “prod-ish” 10. One god component owns the whole screen 11. No analytics, just “feels like people use it” 12. You say “we’ll clean this up after launch” every week 13. Env vars live only on your laptop, nowhere else documented 14. Frontend talks directly to 5 different third-party APIs with no wrapper 15. No monitoring or alerts – you find out it’s down from a DM 16. Logs only exist in your local terminal history 17. DB backups are “automatic”… but you’ve never tested a restore 18. Feature flags = commenting code in and out 19. Deploys are done from your local machine with one random script 20. No input validation, you trust whatever the client sends 21. CORS is set to * because “it fixed the error” 22. CI is “I ran it once locally and it worked” 23. Same API token reused across staging, prod, and local 24. Only one person actually knows how to run or deploy the app Bookmark this to defuse today LOL




























