R u mdrn? How to lure hipster hackers

Do u hv ths stf? Here's what you should -- and shouldn't -- keep in your stack to attract today's developers

Are you keeping up with the JonesCos? Everyone is doing it -- and so should you.

Sometimes it's about fashion, sometimes it's just because, sometimes it's about keeping or recruiting top talent, and sometimes it's about competitiveness. To be hip, what should you have in your stack? What shouldn't you? Behold the shining path:

[ Work smarter, not harder -- download the Developers' Survival Guide from InfoWorld for all the tips and trends programmers need to know. | Keep up with the latest developer news with InfoWorld's Developer World newsletter. ]

1. Hadoop

This is your data warehouse, but for god's sake, don't say "data warehouse." All of your reporting is moving here, including your archival audit logs and even many of your diagnostic logs. There is a plan or process in place to create a larger "data lake" or "enterprise data hub" for analyzing data across departments.

2. MongoDB

This is your operational data store. Since most of your applications are Web and mobile apps, JSON is their native language, and it's MongoDB's default format for storing documents.

3. JavaScript front ends

Objective-C is for suckers, and JSP is for old men who never really learned to code. If you're not using Ember.js, AngularJS, and/or Backbone.js, then your website is partying like it's 1999. AJAX isn't a thing anymore, it's an assumption. The network really is the computer, the browser really is the operating system, and while both the companies that used those slogans are long gone, the vision was realized. Moreover, the next step is one codebase for your mobile devices. Stuff like Appcelerator Titanium let you do this today while you wait to be able to do pure HTML5 (you're in line to get Famo.us, right?). Therein lies the possibility to reuse code from your Web app in your native mobile app.

4. Node.js

Your Web apps should be looking to unify their codebase: JavaScript front end to JavaScript middle tier to JavaScript-oriented database (the last is BSON, but whatever). More than that, you're heading toward a reactive, event-driven architecture. Nonblocking IO is a given for highly scalable applications.

5. Apps for that

If anyone in your company has a BlackBerry, you are not modern. There is Android, and there is iOS and nothing else, and your company needs to support that big time. At the very least, all of your websites should have a mobile screen profile, properly detect tablets (and not force tablets to mobile profile), and enable people to do their job when they are on the run. This means the CRM system, the documents, the bug tracker, and everything in between must be mobile-enabled. The "you have to install this Cisco VPN nonsense that only works on Windows" is for the old and decrepit. I'd rather suffer Heartbleed than slow my computer to a crawl ... or run Windows.

1 2 Page
Mobile Security Insider: iOS vs. Android vs. BlackBerry vs. Windows Phone
Recommended
Join the discussion
Be the first to comment on this article. Our Commenting Policies