This is my tumblelog. It's much more simplistic than a blog, it's just random snippets of things really. Some I've created, many I haven't.

Posts Tagged: programming

"Years later I couldn’t help noticing I was writing more test code than program code and that I’d stopped working on side projects, because every time I started I thought: Ok, I’ll hack out a prototype for this cool little game in no time. So, well, I guess I’d best start by writing a few tests for the core mechanics. Right, time to get my framework out. And… uh… ugh, maybe I’ll go watch some Buffy instead."

Source: coderoom.wordpress.com

Grouping Tests Using JUnit Categories

This is one of the things I really liked about TestNG. Hopefully I can start grouping tests together and generating reports on module coverage within the same project.

Source: java.dzone.com

Top 5 mistakes made by software development managers.

Source: makinggoodsoftware.com

What every web developer must know about URL encoding

Source: lunatech-research.com

How to Manage Programmers

Source: tuomaspelkonen.com

Sten’s Blog » Blog Archive » Interviews with Average Programmers

Source: blogs.citytechinc.com

NetBeans IDE Java Editor Reference Guide

Source: netbeans.dzone.com

Archives - Momoro Machine

An awesome resource for ruby / rails developers

Source: themomorohoax.com

Understanding Ruby Blocks, Procs and Lambdas

2010, I’m going to learn this!

Source: robertsosinski.com

20/20: Top 20 Programming Lessons I've Learned in 20 Years

Some very good points

Source: dcs-media.com

Some Useful JavaScript & jQuery Snippets - Part 4

I could have used the “How to get the number in the ids” one today.

Source: tympanus.net

Problems with TDD

For what I do, TDD isn’t a great fit and I’ve been saying this from the start. Though this article doesn’t touch the issues I have, it still has valid points on its own.

Source: dalkescientific.com

Pivotal Labs: Talks

Wow, looks like a plethora of stuff here.

Source: pivotallabs.com

Simple Guide to Maven

Source: tedwise.com

"1) What have you done since the last daily scrum regarding this project?
2) What will you do between now and the next daily scrum meeting regarding this project?
3) What impedes you from performing your work as effectively as possible?"

Source: abrachan.wordpress.com