Bootstrap Your Project!

BOOTSTRAP YOUR PROJECT! International PHP Conference 2013 Spring Edition

Sorry! :-)

THORSTEN RINNE ‣ Diplom-Informatiker (FH) ‣ Senior Developer ‣ Scrum
Master ‣ Yatego GmbH ‣ Open Source: phpMyFAQ ‣ @ThorstenRinne

THE PROJECT

Deﬁne the vision of the project!

Start with a small team!

We don´t need code monkeys.

Add new developers, but slowly.

Share the vision with the team.

Collect all requirements. Start with the important ones.

Order them by ROI. Collected all requirements?

Document your tasks!

Prioritize the task according to ROI and complexity.

Look for cheap wins!

INFRASTRUCTURE

No Hardware. Not yet.

Virtual Machines

$ vagrant box add base http://files.vagrantup.com/lucid32.box [vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/lucid32.box [vagrant] Extracting box... [vagrant] Verifying box... [vagrant] Cleaning up downloaded box... $ Vagrant

$ vagrant init A `Vagrantfile` has been placed in this
directory. You are now ready to `vagrant up` your first virtual environment! Please read the comments in the Vagrantfile as well as documentation on `vagrantup.com` for more information on using Vagrant. $

$ vagrant up [default] Importing base box 'base'... [default] Matching
MAC address for NAT networking... [default] Clearing any previously set forwarded ports... [default] Forwarding ports... [default] -- 22 => 2222 (adapter 1) [default] Creating shared folders metadata... [default] Clearing any previously set network interfaces... [default] Booting VM... [default] Waiting for VM to boot. This can take a few minutes. [default] VM booted and ready for use! [default] Mounting shared folders... [default] -- v-root: /vagrant $ And done! :-)

Conﬁguration management Tools with an object-orientated model

sysadmin tasks are often repetive new users deploying hosts managing
applications conﬁguring daemons monitoring hosts Why Puppet?

What we´re trying... automate different tasks with scripts but it‘s
getting complex poorly documented customized for each environment rarely scale to large platforms

Puppet Ruby based Apache License Started in 2001 Support for
Linux / Unix / BSD OS X

class nginx::package { anchor { 'nginx::package::begin': } anchor { 'nginx::package::end':
} case $::operatingsystem { debian,ubuntu: { class { 'nginx::package::debian': require => Anchor['nginx::package::begin'], before => Anchor['nginx::package::end'], } } opensuse,suse: { class { 'nginx::package::suse': require => Anchor['nginx::package::begin'], before => Anchor['nginx::package::end'], } } } }

Private and Public Clouds

Why Git? it‘s fast because everyone has the whole history
supports non linear development no single point of failure like SVN distributed development (ofﬁce / train / beach) efﬁcient handling of large projects

Every feature is a branch.

Use <html> diff emails

Automate as much as possible. Devs are lazy.

Use a Wiki. And keep it up to date!

You have to be replaceable. Document that way.

Use a tracking software.

FRAMEWORKS

Use Frameworks. For frontend. For backend.

Use proven frameworks

Use the Community

Check Google hits for technology X

Check GitHub project stats

$ composer update Loading composer repositories with package information Updating
dependencies (including require-dev) Nothing to install or update Writing lock file Generating autoload files

Bower $ bower install jquery bower cloning git://github.com/components/jquery.git bower caching
git://github.com/components/jquery.git bower fetching jquery bower checking out jquery#2.0.1 bower copying /Users/thorsten/.bower/cache/jquery/ 29cb4373d29144ca260ac7c3997f4381 bower installing jquery#2.0.1

Donald Knuth: „Premature optimization is the root of all evil.“

Test Driven Development

The „Cancel“ button? Not tested yet! :-(

Unittests for all the important base classes.

Automate your testing.

Automated API testing.

No Selenium tests at the beginning. Too expensive.

Continuous Integration Coding Style PMD (Project Mess Detection) LOC (Lines
of Code) CPD (Copy&Paste Detection)

MANY, SHORT MEETINGS

Iterative approach

2 week sprints 14 days

XP Communication

XP Communication Simplicity

XP Communication Simplicity Respect

XP Communication Simplicity Feedback Respect

XP Communication Simplicity Feedback Courage Respect

XP feedback loops Release Plan Iteration Plan Acceptence Test Daily
Standup Pair Negotiation Unit Test Pair Programming Code months weeks days day hours minutes seconds

KANBAN

Daily Standup

Team lunch

⇥ Timeboxing ⇤

Prepare yourself for meetings!

Do retrospectives!

Learn from them!

Pair programming improves the team knowledge.

Pair programming reduces the question overhead

Do end-user tests as early as possible.

Rapid feedback: Controls the development.

DO NOT CHANGE EVERYTHING.

Fight the „second system syndrome“

Use old, reusable code

Use mature libraries.

Continuous Refactoring

Monitoring statsd / graphite „Measure Anything, Measure Everything“ Etsy

Monitoring

Have fun at work.

„Stay hungry, stay foolish!“ Steve Jobs, 2005

Questions? Comments?

Thanks for your attention! Twitter: @ThorstenRinne App.net: https://app.net/thorsten Slides: https://speakerdeck.com/thorsten
Thorsten Rinne Yatego GmbH [email protected]

Bootstrap Your Project!

Bootstrap Your Project!

More Decks by Thorsten Rinne

Other Decks in Technology

Featured

Transcript