i like perfection. i use code to get as close to a perfect understanding of the underlying system as possible. the flip side is that once i understand the underlying system i try to insert my code in the system in as perfect a way as possible. of course i am a rewrite fanatic. code is almost never as good as i want it. usually it improves after a few readings, but it rarely reaches the level that i require. reorganizing and rewriting are two of the most hated words for most engineers and managers. i consider these two skills to be my biggest asset. I have no fear throwing out the old, and writing it a new, and it is always better after i'm done. intense thought goes into every rewrite i do, sometimes days of walking aimlessly trying to figure out how to perform these operations in a "perfect" sort of way. I don't like workarounds, and i don't like patches. if something can be done, then it can be done well.

i have many years of experience working for the same embedded systems company, and i have earned company wide respect for my ability to solve anything. my habit for rewriting is known, and was originally "feared" but not anymore. when i want to rewrite something my company is behind me 100%. if it could be done badly then it can surely be done well.

ps. everything has its exceptions but what's written here is the rule.

nachum kanovsky