[wink]

I think the cooking metaphor is actively wrong.

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)

[FinnLobsien]

> A more apt comparison would be to craft a cooking tool that makes your work easier, or possible at all. (e.g a pot)

Which is funny because almost nobody ever makes their own cooking tools. Most people are happy to buy off the shelf—just like software.

I don't disagree that the comparison isn't perfect, but your take just spelled out why this home-cooked software idea is pretty unlikely.

I think this is especially true because Gen Z/Alpha seem to actually be less tech-savvy than previous generations.

[wink]

I reread that part of the post and this makes me disagree even more (not with you):

> The more that build software, the more who will appreciate using great software. Cooking at home makes you appreciate going out to eat.

Like.. no, I don't appreciate great cooking in restaurants.

I'm eating out because I hate cooking and I don't know how to cook certain things and with my tools I am not able to cook certain things. (e.g. good pizza). But the stuff I like cooking (and can do) is not worse than the same dish in a restaurant, sometimes I even prefer it. Same for software.

But I guess that's the thing. If I'm a professional software developer it would be kinda weird if I hated using my own home-made software? So maybe this is actually more true for people who just need a thing but can't do it without (AI) help?