<1/4>

“No Bugs” Bunny

unnamed.png

“No Bugs” Bunny
Sarcastic Architect

Hobbies: Thinking Aloud, Arguing with Managers, Annoying HRs, Calling a Spade a Spade, Keeping Tongue in Cheek

BB_userpic_0012.png

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.

TCP/IP Explained. A Bit

July 1, 2013 by “No Bugs” Bunny

BB_part19_2-e1418376853991.png

Abstract:

A crash course on TCP/IP for developers.

Quote:

For TCP, a delay of the order of minutes is not a fault, it is a feature.

Filed under: On.ProgrammingNetwork Programming

Tagged With: UDPTCPIPOverload
Read more

A Model for Debug Complexity

May 1, 2013 by “No Bugs” Bunny

Yes, it is indeed obvious...

Abstract:

A humble attempt to make some approximation of debug complexity.

Quote:

Our model shows that coupling is a bad thing for debugging complexity, so we can consider this sanity check to be passed

Filed under: On.ProgrammingDebugging

Tagged With: Kinda MathOverload
Read more

‘No Bugs’ Top Five C++ Cooking Recipes

March 1, 2013 by “No Bugs” Bunny

Bit cooking

Abstract:

When cooking a C++ program, there are a few spices to consider.

Quote:

"If strict weak ordering is violated, all kinds of weird things can happen: from identical multiple entries in a supposedly-unique collection, to memory corruption

Filed under: On.ProgrammingTips and Tricks

Read more

(640K) 2^256 Bytes of Memory is More than Anyone Would Ever (Need) Get

January 1, 2013 by “No Bugs” Bunny

Binary Solar System

Abstract:

Physics imposes hard limits on amount of memory we will get in foreseeable future.

Quote:

Even if every memory cell can be represented by a single atom, we would need 1 to 10% of all the stars and planets which we can see , to implement 2^256 bytes of memory.

Filed under: On.System ArchitectureRequirement analysis

Read more