That is quite a mixed bag response. Leaves me between they won’t do nothing, and they might do something.

I wouldn’t recommend staying with a company for 17 years. That’s for sure. Best way to get stuck in a company specific niche skill that is not transferable. For the reasons stated you got to keep yourself positioned well skills wise and relevant so you can jump into any role you need at any time.

Integrity is not for the company. It’s doing things the way you think they should be done and earn your own respect.

I would say all companies don’t replace with cheaper. Many do. Especially the shitty ones. It’s quite easy to avoid those like the plague. Many did, and learnt the hard way, many have staff that have seen failed outsourcing and are in a position to influence that.

Soloing knowledge doesn’t keep you safe though as the penny pinching companies will remove anyway and clean up later regardless. It does not keep you safe. It’s a false sense of security. Complacency is a death sentence in software development.

Professional integrity. Have you ever worked for a company that got screwed by a consultancy? Vendor lock in and charging scandalous amounts for little offer.

You are paid for your skills and your time. If you’re confident in your ability and impact, you shouldn’t have to be worried.

I’m not saying sacrifice for yourself for your company, and if they are a shitty company that would replace you with cheaper, get out, but also, giving nothing for the pay you get is a bit dishonest, and then you are no better than them.

Plus, you make the case that hiring people is bad and paying a consultancy is less risky.

Of course Jared didn’t document anything and made themselves a bus factor. Real success is when Jared makes themself replaceable because hiding detail and making yourself critical is the best way to take a site down when you’re on holiday and prevent other team members stepping in and taking ownership.

Isn’t this just the tech version of cuckooing?

https://en.m.wikipedia.org/wiki/Cuckooing

Illegally using someone’s property to make profit from dodgy business.

Unit tests, yes, but you don’t only do unit tests. Integration and e2e tests still exist.

Was there even tests?

I’m not sure what’s with your first sentence. Everything else you said agreed with the point I was making…

Garbage in, garbage out. Keep feeding it shit data, expect shit answers.

Real mugs.

Henry Ford invented breaks to extract more out of the peasant Labour.

The fact we’re years later and cognitively demanding jobs don’t support this well show how amateur managers are and his spineless devs that enable them are.

It didn’t suddenly go that way. It was always the plan. A loss leader.

Are you a recruited? JavaScript is not Java.

I cannot see this working. Unless it can ask if you have enough anaesthetic and stop when you do not, otherwise, it’ll be an expensive torture device.

It was more than one mistake. Where was the QA, the staged rollout, the CI? It brought unto question how competent this company is to be a dominant player in such a critical market.

“If you would like me to be on call, we need to discuss remuneration.”

If you cannot ignore slack in the evening, weekends, you gotta be bad at your job. If you are good, employer won’t want to replace you and you can condition them to respect boundaries.

“I sent you a message, why didn’t you respond?”

“I didn’t see it.”

“What were you doing?”

“Cooking. Food shopping. You know, the essentials to survive”

Not that I’d elaborate. I much prefer the “I had plans/a prior engagement”.

If they ask, “I cannot really discuss this, it’s private”

You can ignore that also…

Yes, and you do it at the point you need to work on that feature. The business pay for it when they want the change.

You do not pay for the refactor with your time, if the company won’t pay to fix their code. Just make it clear the risks and how bad it could be if you carry on with duct tape fixes.

You have to be strong and firm and not agree to hacks. You need to work with your team to ensure you’re on the same page rather than getting undermined by cowboy dev claiming he can do the feature in 2 days when it needs 2 weeks to do the necessary work.

It’s fine. They said Windows 10 is there last operating system. It sure is for me.

Well Devops isn’t a role. It’s an approach in which bridges development and operations and integrating it in the team. It isn’t sticking a cloud engineer (cloud biased sysadmin) in the team. It’s about collaboration and delegating and supporting.

Cloud engineer is unfortunately what many orgs think devops is.