Thursday, March 27, 2008

Application-delivery architects are key hires

"A need for higher-level architectural management is required across the board, with special emphasis on the communications between server and browser. This includes coding of objects as cacheable versus dynamic, the use of the local browser cache and compression or request pipelining for example," Joe Skorupa, research vice president at Gartner. (...) Proposing the adoption of the "lifeboat method" of application development, where a team must work in unison to ensure success, Gartner said it sees the application-delivery architect taking on the role of "lifeboat captain". (link)

In the present day, working in unison across boundaries is a prerequisite. Anything less is doomed to get shipwrecked sooner or later.

Labels: ,

Wednesday, March 26, 2008

It's Always Your Fault

Jeff Atwood has a great article, called: The First Rule of Programming: It's Always Your Fault.

An excerpt: "You know the feeling. It's happened to all of us at some point: you've pored over the code a dozen times and still can't find a problem with it. But there's some bug or error you can't seem to get rid of. There just has to be something wrong with the machine you're coding on, with the operating system you're running under, with the tools and libraries you're using. There just has to be!"

It is far more likely that something you built is causing the error than, say, the OS, hardware or Network: "of total errors reported, roughly 95% are caused by programmers"

I can't count the number of times I had to deal with resistance to take ownership or cooperate. No, it wasn't the codebase, there has to be something wrong with the system or the network. Even when faced with cold, hard data to prove otherwise. Or, the other way around: no, our network and systems are sized just fine, the application is causing all the issues! They are at fault, not us.

The way I usually deal with these kind of issues is to get everybody together in one room and break down the boundary. This is an issue we have to solve together. After all, what are we really talking about here? This is not about who's at fault here, this is not about personal abilities. This is about a technical issue. Heck, it might even be because of some weird interaction between the network configuration and the code for all we know. Who knows? Hmm... couldn't that be the case?

Once the defenses are down, people are focusing on the issue and willing to work together to solve it, we can really get down to business. And call for pizza of course!

Labels: , , ,

Tuesday, March 04, 2008

Being a Gentleman in Business

handshake Differences should always be solved with the best interest of the client in mind. This will ensure a good  relationship with your client from which both of you will benefit. It is often that I see people or companies struggling and fighting however. Fighting to keep the client which they tend to see as solely theirs, obstinately refraining their employees from transferring to the client and putting their feet in the sand in spite of sound judgement which should be telling them otherwise.

And you know what?
It is okay to defend your hard earned rights and that which you have worked hard for to let grow and flourish. It is okay to not let other people willfully take advantage of that what you have created. It is okay to keep people to their end of the bargain, promise or obligation! But... does this include hanging on to agreements which will end up hurting everybody, including yourself? Blindly clinging on to that -what you perceive to be- opportunity which you alone have seized and is by birthright now solely you and yours alone? The client you're squeezing every penny out of because it is your belief that he or she is yours alone for the taking? The employee who you helped to blossom and now whishes to go over to The Dark Side, leaving you alone in the cold?

Well, wake up and smell the coffee!

The client who needed your guidance has grown up and is ready for their next step. They don't need you anymore. And your employee, once a fledgling and now a fully grown soaring eagle, has found a better working environment: the client he or she currently works for. So what do you do?

  1. We're in it together. You recognize the fact that everything changes over time. You sit down with the client and try to find a solution from which you both will benefit the most. You nullify the contract with the client and even help them get everything adjusted. And after talking with your employee you find out that they really like working there and that he/she will get paid more. You suggest a settlement with the client.
  2. Me! You cry:"foul play!!" and think to yourself: this is rightfully mine! So you heed the client to the contract and threaten with legal prosecution if they don't execute their part of the contract. Sure, there is always a way out, but it will cost them. Dearly. After all, this is your money they are talking about! Apply same scenario for your employee.

Now, what will you choose?

Sadly, I've seen it more often than not that #2 is chosen. This is so bad. For a number of reasons. A sample:

Luckily I've also witnessed some very applaudable behavior from several people and companies. And if you ask around, those companies and people will end up with a more stable base of loyal customers and employees. True, this approach can cost you some in the short run. But it will pay off in the long run. And you'll also sleep better at night.

Addendum: Wharton University's Business Journal has a good read on the subject: "In the Game of Business, Playing Fair Can Actually Lead to Greater Profits", where the paragraph title 'Fairness over Profit Maximization' sums it up rather nicely.

Labels: , ,

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]