There shouldn’t be any shame in writing small software. Everything doesn’t have to “scale”.
If you build something cool it’s valid and good if it makes you or just a few people happy.
This doesn’t make you a bad programmer.
Y’all encouraged me to explore this topic a bit more:
@requiem software that solves one problem for one person once is successful. any use that software sees beyond that first use is gravy; it did its job. and if someone writes a lot of software that in the end did its job they are a pretty damn good programmer, I reckon.
@requiem I think maybe we need to pursue new definitions of "scale" or find a new attribute to aspire to. Maybe "spread" or "inspire". "Yes, but can it spread?" 😆
@requiem That's one reason why I enjoyed Project Oberon so much. Although it's still not refined enough for day to day operation, it's really close. And although it's not super-hyper-optimized like Linux is (or can be, at least), it's plenty fast enough for personal use.
Once upon a time, I used Forth to drive my personal blog. I was told, in no uncertain terms, that Forth was wholesale unsuitable for the task. I took it as a challenge, and named the blog engine Unsuitable as a result. It happily ran my site for about three years, as I recall. ;)
@vertigo @kazriko I am mesmerized by the self-contained nature of project Oberon software (down to describing the processor itself!). I’ve considered building some systems based on it, but it’s a lot to do alone and hard to stay motivated without an audience.
I would love to participate with others on applying that system though, so it’s encouraging to meet people who also get it.
A bunch of technomancers in the fediverse. This arcology is for all who wash up upon it's digital shore.