And you are here why?

/via http://www.commitstrip.com/en/2018/11/26/if-its-not-broken/ Funny cartoon, but the whole " Don’t refactor  craetionDtae ”, thing is a bit far-fetched, right You’d probably fix that typo without thinking twice about it, right? Wellllll, maybe not. After all, this might actually be something that is exposed to users (it’s in the API. Yay), so you need to refactor this  and  the documentation, but that’s OK, you can do that, right? Wellllll, maybe not. Because, now that you look, you notice that you’ve got  two  sets of typos,  craetionDtae  and  craetionDate , which means that refactoring means that you need to update  both  of these in the code  and  the docs, so now it’s  4  things that need to be changed, but it’s ok, you’ve got that, you can do it, right? Wellllll, maybe not. Because, now that you really look, you realize that  craetionDate  also exists as  craetionDates  (becaus...

/via http://www.commitstrip.com/en/2016/10/27/a-magical-cure/ “ Unit tests are a waste of time ”  —   #CowboyDeveloper Yeah, even in this day and age, you still get this. After all these are the same folks who are convinced — convinced I tell you! —  that their s**t doesn’t stink , that  code coverage is something that the QA group is responsible for , and that  as long as the code works, tests are unnecessary . It’s a peculiar mindset, born of the  #CowboyDeveloper’s absolute assurance that They Know Best, and that there is nothing new under the sun (unless they discovered it first, of course). These #TechBros (and they’re always Bros, by the way) can wreak havoc on a dev team, or an organization, and if you have any agency at all, you should weed them out. Tragically, so many of them end up as Founders, CTOs, (CTBrOs?), or both, and continue to perpetuate the cycle, and inflict havoc. Sigh.

So yeah, this was years ago, before AWS was a thing. We provided business phone services (•), and had all our servers at a hosting facility (With cages. Where we had our own servers. Remember, this was before AWS!). This was a  real  hosting facility, with batteries, and a generator to back the whole thing up. And we were a  real  phone company, with tens of thousands of customers. All good fun — for a given definition of fun, mind you. Until the one day when there was a massive snow-storm, and a huge percent of D.C. lost power. Including our hosting facility. Which was fine, because the batteries took over immediately. And the generator kicked in, because the batteries were only good for, like, a minute or two of power. And after two minutes, all our servers crashed. Because, as it turned out, during routine maintenance, some dude had disconnected the generator from the circuits,  and never reconnected them . The good news was that a decent chunk ...

/via http://www.commitstrip.com/en/2016/10/10/a-story-about-css-units/ CSS Is Awesome! No, really, it’s awesome. It’s awesome in exactly the same way as  emacs  is awesome, in that spending 6 weeks away from it means I have to re-learn every damn thing I knew all over again. And yes, I’m saying this because I’m looking at a bunch of CSS that I  know  I’ve tweaked successfully in the past, and it’s all greek to me. Or rather, it’s all CSS to me. Sigh. 

 /via http://www.commitstrip.com/en/2018/06/19/the-world-cup-and-the-sysadmin/ We’ve tried many variations over the years — the one I found the most effective was to actually just put the game up on the TVs that are liberally distributed around our offices. ( And yes, we even bought a couple of extra TVs for a few of the neglected walls, to make sure… )

  /via CommitStrip