smeade/handbook

Ways a software developer works

A Software Developer's Handbook

An accounting of what a modern day software develoment team does and how what they do it.

Copyright © 2017 Scott Meade.

There will likely always be parts of this handbook in draft form and in various stages of completeness and accuracy. Where parts seem week and unpolished it is possible I am an unpolished writer, that those parts are a work-in-progress or both.

Please notice this as a software developer's handbook. This handbook is not authoritative nor intended to be exhaustive. There's many ways to get the job done.

Overview

This handbook serves as:

• A developer's diary. There are many benefits to keeping a developer's diary or journal. I have been keeping a daily developer's journal for some time. It does help get the day's work done. Yet I have not referred to past entries very often. Perhaps capturing and organizing entries in a handbook format will help me extract more value from daily experiences and lessons learned.
• A process manual. A software developer's work consists of many processes that are repeated daily, weekly, monthly or through each project. Formalizing my experiences into written processes helps to clarify and refine those processes.
• A reference to demonstration apps. A wonderful thing about Heroku is the ability to deploy apps for free. I would love to have some demonstration apps deployed for reference and discussion.
• A scratchpad for ideas.

Table of contents

• Introduction
  • About
• Process
  • Fix Bugs
  • How I Work
  • Start Design and Development Work on a New Story

Inspired by

The World is full of prolific writers and people who give freely of their insights and experiences. Current and initial inspiration is from those listed here. This list is sure to grow.

• Nathan Barry
• John Sonmez
• David Heinemeier Hansson and Basecamp
• Baptiste Pesquet and The JavaScript Way