The Stupid Programmer Manifesto
hasen.substack.com
The Stupid Programmer Manifesto
1–10 of 239 posts
Re: The Stupid Programmer Manifesto
#2Re: The Stupid Programmer Manifesto
#3Re: The Stupid Programmer Manifesto
#4Even if I have the experience, I still decide to use sqlite, single binary, local files, vps, monorepo. At least until market-fit is proven.
Re: The Stupid Programmer Manifesto
#5Re: The Stupid Programmer Manifesto
#6I'd reverse that for myself. I am not smart enough to cross-compile my project or statically link, so I throw it in a docker container and call it a day.
Re: The Stupid Programmer Manifesto
#7Though there’s one thing I take issue with. „I’m too stupid“ implies that these techniques are impossible to understand, while I think it’s just a matter of being able to put in the time and effort to learn the intricacies. It’s absolutely fine if the resources (mainly time) aren’t available to you, but I don’t think it’s a matter of cognitive function.
Re: The Stupid Programmer Manifesto
#8How can you store program state on disk like that? You'd need serialization and deserialization. A DB might be easier.
Re: The Stupid Programmer Manifesto
#9It’s important to keep in mind that pretty much all the techniques you’re too „stupid“ for all aren’t necessities for small projects, but rather being able to manage complexity (or workload) at scale. For an MVP or a small product, keeping with the simpler techniques is absolutely fine, and adhering to those standards in many cases can even be considered overengineering. Though there’s one thing I take issue with. „I…