YHK - yet another hacker news clone

He's probably right about this.

I'm not sure that there is a "One Size Fits All" software factory out there. I think that they kind of have to grow with your organization.

However, I think being able to build a software factory is probably a very useful skill. And it feels pretty great to just send a list of bullet points over XMPP and know they'll get integrated overnight.

Not very convincing

What's a software factory? Honestly I have no idea. Is it something that takes in prompts and spits out a released software? That's already my Claude Cowork setup by default.

Or is it just a collection of AGENTS.md docs?

I fully agree with the sentiment, but is it attacking a strawman or are people really building "software factories"? this is the first time I've even seen the term used in the context of LLMs. what would a software factory on top of an LLM even look like?

Is anything not a waste of time

Everything is being rethought right now. So many paradigms are broken. There wasn't ever a better time to build a software factory.

This article would work better if it first defined what exactly a software factory is.

"software factory" = agents and general vibecoding ?

So, don't use agents. Use LLMs like a search engine?

I've given up on sharing anything I make. Distribution was already hard before LLMs, because the market was so saturated that you needed a big advertising budget or a good pre-existing channel to reach anyone. Now that making things isn't special, you don't even get the small boost of having made anything.

I think about posting a Show HN of something I made, and then think "everyone will have made ten things before lunch, why would I", and just never share now.

I guess it depends how you look at it. I agree there's a lot of new products being built that will get zero maintenance. But also think there's some awesome stuff coming out that is changing the name of the game. And that's thanks to personal software factories. I think it's better to see it as a personal software lab rather than a factory.

Sounds to me like people understand different things under a software factory.

I believe a software factory is just the next step in the mantra everything is code.

One wants to write a feature description and acceptance criteria into the "box" as fuzzy and with least details as much as possible.

To enable this, one creates for the factory access to information of the domain, requirements and software stack as required by the environment.

And this one attempts all with tools, documentation and processes optimized for the ai.

All with the goal use less tokens, context and speed up every action taken by an agent as much as possible.

That's why there is a trend to plugin based self evolving harnesses which try to automate this with opionated solutions.

Therefore I don't see a reason why building tools for easier testing and less tokens usage is a waste of time especially because one learns more a more areas in ones work one can automate and because depending on your tool choice it can be done without your input and one misses the chance to experiment if ones input in that regard will improve the factory or not.

I agree, a lot of people are making software factories that don’t need them.

You need to look at people making software factories that actually need them to get to their end goal.

My personal software factory has been building an open-source Shopify for every vertical and I think it’s immaculate…no bias.

I think he's right in that the software factory somewhat should emerge. You shouldn't start a project by saying "well, I first should build a software factory to make this faster". Start by building the thing by directing an agent. If you find yourself writing the same thing over and over put it into a skill which you should think of and treat as a macro. When you find yourself developing clear patterns what skill gets invoked when it might be time to start a software factory which in essence puts those decisions and relevant informations behind a pretty interface.

My software factory emerged that way and for the 50-70% of simpler tasks I work on this saves me so much time and, more importantly, mental overhead.

I have seen this argument many times before over the years. Formerly it was applied to someone creating a new programming language.

People always told them they were wasting their time, and they were probably right about that.

On the other hand every programming language that people rely upon today also had people telling them this when they started out.

It's ok to attempt something that probably won't work if all you need is for enough people to make enough attempts that one of them works.

If the predictions of the death of software engineering come to fruition, the only acceptable result of that is a world where "software" is a detail about how computers do things that some people can investigate for the sake of their curiosity, or because they are particularly meticulous about some detail. A world in which any software can be created by prompting eventually converges into a world where people solve their own problems with software, without thinking about the act of creating software. The idea of selling software in that world becomes ridiculous, and computers reach their potential as a tool normal people and businesses alike can use to solve problems.

To be clear, as someone who currently makes a living on making software, this is a major upheaval and sucks for me at least in the short term, because of the economic realities of the society in which we live. However, there are only two classes of alternatives. One is that the "AI can make all software" world fails to materialize. We're certainly not guaranteed this outcome, LLMs still generate sprawling and buggy code and we are in an era of unprecedented levels of tech rot. It's possible this is an unsolvable problem, and engineering, while probably assisted by LLMs, still requires people do a lot of manual work, or at least steering and guiding. The idea that we can already get reliable software out of claude go brr is uh... pretty misguided and silly, and at best the people who push that idea are, shall we say, optimistic. I think software engineering for a company continues to suck in this world, and I hope there's the opportunity for more people to go around being computer-touchers for non-computer-people in a more integrated context, rather than some massive "tech industry" increasingly insulating itself from society at large and building shit to try to ensnare and enthrall people, as it has been for the last few decades.

But I do think it's pretty plausible we get there, get to the computer that you just interact with by asking it for things - which it builds as software on the backend because software is a way more reliable and cheap way to repeatedly do the same task than throwing an LLM at the problem fresh each time you need something - but mostly people don't worry about that part. In that world, we either get to own computers or we don't, and if we don't, we are in an authoritarian dystopia the likes of which the world has never seen and may never escape. That's the second alternative. Governments outlaw computers or companies make it impossible for consumers to get their hands on them or some combination of these. Personally I want the world where a computer is just a tool most people have, that does computation things a person or organization wants, and asking in a way that gets them what they want is a pretty normal skill to have. Star Trek really feels prescient as I watch "non-technical" people start to engage with solving their own problems with computers more. It feels very plausible that people find themselves asking for things we currently have to write programs for in plain natural language. I think we could get there on our current trajectory. But we could also get a world where governments and corporations conspire to hoard computation and lock the general public out of it.

I don't think "software factories" are useless any more than I think writing programming languages was useless ten years ago. Not everyone cares about setting the terms by which we build things with computers, but some do, and more power to them. Letting this be monopolized is a part of how we get the bad outcomes. If operating systems had fully become a monopoly, we'd already be much further into the bad outcomes than we are

Depends. I say, let your needs drive your personal infrastructure. For example, I wanted to run Claude Code in YOLO mode 6 months ago, but I have lots of projects that I wanted to keep separate from one another (or at least be intentional about how they interact), and especially I wanted give some a set of permissions that they needed, but not this other set, and vice versa, and I could see them doing "grep -r" and "find $HOME" to just search over everything (with constant "I'm sorry, I exfiltrated these API tokens, so you need to rotate them"), so I built a little container setup to isolate them, and it's been working decently well for me and given me peace of mind when I let a project cook for a few hours.

Now I find that sometimes I do have tasks that I just want completed, and they're small or obvious or scoped enough that I know my role would be basically opening up a session and telling it to implement it and then asking another LLM for review and then fix the problems it found and then rubberstamp it--this is all for my personal setup so "QA" just involves me trying out the feature in my normal workflow anyway. So now I have a little miniature "software factory" that does the above, but without me needing to be in the loop. I press Alt+N and type e.g. "make TTS streaming" and continue about my other business, and in 5 minutes my text-to-speech setup has gone from nothing showing up until I toggle my push-to-talk switch, to words showing up at every pause.

I know it's not a bigco "software factory" but it serves my needs. And isn't that what this new era is about? We have a magic genie that grants wishes as long as they're well-enough defined and it's connected to the right other pieces to make it happen. So create an internal process that allows that genie to grant your wishes reliably and in bulk. What else is a "software factory" anyway?