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......

Comments 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.

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 …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …