There's a great annual conference coming to RTP for the first time on May 2nd. The stellar speaker lineup includes four concurrent tracks with six sessions, not counting the morning keynote.
Ultimately, being successful as an individual or as an organization requires more than just transactional engagement. To some extent, we all need to understand that free ice cream isn’t really free.
The underlying issue is tribalism vs. inclusiveness. Do we work hard at empathizing with others and trying to include them or do we settle into a new tribe that aligns with some short term goals? Sadly, most of what I'm seeing in tech these days is simply a realignment of tribalism.
Highlighting IT workers as knowledge workers allows us to learn from the existing body of knowledge on the subject.
Learning Arduino is not simple, especially if you’re not C-minded. It took me a while to see the potential, but if you think about it and join a Raspberry Pi running Node.js with an Arduino with Firmata, there’s not a lot you can’t do.
This article, featured in DZone's upcoming 2014 Guide to Continuous Delivery (releasing April 14th), discusses the widely-discussed design practice of Continuous Delivery. But where did Continuous Delivery come from, what does it offer, and how does it work?
And here I share my newest fun story (a video this time): An engineer as an ‘expert’ in a business/requirement meeting. The task is simple: create seven red lines. But the twist is that these lines must be perpendicular…
What is happening now is that we are at some risk of the luminaries creating an impassable distance between their vision and the on-the-ground reality in many IT shops today.
If you want to understand why I think CI and CD done correctly are almost the same thing, follow me down the rabbit hole.
Consumer Release Testing exacerbates the original flaws of Release Testing. A high value, low cost alternative to Consumer Release Testing is for the consumer and provider to actively cooperate in risk reduction, which can result in a substantial reduction in provider risk.
Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (Mar. 28 to Apr. 03). This week's topics include the virtues of Agile's lack of "control," what Carl Sagan can teach us about lab-lecture balance, and the dangers of allowing Agile to be controlled by non-developers.
When someone else tells you what a standard for your work has to be? How does that feel to you?
I’ll try to explain my favorite 5 misconceptions about Java.
Let those people creating the software, create the system of creation too.
The thing about writing software and especially about writing for open source projects is that the secondary audience becomes an even greater factor. Even if the code speaks for itself you should still create documentation. Something is better than nothing, good documentation is better still.
What if we were able to set expectations beyond a simple number? What if we could say what we know and what we don’t know? What if we could give our best estimate now, and give a better one next week when we know more? Would that help?
Protoypes are good. Well I think so. They give you a better idea of how an application should hang together, where the abstractions are, where there are opportunities for refactoring and re-use. But are there downsides? The classic one is that a prototype sometimes becomes the production code.
What I’m saying is that for candidates with similar extrinsic abilities, their intrinsic abilities will make a much bigger difference in their performance. Don’t overlook a possible standout performer because their extrinsic abilities aren’t a great match.
The point of using agile is to get finish something valuable-to-the-business quickly, to get feedback. Agile is all about change.