Personal software factories are a waste of time

It's natural for a software engineer to desire building their own software factory, but I'd strongly advise against it. In fact, it may be the last thing you should focus on, unless it's for your job. The reality is that we're living in an era where non-developers are leveraging AI in extraordinary ways, and yet, you haven't created anything significant yet. Many of these ideas are merely demonstrations on platforms like X, but they're still more valuable than merely constructing a software factory.

There are several reasons why building a software factory might not be worthwhile. Firstly, it's familiar territory that you've excelled in before. It's comfortable and aligns with your established habits. Secondly, the allure of using it to develop more side projects and eventually leave your current job is compelling. However, the truth is that a software factory is simply an extension of what you've always done: initiating projects, abandoning them, and returning to work the following Monday.

I'm not suggesting you should cease exploring and creating side projects. Rather, I'm urging you to stop investing time in your software factory. Instead of building it, consider interacting with AI tools like Grok Bot or Claude. These are impressive technologies. Perhaps you shouldn't, but I am. At the very least, understanding how these tools function has deterred me from attempting to construct another factory.

The frontier labs are concentrating on both AI models and products, with their primary objective being to minimize friction and enable you to create remarkable things. Their number one goal is to remove obstacles, allowing you to build fascinating products. Confronting this reality, why would I want to build a software factory? If you're still convinced you should create a software factory and believe I'm misguided, it must be for your job.

Your role provides the most practical scenario for automating your job. You understand the system thoroughly (or should), and it involves humans, timelines, and years-old complex systems. You likely have multiple methods for writing the same feature and numerous edge cases. This is precisely why building a software factory at work could be beneficial.

The challenge is far greater, but so is the reward. You've now empowered an entire team of product managers and designers to ship features with minimal friction and high trust. Subsequently, your job would be to maintain that platform or apply your other skills to other areas of the business. If you find yourself unable to devise anything else to build, you're not alone.

This task is indeed challenging, and it requires developing a skill, much like any other. Take a moment to observe your surroundings. Start jotting down your problems and ideas. Let your mind wander. If you write down three ideas daily, the initial thirty will likely be absurd and irrelevant. However, I assure you that this will gradually change as your brain begins thinking differently.

Have you witnessed the individual who de-slopped his parent's Android TV using Claude? It's astonishing. He identified a problem and used Claude to devise a solution. What about the person who integrated a fruit fly brain into the real world, where it's been flying around? How does someone come up with such ingenious ideas? I'm unsure, but I'm confident I'll eventually reach this point through experimentation and allowing my mind to wander.