(no title)
Retric | 6 hours ago
Physical labor may be a tiny fraction of what a team of developers do, but I’ve seen what amounts to several thousand dollars spent on that kind of silly task because teams leverage the tools they have.
Retric | 6 hours ago
Physical labor may be a tiny fraction of what a team of developers do, but I’ve seen what amounts to several thousand dollars spent on that kind of silly task because teams leverage the tools they have.
raw_anon_1111|5 hours ago
Retric|5 hours ago
The point obviously still stands, and no I am not suggesting using Jr devs for physical labor alone is worth adding them to the team. Rather that “Work” includes a very wide variety of tasks that need to get done.
bdangubic|5 hours ago
this part I find fascinating. most places I worked (30 years in, 10 as a contractor so quite a lot) the distinction between Jr, Mid and Sr falls exactly into the kind of works that they do. I, as a Senior, often work on hard shit, Jrs are not (yet) entrusted with those problems and work on entirely different set of problems. I cannot compute how AI makes everyone better at exactly the same kind of problems, problems I am solving today few people on my team are working on and then same goes down the "pyramid"
Retric|2 hours ago
Automation always runs into diminishing returns for similar reasons. If 99.99% of a workload is embarrassingly parallel, what remains becomes important once you can throw enough cores at the problem.
You’ll see a guy in a multi million dollar crane lifting multi ton objects and then people using ropes attached to that same load for final positioning etc. What you don’t see is people using ropes to lift bricks 20 stories by hand as the crane lifts multi ton pallets of bricks as automation is taking care of that kind of task.