1. 29

  2. 11

    I imagine the author must not agree with this article anymore, since now his position is “Head of DevOps” at EarnUp.

    On another note: wget is indeed used for archival https://www.petekeen.net/archiving-websites-with-wget but in modern web, since so much of it is dynamic, this won’t work. Probably the clojure distributed crawler with ec2 is the best option if your core business is parsing pages, if not you won’t get much far.

    1. 6

      Author didn’t just take down their article years ago, they took down their whole blog; this is a mirror.

      1. 4

        If I had written a blog post a decade ago that implied Python is only for people with vaginas, I would have deleted it too. Plus I’d be annoyed at people republishing it without permission.

        1. 2

          We are all publishers now and published information moves in mysterious ways. Sometimes, not in ways we’d want.

          1. 1

            That’s not what “pussied out” means.

      2. 6

        Though perhaps a bit provocative, I do agree with the underlying point. There is a benefit to using composable, small, battle-tested tools.

        I’ve found that at home, I’m reaching more for UNIX-y tools than flashier new tools I found on Github, if for no other reason than I don’t have to deal with (as many) environment/dependency/versioning issues

        1. 2

          The characterization of DevOps seems very unfair to me. For me, DevOps means “automate all the ops stuff you did by hand before”. That’s great because it saves a ton of boring repetitive work and brings reproducibility and documentation into the process.

          1. 0

            This article is just ad hominem, unless it’s satire in which case the joke’s on me. Certainly there’s no shortage of overengineering. He proved his point with a contrived example, but I don’t see how I can extrapolate to other use cases. Maybe sometimes simple Unix tools do get the job done, but sometimes things need to scale or be understandable to the lowly developer or not break if a node dies. In the universe of devops solutions, there is also a middleground between Hadoop and unix tools, and whether or not one or the other or the middle is appropriate is going to vary from case to case.

            The post reads like a rant by someone who doesn’t want to learn something new, who can’t believe the world around him is changing and his toolset (while still quite relevant) isn’t as relevant as it used to be. I see this a lot from sysadmins who swear that “all this serverless stuff [fargate, lambda, etc] could be done much more simply with EC2” without accounting for all of the work that goes into productionizing an EC2 instance (image build pipeline, ssh, metrics, centralized logging, process management, bin-packing applications, etc) that you get roughly for free with serverless platforms.

            I think we would do well to accept that we work in technology and the value of that technology exists in an economic context that generally doesn’t care about how much work we put into learning it.

            1. 7

              What part of this article did you find to be an ad hominem attack, and against whom exactly?

              By contrast the beginning of your second paragraph seems very much an attack on the author.

              1. 1

                The snarky implication that DevOps or whoever is motivated by trendiness and hype (e.g., “cool-kids”, “nonsense known as DevOps”, etc) backed by the straw man example. I’m not attacking the author; at worst I’m speculating about what motivated him to write such a snarky piece (which strike me as rather transparent, but feel free to disagree).

            2. 1

              Taco Bell programming is one of the steps on the path to Unix Zen. This is a path that I am personally just beginning, but it’s already starting to pay dividends. To really get into it, you need to throw away a lot of your ideas about how systems are designed: I made most of a SOAP server using static files and Apache’s mod_rewrite. I could have done the whole thing Taco Bell style if I had only manned up and broken out sed, but I pussied out and wrote some Python.

              Morihei Ueshiba would be proud that someone attempted to “return to the source”. Would be nice to hear a followup for sure.

              1. -2


                Stories with similar links:

                1. Taco Bell Programming via ehamberg 5 years ago | 53 points | 45 comments