new | show | ask | jobs Github

chpatrick 4 hours ago

Typing the code was never the interesting part.

▲

adamredwoods 35 minutes ago | parent | next [-]

>> Typing the code was never the interesting part.

Code is fascinating! An abstract language to compile to program a CPU. So many ways to do this!

Now we're using natural language, which at times is extremely verbose. "[{}]" versus "array of objects", for example.

▲

qalmakka 4 hours ago | parent | prev | next [-]

For me it definitely was

▲

jplusequalt 4 hours ago | parent | prev [-]

>Typing the code was never the interesting part.

But solving hard problems and developing systems intuition was. If you're trying to tell me that people working on code bases predominantly written by AI are still solving hard problems themselves, or understand the systems the AI is building, I think they're lying to themselves.

▲

kolinko 3 hours ago | parent | next [-]

From what I’ve seen they get to the level of understanding of systems way faster than we did because they iterate and experiment with this from day one. We had to spend years understanding code syntax, and other minutia.

Also, you need a different kind of toolset/skillset to grok a system that was vibe coded all the way - different failure scenarios. Older devs tend to just say “see, I told you, it’s just spaghetti underneath, you need to clean it up”, and the newer gen learns to work with that spaghetti.

▲

avgDev 4 hours ago | parent | prev [-]

I have a blazor app in poduction, Codex made errors which it could not fix and it required me reading documentation. I won't argue that it didn't make my life simpler, tasks which would take me days are done in hours, sometimes without touching code.

	▲	unshavedyak 4 hours ago \| parent [-]
		Yea, i still deal with a ton of code in AI heavy workflows. If anything the frustrating part is absorbing the code quickly enough. AI (Claude for me) writes in cryptic text and the code flows can often be non-obvious. I need (and am exploring) custom review tooling to improve this AI->Human code flow. Reviewing PRs were always the hardest part for me in programming. They were often full of the developers decisions and you have to rediscover those as you're reading code for it to make sense[1]. However i find this even more difficult to discover these decisions from AI. However unlike human PRs we can ask more of AI. Rarely have i had a developer put on a presentation for a PR - but AI could right? AI could produce a guided walkthrough of the code. Not sure if it will help of course, but my thought is we're all stuck in the old "PR review flow" but instead of PRs it's AI - and the volume of them is far greater than anything prior. So i expect we need to tweak how we review, how we get information from LLMs. [1]: I'm speaking generally, and about larger PRs. Not some small func where you can easily see what it does. Business logic and complex code can be difficult to decipher in PRs, imo.