Los proyectos suelen empezar con un ritmo de desarrollo muy rápido. A medida que maduran van perdiendo velocidad hasta que llega a un punto en que el coste y tiempo de añadir funcionalidad es extremadamente elevado. En esta charla @luisrovirosa nos habla, desde un punto de vista técnico, cómo podemos diseñar y desarrollar el producto para aportar valor al final de cada sprint. Para ello muestra ejemplos de cómo hemos simplificado un producto y las prácticas que hemos utilizado para mantener la velocidad de desarrollo y la deuda técnica bajo control. También hablaremos del coste de cada una de ellas. Algunas de las técnicas son el vertical slicing, simplificar, test driven development, refactoring y automatización de la infraestructura.

1. Desarrollando a
velocidad de crucero
Luis Rovirosa

2. About me

3. Company dream

4. Reality

5. Reason for slow down

6. What software quality is

7. Root causes

8. Consequences

9. How do we deal with that

10. Business

11. Developers

13. Business

14. Simplify

15. Business

16. Vertical slices

17. Validate the UX
Make it real
Multiple devices
Multiple locations

18. Business

19. Ubiquitous language

20. Developers

21. if (!in_array(
$this->configuration->mainLanguage(),
$this->availableLanguages($companyLanguages)
)){ // do something }
if ($this->mainLanguageIsNotAvailable($companyLanguages)){
// do something
}
private function mainLanguageIsNotAvailable($languages) {
return !in_array(...);
}
Refactor

22. /** @var Centers $centers **/
$centers = $this->centerRepository->all()
->filter(function (Center $center) use ($companyId){
return $center->company()->id() == $companyId;
});
$centers = $this->centerRepository->all()
->fromCompany($companyId);
public function fromCompany($companyId): Centers {
return $this->filter(function ($center) use ($companyId) {
return $center->company()->id() == $companyId;
});
}

23. Developers

24. Unit test for business rules

25. /** @test SocketIoClientTest */
public function retrieves_the_message_after_sending_it()
{
$client = $this->client();
$sentMessage = ['key' => 'value'];
$client->send('aChannel', $sentMessage);
$retrievedMessage = $client->read('aChannel');
$this->assertEquals($sentMessage, $retrievedMessage);
}
Integration test for frontiers

26. /** @test */
public function its_possible_to_call_next_customer_
_when_the_employee_is_logged_in()
{
$this->loginAsEmployee();
$this->makeGetRequest('/callNextCustomer);
$this->assertResponseIsSuccessful();
}
Smoke testing for
controllers and view rendering

27. Developers

28. // Makefile
server-start:
docker-compose up -d
make dependencies-update
dependencies-update:
composer install
composer database:migrate
composer cache:clear
Automatize

29. Infrastructure as code

30. // Dockerfile
FROM php:7.1-apache
# Dependencies
RUN apt-get update &&
apt-get install git unzip -y
# Configuration
COPY apache.conf
/.../001-ourproject.conf
RUN ln -s 001-ourproject.conf
/etc/apache2/sites-enabled/

31. // docker-compose.yml
version: '3.3'
services:
database:
image: mysql:latest
webserver:
build:
context: .
dockerfile: docker/apache/Dockerfile
ports:
- “80:8080”
external_links:
- database

32. Developers

33. namespace MyProjectDomain;
interface HttpClient
{
public function get(...): string;
}
// Library GuzzleHttp
class Client {
public function get(...): ResponseInterface{
// All the logic
}
}
Decouple from infrastructure

34. use GuzzleHttpClient;
use MyProjectDomainHttpClient;
class MyGuzzleHttpClient implements HttpClient
{
private $client = new Client();
public function get(string $url): string {
return $this->client
->get($url, $this->defaultHeaders())
->getBody()
->getContents();
}
Adapter pattern

35. Summary

36. Root causes

37. Best practices
Simplify Vertical slices Ubiquitous
language
Refactor Test Automate Decouple

38. Final thoughts

39. Questions?
Luis Rovirosa
luisrovirosa

40. Thank you