Author Archives: Tim Golisch

About Tim Golisch

I'm a geek. I do geeky things.

Technical debt and interest

In case you are not familiar with the term “technical debt”, it mostly means “messy programming”.  Unfortunately, it is more serious than just ordinary messiness.  It usually happens because a programmer was in a hurry and couldn’t think of a … Continue reading

Posted in IT Psychology, Methodology | Tagged | Leave a comment

Technical Bankruptcy

*** Disclaimer: This is not about my current project, it is about every project everywhere *** Technical-debt is a natural byproduct of software development.  If you don’t recall seeing technical debt in every sw-dev project, it is because most developers prefer to … Continue reading

Posted in Lessons Learned, Review | Tagged , , , | Leave a comment

Current Mission Statement

When I read the book “7 habits of highly-effective people”, I remember my reaction to the suggestion about having a “personal mission statement”.  It struck me as being a little silly.  Am I really going to do that with all … Continue reading

Posted in Professionalism | Tagged , , | Leave a comment

Just like free money, for SQL server

I just discovered something today which got me very excited, like finding a $20 bill, laying on the ground.  It must be my lucky day! Each time a new (or upgraded) development tool or server product comes out, I like … Continue reading

Posted in Optimization | Tagged , , | Leave a comment

Architectural review phrase book

When a project is in its early stages, (or sometimes, much later), it is time to have your system designs and software/system architecture reviewed. When this happens, it is not unusual to have a difference of opinion with your reviewer(s).  In … Continue reading

Posted in Lessons Learned, Professionalism, Review | Tagged | Leave a comment

Scaling a project

I recently read an article from a local “expert” about scalability of a dev team. The author claimed that every project can only be completed by a team of 7-10 people. The size of the project didn’t matter to the … Continue reading

Posted in Lessons Learned, Methodology, Optimization, Team | Tagged , , | Leave a comment

Grave naming

I just heard a new one today.  On the topic of “software development and coding standards” have you ever heard of “Grave Naming”? I guess it refers to the practice of standardizing specific domain (value) names across development layers.  (…from … Continue reading

Posted in Methodology, Programming | Tagged , , , , | Leave a comment