found drama

get oblique

Category Archives: Sundry

A dumping ground for miscellany; the amusing, the thought-provoking, the otherwise memorable.

Eric Clemmons re: Angular vs. React

by !undefined

Angular is Easy. React is Hard.:

Eric Clemmons’ perspective on the perception (myth?) that React is easier to reason about and therefore easier overall than AngularJS. Among his main criticisms of React: that it’s only solving the view problem, that you need to “bring your own architecture”, that there subtle bugs may be introduced by JSX, and that confusion around props vs. state can lead to tightly-coupled components.

Ultimately Clemmons’ opinion is that AngularJS is better for prototyping while React is a better fit for “universal” applications. He admits though that all his points may be irrelevant in the near future as newer versions of these frameworks come online. His conclusions seem even-handed and worthy of consideration (though I think he under-states how useful AngularJS can be when properly applied).

“…they will go off and work in the integrated development environments…”

by !undefined

What Is Code? If You Don’t Know, You Need to Read This:

They will do their standups. And after the standups, they will go off and work in the integrated development environments and write their server-side JavaScript and their client-side JavaScript. Then they will run some tests and check their code into the source code repository, and the continuous integration server will perform tests and checks, and if all goes well, it will deploy the code—perhaps even in August, in some cloud or another. They insist that they’ll do this every day, continuous releases.

Read every word. Every one of those 38,000 goddamn words. Even if it takes you 6000 hours.

on Allspaw’s “On Being A Senior Engineer”

by !undefined

On Being A Senior Engineer:

Essential reading from (surprise!) John Allspaw. Not a new post by any means, but so relevant you’ll think it was published yesterday. It’s a great reminder that what puts the “senior” in “senior engineer” is not knowing 10 languages, or having done 10,000 deploys – it’s having maturity, and perspective, and caring and concern for the peers on your team. Or as Allspaw puts it:

Being able to write a Bloom Filter in Erlang, or write multi-threaded C in your sleep is insufficient. None of that matters if no one wants to work with you. Mature engineers know that no matter how complete, elegant, or superior their designs are, it won’t matter if no one wants to work alongside them because they are assholes.

Seriously. File this one for later and come back to it once a year.

Zakas: no accidental standards

by !undefined

The bunny theory of code:

Nicholas Zakas writes this post underscoring the reasons to emphasize only checking in code that you understand:

In my current role at Box, I’m famous for repeating the phrase, “no accidental standards.” We don’t accept that things are “the way” just because they pop up in a couple of places. When we see this happening, we stop, discuss it, and either codify it as “the way” or disallow it. We then update code appropriately before it gets too far. Through automation, code reviews, and code workshops, we are able to keep an eye on the code and make sure we’re all on the same page.

“I’m just listening and conserving energy”

by !undefined

On Conferencing While Introverted:

Introverts often listen more than they talk in conversations, and the less energy they have, the more quiet they’re likely to get.

Talks specifically about how conferences (though enjoyable) can really wring out an introvert. True stories that translate right back to the rest of our daily lives. (Where “our” is the rest of us introverts.)

“a good thing being able to configure a framework”

by !undefined

The Future of the JavaScript front-end framework:

More/less the same drum getting beaten by so many right now (see also: the Joreteg’s announcement about Ampersand, although this opinion piece is probably a better illustration of the theme) – and by that I mean: “Go ahead and provide an all-inclusive framework, but be modular so I can swap out the parts I need.” Which is great, but I would say misses a big point: discoverability of those modules. Say what you will about Spring’s role in the Java eco-system, but its worthwhile to align with a single trustworthy starting point. Part of what’s missing from the “framework fatigue” discussion is just that – that our “big frameworks” only provide a relatively thin slice of what our whole app needs and we’re in “contrib” (and/or plugin, and/or mixin, etc.) hell for everything else. This glosses over the BIG-Big frameworks of a few years ago (e.g., dojo, ExtJS, YUI), but the point stands.

(A version of this previously appeared as my comment on Prismatic.)