443 karma · joined October 19, 2013
If I may add, when your peers (or managers) take some time off and hand over work to you, write a hand-over document. Always. It's crucial for smooth handovers.
- Task to handover
- Description
- Actions at stake
- Target / Desired Outcome
- Timelines
If you missed an action / task that isn't in that document, then it's really not your fault.
What would the downsides be?
A delayed payment must not exceed 2-3 weeks tops.
The only advice I can give (i've received a lot of good advice here) is to always interview. Always be up-to-date on the job market, with respect to skills, technologies, coding savviness, etc. Interviewing in the beginning may take a lot of your time, but if you do it consistently, it'll only helping you in future interviews. Don't be afraid of rejections, hell, even embrace rejections as a mean to get better in the future.
I was always afraid of having my skills eroded or even becoming obsolete as it got to a point where I was no longer learning new things on the job, so I had to push myself and make myself learn (most times on my own personal time). That's what pushed me to get out of my comfort zone, and do something that I know will be annoying and heck even make me scared.
- crypto crash of 2022. Ethereum will switch to PoS, leading to a global wide sale of GPUs and miners are no longer a thing.
- maybe the stock market will crash similarly to 2022.
Edit: unfortunate for me ofc.
EDIT: for me this is a minor issue. i'll continue using `brew` as it does the job quite well