Generating software still token costs, generating something like ms-word will still cost a significant amount, takes a lot of human effort to prompt and validate. Having a proven solution still has value.
Assume you work for e.g., a cigarette company. A company responsible for many deaths by unethically adding highly addictive substances. By sabotaging the company you are making this world a better place. Ethically it's the right thing to do.
Or, assume you're hired by the Nazi to work in concentration camps. Ethically it's the right thing to do to sabotage their gas chambers.
No, that’s why I wrote “from my perspective”. I started long ago writing 6502 and 68000 assembly, later c and even later Java. Every step you lose ownership of the underlying layer. This is just another step. “But it’s non deterministic!”, yes so are developers. We need QA regardless who or what write the lines of code.
I'm currently a product manager (was a software engineer and technical architect before), so i already lost the feeling of ownership of code. But just like when you're doing product management with a team of software engineers, testers, and UXers, with AI you can still feel ownership of the feature or capability you're shipping. So from my perspective, nothing changes regarding ownership.
It really depends on your interests: I use daylight for sports after work, really like being able to surf until 22:30 midsummer (52 degrees), so DST works for me. On the other hand, also don't mind the switching between wintertime and summertime, it's just like a minor jetlag we all have no problem with when going on holiday.
So far, cli --help seems to work quite well. I'm optimizing the cli to interact with the agent, e.g., commands that describe exactly what output is expected for the cli DSL, error messages that contain DSL examples that exactly describe the agent how to fix bugs, etc. Overall i think the DSL is more token efficient that a similar JSON, and easier to review for humans.
Biggest downside of CLI for me is that it needs to run in a container. You're allowing the agent to run CLI tools, so you need to limit what it can do.
I've been creating a cli tool with a focus on token efficiency. Dont see why cli could not be as token efficient as mcp. The cli has the option to output ascii, markdown and json.
Who says that is my view of the importance of quality? My second sentence starts with "unfortunately"...
I'm just recognizing that businesses have challenges to deal with besides quality. Being able to generate revenue is just as important as software quality. And seeing how easily consumers switch to a competing product if it has a few more features, you can't neglect time to market if you want to survive as a company.
Many customers are pretty shallow: "meh, the new version looks just like to old one, nothing has changed" even if under the hood the product has significantly improved.
Yes, market dynamics are a bit of a catch 22: customers looking for the best deal, companies looking to reduce costs to still make profit. Customers always looking for the newest features, companies releasing faster before the product is done.
A wreck of a product is still better than being out of business by not being able to release fast enough. Unfortunately, the market in general does not reward slow high quality.
I dont understand your response? I'm replying to a message that literally states: "We lack basic education in fitness ... We need to educate ourselves better". Sounds to me he's stating that education IS the problem?
Education is not the problem. People know sugar is bad, people know cigarettes are bad, people know alcohol is bad, still millions use these substances every day.
What works best is to find some form of exercise that you really enjoy. I will get up at 5 in the morning, skip diner, skip appointments when i get a change to exercise, just because i enjoy it so much.
In addition, what also helps is to ensure normal activities require excercise. I will walk to the shop every day for groceries, walk the dog every day, cycle into town, best if you can cycle to work.
That is also getting cheaper, you can now quickly present him with a few working prototypes so he can quickly make up his mind what best suites him.
Another problem is that most users want different things, that's why you get these big bloated software suites. With LLMs it now also becomes more achievable to build custom software per user.
I also have seen lots of dogshit software created by Humans. And i have created useful software with LLMs. If you know how to manage the LLM, it can be very useful.
I don’t understand how you can conclude that LLMs are a dead end: I’ve already seen so much useful software generated by LLMs, there’s no denying that they are a useful tool. They may not replace seniors developers, and they have their limitations, but it’s quite amazing what they already do achieve.
You're mixing up design and manufacturing. A skyscraper is first completely designed (on paper, cad systems, prototypes), before it is manufactured. In software engineering, coding is often more a design phase than a manufacturing phase.
Designers need malleability, that is why they all want digital design systems.
You're proving the point? Sharepoint, teams: availability + price. Every company has microflows, sharepoint and teams are automatically available and part of the price or lower priced than the competition.