Full Stack engineer with 15 years exp.

Location: Bangalore, India

Remote: Yes

Willing to relocate: No

Technologies: .Net, MSSQL, Oracle, MySQL, ESB (WSO2, Oracle Fusion MW). Have worked on Java stack too, but few years back, so bit rusty there.

I think this is applicable to not just CEOs, but project managers and engineers too. Some PMs and Devs just cant function when things cool down.

I know it is a difficult ask for commenters to tell where they are from, but most answers wouldn't make sense unless that information is given. I would have completely different money management principles if I lived in SF bay area or in a developing country. Also, the state of the economy matters a lot. If you lived in a country with 6+% rates of inflation, you would have completely different future planning than say in SF bay. Also important is taxation and rebates in your region. But I am pretty sure you are in SF bay area, as are most other commenters here, so I will excuse myself as I have nothing useful to advise.

Can't the knocker-upper just use an alarm clock?

By we do you mean software engineering in general or bay area? Asking because most people commenting on hn tend to assume the entire universe is just the sf bay area.

Even non-bay area SWE in general is still much better than most other job types and probably much better when it comes to having a nice place to live anyway.

I'd say non-BayArea are relatively in the best position, because remote work always gives a chance for salaries much higher than local to you, while unlike the SF, costs of living won't eat most of what you earn.

Did you mean UPS brown?

Haha, this would be an ideal example of first world problems!!

US mouths eat more than asian and african. Source : https://ourworldindata.org/food-per-person

Ah, but pollution is bigger in Asia.

https://waqi.info/

not to mention that we openly support regimes that will cut their own peoples legs and pollute their own lands for our business.

making our stuff, and disposing of our waste.

Also, poorly written application logic.

In my experience with enterprise applications, we hit database bottlenecks only if you are doing aggregate operations over millions of records or firing 'like' queries over varchar(max) columns without full text indexes. Or generating reports with joins over multiple million record tables.

For most crud operations any production ready database will not bottle neck before you have to fine tune your application server and application itself. Non thread safe application code and libraries have caused more performance issues than large join queries.