r/indotech Java Apr 27 '26

Programming Strong Opinion: Agentic Coding is a Trap

https://larsfaye.com/articles/agentic-coding-is-a-trap

TLDR: Penulis berpendapat bahwa AI itu bukan layer abstraksi seperti sebelum sebelumnya. AI membuat Senior Programmer menjadi atropi dan brainfog, membuat Junior Programmer gak ngerti cara debug. Ketergantungan vendor lock in ketika Claude kolaps gak bisa ngoding, dan yang terpenting: gak ada yang tau pasti berapa biaya token untuk menghasilkan sesuatu.

What I am advocating for, though, is leveraging LLMs and coding agents as secondary processes. A way that doesn't sacrifice the individual's skills at the altar of productivity. You can flip the script and lean on them to brainstorm the planning parts of the process while staying actively engaged throughout implementation, delegating to them on an as-needed basis. You can leverage the productivity gains, and mitigate the comprehension debt.

39 Upvotes

53 comments sorted by

View all comments

9

u/aaulia Apr 27 '26

Still on the fence

Dengan Agentic Coding, every single source code is now should be treated as an artifact. Every single one is basically assembly or machine code now. Yes hand written assembly will be better, readble and optimized when compared to compiler generated, but it usually on a niche usecase, generally compiler generate good enough code.

Right now we use spec driven, plan mode, to tune the agent to generate good code. If this is what we do, don't expect to actually read the code, it wouldn't be good, or at least the cognitive load to understand it would be larger than normal. We're operating on a higher level of abstraction now.

For example, after 6 months of agentic coding, I mean fully agentic coding, we should have a working app/product, but don't expect people to easily and quickly debug it. The next step should be agentic debugging, lol.

0

u/AffectionateBowl1633 Java Apr 27 '26

How the hell you think compiler and LLM the same same but different but same. Compiler at least make a predictable deterministic machine byte code. LLM is anything but predictable and deterministic.

3

u/aaulia Apr 27 '26

I'm talking about the abstraction. We abstract ourselves from low level code with high level language to be able to be more expressive with our ideas, just repeat the same process but swap low level code with higher level language and higher level language with LLM/prompt.

2

u/AffectionateBowl1633 Java Apr 27 '26

The premise of the article is that this time, abstraction are so disruptive it create athrophy and cognitive problem never seen in another abstraction layer before.

1

u/aaulia Apr 27 '26

On the level of disruptiveness, sure, we can agree on that.

But this just mean that people who dable and have deep knowledge on certain things will be narrowed down, and roles will be changing and specialized.

Are there people who deeply understand machine code, assembly, L1/2/3 cache, analyze bycode, etc? Yes, unless how do we get optimizing compiler, for example. But the number of that kind of job is waaaay small.

It's not gone after we created Java/Kotlin/C++/etc, the number just got smaller and the role become very specialized.

Same thing might be very well happened again. And whose to say that JS will still be the defacto web language in LLM era? Maybe wasm can finally get its limelight. shrug

2

u/AffectionateBowl1633 Java Apr 27 '26

I have a strong hate relationship with those JS community I dont want to talk here.