|
|
|
|
|
by hombre_fatal
342 days ago
|
|
I think it's a U-shaped utility curve where abstract planning is on one side (your comment) and the chore implementation is on the other. Your role is between the two: deciding on the architecture, writing the top-level types, deciding on the concrete system design. And then AI tools help you zoom in and glue things together in an easily verifiable way. I suspect that people who still haven't figured out how to make use of LLMs, assuming it's not just resentful performative complaining which it probably is, are expecting it to do it all. Which never seemed very engineer-minded. |
|