Archive
Find The Bug
The part of the conclusion in the green box below for 32 bit linux/GCC (g++) is wrong. A “long long” type is 64 bits wide for that platform combo. If you can read the small and blurry text in the dang thing, can you find the simple logical bug in the five line program that caused the erroneous declaration? And yes, it was the infallible BD00 who made this mess.
Aligned On A Misalignment
After recently tweeting this:
Chris Chapman tweeted this link to me: “Understanding Misalignments in SoftwareDevelopment Projects“. Lo and behold, the third “misalignment” on the page reads:
Chris and I seem to be aligned on this misalignment.
Nickels And Dimes
In mediocre 20th century orgs, some ambitious managers are always trying to get something out of their DICs for nothing so that their personal project performance metrics “look good” to the chieftains in the head shed. Nickle and diming “human resources” by:
- calling pre-work, lunchtime, or post-work meetings,
- texting for status on nights/weekends,
- adding work in the middle of a project without extending schedule or budget,
- expecting sustained, long term overtime without offering to pay for it,
- not acknowledging overtime hours,
- “stopping” by often to see “how you’re doing” without asking if they can help
does not go unnoticed. Well, it doesn’t go unnoticed by the supposed dumbos in the DICforce, but it does conveniently go unnoticed and unquestioned by the dudes in the head shed.
What other “nickel and dime practices” for getting something for nothing can you conjure up?
Human_Being:preserveSelf
As the UML sequence diagram below shows, an “unnamed” Nature object with an infinite lifeline asynchronously creates and, uh, kills Human_Being objects at will. Sorry about that.
So, what’s this preserveSelf routine that we loop on until nature kicks our bucket? I’m glad you asked:
Have a nice day! 🙂
Performance Per Watt
Recently, I concocted a blog post on Herb Sutter‘s assertion that native languages are making a comeback due to power costs usurping programming labor costs as the dominant financial drain in software development. It seems that the writer of this InforWorld post seems to agree:
But now that Intel has decided to focus on performance per watt, as opposed to pure computational performance, it’s a very different ball game. – Bill Snyder
Since hardware developers like Intel have shifted their development focus towards performance per watt, do you think software development orgs will follow by shifting from managed languages (where the minimization of labor costs is king) to native languages (where the minimization of CPU and memory usage is king)?
Hell, I heard Facebook chief research scientist Andrei Alexandrescu (admittedly a native language advocate (C++ and D)) mention the never-used-before “users per watt” metric in a recent interview. So, maybe some companies are already onboard with this “paradigm shift“?
So-Called Reality
Your Fork, Sir
To that dumbass BD00 simpleton, it’s simple and clear cut. People don’t like to be told how to do their work by people who’ve never done the work themselves and, thus, don’t understand what it takes. Orgs that insist on maintaining groups whose sole purpose is to insert extra tasks/processes/meetings/forms/checklists of dubious “added-value” into the workpath foster mistrust, grudging compliance, blown schedules, and unnecessary cost incursion. It certainly doesn’t bring out the best in their people, dontcha think?
You would think that presenting “certified” obstacle-inserters with real industry-based data implicating the cost-inefficiency of their imposed requirements on value-creation teams might cause them to pause and rethink their position, right? Fuggedaboud it. All it does, no matter how gently you break the news, is cause them to dig in their heels; because it threatens the perceived importance of their livelihood.
Of course, this post, like all others on this bogus blawg, is a delusional distortion of so-called reality. No?
The Search For Accountability
As I’ve said several times before, WordPress.com is a sweet blogging platform. One of the many metrics that the customer-and-product obsessed WordPress team provides to its users is the list of terms that people have searched to land on your blog:
As you can see, the search term “accountability” dominates all others. WTF is up wit dat? It also looks like people want to learn more about “CSCIs, CSCs, and CSUs“. The funny ones are “lighten up francis“, “firing squad“, and “disco dancer“. I’m humbled by the fact that some people searched for BD00 directly with “site:bulldozer00.com” and “bulldozer00“. lol.
So, when are you gonna expose yourself to the world and start blogging your thoughts, feelings, and opinions? One of the tag lines of the best boss I ever had was “don’t keep it a secret“. BD00 has internalized it with the addition of “no matter how much it hurtz“.
Sticks and stones may break my bones. But chains and whips excite me. – Rihanna
Hacrobatics
It’s funny how attitudes, preferences, and likes-dislikes change over time via personal experience and the acquisition of new knowledge. Having transitioned from a C background over to C++ quite awhile ago, I used to think pre-processor macros were a kool feature that came along for the ride. However, after having been burned multiple times by scope-ignoring macros, I learned to hate the damn little buggers. The scorchings made me fully appreciate the addition of “const“, templates, and inline functions to C++ in order to wean people off of “hacros“.
Maintaining a “hacro” laced program can drive anyone up a wall because:
I’m bummed, but not surprised, at how many people still think that “hacros” are a kool and useful feature of C++.













