Re:Ending the Era of Patronizing Language Design
by lars512 on Saturday May 22, 2010 @10:12AM
(#1370324)
I had the opposite problem at a student intern gig. I hadn't experienced smart pointers before, and was double freeing memory accidentally. The fun part was that the unit tests for my code always worked. It was always someone else's code which appeared to break inconsistently after my change ;)
You live, you learn. We picked it up remarkably quickly in the end, basically because the company had their process working right: clean codebase, solid testing, and regular code reviews.
Re:Ending the Era of Patronizing Language Design
by jamesbritt on Saturday May 22, 2010 @12:08AM
(#1369764)
Small pieces, loosely joined.
Or do you really write monolithic 1M+ line apps?
One of my favorite stories is we had hired a bright young dev many moons ago. Months into his work we were trying to fix this terrible memory leak, and it looked like most of it was coming from his code. We asked him, "Where do you free this memory, we can't find it anywhere -- you clean up everything else." His response, "Wait, how do you free memory?"