Skip to main content

certification pressure eh?

As you may have guessed , I work in a software development company that is a Microsoft Certified Gold Partner. I have been into this kind of work since 2004 but because of the accessibility of opportunity to take certification exams and aside from the fact that my previous salary may not allow me to take the risk of paying much for an exam, i was not able to take any. It is however one of the goals that i want to achieve and now that im closer to it im excited but not pushing it . Just this morning our senior system architect asked if i am already an MCP ( Microsoft Certified Professional ) which i honestly denied. It turns out that our boss in the US have been asking if me and one of the senior engineers in the team has passed an MS certification exam. Jokingly he said that if we dont get one by the end of the year we could start putting a tattoo of a chicken in our body. Its a joke but its half meant and im in the process of considering taking the exam but definitely not this year. So i guess ill have a hands full for reviewing but ill still be blogging anyway......
Labels:

Comments

Anonymous said…
rex.lallata in da haus! f u need ebooks and tutorials, dami ako nyan pare ko. just tell me. pareho lang naman tau ng certification track. mahirap lang ung unang exam mcts 70-536 kasi all encompassing, all d rest manageable naman.
12:05 AM
Post a Comment

Popular posts from this blog

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

Image Credit: https://www.pioneerrx.com 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 ...
Post a Comment
Read more

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 : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

The Story Behind the Name C#

I remember one time in an exam for employment , the first question was - who is the father of C#? I have been working with the language but never did I ask myself who actually started the language ( of course Mirosoft was the brainchild , right? ) . After a googling expedition I found out who was the culprit - Microsofts Anders Hejlsberg . I was not interested why it was called C# then , but opening my VS2008 today , I stumbled on one of the articles being shown at the VS2008 opening page - "Computer World: The A-Z of Programming : C#". Its an interview with Anders discussing the history and beyond of C# . Heres the cool part , the name for C# prior to its release was actually COOL (C like Object Oriented Language) . Below are some lines taken from the interview: Why was the language originally named Cool, and what promoted the change to C#? The code name was Cool, which stood for ‘C like Object Oriented Language’. We kind of liked that name: all of our files were called .coo...
Post a Comment
Read more