C#, VB.Net, XML and mass consumption of coffee.

I am a busy guy, full time job, wife who recently decided to learn how to code, kids – hockey practices at 7 am on Saturdays and bed time stories and many other things normally occupy my day. On top of this, I have to stay up to speed on what is going on with technology, work on my side projects (partypm.com is cool, sorry for the shameless plug) and occasionally I do freelance.  However lately I am not that enthusiastic about freelance projects and this comic from the Oatmeal perfectly describes the reason why.

Read more…

Many many years ago when I landed my first coding job, I was amazed at how different working in a software development shop was different from what I had pictured in my mind.  At that time, I did not even graduated yet, I was in need of money and it seemed like a great opportunity so I took the job.  While driving to my new place of employment for the first time, I was running some scenarios in my head, trying to remember some tested and true algorithms, thinking of whole bunch of technical things that might help me impress my then new boss; what came as a complete surprise to me was the fact that I had no idea what the work was about.

After couple of weeks, I began to realize that many things that were part of my job were not covered in school at all.  I can’t really blame school for that, after all they were trying to give me as much information as they could about technical aspects – languages, algorithms and all that jazz, I myself had failed to learn the truth about real time work of a coder, and I did have opportunities to do so.  Later on when I became a manager and was interviewing people for coding positions, I realized that I was not unique in this lack of knowledge.  Most of the recent graduates were in the same boat that I was in years ago. Read more…

One of the things that drove me absolutely nuts when our department was in the same building as the rest of the company was the fact that nobody could quite understand what we were doing. Quite often we would get a data entry person storm into our office and demand that we fix their Outlook or install Unix on their machine (it turned out that he needed Putty, not a true Unix install). Usually these conversation started with “You guys are not doing anything, right?”. So many times I was trying to explain to everyone that it just does not work like this. We are not just sitting here pressing keys at random most of the time. Best and by far most common argument to support their need for our involvement that I heard was something like this: “It is not going to take long, could you just do this for me right now”. One of our duties was writing a variety of Excel macros for people(I should probably post some tutorials on this subject). After all when dealing with massive amounts of data, it is faster to write a macro then do something by hand. We did not mind doing macros at all, what we did not like is when the person was sitting on the project for weeks and then decided to approach us at the last minute. Client expects the project to be completed at 5 PM, so the analyst strolls into our office at 4:45. Never mind that it takes him about 3 hours to explain to us what on earth does he want macro to do. Never mind that it takes me couple of hours to code the macro in some cases(trust me, there were some huge macros). It had to be done and that is it.

Number of times we attempted to find a solution to this annoyances. For instance we created a little internal web site that would, in theory, help users solve many issues like setting their “Away” message on Outlook and server connection through Putty and such. I did this web site in about 3 days when my computer was send away for repair and I was working on an antiquated piece of hardware we found berried in a storage. Was this web site ever used? No, it was not. Office people would still storm into our office saying that they did not read the instructions as they would not understand it anyway.

The worst part of these interruptions was that it would completely break my line of thought. So you are working away on a complex algorithm with close to no documentation on the objects that have to interact together available. You are concentrated on the task 100 percent, not even noticing that that cup of coffee is now cold, and then all of a sudden you have someone storms in and demanding that you fix their radio right away, or else.

The idea that you just had about this nice piece optimized piece you are about to write is gone now. I must admit that couple of times I flipped. It ended up with me yelling at a poor data entry person, calling them names, questioning their intelligence and so on. After I usually worked from home for a day, but at home there was a urgent need for a game of soccer or emergency epic hide-and-seek battle with my kids. I do enjoy those, but working from home was not a big option from the point of getting any work done.

Few years have passed and then our lease was up. I knew that was the moment when inaction would cost me dearly; I begged and pleaded with my boss to get us a separate office. Likely he agreed with me, and for the last two years we are in a different building, about 40 minute drive away from the main office. At first, main office was really concerned with who would be helping them out with daily tasks, but after about a month they learned to do it themselves. That little web site was finally used on the regular basis. We were not bothered with those requests and could finally spent close to a hundred percent of our time on coding and related things. Our productivity sky rocketed, we were producing better code more quickly and everyone was much happier.

The point is – developers can’t be disturbed. It is a process where ideas and thoughts need to be followed and processed carefully to produce what could be considered good code. You must create a barrier between your coders and outside distraction to produce quality software, and after all it is the purpose of any development team.

As much as I don’t like freelanceswitch.com or other similar sites aimed at converting everyone and their uncle to the holy new way of life – freelance work, there was an excellent article by Leo Babauta of zenhabits.com on simple project management today. I am not going to go into detail on why I think freelanceswitch.com is not on top of my “favorite sites” list, maybe some other day, but the article itself was simply excellent. If you are not familiar with who Leo is, read zenhabits.com, it’s good for you.

Usually when you read about project management, and you should – it is important, it always starts with “Get the software X and do this, this and that, and you shall be managing your projects just like the pros do”. As seen on TV approach that might get you excited, but at the core of it there is a simple sales pitch to move as many units of “software X” as possible. Leo takes completely different approach, no mentions of any software package that would be a silver bullet for your particular situations, just the basic ideas that often gets overlooked when thinking about managing that runaway train that is your project.

Leo’s idea is simple:

• Define outcome

• Setup process

• Focus on the next action

• Send it to the client

• Communicate

• Focus on the next action

• Repeat until done.

And I would like to go as far as to say that it is not really his idea, it is a universally accepted idea on how to manage most of the projects. What really intrigued me was the fact that there was no fluff in the article, good clear explanation that brings you down to the core concept and let’s you decide how to do this in your particular situation.

I would really recommend Leo and his blog for everyone who is serious about his development not only as a IT pro, but as a human being.

Bad code we all do it.

Well, I had written my share of bad code. Couple of weeks ago I had to fix up a class that was written about 4 years ago. For a while I could not believe I wrote this, but the comments on top clearly identified me as a suspect. The thing is we all write bad code sometimes. If you never wrote any bad code, please raise the hand with which you did not do it.

So, going back to the story – I was looking at it and my first impulse was to try to hide it far away so nobody would ever have to look at it. My second impulse was to rewrite it. I figured, it would probably take me about 5 hours to redo this. I did not do any of it. Instead I brewed a fresh pot of coffee, put my pride far away, printed out copies of it for all developers in the office and decided to play a game. Read more…

Couple of days ago I wrote this. I was trying to look at my career and see what do I really want to do with my life. I know, the thing with management might look like a good idea, but after all, I am a coder. It is not going to be easy, but I will get myself back in coding somehow, I guess by delegating some of the less important paperwork and such. But it looks like this means lots more sleepless nights to get myself back into action.

I have been told many many times that changes are supposed to be good for you (or me, since it’s my situation that we are looking into). I have been a coder for quite some time now. I can’t say that I am absolutely ecstatic about programming. It does not influence my life outside of my office hours and time that I spent at home trying desperately to improve myself. For instance, I don’t watch Star Trek or build some kind of crazy contraptions which could loosely be called a robot in my basement, although come to think of it, that sounds like a good idea; the robot one, not the Star Trek. I don’t wear nerdy t-shirts with BSOD on it. I am not participating in heated discussions like “My IDE is bigger then yours!” and “My OS can kick your OS’s butt” and so on. I can’t say that coding is my passion, it is something I am interested in and it pays my bills. Another factor would be my formal training – I have some in development, but as for the other areas I can’t say that I am properly trained. Lately something had changed in my work – I am doing more managerial things then coding. Read more…

There is something special about the lists. Lists are easy, visually appealing and short, which makes them absolutely favorite format to write blog posts in. When you are reading a popular blog of some sort, you would notice that most of the posts are actually lists. The headlines basically write themselves – X (usually a nice number like 10) things that blah. Users love those because they are basically a Reader’s Digest version of whatever the writer was trying to say, and lets face it, even if you would never admit to reading Reader’s Digest to anyone, fist thing you’d grab in a waiting room of your dentists office would be this regurgitated portion of news, events and literature to help you pass time. Hey, I am the same way, at times I would have Sports Illustrated to hide Readers Digest, just to maintain my manly image.

So the lists, summaries and so on dominate blogosphere, so what? What really gets me is that obligatory post that every blogger must write X things your “insert your profession” guy/girl/person wants you to know/do/act. Worst of all are developers/coders/admins and all other IT people write. I know your job is tough, you are dealing with issues that other people can’t or won’t understand, but for the love of all that’s holly, get off your high horse and face reality. You and I are rarely people who are center of the universe. We are liabilities, not assets. We can be compared by the crew that runs lunch rooms – we are there to serve people – be it clients that purchase your software, annoying guy from AP or a secretary who can’t manage simple task of writing a document to a flash drive. Our clients are people who make money, they do pay our bills. I am coding a software that automates report generation – well guess what – people who use my software make money for their companies. If you are coding an accounting software – accountants are making money. We, on the other hand cost money. We want the best hardware and software available. We want newest and best gadgets out there, we want free coffee and shorter working hours. I know, I get it, I am the same way. But what gets me is posts like this one.

I mean come on, just treat people with respect. Get back to them quickly, speak their language, don’t act all high and mighty in front of the users, and what’s more important to me personally – users pay your bills – listen to them. Don’t tell them what they need, listen to what they are asking you for and make it better. That’s how you run an efficient IT department and maybe even make a friend or two who is not an IT person.

Would like to hear your opinion on this.

This video has has nothitng to do with programming but you should still watch it. It seems like everyone and their uncle are dreaming about getting a start-up going and then quickly getting bought by one of the giants out there. How about developing a good quality product, get users and work on perfecting your project?

I am really impressed and inspired, I know the video has been out there for a while, I still like the philosophy behind it.
Read more…

For last six month my guys and I have been under extreme pressure.  You see, in the ideal world, sales have no control over development, but this is a real world so sales objective is driving us completely mad.  There is a potential client, a very demanding potential client who blackmails us with stuff like “If you not going to build feature x by date y I am not signing”.  Unfortunately this is the biggest contract for us, so sales will do everything in their power to get them.  It’s not that I mind sales guys doing their jobs, but if this client is demanding right now and they have not paid yet, I can only imagine what will be unleashed upon us once they will become our paying customer.

Granted the product is very expensive (more expensive then VS 2008 and Adobe CS3 suite combined) and this sometimes can inspire our clients to demand stuff.  We’ve been through this before.  A company that shell remain nameless was bossing us around for six month.  We only worked on their features, nobody else wanted these things and at the end of six month they said, “You know, this is what we said we need, but not what we actually need”.  I can still remember that conversation.  Incidentally this is the time when my first “Punch Box” appeared at the office; since then we went though a number of  “Punch Boxes” and that was the end of that.

Three times in the last 4 years we went through similar situations, and we have yet secure a contract when too much custom stuff is put in and we basically keep on asking “How high”.  This is the fourth time.

We have to release a newest version on Tuesday, Sept 30, so everyone is up to their necks in testing and bug fixing when all of a sudden “dll hell” makes appearance.  Everyone who coded for Windows knows what I am talking about – one guy decides to mess around with perfectly good reference and all hell breaks loose.  Today its Microsoft.Office.Core.  Nobody can compile, nothing runs, and we can’t roll back.  Unfortunately we have to rely on external references such as Office.Core, because the app produces Excel and PowerPoint documents, we reference other things too, but it seems to me that whenever we are running into DLL Hell it always have something to do with a dll from Microsoft.  This is going to be a long weekend, just me, five guys, IDE and references.