Live data from Hacker News

Will Claude Code ruin our team?

justinjackson.ca

11–20 of 118 posts

Re: Will Claude Code ruin our team?

#11

As an engineer and a daily if not hourly user of Claude Code, I would never dream I could do the jobs of my product / designer teammates. Not because I don’t have opinions on product or design, but simply because they do me the huge service of attending meetings so I don’t have to. I recognize the necessary evil that is Zoom calls and face-to-face time in the larger context of running a business, but I also know what…

When the product marketer, product manager, and designer are the same person there is no alignment meeting.

Re: Will Claude Code ruin our team?

#12
post #3

I won’t take credit for this insight, but as someone else pointed out, everyone oversimplifies other people’s jobs. To PMs engineers are just code monkeys that they won’t need soon. To engineers, PMs are the guys that manage Jira. Designers are the fussy people that make things look pretty. The reality is all these jobs have intricacies AI absolutely sucks at but those intricacies are lost in the larger discussion. A…

And for people who never liked it in the first place and just wanted a quick buck.

which doesn't make sense because the quick buck train is gonna stop. But then again, maybe there wasn't any sense in them in the first place.

Re: Will Claude Code ruin our team?

#13
post #6

It already has. Those jobs PM, designer and engineer are all affected and there will not be a need for too many of them for a product feature and will be reduced over time. While those roles will still exist, there will be a initial shock in people who once believed they were 'valuable' but the business thinks otherwise and does mass layoffs just like Block, because of let's face it; AI. The way to still remain relev…

I think you're probably still going to need all of those people, just less of them to accomplish the same amount of work. It's the nature of LLMs that they will always need oversight. Having 20 or even 100 of them agree on something is never going to be 100% accurate -- it can't, the randomness and hallucinations are part of the secret sauce. There will always be a need for people to verify what they do. That said, it was the exact same when people were doing the work.

Re: Will Claude Code ruin our team?

#14

As an engineer and a daily if not hourly user of Claude Code, I would never dream I could do the jobs of my product / designer teammates. Not because I don’t have opinions on product or design, but simply because they do me the huge service of attending meetings so I don’t have to. I recognize the necessary evil that is Zoom calls and face-to-face time in the larger context of running a business, but I also know what…

The final frontier: a warm body.

Re: Will Claude Code ruin our team?

#15
You need to be sociopathic aggressive right now. We are in a few month window here where execs are very confused even if they parrot their group chat talking points to sound smart and ahead of it. They are all behind and they know it.

This isn’t comfortable but now is the time to ship fast and hard. To overstep boundaries and be the person getting attention. In a few months everyone will be so you need to do this now.

Just don’t. Don’t limit yourself. Ask for forgiveness.

Re: Will Claude Code ruin our team?

#16
I wonder if this could go down similar way some SaaS systems went to lower barrier to customisation so less technical users could do it. For example, having to interface with some ServiceNow instances I often find major flaws with db schema design - similar data in multiple places, lack of constraints, etc. Basically one big mess you are now stuck with that could have been avoided if a db expert was in charge of data model design.

Re: Will Claude Code ruin our team?

#17
This naturally seems to indicate smaller teams will become more normal.

Many of my clients are blown away by what our teams can do with 1 senior engineer now.

Anything below enterprise level software should be thinking very hard about what team composition actually needs to look like to achieve good results. It's likely a lot smaller headcount than it used to be.

Re: Will Claude Code ruin our team?

#18
post #3

I won’t take credit for this insight, but as someone else pointed out, everyone oversimplifies other people’s jobs. To PMs engineers are just code monkeys that they won’t need soon. To engineers, PMs are the guys that manage Jira. Designers are the fussy people that make things look pretty. The reality is all these jobs have intricacies AI absolutely sucks at but those intricacies are lost in the larger discussion. A…

And for people who never liked it in the first place and just wanted a quick buck.

You can't pay Claude with equity though

Re: Will Claude Code ruin our team?

#19
post #9
post #4

I don't know why people are talking so theoretically. This was months ago. My friends have startups, I know a lot of engineers. The startups have been laying off people for months, and many of my engineer friends don't have jobs anymore. Teams are already ruined. I just don't think the companies are. In many cases this seems like rational reallocation of capital to AI, and in a VC funded ecosystem you're failing at y…

I think it's less armchair speculating about the observable outcome, that people are losing their jobs, but the why. AI coding tools aren't making 10x developers, they aren't even making 1.5x developers. They also aren't making "PMs who code" or "designers who code." It would be really cool if this was the case, I would be singing the praises of these tools finally realizing Stallman's dream of end users who can take…

> they aren't even making 1.5x developers

I won't try to speak for anyone other than myself, but my multiplier is definitely over 1.5x, probably higher than 5x.

I choose to sit on my hands in my freed up time so upper management does not catch on to and exploit this fact. Eventually they will though via overzealous coworkers.

Post reply on HN