Long running projects, be it software or city planning, have something in common: the constant change to their environment. The problems to solve in one, two, or even five years from now will be different from those at hand now – and they are yet unknown. Thus dealing with uncertainty is one of the key issues and a well-chosen set of development techniques can help with that. Even if you don't plan to develop a framework, there's a lot you can learn from the development processes for creating your own stable and performant applications.

1. Planning for the Unplannable
Framework-Grade Architecture
Robert Lemke - TechDivision GmbH

2. TEXT HERE
Robert Lemke
!
38 years old
developer for 27 years
lives in Lübeck, Germany
software architect at TechDivision
TYPO3 Association co-founder
TYPO3 Flow & TYPO3 Neos project founder
1 wife, 2 daughters, 1 espresso machine

3. Framework-Grade?

4. Architecture?

6. Image © Arquivo Nacional Brasil

7. Image © 2014 Landsat / © 2014 GoogleImage © 2014 SIO, NOAA, U.S. Navy, NGA, GEBCO, Landsat, Google, Inav/Geosistemas SRL, Mapcity

11. TEXT HERE

12. „this experiment was
not successful”
Oscar Niemeyer 2001
Photo © Marcelo Coelho

13. TEXT HERE

14. If you know that you can’t plan
for something, just
plan for the unplannable.

15. Flexibility and quality are key

16. Experience

17. Design Patterns

19. Loose Coupling

20. High Cohesion

21. Law of Demeter
- each unit should have only limited knowledge about other
units: only units "closely" related to the current unit.
- each unit should only talk to its friends;
don't talk to strangers.
- only talk to your immediate friends.

22. Code against interfaces

23. Dependency Injection

24. !
class IsbnLookupService {
protected static $instance;
public function getInstance() {
if (self::$instance === NULL) {
self::$instance = new self;
}
return self::$instance;
}
}
!
!
class BookSearchController {
public function action() {
$service = IsbnLookupService::getInstance();
…
}
}

25. class ServiceLocator {
protected static $services = array();
public function getInstance($name) {
return self::$service[$name];
}
!
}
!
!
class BookSearchService {
public function action() {
$service = ServiceLocater::getInstance("IsbnLookupService");
…
}
}

26. class BookSearchController extends ActionController {
!
/**
* @var IsbnLookupService
*/
protected $isbnLookupService;
/**
* @param IsbnLookupService $isbnLookupService
*/
public function __construct(IsbnLookupService $service) {
$this->isbnLookupService = $service;
}
}

27. class BookSearchController extends ActionController {
!
/**
* @var IsbnLookupService
*/
protected $isbnLookupService;
/**
* @param IsbnLookupService $isbnLookupService
*/
public function injectLookupService(IsbnLookupService $service) {
$this->isbnLookupService = $service;
}
}

28. class BookSearchController extends ActionController {
!
/**
* @FlowInject
* @var IsbnLookupService
*/
protected $isbnLookupService;
!
}

29. class BookSearchController extends ActionController {
!
/**
* @FlowInject
* @var IsbnLookupServiceInterface
*/
protected $isbnLookupService;
!
}

30. AcmeControllerBookSearchController:
properties:
isbnLookupService:
className: AmazonServiceIsbnLookupService

31. Planned and Unplanned
Extensibility

32. Configuration

34. Signal-Slot Pattern

37. Observer, Dispatcher, Publish-
Subscribe, Event-Notifier,
Event Sourcing …

38. Define a public API
with @api

39. Aspect-Oriented Programming

41. Dependency Management:
Composer, requirejs, …

42. Reinvent the Wheel!

43. Unit Tests

44. Functional Tests

45. System / Behavior Tests

48. Understanding other
people’s code

49. Code Ownership

50. Software Rot

51. Be picky!
Fix broken windows!

52. Remove unused code

53. Write code because it adds value
(not only because you can)

54. But maybe we need it (YAGNI)

55. Be canny with configuration

56. Reviews

59. Change your perspective

60. Readable Code

61. TYPO3FlowCodingGuidelinesononepage
<?php
namespaceAcmeTestPackage;
/* *
*ThisscriptbelongstotheTYPO3Flowpackage"Acme.TestPackage". *
* *
*Itisfreesoftware;youcanredistributeitand/ormodifyitunder *
*thetermsoftheGNUGeneralPublicLicense,eitherversion3ofthe *
*License,or(atyouroption)anylaterversion. *
* *
*TheTYPO3project-inspiringpeopletoshare! *
* */
useAcmeTestPackageServiceFooGenerator;
useTYPO3FlowAnnotationsasFlow;
/**
*Heregoesthedescriptionoftheclass.Itshouldexplainwhatthemain
*purposeofthisclassis...
*
*@FlowScope(”singleton”)
*/
classUniverseAnalyzerextendsBaseClassimplementsSomeInterface{
/**
*Someinjecteddependency
*
*@FlowInject
*@varFooGenerator
*/
protected$someDependency=NULL;
/**
*ShowsifyouareaddictedtoTYPO3Flow
*
*@varboolean
*/
staticprotected$addictedToFlow=TRUE;
/**
*ShowsifyouareafanofTYPO3Flow
*
*@varboolean
*/
protected$fanOfFlow;
/**
*Agreatmethodwhichshowshowtoindentcontrolstructures.
Descriptionoftheclass.Makeitas
longasneeded,feelfreetoexplain
howtouseit.
Namespacestartswithvendorname
followedbypackagekey(name)and
subpartsasneeded
UpperCamelCaseclassname.Class
namesshouldbenouns.
Inotherpackages,import
AcmeTestPackageUniverseAnalyzer
andrefertoitasUniverseAnalyer.
Use@vartag.Optionaldescription
goesinthefirstcommentline
followedbyablankcommentline.
Descriptionofthemethod.Makeit
aslongasneeded.
Methodnamesshouldbeverbs.
Oneusestatementperline.
Oneusestatementpernamespace.
Orderstatementsalphabetically.
Don'timportnamespacesunlessyou
usethem.
NoemptylinebetweenDocComment
andclass,membervarormethod.
Preferrelativenamespaces,unless
FullyQualifiedNamespaceismore
readable
List@Flow*beforeothertags:
@var,@param,@return,@throws,
@api,@since,@deprecated
Capturethejoyofcodingasyou
createexcellentwebsolutions.
Enjoycoding.EnjoyFlow.
http://rlmk.me/flowcgl

62. Naming

63. $path
$pathAndFilename
$filename
$directory
$directoryName
$class
$className

64. © „davic” (Flickr)

65. © „¡Carlitos” (Flickr)

66. borrowed a lot from:
The pragmatic programmer
Code complete
All Martin Fowler Books (PoEAA)

67. TEXT HERE
@robertlemke
!
robertlemke.com
flow.typo3.org
neos.typo3.org
techdivision.com