Tagged with Coding
One of the things that I help companies with are code reviews. I love doing code reviews. It let’s me look at a large codebase with fresh eyes and help a company out with a set of recommendations for improving their process, teams and code.
The purpose of this new course is to show you some of the lessons that can be learned through code reviews. I’ve broken up the lessons into several parts:
I just read this blog entry for Michael Earls and it got me wondering. I am one of these neanderthals that has been coding since before I could drive. I see the value of “Patterns” as a common language to help solve problems, but I am not a huge fan of “Everything is a Pattern” mentality that peeked sometime in the late nineties. I was talking to Chris Sells one day about patterns and we came to the conclusion that patterns are great because they created a common language for stuff that we've been using for years. The problem comes in when a developer tries to fit every problem into the GOF patterns.
At the end of the day, we all use patterns, even if we refuse to call them that. Both extremes have their own problems:
This Outlook Add-In from MS Research and Maryland U. is particularly interesting. It may be a little more of than another consuption of extra CPU cycles in an age over-zealous animations, but I think there is something useful here. There is an intuitiveness to what they have in mind that is very useful.
It adds itself as an Outlook Add-In but doesn't take over any standard functions so don't be worried about what it will do to Outlook. Let me know what you think...
I have been spending a lot of time writing about technology lately. After a phone conversation with Tim Ewald, it got me thinking. During the first half of writing the book, I was working full-time writing ATL/C++ apps mostly and trying to get up to speed with ADO.NET at night. While my girlfriend minds, I don't really.
While in this phase of the project, I learned a lot about the technology and the class signatures, but it was very hard to grasp the big picture of the real problems that people will/are facing.
Soon after I got a full-time position developing a large scale .NET application. This really helped me appreciate the nature of the techology. I started to get really excited about how ADO.NET would help people solve these problems. Later on I started doing a tour of .NET User Groups to talk about ADO.NET and this was enlightening as well. People were asking me real-world questions that I did not always have great answers for. In the end, both of these experiences definitely helped me write a better book IMHO.
As a primarily .NET Guy, it has been fun watching from sidelines what Sun is trying to do for Java...
I've wrote a bit of Java here and there, but I could never find an IDE that was worth a dime. Sun seems to finally trying to address Java's biggest weakness, development tools. Sure, hardcore Java heads will tell me that I am a lesser man for not doing everything with the command-line. This thinking is even permeating .NET lately talks.
Sun has had a ten year head start on .NET. I wish they would have gotten religion about tools before. This is one thing I give MS a lot of credit for. As much as I bitch and moan about the IDE's of the last five years, they really have made me more productive. And that's what it is really about in the long run.
After seeing the story about Justin Frankel and his departure of Nullsoft, it got me thinking about code as self-expression.
I just spent the last week completing two projects. First, I re-architected http://wildermuth.com and I recreated TypedDataSetGenerator so that I could extend it. I learned a couple things about how much I like to write code.