Skip to main content

Of toilet seats and parking

Why do men get a bad rap for leaving the toilet seat up? It's all over pop culture that men are inconsiderate pigs that don't put the toilet seat down after peeing. Well...women are just as guilty. Sure men don't put the seat down after peeing but women also don't put the toilet lid down. Just as you hate seating on a cold toilet, men hate peeing in a toilet when the seat is down ('cos then you'll have to clean up the inevitable spill). Personally, I think the toilet lid should be put down every time! Not only does that solve the argument, it's more esthetically pleasing. And might be healthier.

Enough about toilets. How do you park? Are you one of those people that insist on backing into a parking spot (even when there are no rules requiring it)? I don't get why people do this. Unless you are robbing a bank, and thus anticipating an hasty getaway, there's no reason to back into a parking spot. You have better control going in front-first into a tight space and when it's time to leave, you have more room to back out. And if you are lucky, the car in front of you will have moved and you won't have to use your reverse gear at all! So next time, you find yourself trying to back into a tight parking spot ask yourself why?

Comments

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply