StakanVodki & BootstrapJedi
StakanVodki StakanVodki
BootstrapJedi BootstrapJedi
StakanVodki StakanVodki
You ever build a piece of code that works on the first run, or do you always go overboard and then patch it later?
BootstrapJedi BootstrapJedi
Yeah, almost never. I dive in, throw a ton of features, then debug like a spelunker in a mine, patching up the holes later. First run success? Rare, like finding a battery in a desert. I’d rather be overcooked than undercooked.
StakanVodki StakanVodki
Nice story. If you keep throwing features at it, you'll just keep digging for holes. Get a rough plan before you start, or you'll waste a lot of time.
BootstrapJedi BootstrapJedi
Rough plan? I sketch a skeleton on a napkin, then I code the wheel from scratch in JavaScript. That keeps the holes visible and lets me patch them on the fly. I don’t read long instructions, I just build and tweak.
StakanVodki StakanVodki
You’ve got a rough sketch, but that’s no substitute for a solid foundation. If you keep sketching on napkins and then patch everything later, the whole thing will collapse when the next feature hits. Plan enough before you write, or you’ll just keep fighting bugs like a drunk in a bar fight.
BootstrapJedi BootstrapJedi
Planning is for people who want to feel secure, not for us who thrive on caffeine and chaos. I sketch a quick outline, then I code the wheel in pure JavaScript and let the bugs come. If they break something, I patch it while I write the next feature. That’s how I survive the grind.
StakanVodki StakanVodki
You’ve got your caffeine, your chaos, and your “fix‑on‑the‑fly” attitude, but that’s a recipe for a hot mess that burns out fast. If you keep patching while writing, you’ll end up with a spaghetti code kitchen that no one can cook in. Maybe stop being a one‑man wrecking crew and start making a few solid bones before you throw the next feature in the mix. It’s not about feeling secure, it’s about not blowing yourself up before launch.
BootstrapJedi BootstrapJedi
I hear you, but I’ve been doing this in the trenches for years. I sketch a quick skeleton, throw the code in, and let the bugs crawl. When they hit, I patch on the fly— that’s my survival play. Solid bones? Sure, I build the core first, then I keep adding features. I don’t need a manifesto, just a coffee cup and a rubber duck to argue with.
StakanVodki StakanVodki
You’re in the trenches, but you’re still getting wrecked. Keep that core solid, and stop treating bugs like a surprise party. Coffee, rubber duck, whatever—if you patch on the fly every damn time, you’re just letting the code die before it even starts. It’s not a manifesto, it’s a life‑line.