Every time you make an async call there is a whole state machine that has to be instantiated and managed. The only situations I would argue justify async over sync:
1. You are making an I/O bounded call and most of the CPU time would otherwise be spent idle.
2. You are making a CPU bounded call that the UI thread cannot directly await.
3. You need to propagate an asynchronous call context for one of the 2 above scenarios.
There are situations where you can put yourself in a position where it seems async needs to be everywhere (i.e., sharding a monolith to a bunch of separate networked elements).
Yeah, I’ve moved off vscode entirely, back to fully featured out of the box ides for me. Jetbrains make some excellent tools and I don’t need to install 25 (dubious) plugins for them to be excellent
google argued with me. a lot. I went to school but didn't graduate. not something they were prepared to deal with. never claimed I had a degree. but the fact that they called the school and the school said I didn't have a degree was a huge red flag.
I did a startup. the year before we were incorporated I was doing prototypes and fund raising. We called the company and you're weren't employed until 20xx, but you listed 20xx-1 as the start date! now you're in trouble.
I’ve known people who has dropped out of college after receiving job offers during their internships. The problem is that some companies cap your your maximum pay and promotions unless you finish college even though you had excellent performance reviews. So you either stay on college and lose the job opportunity, or stay knowingly that at some point you’ll have to come back to college to finish your degree.
Individual Contributor, a euphemism for "non-management"? copilot is usually pretty good with deciphering contextual acronyms. Why "IC" instead of "NM"?
No, frugality has been an Amazon "value" from the beginning. Look up the story of Jeff Bezos famously using an old door for a desk. Or all the execs complaining about having to share a hotel room during business trips for the first couple of decades of Amazon's existence.
C++ has been dead and effectively banned at amzn for years. Only very specific (robotics and ML generally) projects get exemptions. Rust is big and only getting bigger
A system built on purely synchronous calls is infinitely easier to reason about and design in all aspects other than e2e latency.
I'd almost approach from the opposite direction, defaulting to sync calls till you have concrete performance reasons not to.