Skip to main content

career planning thoughts

im turning 29 but it seems like i have just started . this what happens when you take a wrong move on what paths to take . the path that i took was not really that bad , i learned a lot from it and basically these things helped me grow . i guess im on a state of trying to reclaim what i should have had (similar to what firefox is trying to achieve - reclaiming the web hahaha). career is a career , it should be well planned . so perhaps a few tips may help me or even help others jump start career planning .

phase 1 : be clear of your goals

a. know your purpose . its a matter of determining the purpose of your existence . it may not be too late to be asking yourself questions such as : why am i here? or what do i want my life to be like? . you can never be fully satisfied if your career now does not fit to what your purpose in life is.

b. start identifying your passions , skills and interest . i know of some who finished a course they did not like but suceeded . why ? because they were not afraid to follow their passion . instead of staying with their degree , they went on and pursue other career inclined to their interest .

c. identify your driving values . knowing why you need to work or why you need your career can help you in most critical decisions that you may have to make . depending on your priorities , several offers can be declined in favor of another . some of the common drives may be : income , power , influence , recognition , security , intellectual challege , advancement , environment , freedom and fulfillment .

once you are firm on what you want to be , start improving and growing . it is the best way that you can boost your potentials and be one of the sought-after human in your profession.

phase 2 : improve and grow

a. diversify your skill set . this means learning more to be more . your current skills may be giving you the advantage now but it may not last . your career is vulnerable should that technology become obsolete. by expanding your skill set you become more marketable .

b. stay current and be flexible . understand how your skill set or application knowledge can be applied in different industries

c. hone your business and leadership skills with additional education. You may have started in your career by managing network systems, but you now need skills managing people, budgets and teams.

d. be aware of what's next. the IT industry is in constant flux, and standing still could cost you. continually research both the job market and the specialties within your field that are growing. then evaluate your abilities and identify the skills you'll need to remain marketable.

e. refine your project management skills. project management skills, particularly in the IT environment, have grown in importance .

f. don't stagnate. stay on top of new developments. change jobs if need be to create dynamic change and a breath of fresh air.

g. life is too short to stay in a job or career field you don't like. if you're feeling dissatisfied at work, figure out what you'd rather do .


Ryan Garaygay said…
That's one long list...

But I have to agree. I share the same sentiments, somehow good for me I was able to shift career before it's very late. But then again, it's always never too late to go for something you truly love doing.

And if I may add, if you already know what you love doing, then be with people who will be able to help you achieve them. if not technically then at least guide you in getting there. If I didn't stay with my brother for sometime, talked me out with electronics, met Rod who talked me more into software development, I wouldn't be even spending time typing this instead I'd be in a plant someone, waiting for the clock to strike 5pm coz i hate my job.
Marvin said…
I admire those people coming from the engineering background shifting to software development .

Ryan , Niko , Me , Roland , Mam Joy ...and the list goes on.....
Mac said…
its the thought that counts!
Macky said…
Its the thought that counts!
Leo Camalig said…
Yes I agree...

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :


renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!

I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless