Skip to main content

simplifying my blogging habits

I guess its a long haitus from blogging. Eversince blogging became a "fad" , I jumped into the bandwagon and started with some several post . Then the fire suddenly died down and I left this page static for how many months or even a year.

After a hell of a roller coaster ride of life , Im back eager to share everything that I can share. Initially , I thought of this blogsite as a common tech blog where I can post anything techie that I pick along the way. It dawned to me that having a monotonous approach to a site may render it uninteresting. Thus I am reintroducing my blog as a new catch all blog .

Reinventing is not only to make my blog more interesting (?) but it would simplify my supposedly "blogging habit" . I used to keep several accounts . Its me jumping to all these famous blogging account (sadly i dont have any mYSpace). Maintaining it is a pain in the ass . So finally , idecided to cut the crap and keep it simple. Heres the new setup : I have decided to keep this blogsite from blogger . Basically because its famous (hahaha for almost 2 years it only got 942 hits and half of that coming from me loggin in to different PCs) . I like the fact that blogger keeps blogging simple and of course I got my adsense all over the page . I hope to be cashing in money ( dreaming is legal) . I am also keeping my Multiply account . I know most of you would shout back that multiply's site is so damn slow, but hey , I like how some templates organize the contents. I dont care if its slow multiplied by 10 .

There are a lot of things going in my head that i want to write about. So keep posted and please subscribe in my RSS feeds....
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