Lately, I have been thinking...
I've been spending a lot of my time (and life) maintaining the technology knowledge that I have and learning up new technologies that maybe useful to my work (or career). I have also been spending a lot of my time and money on certifications.
My weeknights and weekends are dedicated to reading up on what's new and cool, experimenting with betas, writing my pet-project Paladin and contributing to the online community through forums. I spend majority of my time sitting in front of the computer.
It's not to say that I don't enjoy what I do, but I feel that if only the knowledge that I acquire is non-volatile, I could do more (or even wonders). Learning IT is like pouring water into a leaking barrel. Whatever knowledge we acquire becomes obsolete faster than we can say 'obsolete'. Hence, we can never fill our knowledge barrel and move on to the next.
Of course when we first started to learn about IT, it sounds so exciting - apps, databases, architectures. And we all have a dream of "I wanna do that someday". But after nearing a decade in the industry, everything appears to be more or less the same to me. Those COM, VB6 and ASP knowledge that I have acquired are as good as exhibits in the museum.
What more in today's market, solutions are driven by customers. Hence, we got learn (and maintain) stuff like our knowledge in Java and .NET, various database products, various platforms and etc. And they all go obsolete together.
So, I'm thinking. If I spend the same amount of time I used for technology now onto non-volatile knowledge i.e. cookie-making, selling, business, finance, medicine or even history, I could have many knowledge barrels that don't leak (or leak slower). That could make me a more knowledgeable person or even give me a better life. *Man! Those salespeople can go home and bake cakes while I return to my miserable room to read MSDN*
But after saying all that, I'm still in the midst of recalibrating my mentality. Right now, I'm still thinking of getting that MCSA 2003, looking at SQL Server 2005 and even tempted to take OCA/OCP. I guess old habits die hard.
8 comments:
I would compare IT to the Red Queen Principle (inspired by Lewis Carolls' "Through The Looking Glass"); "in this place it takes all the running you can do, to keep in the same place."
But Microsoft's products are designed to do that. It's how they make money from certifications. Revamp everything every few years, and you have to certify yourself again. Some of it can be considered "progress" but most of it is change for change's sake (they need to sell upgrades somehow right?). That's when I decided Microsoftland was too difficult for me. OSS is certainly more developer-friendly.
It not that bad right ?? I mean when u go home u still can go bake cake if u wan... and not reading MSDN ,..em..
Obi,
In my opinion, it is a problem with the nature of the industry and is not vendor, brand or software distribution model specific. All software will become obsolete someday regardless of platform.
I will see this from the perspective of life - being happy, being with family members and being to learn more about the world. Rather than just 'what technology is good for me'.
*HuGs*
Amy,
We are all given a precious item and that is Time. It is for us to decide where we should invest our time. If we invest on sustainable knowledge, it could makes us wiser. Otherwise, we are just a person with the same skills but with an incremented version number everytime.
I guessed when we are young in the industry, we can maintain what we learn because the scope is still very small. However, as the scope grow larger over the years, we will find it more challenging to keep up.
The moment I stop focusing on technology, I may become outdated and less competitive. Therefore, it is essential to read MSDN. :'( So, I end up filling a leaking barrel.
I think one of the main issues is that people dont tend to make distinctions between knowledge and technology anymore.
While technology on how things are done might become obsolete, the knowledge on how things are done or should be done do not.
Unfortunately a lot of people tend to get so worked up over the minute details its gets so overwhelming.
Point being : make sure to keep an eye on the bigger picture. If you dont, the carpet will be swept from under your feet.
Cheers.
Azizi,
I guessed we should look at Software Development, Software Architecturing and Project Management instead of sticking our head-in-the-sand with C# programming, Java programming and whatchamacallit programming.
However, we do need some in-depth knowledge on the technology that we are trying to propose. For instance, it is not possible for us to provide .NET solutions if we are not familiar with .NET - it's purpose, strengths and limitations.
The time for maintaining such knowledge is usually a waste of effort when they become obsolete. Just look at DCOM and .NET Remoting. We can't apply the estimates for implementing DCOM on .NET Remoting.
Sigh!
Hi sifu Serena,
Well, it's IT world. Everyone stay competitive and hope to maintain in the path without being outdated and being thrown outta the path. It same goes to the vendors, they always come out with new technology for the sake of end-users (But not for developers, unfortunately). You are building your hard skills (programming ,architecturing, databases and technologies etc) because you want to stay on the top, which is GOOD. But as you said, these would become obsolete in no time. In fact, every 3 months there will certainly be an update in new products; hardwares or softwares.
The non-volatile you mentioned were soft skills. Cookie-making, sales, presentation, the way you socialise/talk to another person and etc will definitely not (or slower) obsolete, but the contents of course will change from time to time. You will need different recipe to make better cookie, you will need better IT knowledge to give better presentation/consultation.
It's all depends on what and how you want to spend your 24hours of the day. Everyone has the equal hours / day. Decides what makes you happier and strive for it. You would be sad over the times that you had invested to build your knowledge, while others are looking at you and envy your smartness :)
Be balance in life and practise give and take, but there definitely no easy way out in IT world.
*Live a day happier = a day unhappy in your life ;)
Cheers~
I think it might be technology that is giving you those migraines Serena :P
Ok, on a more serious note, I agree with the previous person.
There are things which will remain constant over a longer period of time, and there are other things which change quicker than the time required to snap your fingers.
The important thing is having prior knowledge. Once you have prior knowledge in that area, it is easier to apply it to the new area.
I think this is true in many other professions as well.
Take a doctor for instance, they graduate, they attend conferences, and they practice their medical skills.
They attend conferences, read medical journals and so on in hope to sharpen their knowledge of new things/techniques that are new. Published/practiced by their peers.
What about an accountant?
Ok, so they need to keep up to date with their accounting practices. When the government decides to make changes for how they will be taxing things, the accountants will need to read up on those changes and apply them. (Governments like introducing new taxes...)
But hey, they still have the basis of their knowledge to apply to the new challenge, right?
True, IT is still young, and ever evolving, until it matures, then it will be forever changing. But once you've programmed before, you can apply that knowledge to something new.
I don't mean that 2 years of Java only experience will allow you to easily convert those skills to Delphi.
But, it sure as heck makes it much easier than never having prior programming experience at all and trying out Delphi as your first entry into the programming world.
If there were only two people left in the world, who (if the below) would you rather have bake your birthday cake?
1) Someone who has read about baking cakes, but has never cooked, and has never baked a cake before?
Or...
2) Someone who has cooked before, but has never baked a cake before?
Post a Comment