Nobody cares about internal escalations, if manager is taking shit or not - that's not service status, that's internal dealing with the shit process - it can surface as extra timestamped comments next to service STATUS.
The mathematical answer is that if your interest rate is lower than the expected returns of some kind of portfolio you have, than you'll make more money investing.
But I like to bring up what Morgan Housel, author of the book The Psychology of Money, said on paying down his mortgage:
> It just increased our independence, even if it made no sense on paper. So that's another element of debt that I think goes misunderstood. And a lot of that for both of those points is this idea that people don't make financial decisions on a spreadsheet. They don't make them in Excel. They make financial decisions at the dinner table. That's where they're talking about their goals and their own different personalities and their own unique fears and their own unique skills and whatnot. So that's why I kind of push people to say like, it's okay to make financial decisions that don't make any sense on paper if they work for you, if they check the boxes of your psychology and your goals that makes sense for you. And for me, extreme aversion, what looks like an irrational aversion today, and I would say is an irrational aversion to debt, is what works for me and what makes me happy, so that's why I've done it.
Obviously you need to consider both net worth and cash flow when making a decision like that, but don’t underrate the difference that improved cash flow makes!
If anything this highlights the failure of languages solving for this themselves. I'm looking at you, C++.
It's no surprise Bazel is a hard sell for Rust, Go, Node, etc. because for those languages/ecosystems Bazel BUILD files are not the best tool to represent software architecture.
What has changed in the past ~15 years? Many libraries and plugins have their own compilers nowadays. This increases the difficulty of successfully integrating with Bazel. Even projects that feel like they should be able to properly integrate Bazel (like Kubernetes) have removed it from the project as a nuisance.
Back when it was first designed, even compiling code within the same language could be a struggle; I remember going through many iterations of DLL hell back when I was a C++ programmer. This was the "it works on my machine" era. Bazel was nice because you could just say "Download this version of this thing, and give me a BUILD file path where I can reference it." Sometimes you needed to write some Starlark, but mostly not.
But now, many projects have grown in scale and complexity and they want to have their own automated passes. Just as C++ libraries needed special library wrappers for autotools within Bazel, now you often need to write multiple library compiler/automation wrappers yourself in any context. And then you'll find that Bazel's assumptions don't match the underlying code's. For example, my work's Go codebase compiles just fine with a standard Go compiler, but gazelle pukes because (IIRC) one of our third-party codegen tools outputs files with multiple packages to the same directory. When Etsy moved its Java codebase to Bazel, they needed to do some heavy refactoring because Bazel identified dependency loops and refused to compile the project, even though it worked just fine with javac. You can always push up your monocle and derisively say "you shouldn't have multiple packages per directory! you shouldn't have dependency loops!", but you should also have a compiler that can run your code just like the underlying language without needing to influence it at all.
That's why most engineers just need command runners. All of these languages and libraries are already designed to successfully run in their own contexts. You just need something to kick off the build with repeatable arguments across machines.
It's just a way to ease unsuspecting engineers into management. If you don't suck at management, your team inevitably grows (or you're handed over other teams), and before long, you're managing full-time.
Which means that there are three type of people who remain TLMs in the long haul: those who suck at management; those managing dead-end projects on dead-end teams; or those who desperately cling on to the engineering past and actively refuse to take on more people. From a corporate point of view, none of these situations are great, hence the recent pushback against TLM roles in the industry.
If everyone is using it now prompts aren’t a good gauge.
https://www.twz.com/news-features/u-s-has-attacked-irans-nuc...
and see for yourself if Twitter is dead.
It's a shame. Twitter used to be the undefeated king of breaking news.