Posts

Showing posts with the label framework

Life On The Leading Edge

Image
/via http://www.commitstrip.com/en/2013/08/28/faut-que-jte-dise-un-truc/ Life on the Leading (and yes,  definitely  Bleeding) Edge means that you’re always working around that *one* feature that doesn’t quite work the way you’d like it to. Read this, and tell me if it sounds familiar — 1.  You start working on a new system. It’s important, so you can’t really just experiment with Bleeding Edge stuff, but you’ll use this relatively new framework (or library. or codebase. or whatever) that you really like. It’s been around for a while — not so long that it’s Old, and therefore UnCool — but long enough that it’s got most of the kinks worked out. Besides, it’s perfect for what you want to do. 2.  The thing is, it is  almost  perfect for what you need. There’s this one feature that you wish it supported, but you can work around. So you —  happily!  — work around that feature 3.  Over the next few months, it turns out that that one feature that you...

So this just happened…

Image
 ruc /via http://www.commitstrip.com/en/2016/05/30/very-very-old-projects/ ‘It’s not like the “fun” we had when we swapped out Angular for React, but this pretty much holds for any/all breaking changes. Turnover in the core-services team leads to swapping out SaltStack for Ansible  but only for the new environments, because we’ll deprecate the old environments, right? We should keep up with django updates,  except for that one high revenue client’s environment, because “high revenue” right? I could go on, but there is  always a reason to not update. What’s worse, the reason might actually be a good one 😟

Life Before Frameworks

Image
/via http://www.commitstrip.com/en/2014/02/03/trop-de-code-tue-le-code/ Mind you, nowadays you’re lucky if you get to use the same damn framework twice in a row…

The Truth about JS Frameworks

Image
/via CommitStrip

Every UI Framework Ever

Image
/via CommitStrip