Shit on you, shit on her, shit on me in the end
 
[Most Recent Entries] [Calendar View] [Friends View]

Tuesday, July 1st, 2008

    Time Event
    6:06p
    Разбитое окно
    Читаю "Pragmatic Programmer". На русском она стоит около 100 шек., поэтому рапечатываю и читаю в оригинале. Только начал, но уже очень нравится: ведь я пришёл к таким же самым выводам. Читаю и цыкаю языком. Дано человеческое определение тому, что я называл "бардаком" и "расползанием говна из всех щелей": software enthropy. Именно то, что я с отвращением имел ввиду и из-за чего ушёл из Neomagic. А вот почему так получается:
    In inner cities, some buildings are beautiful and clean, while others are rotting hulks. Why? Researchers in the field of crime and urban decay discovered a fascinating trigger mechanism, one that very quickly turns a clean, intact, inhabited building into a smashed and abandoned derelict.

    A broken window.

    One broken window, left unrepaired for any substantial length of time, instills in the inhabitants of the building a sense of abandonment—a sense that the powers that be don't care about the building. So another window gets broken. People start littering. Graffiti appears. Serious structural damage begins. In a relatively short space of time, the building becomes damaged beyond the owner's desire to fix it, and the sense of abandonment becomes reality.

    One broken window—a badly designed piece of code, a poor management decision that the team must live with for the duration of the project— is all it takes to start the decline. If you find yourself working on a project with quite a few broken windows, it's all too easy to slip into the mindset of "All the rest of this code is crap, I'll just follow suit." It doesn't matter if the project has been fine up to this point. In the original experiment leading to the "Broken Window Theory," an abandoned car sat for a week untouched. But once a single window was broken, the car was stripped and turned upside down within hours.

    Don't leave "broken windows" (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered. If there is insufficient time to fix it properly, then board it up. Perhaps you can comment out the offending code, or display a "Not Implemented" message, or substitute dummy data instead. Take some action to prevent further damage and to show that you're on top of the situation.

    Эти слова надо выжигать калёным железом таким как я, как Йосси, и вообще всем выпускникам.

    << Previous Day 2008/07/01
    [Calendar]
    Next Day >>

About LJ.Rossia.org