My observation is that some of the time what people are picking up on is that a conversation is not the interface they want for examining their problem.
In the real world, not all problems decompose nicely. In fact, I think it may be the case that the problems we actually get paid to solve with code are often of this type.
I see you took a downvote. I'm not sure why. I think it's a reasonable question to be asking oneself generally, though perhaps the way you've asked it implies catastrophic near-term collapse, which I don't think is likely.
This is not financial advice.
I made a decision earlier this year to rebalance my portfolio toward more of a 50/50 split with US equities and international equities. Whatever you think of the current political situation in the US, I don't think it can be ignored that the US has shown itself to be an unreliable partner. I believe there will be real, long-term consequences to this. Believe me when I say that given the history of US markets, it brings me no pleasure to bet against them.
What irks me about so many comments in this thread is that they often totally ignore questions of scale, the shape of your workloads, staffing concerns, time constraints, stage of your business, whether you require extensions, etc.
There is a whole raft of reasons why you might be a candidate for self-hosting, and a whole raft of reasons why not. This article is deeply reductive, and so are many of the comments.
Bad, short-sighted engineers will do that. An engineer who is not acting solely in the best interests of the wider organisation is a bad one. I would not want to work with a colleague who was so detached from reality that they wouldn't consider all GP's suggested facets. Engineering includes soft/business constraints as well as technical ones.
I find it is the opposite way around. I come up with <simple solution> based on open source tooling and I am forced instead to use <expensive enterprise shite> which is 100% lock in proprietary BS because <large corporate tech company> is partnered and is subsidising development. This has been a near constant throughout my career.
I agree, my statement is too coarse. There can be a lot of organizational pressure to produce complexity and it’s not fair to just blame engineers.
I’ve given a lot of engineers tasks only to find they are “setting up kubernetes cluster so I can setup automated deployments with a dashboard for …”
And similarly in QA I rarely see a cost/benefit consideration for a particular test or automation. Instead it’s we are going to fully automate this and analyze every possible variable.
Who cares? Now if you'll excuse me, I'm going to crank up Vordhobsn and write some code.
reply