msilb

> This happened to me ten years ago. My employer expected me to explain to my coworkers how some things work during that time.

Once I was asked to continue interviewing candidates after I gave notice, which seemed a little odd at the time (also in Switzerland).

This. I am 37 now and feel healthier and overall happier than when I was 15, 20 or 25. It really depends.

Not sure about the US but in Europe there is Revolut that allows you to create virtual credit card numbers tied to your main account. They can be deleted/disposed of at any time in the app.

Switzerland with (currently) 19 votes (+1:)) is overrepresented for its relatively small population size (~9m).

> If I had to describe the style of Scala written at Databricks, I’d put it at 50% Java-ish, 30% Python-ish, 20% functional

This is interesting as in taking a different approach to most other Scala shops I’ve experienced so far where die-hard monoid/functors fanatics take over and make the code base completely incomprehensible to outsiders / new hires. This seems to be a much more sensible approach.

I was also wondering about the missing figure 3. In the linked pdf version everything seems to be in place.

From my experience job hopping usually pays off (at least financially). Bumping your salary in the next job by 50% is not uncommon while may be much harder to achieve when staying at the same firm for years.

As others have pointed out before, interviewing is a skill that can and should be practiced. The best way to prep (except grinding through leetcode problems) is to go to a real interview and practice telling real stories from experience and solving problems in real time under stress. So yeah, I would definitely recommend going to at least a few interviews for jobs that might not be your first choice before going for that “dream job” interview.

Purchased U2720Q after reading through a number of rave reviews and can definitely vouch for it. Excellent 4K image quality and works well with MacBook. It's only the monitor though, so no webcam or audio speakers.

Your description resonates quite well with my own experience. I've seen this over and over again in different (mostly large) enterprises. Peter principle at its best where someone with solid engineering skills gets promoted to become mediocre manager to the detriment of the rest of the team.

I think for someone considering engineering manager track your point #9 is really something to keep in mind. Many managers I've met are well aware of the fact that they're simply unemployable outside of their current company, which essentially becomes a "prison" for them.

Looks like Java is slowly but surely catching up to Scala in terms of API, syntactic sugar etc. I wonder if some people disliking Scala compiler slowness would consider the switch back to Java.