I see, didn’t think of the case of somebody with visa requirements. I don’t really know how to compare US salaries to my German salary, since taxes and social security and cost of living are different, but for 162k Euro I’d probably also would rather not resignate, but do “Dienst nach Vorschrift” (= doing exactly what your asked for, but not showing extra initiative)

Wow. Since I presume that you didn’t stay there: how curt was your letter of resignation?

The crucial point to me, which I could not read out of your first post, nor will I implicitly assume it as a given, is that there still is a feedback loop from product development to the staff/principal level.

I’ve been burned by a code base that was created by a principal engineer, who tossed it over for maintenance and moved on to greener pastures (still in the company though). It is more to blame on the organization, than on the engineer, but still such an experience leaves a slightly bitter taste.

So, you don’t actually do real work and have to live with the technologies that are chosen on your recommendation? Sound like a sweet deal. The senior engineers that have to actually make software that is sold and clean up the mess will hate your guts though.

More likely that I am the naive one - I know that there is no place without politics (we’re all humans after all), but I strive to minimize politics, because it drains me.

What I meant specifically were those two points:

How to indulge a senior manager who wants to talk about technical stuff that they don’t really understand, without rolling your eyes or making them feel stupid

and

How to get other engineers to listen to your ideas without making them feel threatened

Beyond basic human courtesy, I don’t agree that the fragility of other peoples ego should be the leitmotif of communication in a professional setting. I’d think a senior engineer should be able to speak up without beating around the bush, both to peers and higher-ups. I would assume for the higher-ups it should be more valuable to get candid responses from those in the trenches than smile-and-nod-yes-men responses.

And I think the counterpart of the second “listen to other engineers’ ideas without feeling threatened” is really good advice, because unlike the other one it is under your control and also a good thing in itself.

Then I also find “How to get another engineer to do something for you by asking for help in a way that makes them feel appreciated” has a bit of a manipulative touch.

Most of the points are good advise, a few of them rub me the wrong way. Considering that the author is somebody in higher management, a few of them sound like “how to collect brownie points” and “how I’d like my butt to be kissed by my underlings”, utterly self-serving - OTOH maybe those indeed are the rules of the game, and those who think that particular game is worth playing might want to pay attention.

Well, if you factor in tuition fees, cost of living and opportunity costs (reduced income because you’ll likely wont work fulltime anymore), do you expect to get a job afterwards - that you could not get with your current qualifications - that will pay off those costs? You’ve got a degree in mathematics, so you’ll do the calculation…

Do you know that scene from Good Will Hunting where Ben Afflecks’ character says to the snobby student who tries to waive with the prestige of his school: “you dropped 150 grand on a fuckin’ education you could have got for a dollar fifty in late charges at the public library”?

If you want to grow your skills you can do it three orders of magnitude cheaper than with a degree program by studying from books or taking dedicated courses and seminars. Consider if you want to go down a path where the credentials are really a requirement or just a nice entry in your resume.

Assuming that your company has a profitable business, and you are working on the part brings in the revenue that pays the bills, you’ll keep that as long as your company is interested in keeping that business. Your CTO is burning money (and fast!), maybe they’ve picked that habit up in a zero-interest environment, but well interest rates aren’t zero anymore, so I’d be more worried if I were part of the secret internal startup.

Java is not very much older than Javascript and at the time it was far from the world’s first programming language. It probably was measured by hype in developer circles the Rust of the mid-nineties.

Not sure if it counts as not widely used, but I think the Collections.unmodifiable(Collection|Set|List…) methods are very useful.

Seconded. Really, anything but the oracle JDK.

Well, it makes the client-side calls a bit simpler if you don’t distinguish create and update via POST/PUT, so at the server-side you have a single POST endpoint which does the upsert, but there it would be sensible to dispatch to separate methods for insert and update each.