←back to thread

1041 points mertbio | 1 comments | | HN request time: 0.284s | source
Show context
strken ◴[] No.42839357[source]
After being laid off more than once, I think I'd adjust the advice a little:

- You're only obliged to work your contract hours. If you do more then make sure that you, personally, are getting something out of it, whether that's "I look good to my boss" or "I take job satisfaction from this" or just "I get to play with Kotlin". Consider just not working overtime.

- Take initiative, but do so sustainably. Instead of trying to look good for promo, or alternately doing the bare minimum and just scraping by, take on impactful work at a pace that won't burn you out and then leave if it isn't rewarded.

- Keep an ear to the ground. Now you've got a job, you don't need another one, but this is a business relationship just like renting a house or paying for utilities. Be aware of the job market, and consider interviewing for roles that seriously interest you. Don't go crazy and waste the time of every company in your city lest it come back to bite you, but do interview for roles you might actually take.

The last two points are fine, however.

replies(7): >>42839395 #>>42839701 #>>42840511 #>>42840982 #>>42842252 #>>42844998 #>>42846494 #
roenxi ◴[] No.42839395[source]
Indeed. The real discovery in the article is that the people who manage performance and the people who manage headcount were completely different people. The article writer had (common mistake) assumed that impressing the former would take care of the latter. It doesn't; the techniques to manage the headcount people are different.

I wholeheartedly endorse your adjustments - it is fine to go above and beyond but for heavens sake people please think about why beyond some vague competitive urge. Going above and beyond without a plan just means the effort will likely be wasted. Some cynicism should be used. Negotiate explicitly without assuming that the systems at play are fair, reasonable or looking out for you.

replies(1): >>42839678 #
mcherm ◴[] No.42839678[source]
> the techniques to manage the headcount people are different

I would like to hear a little bit more about those techniques.

The only one I am aware of is to make sure that you have promotions under your belt: The arm's-length people who plan layoffs know very little about the individual's other than their job title and rank. But this advice is hardly useful: it is extremely rare for an individual to have a choice of whether to be promoted or something different.

What other techniques are you aware of?

replies(3): >>42839840 #>>42840400 #>>42840432 #
michaelt ◴[] No.42840400[source]
There are several types of layoffs:

1. The company-wide 5% layoff. Avoid this by making sure you're not in the bottom 5% of performers, and the people above you know it.

2. The shift-the-legacy-products-to-cheap-countries layoff. Avoid this by making sure you're working on products where you're fixing bugs and making improvements, not just keeping things ticking over.

3. The lay-off-the-entire-department layoff. Avoid this by working in departments that bring in more revenue than they cost, or at least have a good chance of commercial success; and in an area where the company's strategy calls for growth.

4. The lay-off-the-entire-office layoff. Not much you can do about this, except working at the head office, or a very large branch office where important projects are based.

5. The there's-just-no-money / entire-company-goes-out-of-business layoff. Not much you can do about this - but if things are heading in this direction, it's a good time to start sending out resumes and maybe getting the unemployment insurance on your car loan.

Of course these are very risk-averse strategies. I've heard of some people having great success with the opposite strategies - some people say maintaining ancient legacy mainframes for banks is highly profitable. Others have told me the fastest way to get a senior title is a failing organisation, where senior people keep leaving. So none of these are hard-and-fast rules.

replies(6): >>42840523 #>>42840742 #>>42841454 #>>42841606 #>>42842554 #>>42843321 #
1. IMTDb ◴[] No.42843321[source]
Thank you for this.

In the article, the author says that he was fired alongside most of his team. Then makes a lot of statements about how great of a job he was doing. To me it looks like the firing was thus based on option 3, yet the author did not make a single comment about the profitability of the product he was working on, or the team performance of the group he was working on.

As an example, he made "features that helped power users", without articulating how much additional revenue these feature contributed for. How many of those power users were there ? Were they at risk of churning, or were they locked with the product anyway ? If they were, those hours were fully wasted as no additional revenue could be associated to those features. It's all fine if your product is bringing in a lot of money - with the current headcount - and the vision of your company is that you need to need to prevent competition from catching up. But otherwise it's not exactly the feature an exec will look at and be that happy to spend money on.

I read once: "Here is to discern a junior form a senior: If you are a junior, and deliver quality code for a feature that ultimately did not reach it's audience; well you still did a good job. If you are a senior and deliver quality code for a feature that ultimately did not reach its audience; well you failed". In our industry, seniority is about looking beyond just writing code, especially with AI coding agent coming up and taking away that part of the job.