←back to thread

1041 points mertbio | 1 comments | | HN request time: 0.279s | 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 #
myth_drannon ◴[] No.42840982[source]
I never understood the advice of to take on impactful work. How does work? The team is assigned units of work and then individuals are usually assigned the tasks. The only way I see it to work is to be on a team that works on impactful projects.
replies(2): >>42841150 #>>42844485 #
1. closeparen ◴[] No.42844485[source]
>individuals are usually assigned the tasks

The higher you go, the more vaguely your "tasks" are defined, the more scope you have for interpretation and for choosing subproblems and related problems to dig into and run with.