logoalt Hacker News

rc-1140 • yesterday at 9:44 PM • 1 reply • view on HN

What I'm getting from the contents of the blog post is that there's a constant fight the author has with their audience that I'm summarizing as "I think your endeavor is foolish and you shouldn't do it, but I'm not your boss so who cares, but it's a bad idea, but it could be useful, but you shouldn't do it".

I think if you have plans for a software factory (read: some kind of conceptual framework for a loop that turns tasks into code/features), you should try it. My opinion is that even if your implementation is a bust or you never take it past a proof of concept, you've at least done something to inform yourself about what's out there and what you've tried.

Better to have a graveyard of barely started projects that give depth to your knowledge instead of relegating yourself to prompt slavery because [frontier model of the financial quarter] can do Marvel + Bioshock + Ted Lasso + Command and Conquer or whatever horrifying Consumptionslop™ that people like Nikita Bier love so much.


Replies

honr • yesterday at 10:44 PM

Exactly. As for the article itself, I would take with a grain of salt as the author's previous company built some sort of software factory. I think we can give them the benefit of the doubt and move on.

With that out of the way, I think trying out developing software-building automation is a great learning experience, regardless of the final outcome. Beside [re]learning various ropes that might have been modernized recently, you are likely to end up with bonus [possibly tiny] helper tools that you can carry into your other software development projects. Or you might learn new [non technical] disciplines around software development life cycle.