Archives for the 'Software engineering' Category

The first key to programming is to type, not to think

I remember vividly this scene from Finding Forrester, which, in my memory, goes something like this: Jamal is stuck. Forrester grabs the typewriter and proceeds to type furiously. Jamal reads what Forrester has written, amazed. Forrester says, “No thinking – that comes later. You must write your first draft with your heart. You rewrite with […]

15 September 2010 | Software engineering | 1 Comment

Centralized Decision List

During the implementation stage of software development there are always edge cases not covered in the functional specifications. What if the data imported from the other system is incomplete? Which user input fields should be made mandatory in the case of unforeseen dependencies? If there is no value for a field, should an empty string […]

16 January 2009 | Software engineering | No Comments

The Programmer’s Alphabet Soup

.asmx, .bat, .NET, .exe, AJAX, ASP, ASP.NET, C, C++, C#, CSS, DB, DLL, DOM, DRY, HTML, HTTP, IIS, JSON, MVC, MVP, MXML, PHP, REST, RIAs, RUP, SEO, SLES, SOA, SOAP, SQL, TCP/IP, UI, UML, VB, WCF, WCSF, WPF, WSDL, WS-*, XAML, XHTML, XML, XSD, XSLT.

13 January 2009 | Software engineering | No Comments

You Can’t Rush Code

Effective time management means knowing when not to be a perfectionist. For example, it’s better to do something hurriedly when other people’s tasks are dependent upon it, and when a first (or second) draft would suffice. Revisions could be done afterwards as necessary. However it has been my experience that it’s never OK to code […]

26 December 2008 | Software engineering | 1 Comment

.NET Architectural Cheat Sheet

CodePlex (Microsoft’s open source project hosting web site) has a Patterns & Practices Catalog At A Glance Cheat Sheet. It’s quite a long list. You might want to at least glance through it before starting on the architecture of your next .NET solution.

15 October 2008 | .NET, Software engineering | 2 Comments