Skip to main content

The three stages of a tech career

  • Stage one - You don’t know much
    You are in awe of all the other techs. You make a lot of dumb mistakes. You feel like you are swamped all the time. You have to read a lot before you dare try anything for fear of breaking something. Everybody dumps on you because you are the new kid. Things take longer for you to accomplish. You work a lot of overtime, often without pay. You don’t get paid a lot. You wonder if you’ll ever get a break. You realize that school didn’t quite prepare you for the real world. Work hard. You’ll make it.
  • Stage two - You know a lot of stuff
    You’re good and you know it. So does everyone else around you. They can see that you are good. You don’t have to tell them. Things get done quickly. You even amaze yourself sometimes. You are valuable and can command a good salary. The managers and business owners want to keep you on board. They want you to be happy and offer perks to entice you to stay. You get calls from headhunters all the time. It is very flattering and a nice position to be in. Life is good. Enjoy it while it lasts.
  • Stage three - You don’t know much again
    Technology is passing you by. The young techs seem to know so much more than you. It takes longer to figure things out again. You are probably in a position where you can delegate so you do. You are most likely in a management role and spend more time with people issues than tech issues. You are looked on as wise and experienced. You seek input from other techs before making big decisions. It’s not a big deal that you don’t know all the details anymore. You’ve got the big picture. Let others work out the details.

Ref: Techrepublic.com

Comments

Luke Clifford said…
It's sooo true!

made me laugh.
good blog. :)
May 28, 2008 at 12:29 PM
Post a Comment

Popular posts from this blog

Dhivehi to English translation with Microsoft translator

  The Dhivehi language translation feature included in Microsoft translator and Microsoft 365 lets you press a button and translate written Dhivehi into English. Though there are a few hiccups here and there, the service is great and provides an understanding of the overall document. This is more than what we see from any existing models. I was amazed to see a link in one of my outlook web emails, it says “translate message to: English” which could mean nothing usually, however, when I saw the next sentence which said “Never translate from: Divehi”, I thought why would it says Divehi specifically if it doesn’t understand that the entire email was written in Dhivehi? Out of curiosity, I pressed the button, and to my surprise, it was quite good. The essence of the message was retained very well. For example, something like އިޙްތިރާމް ޤަބޫލުކުރެއްވުން އެދެން could be translated as “ I would like to respect you ”, which is ok in terms of translation, but what it meant was greeti...
Post a Comment
Read more

Google dialogflow - How to train a chatbot to answer questions related to your office and how to make it better than just a Q&A bot?

  First lets look how to do it the basic way. To train a conversational AI chatbot for answering office-related queries using Dialogflow, you will need to follow these steps: Create a new agent in Dialogflow. Collect a dataset of office-related queries and their corresponding answers. This dataset can be obtained through various means, such as scraping websites, conducting surveys, or manually creating a dataset. Create intents in Dialogflow for the queries in your dataset. An intent represents a user's intention, such as asking for office hours or requesting a vacation day. Add training phrases to each intent, which are examples of how a user might ask the question. Provide responses for each intent, which will be the chatbot's answer to the user's query. Test the chatbot using the "Try it now" feature in Dialogflow. Once the chatbot is working well, you can deploy it to a platform of your choice, such as a website or mobile app. However, if you follow the basic ...
Post a Comment
Read more

Is IT no longer about technology?

Author: Jason Hiner Writes... It’s become horribly cliche to talk about the importance of IT-business alignment and the need for IT professionals to become much more business-savvy, but Gartner’s Tom Austin (right) takes it to the next level. He believes that the IT professional of the future will be less of an engineer and more of a social scientist. What? Yes, you heard that right — the word “social” will become a key part of the IT professional’s job description. It flies in the face of most of the stereotypes about techies and it sounds a little corny, but Austin does draw some interesting conclusions that are worth a look, if only because they are so unconventional. Here are some of the most salient quotes from Austin on this subject (from an interview in Fast Company ): “The problem with IT today is there are too many engineers and not enough social scientists.” “Too often, we have measurement and reward systems that are focused on how many transactions did you process, how man...
2 comments
Read more