←back to thread

Building a Mac app with Claude code

(www.indragie.com)
165 points gdudeman | 1 comments | 06 Jul 25 14:55 UTC | HN request time: 0.238s | source
Show context
pyman ◴[06 Jul 25 16:01 UTC] No.44481864[source]▶
Two years ago, I saw myself as a really good Python engineer. Now I'm building native mobile apps, desktop apps that talk to Slack, APIs in Go, and full web apps in React, in hours or days!

It feels like I've got superpowers. I love it. I feel productive, fast, creative. But at night, there's this strange feeling of sadness. My profession, my passion, all the things I worked so hard to learn, all the time and sacrifices, a machine can now do most of it. And the companies building these tools are just getting started.

What does this mean for the next generation of engineers? Where's it all heading? Do you feel the same?

replies(14): >>44481903 #>>44481916 #>>44481936 #>>44481940 #>>44481953 #>>44482060 #>>44482216 #>>44482387 #>>44482415 #>>44482445 #>>44482480 #>>44482816 #>>44483165 #>>44486453 #
1. anon7000 ◴[06 Jul 25 16:12 UTC] No.44481953[source]▶
I think it’s yet another layer of abstraction on top of complex ideas. There will always be room for people working on the infrastructure, tools, maintenance, and operations side of things. The biggest danger is if you stop learning because you trust AI to just do it.

I’ve been (carefully) using AI on some AWS infrastructure stuff which I don’t know about. Whenever it proposes something, I research and learn what it’s actually trying to do. I’ve been learning quickly with this approach because it helps point me in the right direction, so I know what to search for. Of course, this includes reviews and discussions with my colleagues who know more, and I frequently completely rewrite what AI has done if it’s getting too complex and hard to understand.

The important thing is not allowing AI to abstract away your thought process. It can help, but on my terms