• submit to reddit
Rob Allen03/17/14
4 replies

Use Statements and Code Readability

I was having a discussion on IRC about use statements and whether they improved code readability or not. Having thought about all the responses I received and having slept on it, I think that it’s preferable to be able to organise your code and name your classes such that when importing we minimise ambiguity. If we reorganised, we could come up with something like this:

Lubos Krnac03/17/14
0 replies

Trigger Continuous Delivery every GitHub Commit

I am going to show how to set up this process using Maven and Jenkins. Target environment is hosted on Tomcat7. Source code is hosted on GitHub. Because I am the type of developer who tries to avoid polling as much as possible, I am going to show how to trigger this process by GitHub's cool feature called WebHooks.

Antonin Januska03/14/14
7 replies

What Fibonacci taught me about programming

A few weeks ago, I was solving the Fibonacci sequence problem: "Given an index, return the correct number from the Fibonacci sequence." I tried different approaches, looked up how others have done it and learn a few awesome things.

Johanna Rothman03/14/14
0 replies

Design Your Agile Project, Part 1

The more I see teams transition to agile, the more I am convinced that each team is unique. Each project is unique. Each organizational context is unique. Why would you take an off-the-shelf solution that does not fit your context?

Edmund Kirwan03/14/14
0 replies

What's the opposite of duplication?

Strange that we still worry about duplication.

Mike Bushong03/13/14
0 replies

Automation: More than saving keystrokes

My point here is not to put down the DevOps tools. Instead, I want to point out that how these tools are used is important. If you view tools like Chef or Ansible as a means of cutting out keystrokes (read: pushing config), then you are likely missing the point of automation. What these types of tools are really trying to do is much more profound.

Leigh Shevchik03/13/14
0 replies

Kanban for Ops Teams

All ops teams share the need to meld an interruptive work stream with a planned one, and it’s hard to get that right. In the Site Services team in Site Engineering at New Relic, we have a Kanban process that we use to manage our workflow. We’re pretty happy with how it’s working for us, so in this post I’ll share what we did and why.

Juri Strumpflohner03/13/14
0 replies

Automating the build of MSI setup packages on Jenkins

A short "how-to" based on an issue one of my work mates recently faced when trying to automate the creation of an MSI package on Jenkins.

Dave Booth03/13/14
1 replies

Does your DBA hate you? 5 Tips for writing efficient SQL queries that get you some DBA love.

I spoke with my DBA friend today who runs an Oracle data-warehouse that’s about 2 terabytes big, at an international bank. I asked him: "What are some typical problems that users, data analysts, and DB developers have, that make you want to pull your hair out?" (to be fair, he doesn’t have much hair left, so if he’s willing to make that final sacrifice, these must be some big issues). In his experience, the vast majority of performance problems fall into these categories.

Alec Noller03/12/14
0 replies

Dev of the Week: Johan den Haan

Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Johan den Haan, CTO at Mendix.

Roman Pichler03/12/14
0 replies

A Template for Formulating Great Sprint Goals

I find it helpful to consider three questions when choosing a sprint goal: Why do we carry out the sprint? How do we reach its goal? And how do we know that the goal has been met? My sprint goal template therefore consists of three main parts: the actual goal, the method employed to reach the goal, and the metrics to determine if the goal has been met.

Dalip Mahal03/12/14
7 replies

The Programmer Productivity Paradox

If the average programmer writes about 50 lines of production code a day. A 50,000 line program would take 1,000 man days to produce. The 50,000 line listing can be entered by a programmer at about 1,000 lines a day or about 50 man days. So what the heck are the developers doing for the other 950 days?

Andrew Fuqua03/11/14
0 replies

Don’t Estimate Software Defects

I don’t estimate software defects. Well, I have two exceptions: If I have a backlog of old defects to burn down, I may estimate those. If I have found some new bug that we plan to fix in some later sprint, I may estimate those (though I really don’t like to defer defect fixes). Otherwise, I don’t estimate defects.

Michael Heinrichs03/11/14
0 replies

3 Reasons to Choose Vert.x

The application platform Vert.x takes some of the innovations from Node.js and makes them available on the JVM, combining fresh ideas with one of the most sophisticated and fastest runtime environments available. Vert.x comes with a set of exciting features that make it interesting for anybody developing web applications.

Vlad Mihalcea03/11/14
0 replies

Choosing a Leader like an Agilist

We need to trust our teams and respect their opinions. I like this approach since it’s a very good way of spotting leaders that you weren’t aware of. People with leadership potential are rare gems and I always stay open-minded to any method that can bring me the next great leader.