Best Practices

Software development problems

  • Poor software quality
  • Unacceptable software performance
  • Software that is hard to maintain or extend
  • Inaccurate understanding of end user needs
  • Inability to deal with changing requirements
  • Late discovery of serious project flaws

There isn't a "playbook" on the components of the ideal software development.

What do you think about when you hear

"Best Practices"? 

Let's focus on 5 points

  1. Writing simple code

  2. Testing

  3. Following standards

  4. Reviewing code

  5. Estimating work

Writing simple code

"Strive to keep your code simple."

Software principles:

 

  • SOLID...

  • DRY (Don’t Repeat Yourself)

  • YAGNI (You Aren’t Gonna Need It)

  • KISS (Keep It Simple, Stupid)

Testing

"Continuously test from end to end."

 

TDD

Test Driven Development

BDD

Behavior Driven Development

Following standards

"Keep it consistent across your team."

Reviewing code

"Don’t be shy, allow someone to check your code."

Estimating work

"Set your time and budget estimates realistically."

Exercise

https://github.com/LinioIT/shop-front/blob/master/src/Feed/Adapter/DynamicYieldAdapter.php

More information

Made with Slides.com