101 reputation
13
bio website
location
age
visits member for 2 years, 7 months
seen Dec 15 at 19:52

Mar
17
comment How would you know if you've written readable and easily maintainable code?
+1 for incremental learning and not trying to become perfect overnight
Mar
17
comment How would you know if you've written readable and easily maintainable code?
@MichaelDurrant Each time you review old code you'll find pieces that should have been written differently and then you'll take that into account for the code that you're writing "today". Yes, it does take time to learn how to write good code.
Mar
17
comment How important is it to clean up someone else's code when faced with a tight deadline?
@Phil When calculating a deadline, time for code review sessions should be taken into consideration. It is not an extra step on top of the devleopment process - it is an integral part of the development process.
Mar
13
comment What is a O(n) algorithm to solve this puzzle?
+1 This somehow explained it to me better than the answer with the code
Mar
12
comment Single Responsibility Principle - How Can I Avoid Code Fragmentation?
+1 for "does every change only affect one class?"
Jan
8
comment Is it okay to mock multiple objects in one class?
Mocks Aren't Stubs
Dec
20
awarded  Civic Duty
Aug
6
awarded  Commentator
Aug
6
comment Unwritten rules of rewriting another team member's code
One other thing: A month after putting aside a piece of code - no, more than a month if you're counting from when it was tested - most developers are on the other side of the code base by that time and cleaning up code that they wrote "ages" ago is the last thing on their list.
Aug
6
comment Unwritten rules of rewriting another team member's code
That's another function of a proper version control system: you can view when changes were checked in, compare versions to see exactly what changed from one checkin to the next, and associate comments with checkins to explain why a modification was made. If it is so important for others to know right away that a piece of code was changed, perhaps send out an e-mail notification instead of waiting for the other developers to chance upon your comments.
Aug
6
comment Unwritten rules of rewriting another team member's code
"I suggest you delete the code some time later" - where should it stay in the meantime? In a commented block? That's what source control is for, to keep a backup copy of all changed/deleted code for easy retrieval, while keeping the current source code clean.
May
24
awarded  Citizen Patrol
May
23
comment Working on someone else's code
"good comments never go out of style"...unless the code changes. While comments can sometimes be helpful, always take them with a bucket of salt - you'll have to verify that the code actually does what the comment says it does. Too often someone will change a line of code but leave in an existing - and now irrelevant - comment.
May
21
comment Is inconsistent formatting a sign of a sloppy programmer?
Thanks for the great link.
May
17
comment Making an internship most effective, useful and fun for both parties
+1 For part A - I'd give +5 if I could. That was definitely what made my internship rewarding and enjoyable.
May
16
comment How can I apply OOP concepts to building a simple, but real-world, web app?
+1 for composition vs inheritance
May
8
awarded  Supporter