|
|
|
|
|
|
by verdverm
1161 days ago
|
|
|
Truth, I've built a lot of automation for a CI / ops system. The devs have not taken the time to learn it, because business needs them to deliver value to the user. This certainly adds pain at times, but overall the business is better off with specialization and experts. In an ideal world, it would be great for everyone to be aware, but people have limited time and the systems naturally grow large enough that you would have to spend all of your time just keeping up with the changes. |
|
|
This is where we have architects, microservices and layers of complexity and abstraction.
> and the systems naturally grow large enough that you would have to spend all of your time just keeping up with the changes.
I've seen more cases where it doesn't actually need to be that large - just like you don't need infinite scaling or 1000 microservices and microfrontends. Instead of accepting that it has to grow - think about how it can work together more efficiently. In a lot of situations there's been more downtime due to redundancy, DR and other setups than having a simple instance.
Everyone architects their own part and a build tool / process for each of it... when does it end?
I see these "systems" that mention more as a mess and most people spend 80% of their time to workaround it or just procrastinate at how fragile it is.