Applying Agile methods to an organization on an enterprise level can be difficult. In order to ensure product quality, minimal time-to-market and increased value, avoid these mistakes when embarking on this transformation.
It's a well known deficiency of most existing sampling Java profilers that their collection of stack traces has to happen at a safe point. A while back Jeremy Manson open sourced some proof of concept code where calls are made to the AsyncGetCallTrace JVMPI method which avoids the need for threads to reach a safe point in order to read their call trace. I've taken this code dump and started converting it into a usable open source project.
If you're looking for a practical application to help you get started with MongoDB (or Node.js, or Express.js, for that matter), you might be interested in this presentation from Karan Goel on getting started with Node.js, Express.js, and MongoDB. You can find the video below, and Goel's slides here.
Sometimes you want to set the state of your project back to a previous commit, but keep the history of all the preceding changes. You want to make a commit that reverses all the changes between your previous commit and the current HEAD.
In particular, we current have over three thousands tests, and they take hours to run. We are doing a lot of stuff there “let us insert million docs, write a map/reduce index, query on that, then do a mass update, see what happens”, etc.
The key challenges around compensation, at least for me, center around figuring out how to reward individual performance without encouraging internal competition, local optimization, or one person feeling rewarded while another feels punished. You want compensation to motivate people, not to have a negative impact on performance.
This article includes an original presentation about AngularJS given as a slideshare. This article includes the original 20-minute screencast about AngularJS. The slideshare shares the author's thoughts on the learning process and resources that he felt were particularly helpful.
Agile software development is not about productivity; it’s about working well. Yes, I think there are potential gains in productivity for most teams. Even then, the bulk of the gains are from “maximizing the work not done” rather than becoming more efficient programmers.
Old crotchety principles sometimes surprise. The dependency inversion principle has long earned respect from programmers for its prowess at smashing the rigidity and fragility of otherwise un-lubricated systems.
Here at DZone, we are dedicated to providing our community with the knowledge needed to understand the latest technologies and trends and make the best decisions. That’s why we are excited to announce the release of our biggest research undertaking to date: DZone’s 2014 Cloud Platform Research Report.
This post is about a recent performance tuning exercise. A closer look to the application revealed it consisting of several batch jobs bundled together. The troubled application was a pretty innocent-looking small JAR file. Which, to my luck also bundled the load tests.
In this article we look at how and why an agile team should gather elementary metrics, including lead time, throughput, velocity, and burn. We also look at cumulative flow, and briefly consider why the "actionable metrics" of the Lean Startup movement are so important to business.
If you are a long-time PhoneGap developer like the author, you may have missed a release note somewhere like he did. When PhoneGap released version 2.0, they dropped support for Xcode templates. While that sounds like a bad thing, it wasn't.