My team came up with an architectural pattern a few years ago. I think it’s good.
I came up with the name this year, it signifies that the control plane (logical, Greek) and data plane (structural, Roman) often share many similarities, but they’re different alphabets, and there isn’t always a bidirectional, information-preserving mapping between them. There always needs to be a one-way mapping (control -> data) though!
I’ve been thinking for awhile (but perhaps not always saying publicly) that I thought E contained a lot of great ideas but they should just give up on being a full-fledged language and become Just A Library In...
Originally posted to dzone but I thought I’d promote it to a blog entry:
Scala teams should live by the Spider-Man™ principle—“With great power comes great responsibility.”
Meaning, when you’re using a very flexible and powerful language, be sure that you...
This happens to me constantly. Here’s my definition:
To refractor code is to start out with the intention of merely refactoring it (such that it still works the same), but then you find that you can’t achieve your goals...
Quoth one plastician:
Evangelical Christians in America are part of a long tradition of the ignorant taking with one hand the enormous benefits of science and vehemently rejecting with the other the fundamental (ha ha) premises that lead to those...