Clean Code
Splitting Code #6
Today I am going to go through the AngularJS’s testability.js file, for two reasons; first, to learn how they approached making the framework testable and second to see if there are any opportunities to clean up the code. Making your code testable appears to be a topic of some debate, Read more…
Clean Code
Splitting Code #5
Today I am going to go through AngularJS’s urlUtils.js file and see what we can learn from going it. Documentation, this file has a lot of it, and most of the documentation is used for generating their documents, a feature I like but also one that tends make the code Read more…
Clean Code
Splitting Code #4
Today’s subject gets a small refactor, as the existing code is already in good shape. As I have been going through the code base of AngularJS I have been noticing a majority has been written with care for future maintenance. The document file was selected to show method extraction; this Read more…
Clean Code
Splitting Code #3
Taking the shallow copy function in AngularJS and making it more readable.
Clean Code
Splitting Code #2
Duplicate code shows up for its time in the lime light, see how we promote him to a new role, by following Clean Coding practices.
Clean Code
Splitting Code #1
First in a series where we take good code and make it better, by following Clean Coding practices.
Code Quality
Use Guides to Help You Communicate Clearly to Others
Guides are documents that contain answers to questions you will encounter while you develop your applications. Some of those questions will be what should I use to prompt a user for input, and others suggest what is the best way to communicate your intent of the code you are writing Read more…
Code Quality
TODO’s Should Not Live in Source
TODOs do not belong in the source code they get lost and forgotten. I was recently reminded of this when I had gone through some code to remove some code quality issues, that when resolved revealed that there was a to do in the comments of the code that had Read more…
Code Quality
One Brick at a Time
This weeks tip ties with the previous one: Drawing the Line, take one step at a time. Just like a bricklayer places one brick at a time to build a wall, you need to take on one code quality step at a time. Let’s continue with the previous example, you have Read more…