Evidence based estimating

Evidence Based Scheduling from Joel on Software

Using Evidence-Based Scheduling is pretty easy: it will take you a day or two at the beginning of every iteration to produce detailed estimates, and it’ll take a few seconds every day to record when you start working on a new task on a timesheet. The benefits, though, are huge: realistic schedules.

Realistic schedules are the key to creating good software. It forces you to do the best features first and allows you to make the right decisions about what to build.

You code like a Klingon

Source

You learn something new every day, thanks to Not Invented Here

var'aq is a speculative exercise in language creation: what does a programming language used by Klingons look like? It is a real programming language (not just a toy) that tries to imagine what it's like to be a hacker of the best-documented alien race in science fiction.

I think it should be called K# or K Sharp. Sharp like a Bath'leth

Code fury

I've felt like this before too

Source

How to write good code

XKCD does it again

Source

Useful Links: HTML Mockups and Interaction Specifications

Useful links:

Make Your Mockup in Markup 
At http://24ways.org/2009/make-your-mockup-in-markup

With the advent of CSS3, browsers are just as capable of giving us beautiful, detailed mockups as Photoshop, and in half the time.

Specifying Behavior: With an Example Menu Behavior Specification
At http://www.uxmatters.com/mt/archives/2010/01/specifying-behavior-with-an-example-menu-behavior-specification.php

inadequate behavior specifications too often result from poor design documentation standards and practices or designers’ inability to clearly communicate behavior. Solving these problems is solely the responsibility of UX Design and is the focus of the remainder of this column.