The Software Gardener

Get Started. It's Free
or sign up with your email address
The Software Gardener by Mind Map: The Software Gardener

1. Pair Programming: Pair Gardening

1.1. Two programmers work side by side

1.1.1. gardeners working together

1.1.2. planting trees

1.1.3. digging and shaping

1.1.4. moving the wheel barrel

1.2. Troubleshooting

1.2.1. misery loves company

1.2.2. sweating in the sun together

1.3. pairs

1.3.1. expert novice grandma grandchild

1.3.2. advanced novice wife husband

1.3.3. Outsourced hired labor

1.4. We still do individual work

1.4.1. emails, refactoring, entering bugs, testing

1.4.2. watering, pruning, spotting weeds,

2. Test Driven Development: Test Driven Planting

2.1. often not done

2.1.1. start programming immediately quickly glance at apis and how to use things

2.1.2. go to store, start buying plants, flowers roughly read the 2" card in the flower pot

2.1.3. can program bad, lucky, or decent without it can pot in dirt, all potting soil, or mix the 2

2.2. most experienced do TDD

2.2.1. determine requirements, best way to interact with an api, setup tests

2.2.2. draws out the plan, defines the size of flowers/plants for the area, determine amount of sun required

2.2.3. define what passes and what fails, not just making progress toward an unknown goal

3. Refactoring: Planted Debt

3.1. Making changes that don't affect behavior

3.1.1. cleanup code better designs fight off garbage collection locks and memory leaks

3.2. Making changes that don't affect overall garden

3.2.1. clean out weeds turn plants at different angles fight off squirrels & leprechauns

4. Mythical Man Month: time is Needed

4.1. Book known for the analogy

4.1.1. A baby takes 9 months to make, no matter how many women you put on the job

4.1.2. Software takes time, you can't always throw developers at a project to complete it sooner

4.2. Gardening is the same

4.2.1. Can't have 9 gardeners grow a tree in a day

4.2.2. needs sun, water, pruning, rain, time refactoring, upgraded, memory, time

4.3. Commercial off the shelf solutions

4.3.1. can purchase a tool to solve a problem sometimes it doesn't work out sometimes need to develop the right solution

4.3.2. can buy a tree from a store sometimes the tree still dies sometimes you need to buy the land, the seeds, the shovels and put in the hard work for the right solution

5. Design

5.1. pull out hose

5.1.1. make shape of flower bed decide how much money you want to spend spend more money than desired

6. Peer Review

6.1. syntax nagging

6.1.1. color of anything you have ever done is always wrong actual good feedback

6.2. shrub should face the street

6.2.1. color of mulch should be more dirt colored suggestion on frequency of watering

7. Continuous Integration

7.1. plant a flower in pot first

7.1.1. migrate flower to bed sometimes plant directly into the bed

7.2. develop feature on branch

7.2.1. merge code Facebook changing prod harder in development

8. On Call Support

8.1. Server is down!!

8.1.1. bugs Dogs crap in the begonias we clean up

8.2. Fountain in front yard (broken sprinkler head)

8.2.1. bugs user puts in crap we clean up

9. Development Duck

9.1. add yard gnome

9.1.1. spouse complains about it spouse misses how you didn't plant the flower facing the street

9.2. add a feature you don't really want

9.2.1. manager complains about it leaving the rest of the program comment free

10. Deliver Features

10.1. agile focus on delivering end user features

10.1.1. instant usability and enjoyment rarely do you create the framework from scratch in batches to the user, iterations, sprints

10.2. you plant one flower at a time

10.2.1. instant usability and enjoyment rarely do you plant seeds in batches, multiple flowers, plants etc