Tag: career

Today’s editorial was originally released on Dec 3, 2007. It is being republished as Steve is at SQL in the City in Seattletoday.

Or will you be working your 35, 30, or even 20?

I saw this article about a report from Gartner that by 2015 many of us will work less than 40 hours. As someone that’s had some success in IT over many years, I could actually see this happening.

Not I, you say. They can’t mean IT workers. Perhaps those secretaries, accontants, marketing folks, and others will negotiate less work per week, but not with those in IT. We work long hours to meet deadlines and have large workloads, on-call and after-hours work, and more.

IT has been one of those areas that has really slipped between the cracks with regard to employment laws and customs in my opinion. We’ve almost been treated like blue-collar workers but paid and expected to work like white collar workers. Add to the fact that most of the time the average person can’t understand what we really do or see the results of our work until it’s finished, and IT workers haven’t really been easy to classify.

But in my opinion we have one huge advantage over many other types of workers: we can work anywhere.

I’m not sure we’ll get better staffing at companies or even lower workloads. But I can see our “core hours”, those times where we have to be in an office, or available for phone calls, shrinking below the 40 hour mark. Especially as telecommuting grows, I’m sure we’ll have less and less structured time in the office.

Initially I would guess that many of us will make up shortfalls with work from home, after hours, on-call, and other methods. I know I typically work 40-50 hours, but it’s 7 days a week, and spread out in 2-3 hour segments throughout those 7 days. I’m as likely to be working Saturday morning as Tuesday afternoon, or even late Sunday night.

I do think that the 20 hour job that is described in the article is interesting, and if someone can figure out how to balance the work and communication in a company, it would be a great idea. How many parents that don’t work would love to apply for a “20 hour, full-time job”, while their kids are at school? In Colorado, we have a number of “year round schools” where the kids go to school for 9 weeks and are off for 3, in four quarters. A few employers have taken advantage of this by balancing 4 workers for 3 slots, knowing that one of them is always off from work, taking care of their children during a break.

I can certainly see that this would be a boon for DBAs. I’ve seen plenty of DBA production jobs that could be handled most of the time in a 20 hour week. Short term consulting could help those crisis situations and if they pay was in the 50-60% of the current range, it would be interesting to me.

I just wonder how many of you would be looking for 2 20-hour jobs. I know I would.

Steve Jones

---

The Voice of the DBA

The podcast feeds are now available atsqlservercentral.podshow.com to get better bandwidth and maybe a little more exposure :). Comments are definitely appreciated and wanted. You can get feeds from there.

• Video Podcast – 40MB, Quicktime
• Video Podcast – 14.6MB WMV
• Audio Podcast – 5.3MB, MP3

Today’s podcast features music by the beautiful, jazzy, Robin Stine. Check her music out at www.robinstine.com.

I really appreciate and value feedback on the podcasts. Let us know what you like, don’t like, or even send in ideas for the show. If you’d like to comment, post something here. The boss will be sure to read it.

This editorial was originally released on Nov 30, 2007. It is being republished as Steve is traveling to the PASS Summit.

Microsoft got in on a deal to Nigeria that Mandriva Linux negotiated with the government there. The story almost sounds like a bad email: the provider of a “free” product complaining that another company gave their product away for free? So does that mean that in a free market where the cost is the same ($0), that Windows is superior?

There’s some other editorial on that topic, but in this case, what was interesting is that the CEO of Mandriva fired off an open letter to Microsoft, which you can read here. The tone of the letter was a little whiny, and it didn’t seem as though Mr. Bancilhon really thought through what he was writing.

It’s Friday, and with the holidays approaching, I thought this would make a good poll.

Do you pause before sending emails?

In the old days, back when I was younger, if you wanted to fire off a letter, you had to write it and then mail it, usually ensuring some type of delay. Often you had at least one night to think about what you’d written before you dropped it in a mailbox.

There are plenty of people that still recommend that you delay sending an emotional email for at least a day. I know quite a few people that rethink their position before sending, often saving the email to a drafts folder for ten minutes, an hour, some delay to give themselves a break between writing and proofing.

I’m actually pretty bad. As I’m sure many of you have noticed, typos slip through the editorials from time to time, often because I’m in a rush. My self-proofing skills aren’t the greatest, and I tend to make mistakes more often than I’d like.

However I’ve also learned that delays can be good things. I’ve often incorporated a delay in restoring a secondary log-shipped database to give me the chance to recover from an accidental deletion of data. Delaying the send of a potentially inflammatory email allows me the time to cool down and can prevent me from making a big mistake.

Email is quick and a great tool, but it shouldn’t be abused. Take the time to be sure that the message you’re sending is the one that you want received.

Steve Jones

---

The Voice of the DBA Podcasts

The podcast feeds are now available at sqlservercentral.podshow.com to get better bandwidth and maybe a little more exposure :). Comments are definitely appreciated and wanted, and you can get feeds from there.

The RSS Feed: or now on iTunes!

• Video Podcast – 26.6MB Quicktime
• Video Podcast – 12.8MB WMV
• Audio Podcast – 5.6MB MP3

Today’s podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

I really appreciate and value feedback on the podcasts. Let us know what you like, don’t like, or even send in ideas for the show. If you’d like to comment, post something here. The boss will be sure to read it.

This editorial was originally published on Nov 26, 2007. It is being republished as Steve is at DevConnections.

These days it seems that the demand for IT workers is still growing, but there is no shortage of companies still looking to lay people off or get rid of employees that aren’t performing up to some standard.

I saw an interesting article on how to better ensure IT job security and wanted to comment on a few of the items listed from the DBA perspective. I think that different groups of IT workers have different tendencies, but DBAs often are in a very strange position in a company and they need to ensure that their contributions are recognized as well as their work is valued and understood.

I remember in the dot-com boom days when “quirky” IT workers were tolerated and even valued. The strange people wearing flip flops and t-shirts could perform wonders with computers and their eccentricities were tolerated. Often when they were just competent at their jobs and no one really understood just how much or little they actually could do with systems.

The world has changed and expectations for most of our systems are higher than they were a decade ago. Management is more realistic in their view of their business, with most of our employers not expecting to get bought out by some large corporation and retire. Our job is to provide stability and long terms strategic value to our companies.

As a DBA, you have a varied job. You’re in charge of data, need to technically manage the systems, but also work with business users to ensure their data is properly qualified, the meta data is understood (even if not explicitly written down) and you can help them ensure data quality and recognize the importance of the information that is being stored in databases.

This means that you need to better fit into the business as well as providing value. You should respect the dress codes and other habits of the rest of the company. You also need to learn to communicate effectively with others. Don’t talk down to someone with technical acronyms and descriptions and make sure that you are trying to solve the business problems, not fit the solution into come cool piece of technology.

By trying to better fit in, you become an asset to the business as a whole. People should feel comfortable asking for your help and appreciate the work you do.

And they’re likely to keep you around for the long term.

Steve Jones

---

The Voice of the DBA Podcasts

The podcast feeds are now available at sqlservercentral.podshow.comto get better bandwidth and maybe a little more exposure :). Comments are definitely appreciated and wanted, and you can get feeds from there.

• MOV Video – 9.4MB Quicktime
• WMV Video – 10.0MB WMV
• MP3 Audio – 5.5MB MP3

Today’s podcast features music by Joe Sibol. If you like it, check out his stuff on iTunes or at www.joesibol.com.

I really appreciate and value feedback on the podcasts. Let us know what you like, don’t like, or even send in ideas for the show. If you’d like to comment, post something here. The boss will be sure to read it.