November 3rd, 2010, 2:50 am
QuoteOriginally posted by: traderjoe1976I have come across too many of these computer science grads who are very knowledgeable from a technical standpoint, but they insist on writing spaghetti code which is not properly documented. They need to pass a law which forces people to maintain their own code for 2 years after it goes into production. That is the only way to get some discipline in coding.There are many reasons for this-1. Pressure to deliver yesterday.2. Bosses who do not care about code quality or worse still do not understand the value of code quality. These reward the fastest not the most disciplined coder.3. Politics - Even if you care about code quality if (2) above is your situation and you do not have influence in a given place you stand to lose if you insist on spending an extra day or week on refactoring code.Often times you cannot create perfect code the first shot. Refactoring when you reach a quiescent state between project phases is essential. But if you have another team member who does not give a shit having more influence with your boss , good luck with it. Its a political battle not an intellectual one.The problem is that in the recent times two types of bosses exist in the IT world-1. One whose deep expertise does not go beyond SQL.2. Another who thinks becoz he can write procedural code in Java - he is a fucking object oriented genius. The educated CS boss is not very common place in IT. Enough rant for the day. My boss btw is a CS graduate so the above does not represent my situation but it sums up the situation in my last job.
Last edited by
capafan2 on November 2nd, 2010, 11:00 pm, edited 1 time in total.