“No Bugs” Bunny
“No Bugs” Bunny
Sarcastic Architect
Hobbies: Thinking Aloud, Arguing with Managers, Annoying HRs, Calling a Spade a Spade, Keeping Tongue in Cheek
Once upon a time, in a rabbit outsourcing warren of Bunnylore, there was a young software developer bunny. And as a developer, she has had one very unusual treat: she was obsessed with eliminating all the bugs she can get his forelegs on. So, it is not surprising that her friends called her a “No Bugs” Bunny (or simply “NoBugs”).
Later on, she grew up, so she decided that “Bunny” in her name has became inappropriate (not to mention potential arguments with Warner Brothers), so she has asked all her friends to call her “No Bugs” Bunny. She has made a career as a team lead and software architect, and they lived happily ever after.
Over-Generic Use of Abstractions as a Major Cause of Wasting Resources
September 1, 2011 by • “No Bugs” Bunny
Abstract:
Trying to be too generic can easily cause many-fold inefficiencies.
Quote:
It was a quiet night and I was downloading a 2G ZIP file with Internet Explorer...
Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingOptimizations
Read moreThe Guy We’re All Working For
July 1, 2011 by • “No Bugs” Bunny
Abstract:
If we like it or not, developers exist solely for one purpose: to make user happy.
Quote:
If developers are forced to do something outright stupid, one cannot possibly expect them to work with enthusiasm.
Filed under: On.DevelopmentDevelopment Philosophy
Read moreOn CMM, Formalism and Creativity
May 1, 2011 by • “No Bugs” Bunny
Abstract:
CMM, if taken literally, inhibits creativity “by definition”. See if we can find a creative way to allow creativity to survive.
Quote:
“…where the head of the organization is second-rate, he will see to it that his immediate staff are all third-rate; and they will, in turn, see to it that their subordinates are fourth-rate.” – C.N. Parkinson
Filed under: On.DevelopmentDevelopment PhilosophyDevelopment Processes
Read moreOverused Code Reuse
March 1, 2011 by • “No Bugs” Bunny
Abstract:
When done imporerply, code reuse can cause severe problems, including loss of life.
Quote:
Reusing code from other projects or (even worse) from 3rd-parties SHOULD NOT be taken lightly. Or else...
Filed under: On.System ArchitectureDesign decisionsOn.DevelopmentDevelopment Philosophy
Read more
Six Impossible Things Before Breakfast Ltd. © 2026. All rights reserved.
