> I can talk to Claude myself OK but can you talk to my specific claude code conversation that has 6 months of context on the mechanism you are struggling with?
Don't be a meat proxy
421–430 of 786 posts
Re: Don't be a meat proxy
#422If you create a machine for laziness you're going to get lazy people. It's only going to get worse I'm afraid. Do you guys think we're going to see a de-evolution of human beings due to technology?
It’s tempting to use what engineers were 70 years ago vs now as an analogy. From a technical point of view, I was told we would be struggling to solve the maths and physics exercises our grand fathers took as students in college, and they had to deal with additional disciplines that disappeared like industrial design (ie drawing blueprints by hand) or manual calculus. So it is tempting to think that the level of engi…
That isn't what was asked. The capabilities of "human + machine" clearly are increasing, but the comments above posit that as a result the average capabilities of "human (sans machine)" may decrease. The relative value of each change is far from clear.
Re: Don't be a meat proxy
#423Earlier quoted context omitted.
At my dayjob there is a person spearheading ai across the enterprise. They generated lots of documentation across the whole stack and now makes all PO/BAs read it if it's correct. So not just 300 lines - he unironically generated thousands of lines of "documentation" and is now making hundreds of people review it for him Complete brainrot Au psychosis is getting seriously outrageous at this point Thankfully I'm a dev…
I think a lot of that is people who were always very insecure because they’re mediocre engineers. Previously asking questions or not understanding something was a bit painful but now you can hear “you’re absolutely right!” and make progress all day every day. Until you need to interact with actual humans and that’s why you try to minimise it, hiding behind ai generated content.
But I think we should decouple mediocrity from laziness. I haven't seen any team invest in the mentorship required to develop juniors in years, for example.
Re: Don't be a meat proxy
#424Re: Don't be a meat proxy
#425> I can talk to Claude myself OK but can you talk to my specific claude code conversation that has 6 months of context on the mechanism you are struggling with?
If you've been working on the issue for 6 months you should understand it well enough to answer in your own words.
Re: Don't be a meat proxy
#426On social media, I saw the much more vulgar “Learned engineering just to become the condom between Claude Code and prod” And that (re)framing helped as well to think about the “what are we even (left) doing” as an industry
You guys are using protection?
Re: Don't be a meat proxy
#427Earlier quoted context omitted.
I would bet real cash money that many many people, including your coworkers, think that anyone who unironically uses the term "midwit" is completely and totally obnoxious.
People who uses the word "obnoxious" are also obnoxious. There are many unpleasant words, you have to use some of them and people don't like any of them.
Re: Don't be a meat proxy
#428Earlier quoted context omitted.
> Chip manufacturing is so complicated that there's probably no single person who could understand the entire process, from end to end. There are YouTube videos of a guy doing chip fabrication in his clean room shed. Just as I understand the assembly output of my compiler (… and no, I don't work in a low level language), he understands chip fabrication end to end. CS is not that wide, not yet. No, one cannot know eve…
> There are YouTube videos of a guy doing chip fabrication in his clean room shed The fact this is "a guy", and probably there are very few people in the world who would be able to execute such a thing, probably should tell you how difficult that actually is. You're actually unintentionally making parent's point stronger, as obviously the production processes used for market products is much, much more complicated th…
You could just as easily point out that subsistence farmers exist. That’s great, but we still need industrial agriculture to feed everyone. No single human fully understands that domain either… even ignoring the chemistry, biology and meteorology, those farms use digitally controlled tools! That means all of computer science is embedded in farming.
It’s great to pursue broad knowledge. It’s important to understand your dependencies and respect the abstractions you build on. It’s pure hubris to think an individual auteur can challenge a multi-billion person civilization.
Re: Don't be a meat proxy
#429Earlier quoted context omitted.
I think a lot of that is people who were always very insecure because they’re mediocre engineers. Previously asking questions or not understanding something was a bit painful but now you can hear “you’re absolutely right!” and make progress all day every day. Until you need to interact with actual humans and that’s why you try to minimise it, hiding behind ai generated content.
I’m not a developer, but when I watch devs whose work process is prompt, copy-paste, try to run, paste error into code, try to run, etc. I can’t help but think they’re unskilled. There’s no brain engagement, no understanding of the bigger picture, just being a worse slower agent.
I see no difference there except speed at the cost of whatever little understanding may have been gained by the manual inspection between steps.