Google broke our RSS feed. FeedBurner, which we are using now, is being moved over to the Google “platform”, which caused some problems involving their MyBrand service, Yahoo Pipes and a bunch of other minor inconveniences. Don’t know, don’t care. Remember what I said once about strict decoding and all that stuff? I lied. That might be good for signaling, but for the media, for something that humans are supposed to be consuming in the end, accept anything that you can make remote sense of, in hopes that the human in the end would be able to receive it, or maybe realize that something is wrong and try to fix it from his end.
Well, we’re back. We managed to fix what needed fixing.
As it was, people didn’t get the feed for a couple of months. Therefore, I’ll review what you missed.
TODO or not TODO, That is the Question
One of the customers went over our code, and found many TODOs in the code. That made me think: from the client’s side, isn’t checking for TODOs in our code a little bit counter-productive? The direct result would be that we will remove the comments from our code, and will be more likely to forget about them. When a programmer writes a TODO comment, it could mean one of several things, not all bad.
Commenting Can Be Bad For Your Soul
Following the post about the usage of TODO style comments, I asked the developers here at RADVISION to send me stories about inappropriate comments that they found in code. A wicked funny post, plus a guide for writing your own bad comments.
By the way, I also wanted to write an additional post about assertions, but Miško Hevery from Google’s Testing Blog beat me to it.
Why I Won’t Work For Joey DeVilla
Joey DeVilla writes about Captain Chesley “Sully” Sullenberger, and drives his point home with his recommended interview question: “What do you do in your spare time?” I don’t code, Joey, and I want my employees to have interesting hobbies.
“Hello, I’m a Slave” “And I’m a PC”
While your PC may be the grease lightning of computers, it usually can’t handle multiple, intensive memory, disk and network accesses. That’s where the Slave Computer, or SC, comes in, to aid the PC, the Primary Computer. This post covers some uses and utilities for a Slave Computer.
Five Bad Medicines for a Sick Code
I write about five signs that the developer in charge of the code could not figure out how to fix it. You still find a crutch here and a splint there added to keep the sick code “breathing”, like strange constants, data out of place, extensive error returning, code replication and code preservation.
About The Intel Threading Tools, Our SIP Stack, and Me
I asked Ofer Goren, a software engineer in the SIP Stack team, and one of those given the optimization task, to write a few words on multi-core optimization. Spoiler: they increased calls per second by 50% (!), to 94% core utilization.
Tags: developer, developers, optimization, Testing, Tools
Trackback this post | Subscribe to the comments via RSS Feed