Igor Costa

I'd like to share a few thoughts and observations I've seen on my timeline here, I find it interesting when people wonder whether software is becoming a solved problem, whether AI will eliminate the moats in software, or whether there is anything left to build. LT;DR. Software is still the MOAT. let me share my side of the story. I never assume malice when I read these posts. I understand where the concern comes from, and I want to share how I see it. 1. Excel might be the best example of why simple primitives win. Excel is arguably one of the most successful pieces of software ever built. Why? Rows and columns give people a simple way to organise data, build models, run calculations, and present information however they want. The power is not in what Excel does out of the box. It is in what people can make it do. Much of the software industry has been trying to improve on that basic idea: give people primitives they can use to solve their own problems. 2. Software factories are about personalised software. I often see the term Software Factory to describe a new way of producing software faster and thousands of PRs, but i see software factory as more of its that is personalised, adaptable, and shaped around the needs of the people using it. look how @badlogicgames did with pi and @steipete did for openclaw. Until now, if your software did not do what you needed, you had to wait for the vendor to ship an update, pay someone to change it, or build something else. That constraint is starting to disappear. You can change the software yourself. You can make it fit your work, rather than changing your work to fit the software. 3. Being able to build something does not mean everyone will. Walk into Home Depot and look at all the circular saws. The tools to build things are available, but not everyone buys one. Not everyone wants to build their own furniture, either. Some people want to make things. Others want to buy them. Many will do both. Software will be no different. The ability to build your own tools does not eliminate the market for products. It gives people more choices. 4. Software is becoming accessible to a new group of builders. What is software, after all? It is a way to turn needs, ideas, and processes into something a computer can execute. For decades, the cost and expertise required to produce software created a high barrier to entry. AI is lowering that barrier. People with good ideas can now build tools for themselves, their families, their communities, and their businesses. They do not have to convince a vendor that their problem is worth solving. That creates a much larger group of people who can participate in the software economy. 5. Software 3.0 opens up more problems to solve, not fewer. @karpathy and others have written about Software 3.0. Whatever terminology we settle on, we are entering a new phase in how software is created and used. or @tobi with Qmd, out of request, it would cost him way more than a few prompts and tokens, it would cost more money and more time to build. One vendor, one model, or one agent harness will not serve every need in this new economy. Think about it for a second. If AI agents are already solving so many mundane problems, why are my friends working at frontier labs and AI startups sleeping less? Because we are working on a new set of problems. The old constraints are falling away, and we are discovering what becomes possible when they do. 6. Every layer of the stack can become adaptable. Think about the entire chain, from the software used to design a transistor to the software powering a fighter jet, an industrial machine, or a mobile app. Every layer has the potential to become more adaptable to the needs of its users. That includes the models themselves. We should be able to distil and adapt models to the needs of the people using them, including through private and local deployments. The data and knowledge used to train these systems came, in large part, from human activity and collective work. We should be building ways for people to benefit from that intelligence directly. 7. New abstractions create new jobs. Look back at the rise of reactive architectures and digital transformation. People worried about how new tools and architectures would change the roles of frontend and backend developers. The industry did not stop needing software engineers. New abstractions helped create the full-stack developer, a role that could work across boundaries that previously separated teams. We should expect similar changes again. Some jobs will disappear, others will change, and new roles will emerge around problems we have not yet learned how to solve. Making something easier to build removes a constraint. It also creates room for new products, businesses, and careers. Consider dental floss and toothpicks. Dental floss did not make toothpicks obsolete. In Brazil, Gina has built a major toothpick business, with reported production of around 40 million units a day. A better or newer solution does not automatically eliminate the demand for an existing one. People have different needs, habits, and preferences. 8. Taste and understanding the user become the moat. If everyone can build software, simply having the ability to build it becomes less of an advantage. What matters is understanding which problems are worth solving, how people want to solve them, and what makes a product worth returning to. That requires more than waiting for feedback. It means observing how people use software, where they struggle, what they change, and what they build on top of it. It means giving users the tools to adapt the product themselves, while learning from those adaptations to improve the experience for everyone. This is why I started with Excel. Its lasting value is not just its spreadsheet. It is the freedom it gives people to create things the original developers never anticipated. I believe the next generation of successful software companies will understand this. The opportunity is not simply to build software faster. It is to create software that people can make their own, let them choose, ship in a way they can truly own their data and the way you ship will get the attention it deserves. The barrier to creating software is falling. The number of problems we can solve is growing. And I think we are still at the beginning. - I wrote about the future of new roles soon, teapawt.net/compose/articles/edit/… and @GeoffreyHuntley recently wrote about interviewing process for this new kind of role here teapawt.net/GeoffreyHuntley/status… gist.github.com/igorcosta/bb…

LinkedIn is a total sloppy, they are not alone. Showing fake status on posts on Autohand and when you click nothing there. We are not immune from the same issue our agents decide to write a entire wall of fake lies and testimonies from users that never been ours. They published the pages and translated into 8 locales. While I was sleeping. We tight knot on our side. Even with all release controls they just decided to fake it.

the only apps i actually care about it.

Anything you want to build, whenever you’re ready. autohand.ai/code/desktop/

🌈

autohand.ai/code/desktop/ The best Agentic Development Environment in the market. Try Automations.

I've been doing a phone call with my chief of staff every day on my comute from work, it's the most hyped team i've ever worked with. Better than listening to podcast or listening to music.

I demoed Tui our internal model for office desk work to a few friends, I asked Moa to teach a new model based off fantail and i did similar approach here. It's finally going to be mainstream in 2028. You can literally do dynamic tool calling for a model to modify it's own tensors on the fly.

We understand through our partner ecosystem that your company may be exploring additional compute capacity. I wanted to reach out directly to see if there might be an opportunity to connect with you and your team, understand your requirements, I got 4 neo clouds offering “free compute” first year on 3yrs commitment. No thanks. We got that covered. @elonmusk was right. DRAM is like GameStop.

We're running into constant constraints at autohand.ai The demand has increased A LOT. such a good problem to have. I made the executive decision to support more paid customers. We reduce a few free tiers. Before we had 2GB cache support Now we have 1 GB cache support Before we had 150 messages free now down to 50 messages free Before KV_cache from 60 minutes Now KV_cache to 30 minutes. I know it sucks for free users, but we're bootstrapping and we love our users but paid customers have a special space in our hearts. No further more.

Since @elonmusk and @xai can't give our account @autohandai We just released our latest coding agent in the market 0.9.9 comes with a ton of new features and bug fixes. github.com/autohandai/code-c… autohand upgrade for the thousands of users already using. if you're new to the game download via autohand.ai/code/cli/

Can I design drugs and medicine the same way I design code? There's only one way to find out!

We're making Autohand Software Factory available for a few selected startups. If you're at a breakneck speed, get early access to ours the first 1B token is on us. autohand.ai/code/assembly/

I love to see sci-fi craft in the hands of the crowd. Kudos to team. They achieved what @autohandai is doing and finally we are not alone.