November 16, 2004·
spout
Art Tips for Programmers
As I think I've said before, as the capabilities of our UI platform expands, programmers are going to need to know a lot more about user experience and graphic art. Towards that goal, I offer a recent post on Slashdot that provides
advise on how programmers can bone up for the latter. Anyone got any ideas about the former?
November 13, 2004·
spout
Outsourcing to Arkansas
I love the idea of outsourcing to rural parts of the country because a) I like keeping jobs in the US if possible (although I’m not a protectionist by any stretch of the imagination), b) it gives the under-employed more choices and c) it’s another step toward my dream employment environment.
I see a future where people are listed like books on Amazon with ratings, reviews, descriptions (aka resumes), prices and availability, to be placed into a shopping cart to form ad hoc project teams based on the needs of the project and not on the locale of the participant or something as restrictive as “employer.” I admit that I this article is only a small step and may not even be in the direction I’m hoping for, but as I’d like to live in a rural area (central Oregon) and still get to do interesting work at reasonable pay, I’m more than happy to read into things.
November 11, 2004·
spout
A Guy Worth Hiring
This guy deserves a flood of job offers. Make yours good!
November 7, 2004·
spout
Concrete Examples of Software Factories?!?
I've been reading each of
the Software Factories articles with great interest. Part 1 and part 2 did a particularly good job describing the elements of the problem space, I thought. However, when I get to
part 3, I was ready to see a solution. Instead what I got was a long abstract piece defining the bits of what makes up a software factory. This is the kind of thing I'd be ready to read after I was shown a concrete example or two of working, running software factories. Do other people like reading these long, abstract articles? I find them tedious unless they're filling in and generalizing the details of something that I've already got a handle on.
November 4, 2004·
spout
The Importance of Reputation
My youngest son was called into the office today for pantsing a kid on the school playground. That is not at all like my son (he’s the sweetest kid you’d ever want to meet), but the principal was new, so she was talking about suspension. Luckily, the secretaries knew my boy, so they were able to point out the inconsistency of that behavior with the reputation he had built in 4 years at the school. It turns out that the pantsed boy was cutting in line in front of my son, who didn’t like it, so pushed him right back out of line again. The “cutter” took a swing, my boy swung back and in the process (they’re only 9) they both fell. My son reached out to grab the boy’s shirt to catch himself, not knowing that the other boy was also falling and got the pants instead, causing the aforementioned “pantsing.”
The moral of this story is an old saying I heard when I was a kid and have lived by since: “If you rise at dawn, you can sleep ’til noon.” In other words, if you build yourself a reputation for good things, when occasionally you stray, folks will cut you some slack. The converse of this rule is that if build yourself a reputation for bad things, that could well stick with you for a long, long time…