3 ms·
Stop focusing on stuff you disagree with. Tell us why. For example, devops may be BS, but if so, why, and what is the alternative? There are answers. Try to ke
by jchw 8y ago
Stop focusing on stuff you disagree with. Tell us why. For example, devops may be BS, but if so, why, and what is the alternative? There are answers.
Try to keep in mind that just because you're challenging a trend does not mean you're correct and you should always consider that A.) There are absolutely things you do not know that might change the answer(s), B.) When you disagree with a trend you're often disagreeing not just with people who follow the trend, but a large population of smart people that set trends too, and those people often have reasons for their ideals (which are often valid in context.)
Sometimes it turns out a lot of ideas do make sense with some constraints. Few ideas make sense if you consider every single possible parameter. You probably don't want to build a web of microservices running with several internal and external load balancers that call through webs of RPC requests in order to serve your personal blog that sees 1000 requests per day, for example, but that doesn't mean designs utilizing some of those patterns are unilaterally incorrect or not effective to solve problems at a different scale.
- stanislavb 8y agoThat's a very good answer and the example is quite valid. I think the trend of microservice-everything is going out of hand in many teams. Yeah, many smart people set it, but what if most of those smart people were working in companies that a magnitude bigger than yours? Moreover, sometimes challenging the trend is so costly that you are better off going with the "wrong" solution than fighting it. In general it's a tricky one, and I'm sure there isn't a single correct answer to it.
- throwawayjava 8y ago> Stop focusing on stuff you disagree with. Tell us why. For example, devops may be BS, but if so, why, and what is the alternative? There are answers. Also, consider the possibility that you are wrong about the fad being stupid precisely because you've already accepted the fundamental premise behind the koolaid. The original instantiation of devops is actually the "fad" that made me realize this particular truth. I had only ever worked in situations where all the infra people sling scripting languages along with the best of 'em and the software developers are as comfortable with iptables and apt and load balancers as they are with their editor/ide/compiler of choice. So to me, devops sounded like a lot of ridiculous hot air -- it's just a new name for how things have always been; how can all these promises about productivity improvement make any sense to anyone?! And besides, the stuff that wasn't obvious was often ridiculous cargo culty stuff. What I didn't know was the sheer number of shops where the IT people didn't have any programming skills and the programmers had never become competent with CLIs! In many shops, IT folks knew some recipes in the Windows Server GUIs and the devs knew how to use one IDE. When I first encountered a shop like that, I suddenly realized devops isn't hot air, even if for me the core tenets are just a description of how you should obviously do thins and how they've always been done...
- dasil003 8y agoAnd what do you think about the current trend wherein 60% of people who use the term DevOps do not understand any of what you said and just use it as the new word for System Administration?
- amanzi 8y agoThanks - points taken. By the way, I didn't mean to imply that I disagree in general with those items I listed, those were just some examples that I had been thinking about recently.