undefined | Better HN

0 pointsthrowmeaway_665y ago0 comments

That's a good point and that's the drop of fear climbing making his way up to my brain. But I interview around, I got some offers that I have declined so far and I do some work, just a few hours a week.

You wrote: "Compensation for a job is about more than money. It's about where you end up as a person when the job is over.". It sounds good in theory, but in practice? Should I switch job, maybe/likely accepting less money and more stress in the coal train now because when the luxury train stops I will be in a better place (I am exaggerating for conversation purposes)? I have my doubts. This is specific to my situation and I don't want to explain too much (and that's why I use a throwaway account), but outside of the US that would sound bizarre. Switching from a cushy well-payed job to a demanding, paying-less job because in a few months/years it will be over? Yes, maybe I will get rusty here and there, but I can move to Tulum for 3 months and get ready for interviews, no?

EDIT: typo

0 comments

4 comments · 2 top-level

011000115y ago· 2 in thread

I didn't say you should quit your job. Ride that train as long as you can. I'm saying you should manage yourself. If you only work half the day, spend the other half of the day:

- Look for opportunities to contribute more at your job. Don't wait for a manager to tell you what to do. Rewrite some code. Propose a new feature. Improve the documentation. Write more tests.

- Teach yourself new skills. Don't just skim books on new languages/technologies. Develop a personal project and pretend like you're being paid to work on it.

- Take practice coding tests. Stay up to date with relevent skills.

Enjoy the job you have now, but keep yourself ready for the day when that job goes away. I had a very easy job for about 6 years. I automated most of my job and effectively did not have a boss. I made great money and spent most of my time working on hobbies, hiking, or working on my house. When the job ended I suddenly realized all of my skills were rusty. I regret wasting all of that time, and wish I would have used it to better myself.

throwmeaway_66OP5y ago

All very good points. However, if you do (1) (Look for opportunities at work), you don't have the time and energy for (2) and (3) with the regularity needed for making serious advances. At that point, you have a well-paid, non-stressful, truly full-time job. I would skip (1) and keep mostly (3) (well, that's what I do, more than advice. A pat on my shoulder, if you will). They are not paying you more, the more you do, the more troubles, stress, and annoyances you call in your direction, and when the tide turns, it is not that they are looking at some code review you did or improved documentation you wrote to keep you onboard.

As I like to say: there is no second life, the only one that was build was virtual and "failed".

011000115y ago

Yeah I didn't mean to suggest doing all 1, 2 and 3. Pick one. Do something for at least half of your idle time, and do it with purpose.

> when the tide turns, it is not that they are looking at some code review you did or improved documentation you wrote to keep you onboard.

I mostly disagree, but it depends on your employer. As a senior engineer, I very much have the opportunity to differentiate myself and protect my position longer than others. I lost my easy job to lower paid, lower skilled engineer because I chose not to put in the work which would have defined my role as a more difficult one. It was easy to replace me when the time came because I allowed the scope of my role to shrink to menial tasks which did not require much thought.

46Bit5y ago

> I can move to Tulum for 3 months and get ready for interviews, no?

I've worked with plenty of sysadmins who suddenly had no choice but to become software engineers. That learning is brutal for some of them–years long process, maybe never. 3 months may not be enough if you coast for long enough.

j / k navigate · click thread line to collapse