Learning by Hacking

And it looks like they've found what could be a great slogan for their campaign. "Coding is the new Latin," says Alex Hope, co-author of that Next Gen report which kicked things off. "We need to give kids a proper understanding of computers if they're to compete for all kinds of jobs.

I. Codebase

One codebase tracked in revision control, many deploys

II. Dependencies

Explicitly declare and isolate dependencies

III. Config

Store config in the environment

IV. Backing Services

Treat backing services as attached resources

V. Build, release, run

Strictly separate build and run stages

VI. Processes

Execute the app as one or more stateless processes

VII. Port binding

Export services via port binding

VIII. Concurrency

Scale out via the process model

IX. Disposability

Maximize robustness with fast startup and graceful shutdown

X. Dev/prod parity

Keep development, staging, and production as similar as possible

XI. Logs

Treat logs as event streams

XII. Admin processes

Run admin/management tasks as one-off processes

Focus on the product, not on your code

 

Good software trumps elaborate code. And unfortunately, you can’t usually have both. The real world has deadlines and ship dates. It’s a game of pick two:

• Ship on time
• Ship with elaborate code
• Ship with a fantastic product

Almost always, you should pick the first and the last when you’re building software applications for users

A designer who does not write markup and CSS is not designing for the web, but drawing pictures.