any good books on code review?
-
I am assigned to new role now: review peers' code. do you have any good books or documents to recommend on this topic?
diligent hands rule....
-
I am assigned to new role now: review peers' code. do you have any good books or documents to recommend on this topic?
diligent hands rule....
How to Win Friends and Influence People - Dale Carnegie
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
How to Win Friends and Influence People - Dale Carnegie
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
thanks for this great book! I bought it right away as my thanksgiving gift for myself...
diligent hands rule....
-
I am assigned to new role now: review peers' code. do you have any good books or documents to recommend on this topic?
diligent hands rule....
-
I am assigned to new role now: review peers' code. do you have any good books or documents to recommend on this topic?
diligent hands rule....
Once upon a time there were a bunch of coders that were given some incomplete requirements. They sat is a dark room with an illuminated white board and tried to figure out what the requirements were supposed to be. Then they sat in a dimly lit pub and worked out the architecture on beer-stained napkins. Then they sat in front of glowing monitors and LED illuminated keyboards and pounded out the code. One day, a shining knight was added to the project to review their code. He discovered that his "peers" had decided to use to twelve incompatible frameworks, eleven coding styles, ten unit test frameworks, nine different databases, eight different REST API styles, seven different TypeScript versions, six back-end languages, five UX tools, four different CI packages, three bug trackers, two ticket managers, and one partridge in a pear tree that nobody knew was part of the requirements. The knight, now with dulled and dented armor, went to management and recommended the whole thing be rewritten. Management went to marketing with the bad news that the product would be delayed for another year. Marketing went to the CFO with the bad news that the product would be $1,000,000 overbudget and cost the customer 10 times what they had planned for the street price. The CFO went to the CEO and suggested an illegal inside trader move before the stock price sunk. The CEO told marketing to ship the product and advertise the bugs as features the customer must have. The CEO told the CFO to freeze all hiring and fire half the developers. The CEO told the managers to outsource the remaining work. The managers told the programmers they would be in maintenance mode only. One dark and stormy night, the remaining programmers took the peer review knight out to a lonely field where the crows crowed "nevermore" and declared the knight to be a heretic of the all the dogmatic religions in the programming world, the Vue-ites, the React-ians, the Angular-ons. The knight was burned on the stake with much functional language incantations. It was all done with svelt discretion. The competition lived happily ever after. THE END
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain -
I am assigned to new role now: review peers' code. do you have any good books or documents to recommend on this topic?
diligent hands rule....
Southmountain wrote:
I am assigned to new role now: review peers' code.
Your organization has a special role for that? :) At my company, every dev is required to take Andrejs Doronins' course Code Review: Best Practices[^]. It's brief, to the point and IMHO very effective. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Once upon a time there were a bunch of coders that were given some incomplete requirements. They sat is a dark room with an illuminated white board and tried to figure out what the requirements were supposed to be. Then they sat in a dimly lit pub and worked out the architecture on beer-stained napkins. Then they sat in front of glowing monitors and LED illuminated keyboards and pounded out the code. One day, a shining knight was added to the project to review their code. He discovered that his "peers" had decided to use to twelve incompatible frameworks, eleven coding styles, ten unit test frameworks, nine different databases, eight different REST API styles, seven different TypeScript versions, six back-end languages, five UX tools, four different CI packages, three bug trackers, two ticket managers, and one partridge in a pear tree that nobody knew was part of the requirements. The knight, now with dulled and dented armor, went to management and recommended the whole thing be rewritten. Management went to marketing with the bad news that the product would be delayed for another year. Marketing went to the CFO with the bad news that the product would be $1,000,000 overbudget and cost the customer 10 times what they had planned for the street price. The CFO went to the CEO and suggested an illegal inside trader move before the stock price sunk. The CEO told marketing to ship the product and advertise the bugs as features the customer must have. The CEO told the CFO to freeze all hiring and fire half the developers. The CEO told the managers to outsource the remaining work. The managers told the programmers they would be in maintenance mode only. One dark and stormy night, the remaining programmers took the peer review knight out to a lonely field where the crows crowed "nevermore" and declared the knight to be a heretic of the all the dogmatic religions in the programming world, the Vue-ites, the React-ians, the Angular-ons. The knight was burned on the stake with much functional language incantations. It was all done with svelt discretion. The competition lived happily ever after. THE END
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainThat's the best code review story I've heard :). All my code review stories are drab tales of rolled eyes and ignored comments.
Mircea
-
Once upon a time there were a bunch of coders that were given some incomplete requirements. They sat is a dark room with an illuminated white board and tried to figure out what the requirements were supposed to be. Then they sat in a dimly lit pub and worked out the architecture on beer-stained napkins. Then they sat in front of glowing monitors and LED illuminated keyboards and pounded out the code. One day, a shining knight was added to the project to review their code. He discovered that his "peers" had decided to use to twelve incompatible frameworks, eleven coding styles, ten unit test frameworks, nine different databases, eight different REST API styles, seven different TypeScript versions, six back-end languages, five UX tools, four different CI packages, three bug trackers, two ticket managers, and one partridge in a pear tree that nobody knew was part of the requirements. The knight, now with dulled and dented armor, went to management and recommended the whole thing be rewritten. Management went to marketing with the bad news that the product would be delayed for another year. Marketing went to the CFO with the bad news that the product would be $1,000,000 overbudget and cost the customer 10 times what they had planned for the street price. The CFO went to the CEO and suggested an illegal inside trader move before the stock price sunk. The CEO told marketing to ship the product and advertise the bugs as features the customer must have. The CEO told the CFO to freeze all hiring and fire half the developers. The CEO told the managers to outsource the remaining work. The managers told the programmers they would be in maintenance mode only. One dark and stormy night, the remaining programmers took the peer review knight out to a lonely field where the crows crowed "nevermore" and declared the knight to be a heretic of the all the dogmatic religions in the programming world, the Vue-ites, the React-ians, the Angular-ons. The knight was burned on the stake with much functional language incantations. It was all done with svelt discretion. The competition lived happily ever after. THE END
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainToo soon, man, too soon.
