u/Ok-Motor-9812

I see a lot of devs got laid off this year, and most of them do the same thing. They go even deeper in one stack, polish the CV and apply to companies that are cutting people too.

I think the cuts happen for a simple reason. A few years ago a client asked their IT partner something and waited a couple of days for the answer. Now AI gives that answer in a minute, so the company needs fewer people in the middle.

From what I see with my clients, they don't care if the code was written by hand or by AI, as long as it solves their problem and it's secure. And that part still needs a developer who understands the business.

So I don't get why people keep doing exactly what worked 2-3 years ago. I'd stop sending CVs, go sell the solution to businesses directly and use AI to the max for everything it can do now.

If you got laid off, what stops you from going to clients directly?

Do someone know the limits of using the official upwork MCP?
2 days ago i received Policy violation. And its quite very weird.

Like here is our new MCP. PLease, use it, but we will not give you any information about the limits, but once you'll reach them, the policy will be in 1 sec...

https://preview.redd.it/ol32x08vyu3h1.png?width=1080&format=png&auto=webp&s=434ee4da9de9d3368feb34882dee01103d61a85b

https://github.com/nesaminua/claude-code-lsp-enforcement-kit

Saving tokens with Claude Code.

Tested for a week. Works 100%. The whole thing is genuinely simple: swap Grep-based file search for LSP. Breaking down what that even means

LSP (Language Server Protocol) is the tech your IDE uses for "Go to Definition" and "Find References" — exact answers instead of text search. The problem: Claude Code searches through code via Grep. Finds 20+ matches, then reads 3–5 files essentially at random. Every extra file = 1,500–2,500 tokens of context gone.

LSP returns a precise answer in ~600 tokens instead of ~6,500.

Its really works!

One thing: make sure Claude Code is on the latest version — older ones handle hooks poorly.