- Hardly anyone is saying “SOA” but everyone is talking about SOA. This was especially evident during Jon Sullivan’s talk. Jon mentioned using Node as a façade or proxy for other, older, legacy applications — pulling data out and sending it along to the newer, smaller, purpose-specific applications. And then boom here come the questions/comments from the audience about their old and crufty and monolithic monster legacy apps. (For those of you that were there: here is one of the Songkick dev blog posts about their migrating-to-SOA process.1) Anyway: the conversation kept veering toward SOA, but the social pressure of “hey we’re here to talk about Node!” kept pulling it back the other way and… Anyway, this might make for a good talk or round-table sometime, since there’s so much interest.
- Getting involved in open source. This was the other “meta-theme” of the night. Again: the theme of the night was Node, and as such, npm modules came up over and over. How do you find them? How do you find good ones? What makes a module “good”? If it’s technically superior to the alternatives but it isn’t actively maintained, is it still “good”? This is not a problem that’s unique to Node, of course, but do a search for “template” in npm sometime and you’ll see what I mean. One of the points that we made2 was that while it is tempting to write your own module… sometimes the right thing to do is instead to fix that bug or add that feature or write that contrib lib and submit a damned Pull Request. And if a project looks DOA, maybe contact the original author and offer to take over stewardship. And now that GitHub has enabled redirects on repos,3 there’s even fewer excuses.
Anyway… The meet-up was great and I’m looking forward to the next one. If you see Patrick or Pete, give them a high five or buy them a beer or something. BurlingtonJS is a thing that needs to keep happening.
- From there, the rest are easy to find. [↩]
- I say “we” because: as part of his talk, Jon was talking about contributing back to the modules they used; and Artur was urging people to make Pull Requests instead of just forking or writing their own thing all the time; and I was right up front nodding vigorously. [↩]
- Wherein I praise GitHub’s repo redirect feature and explain why it’s important: link. [↩]