Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Developer Productivity

No description
by

Alex Staveley

on 24 January 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Developer Productivity

Developer Productivity
Developer Productivity?
Difficult to objectivity, difficult to quantitify?
Lines of code, Hours worked?
Number of stories?
Framework proliferation - a false sense of progress.
Is a Lawyer's or Doctor's productivity and easier to measure?
Architectural Thoughts
Architecture
Non functional requirements
Abstractions at correct level
Choices with trade offs
Important contracts well defined
Right level of decoupling
Tech stack fit for purpose
SLAs
Code Reviews in the 21st Century
Productivity is the path to Greatness
Agree a style guide
Code is tested (code coverage)
Automate (Sonar, codenarc, gmetrics)
Respect Design
Avoid big bang reviews
Every project is different
Every Project is different
Rapid prototype, incubation, SLA
Number of developers
Developer back ground
Golden Hammer
A quantitive problem but not an existential one
Meet requirements in reasonable time frames?
Can you scale a team?
Could a competitor beat you?
Technology choices:
Scala V Ruby
Java V Scala
Modular design
Separate developers
Consistency
Concepts (bounded context)
Explain yourself - Project dictionary, patterns
Make it harder for people to make mistakes
Dependency control
Process (CI, code review)
Fail fast (Config errors, Defensive code at key points but don't forget the trade off)
Architecture - Developer Productivity
Alex Staveley
September 2015
Full transcript