Month: March 2008
-
Top 5 reasons why “The customer is Always Right” is wrong
Pretty related to an earlier post I made about how programming shops are not dry cleaners… It’s not saying ignore the customer, but that random customer demands aren’t the way to run a business well. Top 5 reasons why “The customer is Always Right” is wrong
-
Maybe a PythonShop #2 is in the works…?
Looks like IronPython is not only steps away from their 2.0 version, but is python compliant enough that Django runs. Plus, you get to use .Net stuff like Silverlight, which apparently provides some nice UI functionality. This could be interesting… As for the article title, well sure, I understand the sentiment, but the truth is,…
-
SharpShop in Progress…
Like PythonShop (which could still use some touching up) the current task is to build the same functionality in .net. As I’m the .Net person (and *I’m* not at PyCon this weekend) I started up the project groundwork. I’m trying to do it with NHibernate, log4net, mysql (yeah, thought it might be interesting to hit…
-
SharpDevelop Initial Review
As I mentioned in this post, I was interested in SharpDevelop, a free .net editor. I’ve been writing some with it a bit at home yesterday and today, and it strikes me as adequate for basic messing around at home on projects. Two months ago, I might have said it was super and all you’d…
-
Another book on the stack…
Working Effectively With Legacy Code is supposed to be fantastic.. and who doesn’t work with legacy code? I know I do…
-
Is #Develop any good?
http://www.icsharpcode.net/OpenSource/SD/ Haven’t looked at it yet, but since ReSharper plus VS staundard is a bit costly for futzing around at home for the soon-to-be-started SharpShop, I think I’ll give this a go. Review to come in a future post…
-
Agile Principles, Patterns, and Practices in C#
i hear it’s a good book- another one to add to the stack of books-to-read…
-
Refactoring
Currently reading Refactoring by Martin Fowler. Yeah, any programmer worth the space he/she takes up is going to do some version of refactoring, but this is really attacking refactoring with a systematic, safe, testable approach. It seems like a better way of approaching it than the normal way: Oh god, this code sucks, it makes…