godzilla82

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.

Did you mean UPS brown?

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

I know its frowned upon to ask why you are being downvoted, but honestly I would like some feedback on why the comment is being downvoted. The commenter I was replying to, it seemed to me had missed the part and so was forming an opinion on what they think a "taker" is. In the article, you will find that he defines takers the very next paragraph after he uses the word takers. In the Joe Rogan podcast, infact he elaborates on this.

Yes, the Zero Rupee Note does not achieve anything at all. For e.g. if a traffic cop stops you, the first thing he does is that he takes your driver license. Good luck getting it back with your fancy Zero Rupee note.

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.

He does define takers in the very next paragraph.

Maybe you missed the part where he defines takers. Here's the part :

>Then there are people who come along with a sword, or a gun, or taxes, or crony capitalism, or Communism, or what have you. There’s all these different methods to steal.

There is no beauty in it, you need to understand power play and how it manifests in real life. The official is taking bribe, because you have a need for some thing to be done and he wields power over you. If you do such nonsense, your work simply won't be done, and the official will simply create additional hurdles.