|
|
|
|
|
|
by Nextgrid
926 days ago
|
|
|
Before looking at technical problems, we need to look at organizational problems. Is the tech there to solve a business problem, or is it there to solicit the next VC round, an invite to a cloud provider conference, an expensive dinner paid for by some vendor, or to perpetuate a career based on flawed technology? A lot of the problems, associated tooling and "best practices" you mention arose as a result of the VC bubble from the last decade, where the primary objective was not to solve the business problem but to manufacture complexity so the next VC round and large headcount could be justified. Sadly, this is not limited to VC - either collusion or technical incompetence is rampant at the executive level, which means crap vendors can nevertheless get their "solutions" into companies and lock them in. Do this long enough, and entire careers start relying on these "solutions" so you get a guaranteed supply of people who can collude with you to bleed their company dry. See also: * cloud computing * blockchain * microservices * resume-driven-development |
|
|