Design when software becomes a commodity
I've been thinking about what happens when software becomes a commodity. As the tools for building it get better, more people can turn an idea into a working product. Features that once took a team months can become a starting point rather than a competitive advantage.
That doesn't make software engineering irrelevant. Reliability, security, and maintenance still take work. But it does change where a product can stand out. If everyone can build roughly the same features, having those features is only the beginning.
This is where design matters. Design is the work of choosing what a product should do, how it should behave, and what it should leave out. A polished interface helps, but the harder question is whether the product fits into someone's life without asking them to learn a new way of thinking.
Consider two tools that help you plan a week. Both let you create tasks, set dates, and send reminders. One asks you to configure a workspace before you can begin. The other helps you choose what matters today. The feature list might look similar, but the experience carries a different point of view.
When adding another feature becomes cheap, restraint becomes a deliberate choice. Every option has a cost for the person using it: another decision, another setting, another thing to understand. Good design spends that attention carefully.
I suspect the advantage will increasingly belong to people who understand a particular problem well enough to make useful choices about it. That understanding comes from listening, observing, and testing assumptions with the people who will actually use the product.
Software may become easier to produce. Making something worth using will still require judgment. For me, that's a reason to spend as much time asking why a thing should exist as figuring out how to build it.