Reading and digesting classical authors


You just narrated part of my story exactly! But there is a second part of my story that led to my current ‘reflective’ stage in my professional career on software design. That second part includes reading and digesting some other kind of texts by classical authors (Dijkstra, Dahl, Hoare, Knuth, Meyer, Tanenbaum, Myers, Mills, Weinberg, Parnas, Gilb, DeMarco, Abelson and Sussman, etc.). This current stage feels like another career entirely different than the career in my previous part of my story. Nowadays, I talk to others about that in the context of my Reflective Developer Program’.

Comments (1)

  1. cheong00 says:

    This advice might be good for people who don’t work on team. For people that work as team, if the pattern differs a lot than the pattern they’re using, this might introduce conflict and/or confussion. And if the team is already using similar coding pattern, it fits much more by diving in the source control of your company and visit other projects written in similar style, but solving different problem.

    It’s really a problem with “new hire” who try to introducing code with their own style into codebase. Even if that style might be a better one, mixing coding style creates chaos and do more harm than good to overall system stability (the senior folks cannot reaily review their code to identify bugs, allowing simple bug that should have caught sneaks in) and productivity.

Skip to main content