4 ms·
Microservices aren't the problem. Incompetent people are
- zug_zug 3y agoEnough things are wrong win the first paragraphs of this article that I can't be bothered to skim it. But the attitude that "X that fails at 9/10 companies isn't the problem, we just need to change millions of engineers" is a naive attitude.
- threeseed 3y agoEnough things are wrong win this comment that I can't be bothered to skim it. If you're going to make claims that micro-services are failing at 9/10 companies you really should have a source.
- spandrew 3y agoAgreed. This is like blaming the user for your bad UX. Nope, the solution increased the complications of a very complex problem set (scaling software development). There are no silver bullets that can solve this. Only well-designed systems accommodate for the flexibility of human error and hubris can do that.
- brodouevencode 3y agoYeah, it is a bit of a blanket statement, and it's quite common to headline with provocation, but there are some good things in here. He admits upfront that MS is his personal preference. > I understand it’s a harsh title and at times a harsh essay. Such is life. All opinions are my own. Some takeaways you might have missed: * Use the right tool for the job - one-tool shops are bound to fail * (Similar to above) There is a tendency to find _a_ solution rather than the _optimal_ solution * The engineering halo effect is real and prominent Then the author goes on to provide some possible solutions: * Using the SOLID framework for building * Use services * KISS * Developer experience is very important * Protect your time and your work * Governance is required to enforce certain principals. I don't agree with all of these, but they are certainly worth considering.
- Nondv 3y agoHey! I'm the author and thank you for this! I did find that lots of people who disliked it, mainly just got put off by the overall tone and the provocative statements from the get go. I basically blame my writing skills (and maybe personality haha). This essay lacks structure and it's more of a stream of thought (sometimes jumping all over the place and going off topic). I'll just have to live and learn :)
- piva00 3y ago> But the attitude that "X that fails at 9/10 companies isn't the problem, we just need to change millions of engineers" is a naive attitude. It's even worse than naïve, it's a literal fallacy, a "No true Scotsman" with technology. System resilience is important at scale, and resilience includes being resilient to the failures in the human component of development; if a system depends that every one developing it to be a master of the underlying foundation then you'll require lots of very specialised, competent people who mastered the technique. That is very costly, if microservices depend on high mastery then we should budget the cost of the talented people required to run it. My experiences with how to successfully deploy microservices include much the opposite: giving tooling to incompetent people to avoid the worst footguns, training them in best practices over time while designing an architecture that is somewhat resilient to their inevitable failures, one that is easy to be fixed when they've learned how to best use it.
- wmidwestranger 3y ago> "X that fails at 9/10 companies isn't the problem, we just need to change millions of engineers" And even in those 9/10 companies, the failure doesn't even prove that the engineers are the ones unable to create meaningful service boundaries, within a monolith or distributed to multiple services. All of those engineers have bosses and, I don't know what others are seeing, but I feel like I've seen Software Development Manager increasingly become Manager of Software Developers. I suggest that those same management structures which failed to enable their engineers to create meaningful service boundaries in their monolith, which led to the desire for a cure-all solution, also failed to manage (or protect) their developers such that those developers _could_ turn the existing system architecture into one based on microservices. Technical leadership has just become increasingly abysmal. Developers are tasked to fulfill user stories but those are often written in a way that completely ignores the technical work required to fulfill such a story. That creates a painful disconnect between expectations and reality, even in 90% CRUD, monolith web apps. Even in a monolith with proper separation of concerns, its easy to imagine one service being the "user" of another service for the purpose of more granular and clear tasks but, "that's not how user stories work." :(
- drekipus 3y ago> "incompetent people are" Yep, which is why it's the problem. You will always have incompetent people.
- mad_vill 3y agoBingo. Design for incompetence. There are few codebases in this world that don't need incompetent people to contribute to them. (This is typically driven by business incentives) If you get to work on one of those codebases ... good for you. The rest of us are just trying to gatekeep piles of shit from getting in while being pushed by management to open the flood gates.
- devbent 3y agoEveryone is stupid at 3am when the on call alert goes off and a critical service is down. Write code and design systems so 3am you can fix them!
- cirgue 3y agoThere are a lot of things in life that would be trivial if everyone was really good at what they did, had the most perfectly pure of intentions, and were omnisciently aware. Unfortunately that’s not the world we live in, and even farther from the companies most of us work for. Good technology is about figuring out shortcuts around hard problems, and “large groups of people trying to coordinate their activities across space and time” is a hard fucking problem.
- apatheticonion 3y agoI feel like there is an unfair sentiment of competence elitism in the software engineering world. I don't think you can stop less experienced engineers (or experienced but still bad engineers) from contributing to projects - especially at the scale of a lot of these large organisations. After all, for people early in their careers, being bad is the first step to being good and it's impractical (or impossible) for organisations to exclusively hire "premium" engineers. There's also nothing wrong with engineers who program exclusively to collect a paycheck and aren't actually passionate about their work. I believe this is an inevitable side effect of the accessibility of programming today. Project architects should instead strive to design their systems such that they expect low quality contributions and limit the potential damage those contributions can have. Systems should be able to take a low quality contributions and if the need arises, have the capacity for those circuits to be optimised at a later date without rewriting the entire thing. I personally find the argument that "bad engineers make microservices bad" to be silly. Bad engineers would poison any poorly architected project, be it a monolith, microservice or otherwise. Microservices are just an architectural optimisation with trade offs that some organisations find value in.
- PH95VuimJjqBqy 3y agothey're called juniors and every other industry has seniors to help guide them and ensure they don't make major mistakes. Except in our industry. In our industry the juniors often are the ones making the decisions.
- ryanmcgarvey 3y agoThat's the problem with software - it's decisions all the way down. Outside of prototyping, there's very little "work" to be done that doesn't contain some kind of systems decision.
- calvinmorrison 3y agothis can be limited though. I just went through refactoring a whole set of classes that implement the same interface, but it was not defined as an Interface. now any new class that implements this _must_ meet at least some expectations, enforced by the code. So in one way, OOP is great for limiting side effects.
- jayceedenton 3y agoThis article seems to be trying to get in way too much, but I appreciate the initial sentiment. The sad truth is, a smart team can do well with any architecture. A weak team will fail with any architecture. And maybe it's not really too sad. I've seen organisations that really kick ass using microservices, and I've seen some microservices horrorshows too. The difference is having teams that are talented enough to get the benefits of any given technique and mitigate the drawbacks well. Those teams will execute any architecture to its maximum benefit.
- Veuxdo 3y ago> There’s also another category of people. Good (sometimes brilliant, even) engineers who know exactly what they’re doing but who simply don’t care enough to do the right thing. Sometimes not doing the right thing is the right thing to do.
- SoftTalker 3y agoI don't know how CS is taught these days. In the 1980s I learned a lot about data structures, algorithms, and programming languages, virtually none of which I ever directly used in my later career. I've never had a job that required leetcode knowledge. I've never had to write a sort or a search or a tree balancing algorithm from scratch. There are libraries for anything you might want to do (and if there aren't, that's often a big red flag that you're doing something wrong). I learned almost nothing about engineering. It took me quite a while on the job to learn and appreciate the practices that result in long-lived, maintainable systems. Overly complex, fragile systems with inscrutable interdependencies using esoteric frameworks are often the product of smart people who don't understand engineering principles (yet we often call them "engineers").
- Samisp 3y agoBut CS is not engineering, CS is a branch of mathematics. I studied Finance at university and I've seen people complaining how it doesn't teach you how to invest in stocks and do M&A. Later, talking to professionals about what they do in their jobs I realized that what I'm being tough is adjastent, but they are not preparing you for a job. It's not like medicine where you get placements and they literally train doctors. Same with Computer Science, it's not software engineering and while the two are obviously adjacent. Damn I'm 6 years into my software engineering career as a self-taught guy, and I've contributed, implemented, and released projects that work well in the real world for non-trivial companies, but I am only now learning about algorithms and CS theory as a side project. I think bootcamps try to fill that field but most of the ones I've seen are quite trivial, getting you through the basics. If you're asked to implement 10 greenfield CRUD APIs and then go to a job and have to maintain some huge monolithic repo it's going to be hard. I think an educational approach where the curriculum involves some sort of "For this task, you have to change this thing in this codebase and deploy it without crashing the thing", "refactor this code base", giving people some sort of project and then switching it up in the middle would be valuable because it's mostly what software engineers do day to day: write tests, fix bugs, implement features in existing projects.
- wvenable 3y agoIn the late 90's and early 2000's I learned all that data structure stuff but that was mostly in the first 2 years. Beyond that many classes were about software engineering, project management, etc. I learned Agile (then in it's infancy) as well as doing a complete waterfall project (which turned out poorly -- as expected). But even at that time most other schools did not offer those kinds of courses in their CS education.
- willsmith72 3y agowhat a ramble > Not being smart is totally fine (I certainly am not one). We just need to avoid being stupid. > Let’s face it, engineers, most of us aren’t smart > most people don’t give enough shit to improve Barely even makes sense, and is just a bunch of random opinions
- safetytrick 3y agoAn under-rated solution to this problem is saying No and having quality retrospectives. Microservices adoption has largely become a cargo cult thing. It is a part of being cool like FAANG. Instead of being cool, focus on solving your problems.
- willsmith72 3y ago> Instead of being cool, focus on solving your problems. This needs repeating to every dev every week. Myself included
- tdeck 3y agoMicroservices are a solution to an organizational challenge: how do we set clear boundaries of ownership within a complex system? From a technical perspective there are pros and cons. Unfortunately, I don't see a wealth of other ready-made practices for companies to copy when they grow and need to solve this problem. I once worked on an enormous Rails monolith that was very well organized and had layered on several additional patterns to improve modularity and maintainability. Still, a SEV in a minor product area could (and did) bring down the whole system, and they were in the process of dismantling it.
- drewcoo 3y agoActually, loosely-coupled microservices improve testability, too. And improve it by far if we're comparing with monoliths (where tight coupling is considered a "feature"). One of the troubling practices is tightly-coupled containerized services, though, which only gives us all of the problems of microservices at the same time as we have all of the problems of monoliths.
- sisve 3y agoA microservice architecture is a good way to solve the problem with the monolith. The problem is the word mikro. It should have a better name. If it was called "boundary architecture" or similar it would make people stop creating to small pieces. One team should not manage 15 services.
- obviouslynotme 3y agoMicroservices are Resume Driven Development, the leading paradigm of our industry and others. People will always optimize for the incentive structures of their environments. The most important person in every company is the CEO. He sets down the culture of the company and creates these incentives either directly or indirectly. The only solution to RDD is for the CEO to be tech oriented, avoid hiring people who jump companies every couple years, build a great work environment, and compensate people well.
- mschuster91 3y ago> avoid hiring people who jump companies every couple year You don't get many of those people any more, because just about every other employer has burned that bridge to the ground. People, especially the young ones who entered their careers around the 2008ff megacrisis, have zero trust left in anyone. When companies don't care and ditch us at the first sign of problems (easy, because we were the freshest hires), why should we show any sign of loyalty in return? If you want loyalty, pay us.
- obviouslynotme 3y agoAs I said, RDD is the dominant paradigm because it is rewarded. The career trajectory of someone who hops companies versus someone who doesn't is wildly different. I also pointed out that the problem isn't with the developers but the leadership, starting at the top. The programmers are just acting rationally in the environment they are given. The value of a programmer is exponential with time in the code, and yet, they aren't compensated for it. What they are compensated for instead is decorating their resume for their next job.
- alex_lav 3y agoThere can be two problems.
- deanCommie 3y agoCompetent engineers never understand why others are not as competent as them. It'd be cute if they didn't then write thoughtleadership about how it's really simple to get rid of the cloud - you too can run your own datacenter, and custom kubernetes orchestration competitor. Just hire competent people! Looking at ya, DHH. And of course, it's the same thing here: > The real problem, I think, is the lack of engineering competence and the lack of “giving a shit” in companies OOOOH they should just hire competent people? I guess they never thought of that...
- readthenotes1 3y agoX isn't the problem, people are.
- andrewstuart 3y agoAh, it's not a problem with the phone, "you're holding it wrong".
- the-anarchist 3y agoThe author is not wrong, yet there's not enough sugar-coating to make this post appealing to wider masses. I believe that more than just a handful of us share some of those opinions and experiences, though. These days everyone and their dog can become a "software engineer", unlike in other professions where the entry bar is significantly higher. Hence, you will find cabals of similarly average engineers agreeing with one another's opinions simply because it's an echo chamber.
- reedf1 3y agoThis article misses that there is a business case for bad decisions. Sometimes there is no other choice than making a design shortcut, doing things that don't scale, overcomplicating or overabstracting. There is no sense criticising these decisions, typically made for good reasons for which the current view of the code does not provide an explanation. Sometimes you don't win the contract if your service doesn't work in three months (game over), sometimes there literally is no funding for more engineers, or a system hemmoraging existential amounts of money needs to be hotfixed. Moreover building a system can be like discovering a new scientific theory, only once it has been developed in an overcomplicated or overabstracted way, does the simple case actually become obvious. If there is an "epidemic" of anything it's hindsight criticism of engineers who made the best decisions that they could. "Incompetence" is doing a lot of leg work in this article, this is not a real specific criticism by itself. To me this a symptom of over antrhopomorphising the failures of a company and glomming them onto a theoretical goblin for which you can blame the ills on. I believe this behavior emerges from engineers that have not participated at a decision making level in the entire software development process at many different sizes of company in many different contexts. This means a startup from zero, a large company where the marginal cost of issues is so extreme that all code is mobbed, a mid size company being bought out, being in charge of a service from ideation, to development, to maintenance and deprecatio.
- hu3 3y agoThis is my main gripe with some newcomers of projects I have worked on. They tend to spit out destructive criticism towards legacy code with such an ease and without any context on why things are the way they are. My usual response, albeit in a more polite manner, is something along the lines of: "Yes I know the code in this part of the system is not as nice as other parts. And if you bothered to ask why, I'd tell you it's because this code is 6 years old and we learned better ways to do the same thing since. It's called technical debt and we are always working to reduce it. There's no need to demoralize the engineers that worked on that part of the system."
- easywood 3y agoJust from the title, I can deduce the article is based on a logical error. There will ALWAYS be incompetent people involved in any solution. So if solution X fails because of incompetent people, but solution Y succeeds, then solution Y must be better. The same goes for the disclaimer at the end, "it's actually about incompetence across organisations", you will always have that.
- camila45 3y ago[flagged]
- Nondv 3y agoThe author here. Thanks for sharing! I usually just go with reddit and my linkedin (which barely has any network anyway haha).
- AnetteJourdan 3y ago[dead]
- flappyeagle 3y agoIncompetent people who choose microservices