Live data from Hacker News

Ask HN: Am I dead meat already?

news.ycombinator.com

81–83 of 83 posts

Re: Ask HN: Am I dead meat already?

#81
post #20

Lie about your age and fabricate new skills on your resume/CV. Put “I code in C/Java/Go/Python/Javascript/whateverYouNeed”. Also you’re in the EU so could feasibly move to where needs your exact skill set. But web/frontend/backend is needed everywhere so it’s likely worth adding that to your C skills.

Don't lie. Do remove years that you received any degrees to make it harder for them to infer your age with certainty.

Re: Ask HN: Am I dead meat already?

#82
post #74

Earlier quoted context omitted.

The unfair thing in the scenario you describe is the employee choosing to upskill while they continue to do their jobs? And not the company firing them for speaking their mind - giving them 3 months of runway to switch careers in a situation OP already said felt like a shit job market? Micromanaging employee time is one of the worst signs of a toxic company culture. And definitely not a sign of an efficient one

Op is not upfront about the toxicity situation to their management.And he haven't said anything about how toxic it is. > Micromanaging employee time is one of the worst signs of a toxic company culture I agree micro managing alot is bad but I don't agree it is toxic. I agree if leadership knows nothing about software engineering and microing it it is bad. There's always two sides. I had seen projects fail because dev…

If you have saved projects by coming in and micromanaging the devs... are you sure that was the only way to incentivize them to stay focused? And are you sure that they appreciated being micro-managed and did not think it rude and toxic? Because the success of a project and the toxicity of its leadership are orthogonal to each other. It sounds like you are coming from a perspective that if the business succeeds, the environment must not be toxic, which is sadly not at all true.

Re: Ask HN: Am I dead meat already?

#83
post #45

I learned Go "on the job" - I wrote a codebase during a company hackathon, and it ended up being shipped into production not long after. The good thing about Go is that the tooling and libraries quickly steer you towards using the language in a particular way, meaning that you learn how to write idiomatic Go quite quickly. In my case, my Golang code was reviewed by those with years of Go experience and they were surp…

"and it ended up being shipped into production not long after" - To me that seems like a reason to run from that company.
Post reply on HN