Comments by "Inconspicuous Chap" (@InconspicuousChap) on "Continuous Delivery"
channel.
-
Microservices are a way to split the work between developers, how the corporate management sees it, and that's the primary reason of their popularity. Just like OOP was 20-30 years earlier. The corporate approach to software development is hiring mediocre easily replaceable coders, as cheap as possible, split the work between them and expect them to build something working without designing it as a whole. Since no working software can be built without a design stage, they just pick up a "one size fits all" trendy design, whether it's applicable or not. The whole point of splitting the work is an attempt to evade exponential dependency of development and maintenance costs on the size of the product, resulting from poor design and mediocre coders' decisions along the way. Managers use scholar math to estimate that exp(N) is significantly higher than e.g. exp(N/k) * k (for k microservices and N code lines in the product), totally ignoring the fact that the multiplier here would not be k, but some kind of exp(k^2) because there would be k^2 interactions, and the complexity of mediocre programmers' work always grows exponentially with the size of the domain they try to model. So that actually results in the costs still being exponential, with even higher multiplier (exp(Ck^2 + N/k) instead of exp(N), where C is the average number of code lines per microservice interaction, and that's an optimistic approach assuming services behave consistently, which never happens in mediocre programmers' implementations), and no chance for developers to lower them even if they wanted to and knew how to do it.
16
-
12
-
8
-
2
-
2
-
2
-
1
-
1
-
1
-
1
-
The business now does not require brains, they want hands on a pipeline of primitive tasks. Apparently you should dumb your CV down and find 2 parallel middle jobs, each 100% remote and without daily meetings. When you get interviewed, try to speak in CRUD application developers' language, the managers should believe they can control you, so you should look like their average employee. Never show that you are smart, let alone smarter than they are, before you are hired (perhaps it's also worth playing dumb after). If you could complete a middle developer's 8hr job in 4 hours, then you are in a fair situation. If you work faster, that's a net profit for you. It might feel bad not to be recognized as a smart guy, but after all, what do you need more - money or that recognition? A friend of mine had owned a factory once. He knew lots of people high up, at a city mayor level. Then he got bankrupt, lost all his luxury, was working as a taxi driver for a few years. He once said he started feeling much better when it happened. But a businessman is a businessman - eventually he learned how the system worked, bought several cars and other taxists pay rent to him now.
1
-
1
-
1