Great post! Did you migrate your old database to Azure Flexible Server, Hyperscale (Citus) or a standalone VM, as Postgres 13 does not seem to be available for Azure Postgres Single Server.
I was in management for 4 years and moved to another company as an IC. There was a lot of responsibility and stress being a manager and it was taking a toll on my health. I'm now a lot more happier and healthier in my technical role and it actually pays more too!
I have been at the same company for 25 years, and so have many of my co-workers, who have grown up with me, and I always wonder if that has been a mistake.
Financially I have to imagine it is because of the pay raises that you get from switching vs not. Companies simply do not value their employees enough.
What if you're happy where you are, you're perfectly satisfied with your salary (above median income right after leaving school and increased ~35% since then), and there is basically 1 alternative company nearby (where you'd have a lot more travel) and the rest is either a leap (hoping that you'll like a different kind of work) or more than doubles your commute time (to >1h one-way)?
I heard this advice before and at 4 years I'm quite due for a change in the statistical sense, and I've been offered more money already but... I feel like I'm already rich with no expensive hobbies and the money just flowing into long-term ETFs for retirement. Am I just in an exceptional situation or does the advice still apply to me and should I leave within the next 1-2 years?
I think it really depends on the industry and location. There's a clear tendency on HN to only consider the tech market in California, where it makes the most sense to hop companies regularly. It's not the case for everyone.
I work in a large European industrial company in aerospace, and the vast majority of the employees stay until retirement. Yes most change job regularly, even relocate to different countries, but within the same company. Outside options aren't great, you're not looking at large potential raises and will have difficulty finding as good of a package unless you go into another industry completely. If I was fired I'd probably have to move to a different country and get into another industry to get a good offer.
An argument I would make would be for future proofing your employability. You clearly care about thinking long-term. What if the current gig goes under, are you properly trained in technologies other companies in 5-10 years would use, that maybe your current gig doesn't?
Just spitballing. If you really are 10/10 happy, and aren't concerned with the possibility of that company blinking out of existence and being screwed, I would probably just say ride with it until you feel like quitting.
There's an opportunity cost in _moving_ too; ever heard the saying that three moves equals one fire? If you're in a position you find satisfying, and see a technical and financial advancement path that seems acceptable, don't trade the roots you're putting down for some theoretical improved later slope of earnings.
But keep your resume up to date, and go on interviews from time to time. See what the offers are, and do the math on them. And if the math says "Stay put", ignore the techbros who disdain roots. :)
At the very least, preserve the option to come back. Be honest with your employer, tell them you enjoy the work but are just curious what else is there.
This is a strange attitude; if you change jobs every three years, then how much are you going to get done, really? If everyone took this approach, then would any large project ever get finished?
Well, OP is talking about their first job, so my advice is targeting that specific situation. As a general rule, engineers see a fairly large bump in pay when going from their first to their second job, particularly if they did a poor job of negotiating their first salary. So yes, in terms of career development and realizing your earning potential, you should not stay at your first job for more than a few years.
In many startup product companies, the specific knowledge about the product is not interchangeable with other tech companies. The tech skills and the soft skills are, but a large part is know-how about the product and the market.
It makes sense to stick around longer if you see yourself as a "knowledge worker" rather than as an interchangeable techie. It certainly makes sense from the company's perspective to keep knowledgeable people around.
It's very likely. 2 years seems to be standard, and I'm moving jobs after 1.5 next week. 20% raise for very similar work, there's no reason not to move.
Part of me says I did this with my first job in the computer industry. On the other hand I was reasonably compensated (for the time) and that job led directly to a progression of a few other jobs that have served me fine.
Sounds like you're in a high management role with potentially a lot of power. Why don't you control you're environment to make it more suitable for you? Delegate tasks you don't like. Make other people attend meetings for you.
With infrastructure in multiple regions, do you have independent Aurora databases running in each region? Do you have any data synchronising between regions or are they running completely independently?
For users, I'd add a OAuth layer to the application layer and still have this application using a HMAC like above. You want to try keep things 'stateless' when it comes to your API's.
Within your own network a simple key/secret combination is enough, as the secret can just be stored as an environment variable, for example.
For users you'd need some way for the users to "fetch the secret", which is effectively what logging in is. At that point you should just use JWT or oAuth.
