Author Archives: Tim Golisch

About Tim Golisch

I'm a geek. I do geeky things.

Why communication is hard, and what to do about it

I know IT folks sometimes seem under-socialized and (to varying degrees) awkward. However, they don’t have the market-cornered on communication problems. Gosh, just turn on any TV sitcom and you will probably see a people who are having conflicts because … Continue reading

Posted in IT Psychology, Professionalism, Team | Tagged , , | Leave a comment

Why bother with a plan

I have met plenty of cowboys in my day. I’ve written about this topic several times. One thing that cowboys hate, is writing-up a plan. It makes me think of the times when I MAKE my kids do homework. Their … Continue reading

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

Getting through to someone

Today was like a whole new day for me. I got through to someone. Maybe it doesn’t sound like a big deal to you, but I have teenage kids. So, I don’t exactly feel like “I’m getting through” to people … Continue reading

Posted in IT Psychology, Lessons Learned, Professionalism | Tagged , , | Leave a comment

Switching from dev-process to maint-process

I was going to name this article “Maturity model for maintenance programming”, but every time I read that title, I cringed. Maintenance programming is not much fun. It sounds a bit like “prison guard” or “mortician”, or some other unpleasant … Continue reading

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

How to get people to follow a process

Years ago, I worked on a team who was making an online trivia game. The concept was a very brilliant solution to a common problem. The customer was a huge company who processed credit applications for car purchases. Their financial … Continue reading

Posted in IT Psychology, Professionalism, Team | Tagged , , , , , | Leave a comment

Refactoring code that is too big

“If your code is so big that you need Regions to collapse areas of it, then your code is probably too big and you should consider refactoring it”. I’m sure everyone has encountered a programming task, where someone wrote a … Continue reading

Posted in Lessons Learned, Optimization, Professionalism, Programming | Tagged | Leave a comment

How your processes save your backside

When you have a well-defined process, it can be tedious at times. Sometimes you even want to throw unpleasant terms on it, like “bureaucracy”. Bureaucracy sounds nasty. I’m trying to think of someone who could make it sound palatable. Maybe … Continue reading

Posted in IT Psychology, Lessons Learned, Professionalism, Team | Tagged , , | Leave a comment