Have you ever worked on a system that was just impossible to maintain?
You spend hours trawling through the code until you finally think you understand what’s going on but when you make your change things fall apart. You introduce ten new bugs in places you thought had nothing to do with the code you changed.
You wade through line after line of code only to discover the method you are trying to understand isn’t being called anymore. It’s dead weight dragging the codebase down.
It feels like you’re seeing double, there are multiple pieces of code that seem to do almost the same thing but not quite. They are 90% the same with a few minor differences.
You are not alone.
This scenario is more the norm than an exception. Luckily there is an explanation and a way to avoid having your code end up in the same situation:
Really looking forward to this upcoming book by . I've had a chance to get a sneak peak at the internals, and it's going to be a great reference for the novice and professional perf programmer alike.
- City University of New YorkComputer Science, 2011 - present
- State University of New YorkComputer Science, 2009 - 2011
Memory consumption of popular Java data types - part 2 - Java Performanc...
This article discusses memory consumption of standard Java sets and maps and ways to improve it by replacing them with the Trove equivalents
Nikola Tesla Wasn't God And Thomas Edison Wasn't The Devil
The Oatmeal published a webcomic praising Nikola Tesla earlier this week. Tesla is deserving of praise, but alas, there's a lot wrong with t
Gamasutra: Tommy Refenes's Blog - How do I get started programming games???
The following blog was, unless otherwise noted, independently written by a member of Gamasutra's game development community. The thoughts an