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

Comments

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

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...
1 comment
Read more