Of the four coding examples you describe, I find none of them compelling either in their utility or as a case for firing a dev (with one important caveat [0]).
In each example, you were already very familiar with the problem at hand, and that probably took far longer than any additional time savings AI could offer.
0. Perhaps I consider your examples as worthless simply because you gloss over them so quickly, in which case that greatly increases the odds in most companies that you would be fired.
From what you describe it sounds like software development is starting to get categorized as 'labor', and that a lot of companies will be having system problems over the next few years.
It's a way to discover their content - content you might miss if you only go on HN once or twice a day.
HN is great for diversity of topics, tech news, random discussions with tech-celebs etc., but e.g. Simon's blog is the best content there is on what the latest LLM gizmo is and how well it works.
In each example, you were already very familiar with the problem at hand, and that probably took far longer than any additional time savings AI could offer.
0. Perhaps I consider your examples as worthless simply because you gloss over them so quickly, in which case that greatly increases the odds in most companies that you would be fired.
reply