Fun Stuff

The x86 Prayer

Here's a little something I dreamed up one night, based upon the Lord's Prayer. Unless you've done your share of Intel assembler programming, some of it won't make much sense.

Our Caller, who art on the stack frame
Hallowed be thy Parameters
Thy Address Space come
Thy I/O be done
In Registers, as it is in Memory
Give us this day our periodic timeslices
And forgive us our page faults
As we forgive those who pass invalid parameters
Lead us not to unconditional JMPs
But deliver us from segment registers
For thine is the Address Space, the Registers, and the I/O ports
Jmp $


Matt Pietrek, 1998

But I Got High (.NET Version)

I can't take credit for this, but wish I could!

I was gonna write some C++, but then I got high

I was gonna skip all that .NET stuff, but then I got high,

Now I'm stuck with non-deterministic finalization, and I know why.

Because I got high, because I got high, because I got high.


A Day In the Life Of The Win32 Loader

This was originally entitled "A Day In the Life Of the Image Activator"  I got it from some ex-DEC'ies, and found it to be one of the funniest things I've ever read.  I've translated it as faithfully as I could to Win32 terminology for the benefit of non-old timers.  Comments are of course welcome.

It's long, so I've placed it on its own page.  Click here.

Time Sheet Fun

I used to work for a major corporation.  One of the joys of this job was filling out the monthly time sheet.  Yes, even salaried employees had to do this.

Here's a sample time sheet, with a few minor additions to make it easier to fill out.  I can't take credit for doing this, but the guilty parties know who they are.

Dead Horses

Dakota tribal wisdom says that when you discover you are riding a dead horse, the best strategy is to dismount.

However, software companies, often try other strategies with dead horses, including the following:

1. Buying a stronger whip.
2. Changing riders.
3. Saying things like "This is the way we always have ridden this horse."
4. Appointing an inter-departmental committee to study the horse.
5. Arranging to visit other countries to see how they ride dead horses.
6. Increasing the standards to ride dead horses.
7. Appointing a tiger team to revive the dead horse.
8. Creating another inter-departmental committee to increase our riding ability.
9. Comparing the state of dead horses in today's environment.
10. Changing the requirements to declare that "This horse is  not dead."
11. Hiring contractors to ride the dead horse.
12. Harnessing several dead horses together for increased speed.
13. Declaring that "No horse is too dead to beat."
14. Providing additional funding to increase the horse's performance.
15. Hiring a consultant to see if contractors can ride it cheaper.
16. Purchasing a product that makes dead horses run faster.
17. Declaring the horse is "better, faster and cheaper" dead
18. Forming yet another inter-departmental committee to find alternative uses for dead horses.
19. Revisiting performance requirements for horses.
20. Saying this horse was procured with cost as an independent variable.
21. Promoting the dead horse to a supervisory position.

Information Passing

Programmer to Team Leader:

"We can't do this proposed project. **CANNOT**. It will involve a major design change and no one in our team knows the design of this legacy system. And above that, nobody in our company knows the language in which this application has been written. So even if somebody wants to work on it, they can't. If you ask my personal opinion, the company should never take these type of projects."

Team Leader to Project Manager:

"This project will involve a design change. Currently, we don't have any staff with experience in this type of work. Also, the language is unfamiliar to us, so we will have to arrange for some training if we take this project. In my personal opinion, we are not ready to take on a project of this nature."

Project Manager to 1st Level Manager:

"This project involves a design change in the system and we don't have much experience in that area. Also, not many people in our company are appropriately trained for it. In my personal opinion, we might be able to do the project but we would need more time than usual to complete it."

 1st Level Manager to Senior Level Manager:

"This project involves design re-engineering. We have some people who have worked in this area and others who know the implementation language. So they can train other people. In my personal opinion we should take this project, but with caution."

Senior Level Manager to CEO:

"This project will demonstrate to the industry our capabilities in remodeling the design of a complete legacy system. We have all the necessary skills and people to execute this project successfully. Some people have already given in-house training in this area to other staff members. In my personal opinion, we should not let this project slip by us under any circumstances."

 CEO to Client:

"This is the type of project in which our company specializes. We have executed many projects of the same nature for many large clients. Trust me when I say that we are the most competent firm in the industry for doing this kind of work. It is my personal opinion that we can execute this project successfully and well within the given time frame."

Back to Wheaty.NET Main Page