You want the best and the brightest money can buy. Or do you? In fact, you're better served by a group of developers with mixed skill levels who focus on getting the job done
A big, important project has launched -- and abruptly crashed to the ground. The horrible spaghetti code is beyond debugging. There are no unit tests, and every change requires a meeting with, like, 40 people.
On the other hand, maybe not. A team of senior developers will often produce a complex design and no code, thanks to the reasons listed below.
Durham, NC - August 23, 2012- Yesterday, the Wall Street Journal announced Neo Technology's Graph Database Partner Program. Among those in the partner program, Open Software Integrators was claimed as an intricate part of the portfolio due to its outstanding track record in delivering valuable solutions to clients. OSI is excited to collaborate with Neo Technology and eager to provide successful solutions with Neo's graph database program.
I've been credited with coining the term "do-ocracy." When I've had the opportunity to lead an open source project, I've preferred to "run" it as a do-ocracy, which in essence means I might give my opinion, but you're free to ignore it. In other words, actual developers should be empowered to make all the low-level decisions themselves.
When you think about it, the hacker group Anonymous is probably one of the world's most do-ocratic organizations. Regardless of where you stand on Anonymous' tactics, politics, or whatever, I think the group has something to teach developers and development organizations.
Online tech publication the The Register published an article by Matt Asay, Unstoppable JBoss 'mafia' has big biz tech in its crosshair, featuring JBoss extraordinaires that have made it big in the enterprise world. Needless to say, enterprise "mafiosos" were exalted, companies credited and innovative projects given their glory in an article with the abstract stating, "Welcome to the hits factory."
So you get the gist...
Anyone who watches even a small amount of software development is familiar with the scene: The agent, be she new hire or consultant, comes in assuming that success of the project at hand is the goal and that everyone is familiar with its pre-requisites. “Show me to your revision control system” she says.
Some are bad habits to overcome; some are poor decisions forced by managers who don't know what they're doing. Read 'em ... and weep
Writing great software is not that hard. But software developers can be their own worst enemy in trying to code the good stuff because they lapse into sloppy or wrongheaded practices.
Actually, scratch that: The developer's worst enemy is really the eager technical manager who tries to deliver a project faster than possible and pushes developers to engage into ill-advised practices. In high-end enterprise and Web-scale projects in particular, that can result in wholesale disaster.
OSI President and Founder, Andy Oliver is set to speak at the Association of IT Professionals of RTP at the NC State University Club this Thursday, August 9. The topics include Trends in Mobility and Cloud Computing.
Other featured panelist will include: Paul Denham, Mobility Applications Consultant, AT&T Advanced Enterprise Solutions Sumit Deshpande, VP, Mobile & Messaging Services, BB&T Bob Dieterle, Sr VP & General Manager, Smart Online Angela Bailey, Director, Product Marketing Management, AT&T Hosting, Cloud and Application Services
In the era of big data, good old RDBMS is no longer the right tool for many database jobs. Here's a quick guide to choosing among NoSQL alternatives
I've been in Chicago for the last few weeks setting up our first satellite office for my company. While Silicon Valley may be the home of big data vendors, Chicago is the home of the big data users and practitioners. So many people here "get it" that you could go to a packed meetup or big data event nearly every day of the week.
In plain English, domain-specific languages let users define business rules and help ensure applications do what they're supposed to ...
A DSL (domain-specific language) is a language designed for a business or industry domain such as health care, finance, or insurance. It defines processing in terms of the nouns and verbs of your business rather than in terms of a pure computer language.
In most cases, domain-specific languages look like stripped-down versions of English that incorporate business jargon. DSLs are especially powerful when used with a rules engine -- and most rules engines support some kind of DSL system.
Workflow engines help ensure enterprise application development stays on track -- if you know how to use them
Workflow engines are underused and underappreciated. Most companies configure or develop enterprise software so that it implicitly reflects their business processes and leave it at that -- big mistake.
Instead, workflow engine can be used to provide state diagrams for developers. They enable you to map and store the state of the system, as well as hook into state transitions that trigger events and functionality.