Show MenuHide Menu

Tag: programming

Agile Manifesto

April 29, 2011

Thanks to an article by Danny O’ Brien writing in the Irish Times for pointing out the origins and core principles of Agile Development. The principles were laid out by 17 developers in 2001 and are listed below, more information about Agile development is available here: 

Principles behind the Agile Manifesto

We follow these principles:

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers must work
together daily throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity–the art of maximizing the amount
of work not done–is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.


What is a Full-stack programmer?

January 3, 2011

Carlos Bueno has a very interesting article in Facebook’s Engineering Notes which defines the concept of the “Full-Stack programmer”. Carlos defines a full-stack programmer as:

a generalist, someone who can create a non-trivial application by themselves. People who develop broad skills also tend to develop a good mental model of how different layers of a system behave. This turns out to be especially valuable for performance & optimization work. No one can know everything about everything, but you should be able to visualize what happens up and down the stack as an application does its thing.

Programming IQ test: Round 1 & 2

December 12, 2010

Neil McAllister has compiled two general IQ tests for programmers. Give them a go there are some tricky questions and then some of the humorous variety exhibit A below:

4. What is a singleton?

A) class that is instantiated exactly once, producing just one object of that class

B) complete program that takes up only one line of code

C) data structure, such as a linked list, that contains only one member

D) The typical programmer on a Friday night