Contents tagged with goals2004_CodeQuality
-
Code Review Tip: Poorly named variables are symptoms
When reviewing code one of the ways to quickly spot "messy" logic is to look for module-scoped variables with whacky names. Poor naming is often an indicator that the reason for writing code was unclear to the developer at the time.
-
Some golden rules to adhere by when thinking about features
When we started doing a spec for ProjectDistributor Justin and I had some long chats about what features we wanted in and how they would be implemented. In fact, there were dozens of features that we discussed and, as we progressed we found that we needed a better methodology for quickly deciding whether features would be winners or losers. Additionally, we needed a better way to describe new features to one another so that we didn't waste cycles trying to understand what the other person was trying to say.
-
Some books for reviewing code and develoment activity
-
Resource: Tips for creating successful architecture
A nice list to review next time you are in planning and wondering: "Will this succeed?" :-)
-
Hallmarks of a great developer
I got forwarded this link today:
-
Cleaning my desk...
This is my last week here at work and, while cleaning my desk I found this quote:
-
Writing Use Cases
I'm thinking that with all of the new tools which will soon be arriving in my favourite IDE that it might be a good time to learn more about writing Use Case statements.
-
Effective Collaboration... let me count the ways
Interesting... today I saw the word "collaborated" mentioned in 2 blog articles which were only about 7 items apart on the main feed.
-
Some quality developer time
My previous 3 weeks has re-installed the feeling that building computer applications is a great thing to do. Some quick reminders for myself:
-
How to build a comma-separated list
Dave has an interesting little thread going about how to do build a comma-separated list and what you can do with that annoying, left-over ',':