Skip to main content

trying to be street smart v2.0

i know i have posted something like this before . well i had another route to discuss and this time i learned it the hard way ( jack ass me) . this morning i accompanied my parents together with some relatives to the domestic airport. i didnt have problem going to the airport because we took the cab , going back was the tricky for me . its my first time so pardon my stupidity.

so to get back i need to either be in cubao or in recto , so i took jeepney ride going to baclaran. then i walked passed the LRT baclaran station to ride a jeepney going to recto. the traffic was so horrific and i have to take all those pollutions that the city has to offer. the sad part , i missed recto (hahaha). i went as far as monumento and not noticing it . so i had to go down and this time took the LRT to recto (doroteo jose station). well thats me playing street smart again.

heres the route for Domestic Airport to Recto
1. take a jeepney ride to baclaran , then ride a jeepney to recto ( dont miss !)
2. take a jeepney ride to baclaran , use the LRT to go to Doroteo Jose (Recto)
the fare is almost the same....

heres the route Domestic Airport to Cubao
1. take a jeepney ride to baclaran , then ride a bus going to cubao.

till my next stupidity .....

Comments

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 :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

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, …