Joe Kuemerle does an INCREDIBLE job of laying the foundation for why developers need aspect-oriented programming, introducing the paradigm, and tools available that support AOP. The InfoQ recording is from his presentation at CodepaLOUsa earlier this year. "If you’ve done any WPF programming, you’ve got your model view classes and you’ve got that INotifyPropertyChanged implementation in every…single…setter…in…your…type. Why? It’s 2012, why do you have to do that ceremony — put that boilerplate code in for something you know should be there and everyone else knows should be there?"
Writing a good code is a art. if a programmer follows some good programming habits then he can be a good programmer. Actually any code you write is likely to spend most its time in maintenance; application maintenance is a large expense. Establishing good coding habits will enhance design factors like modularity, and your code will be easier to understand and, thus, easier and cheaper to maintain. bad coding habits create defects in code and can cause code to be difficult to modify without introducing new defects.
This morning I was asked a question that took me by surprise: “Your examples for PasswordLib are in OOP style, how do I write it in procedural style”… This took me by surprise, because the examples actually are in a procedural style. So I felt that I should write a post about the real differences between OOP and Procedural coding styles. Hint: whether you use classes and objects or not has very little to do with the answer…
I have recently started “taking seriously” making coffee. By that, I mean that I have spent a considerable amount of money, time, and effort, learning to brew espresso at home. Rather than bore you with the history, suffice it to say that this has become my latest expensive hobby. I wanted a challenge outside the realm of building software, and I’ve found it.
Since I had one week before my next contract I decided to finish my “cycle of id”. After Doom, Doom Iphone, Quake1, Quake2, Wolfenstein iPhone and Doom3 I decided to read the last codebase I did not review yet:
Python code analysis can be a heavy subject, but it can be very helpful in making your programs better. There are several Python code analyzers that you can use to check your code and see if they conform to standards.