I could probably be a pretty damn good cook, perhaps even a sous chef. But there is so so much I want to do that is not cooking. Is it really so difficult for CEOs and devrels of AI companies to imagine that some people don't want to spend their time making software, even if it is accessible?
FinnLobsien|1 year ago
A cookbook lets you cook like Thomas Keller or Eric Ripert or whoever because you get their exact recipes, even when those recipes have 18 steps and take 7 hours.
An air fryer lets anyone make something acceptably tasty in 20 minutes and with zero technique.
Imo this is what AI is doing for software building. It lets almost anyone build something that accomplishes a job. But we don't have to expect it to have scalable architecture, beautiful UI or follow security best practices.
I think part of the problem is that most software engineers rightfully care about these things for their jobs. But maybe they don't matter if you're building "home-cooked software".
The same way you can read cookbooks from 3 michelin star chefs and wonder if anyone will ever follow the recipes in them (check out Marc Pierre White recipes for an example).
wink|1 year ago
Cooking (manually) takes skill (let's say that's a one-time thing you need to have acquired in the past) and then it needs time (repeatedly).
The outcome (food) is a temporary benefit.
Software meanwhile, in general, is written once in order to solve a problem at all, or make a task easier/more repeatable. The software is the cook, so to speak.
A more apt comparison would be to craft a cooking tool that makes your work easier, or possible at all. (e.g a pot)