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.