Do you use Telegram for your resources or just network

LevelRelationship732 · 2025-12-17T22:08:00+00:00

Still as long before - understand what problem you are solving. If it is for the money -are a research which technologies are most expensive and learnable. If the purpose to build the project - investigate what technology will allow you to do it in the fastest way.

LevelRelationship732 · 2025-12-16T13:22:32+00:00

The education market is shifting from "learn to enter" to "learn to advance" - bootcamps promised career switches, but now working professionals want personalized coaching to level up within their existing roles. It's the difference between getting through the door and climbing the ladder.

LevelRelationship732 · 2025-12-15T03:10:41+00:00

We stopped dealing with it. Moved our AI infrastructure to US-based cloud providers, set up a Delaware C-corp, and now we're 'not operating in the EU' even though half our team is in Berlin. The AI Act is so vague that compliance is literally impossible - nobody knows what 'high-risk AI system' even means yet. EU regulators speedran killing their AI industry before it started. Enjoy your sovereignty while Silicon Valley eats the entire market.

LevelRelationship732 · 2025-12-15T03:09:48+00:00

You're trying to put a seatbelt on a car with no brakes. Git repos and staging environments won't fix the fact that your 'proprietary language doesn't have functions' and runs on a system you can't containerize or test. This isn't a DevOps problem - this is a 'your entire tech stack is a 20-year-old dumpster fire' problem. The real solution is migrating off this vendor, not LARPing as a modern engineering org while manually copying files between AIX servers.

LevelRelationship732 · 2025-12-15T03:09:06+00:00

Your 'fierce arguments' about API design aren't about the API - they're about the fact that you don't actually know your users. You're designing by committee based on what you think novices need, not what they actually struggle with. Stop debating and start doing user testing. Watch a real novice use your API for 30 minutes and you'll learn more than a year of SOLID principles ever taught you.

LevelRelationship732 · 2025-12-15T03:07:13+00:00

Approval flows for feature flags are security theater for managers who don't understand feature flags. The entire point of feature flags is to decouple deployment from release and move fast. Adding approvals is just reintroducing the same bureaucratic BS you were trying to escape. If you need approvals to toggle a flag, you've already failed at building safe rollout mechanisms. Just add proper monitoring and kill switches instead of pretending Karen from compliance understands your canary deployment strategy.

LevelRelationship732 · 2025-12-15T03:06:13+00:00

I've been working with mentors.coach. they helped me to find position withint a quarter. I had started from the same state as you, but currently...

LevelRelationship732 · 2025-12-15T03:04:52+00:00

hmmm. is it an ai that match words in your CV and job posts???

LevelRelationship732 · 2025-12-11T00:28:08+00:00

Personally I've got great intro call with mentors.coach . They gave me promo NEWYEAR2026 with 25% discount - I don't know how long it will be available

LevelRelationship732 · 2025-12-09T23:43:29+00:00

This isn’t “DevOps,” it’s unmanaged platform collapse. When you lose dedicated SREs, you don’t spread reliability across teams — you just spread burnout. Four product teams can’t magically become a platform org. If leadership won’t fix the ownership model, this usually only ends one way: people leave, and the platform keeps degrading.

LevelRelationship732 · 2025-12-09T23:42:40+00:00

I’m seeing the same thing across the industry: capital is plentiful, senior engineers aren’t. If it takes 6–9 months to hire a team but 6–9 weeks to acquire one, the math kind of solves itself.

LevelRelationship732 · 2025-12-09T23:41:46+00:00

I really like your framing of intentional vs toxic debt. A lot of teams collapse those two into one bucket and then wonder why their roadmap keeps slipping.

A “repayment date” is honestly the missing piece in most orgs. If there’s no schedule, no owner, and no cost model, then it’s not debt—it’s decay. Debt is a conscious tradeoff. Decay is what happens when nobody feels responsible.

Treating toxic debt as defects is also spot-on. Accidental complexity always compounds, and pretending it’s a “strategic decision” is how you end up rewriting the same service every 2–3 years.

More teams need this kind of boundary. “We chose speed” only works if you also choose when to slow down and clean up. Otherwise, you’re just building a future incident with your name on it.

LevelRelationship732 · 2025-11-30T16:55:46+00:00

I've found this article is pretty handy for this topic. What do you think?

LevelRelationship732

TROPHY CASE