←back to thread

548 points kmelve | 1 comments | | HN request time: 0s | source
Show context
ale ◴[] No.45109875[source]
It’s about time these types of articles actually include the types of tasks being “orchestrated” (as the author writes) that aren’t just plain refactoring chores or React boilerplate. Sanity has quite a backlog of long-requested features and the message here is that these agents are supposedly parallelizing a lot of the work. What kind of staff engineer has “80% of their code” written by a “junior developer who doesn't learn“?
replies(6): >>45110352 #>>45111148 #>>45111902 #>>45112019 #>>45113025 #>>45116018 #
dingnuts ◴[] No.45111148[source]
the kind of engineer who has been Salesified to the point that they write such drivel as "these learnings" instead of "lessons" in an article that allegedly has a technical audience.

it's funny because as I have gotten better as a dev I've gone backwards through his progression. when I was less experienced I relied on Google; now, just read the docs

replies(1): >>45112587 #
juped ◴[] No.45112587[source]
Yeah, the trusty manual becomes #1 at around the same time as one starts actually engineering. You've entered the target audience!
replies(1): >>45114394 #
1. skydhash ◴[] No.45114394[source]
These days, I often just go straight to the source (when available) to clear some confusion about the library/software behavior. It can be a quite nice 10 mn break.