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.
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.
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.
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.
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.
|Implementing and Securing an API with ASP.NET Core (new)|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||188.8.131.52||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.24628.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|