Skip to main content

solving unsolvable problems

In most of the task that i do everyday , there is one word that always pop out : bug . Bug or simply errors in an application usually happens every time. Even the well designed software have their own glitches. This is the reason why we have blue screens , patches , service packs and support sites.

Is there such a thing as an unsolvable bug ? As long as the bug is not attributed to the limitations of the architecture or the infrastructure , in my own opinion all bugs are solvable .

Elevating further , bugs came from problems. When problem occurs in a software, most often time its related to bugs. Are there unsolvable problems? Most problems can be solved if the proper process is done. It may not be coming up with a solution but more often times knowing why the problem occurs and what causes the problem is already a good step .

I was browsing on an article by a security adviser and though he explained it on network related context the idea is pretty generic. It can be used even of software development. It basically boils down on trying to isolate the root cause of the problem. A problem may be too big at first but once analyzed properly it may only be pointing to a few lines of code. Neat isn't it? Its easily said than done though, you have to be wise enough and utilize several utilities and tricks you know to hit the right spot.

Get ideas from the article which can be read through this link.

Happy bug hunting.

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