jc_811
Joined 11 years ago
Karma
2,169
Submissions
381
Member since
Nov 12
Recent submissions
Comment · 8 days ago
Comment · 1 month ago
Full tweet text for those who can’t see it:
“I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.“
Comment · 2 months ago
Genuine good faith question, what would you recommend the solution or alternative to be? How could we be able to get the benefits Cloudflare provides, without the inherent drawbacks?
Comment · 3 months ago
If you look at their financials, they’re clearly making money. In 2025 they had 33B in revenue with a net income of 5.2B
Comment · 5 months ago
Full quote: "Some truth to that. There’s a whole bunch of back office you needed to be public which AI has made a lot more streamlined. Very few engineers or customer-facing sales people impacted by our layoff. And we’ll continue to hire like crazy in those roles — like we did as a startup."
More quotes by him in other comments too:
[1] "Roles are being cut. Whole functions. Who will survive and thrive are anyone who’s building the product to be sold, or anyone who’s selling the product. We and others will hire everyone good we can find for those roles."
[2] "We’ll still be on a roll hiring. Just shifts to focusing on people who either build or sell products. Fewer roles needed to act as scaffolding supporting those functions"
[3] "Agree! Hence we laid off very few software engineers. Very few customer-facing sales people either. But if you don’t think AI changes how SalesOps, for instance, will be done going forward then it probably means you don’t know what SalesOps is."
[4] "We’ll still be hiring at a rapid pace. This isn’t about cutting headcount. It’s about shifting what roles we need. More people building and selling product. Less providing back office functions to support them."
[5] "We’re not slowing down hiring. We’re just shifting for what roles we’re hiring. This isn’t about cutting staff, it’s about changing what roles we need."
[1]- https://xcancel.com/eastdakota/status/2052598611679097040#m [2]- https://xcancel.com/eastdakota/status/2052559855274144039#m [3]- https://xcancel.com/eastdakota/status/2052560831909433554#m [4]- https://xcancel.com/eastdakota/status/2052557234182172932#m [5]- https://xcancel.com/eastdakota/status/2052557696650428882#m [6]- https://xcancel.com/eastdakota/status/2052561977080205637#m
Curious what you all think of this, or if this matches what you're hearing/seeing out there? From public forums it seems like quite a few engineering roles were impacted.
"I don't know how to stop it [...] there was never any intent to write a programming language [...] I have absolutely no idea how to write a programming language [...] I just kept adding the next logical step on the way."
And 23 years later here we are with php2shell and it powering 70% of the internet’s websites