Forms

•Download as PPT, PDF•

0 likes•115 views

Thanos Stasinopoulos

forms
TNS PhotoGraphics

07082321
22

07081359
33

07080531b
44

07081360cw
55

080526a15c3
66

C080428-91cw3
77

07080558b
88

07080571BcD
99

05061229b
1010

070424a5
1111

07080573b
1212

080712219w
1313

080714-10e
1414

080712274q
1515

07081363C2bCQ
1616

080410151c
1717

07081355RQC
1818

080406C-79w
1919

07081371w
2020

07042818www
2121

080712275qRC
2222

080714-03PQ
2323

07081365Cq
2424

07042831qw0
2525

C080425127wq
2626

07080586Q
2727

06081140Zw
2828

07042487zQs
2929

010111-005q
3030

04101753RCQCQmq
3131

07031712CQZ
3232

05061316q
3333

845418S2-anC2NQC
3434

07082332C
3535

07082314Cq
3636

07012736zq
3737

06070819zRCQ
3838

05101056q
3939

Forms

More Related Content

Viewers also liked

f you’re a programmer you make design decisions every second. Statements, functions, classes, packages, applications, even entire systems: you need to think, and often think hard, about everything. Luckily there are many useful design principles, patterns and best practices that you can apply. But some of them merely expose code smells. Others only help you design your classes. And some are applicable to packages only. Wouldn’t it be nice to have some more general, always useful, invariably applicable, foundational design principles? In this talk we’ll look at software from many different perspectives, and while we’re zooming in and out, we’ll discover some of the deeper principles that lie beneath proper object-oriented design. They are the foundation of many of the well-known design patterns and they may even serve as an explanation for code smells.

Dutch PHP Conference 2015 - The quest for global design principles

Dutch PHP Conference 2015 - The quest for global design principles

Dutch PHP Conference 2015 - The quest for global design principles

Matthias Noback

The journey behind a child of mine

The journey behind a child of mine

The journey behind a child of mine

DeneDanceSchool

What is an event really? How can you best describe an event in your code? What types of events are there, and how do you decide whether or not to implement something as an event? In this talk we start with a straightforward command-only piece of code. We extract events from it and start moving the event handling code out, trying different design patterns on the way. First we try Observer. Then we introduce event data, event handlers and a Mediator between our code and the event handlers. Finally we pick a well-known event dispatcher implementation (the Symfony EventDispatcher) and see how it uses the Chain of Responsibility design pattern to control the entire flow of a web application request. In the end I will answer some burning questions like: is it safe to use events all over the place and rely on event handlers to do some really important stuff? How do I overcome the indirection in my event-driven code? And how can I quickly find out what happens where?

A Series of Fortunate Events - PHP Benelux Conference 2015

A Series of Fortunate Events - PHP Benelux Conference 2015

A Series of Fortunate Events - PHP Benelux Conference 2015

Matthias Noback

Blooming shibazakura flowers in japan

Blooming shibazakura flowers in japan

Blooming shibazakura flowers in japan

The Bundle system is one of the greatest and most powerful features of Symfony2. Bundles contain all the files related to a single feature of your application: controllers, entities, event listeners, form types, Twig templates, etc. But how much of that actually needs to be inside a bundle? In this talk we’ll take a bundle, containing all those different types of classes, configuration files and templates, and strip it down to the bare necessities. And I promise that after moving many files out of the bundle, everything still works. While looking for ways to move things out of the bundle, I will discuss some of the more advanced features of bundle design, like prepending configuration, compiler passes and Doctrine mapping drivers. We will end with a very lean bundle, surrounded by a few highly reusable, maximally decoupled libraries.

The Naked Bundle - Symfony Live London 2014

The Naked Bundle - Symfony Live London 2014

The Naked Bundle - Symfony Live London 2014

Matthias Noback

Causes of delay and cost overruns in construction of groundwater projects in ...

Causes of delay and cost overruns in construction of groundwater projects in ...

Causes of delay and cost overruns in construction of groundwater projects in ...

Charles Abraham Scheck

If you’re a programmer you make design decisions every second. Statements, functions, classes, packages, applications, even entire systems: you need to think, and often think hard, about everything. Luckily there are many useful design principles, patterns and best practices that you can apply. But some of them merely expose code smells. Others only help you design your classes. And some are applicable to packages only. Wouldn’t it be nice to have some more general, always useful, invariably applicable, foundational design principles? In this talk we’ll look at software from many different perspectives, and while we’re zooming in and out, we’ll discover some of the deeper principles that lie beneath proper object-oriented design. They are the foundation of many of the well-known design patterns and they may even serve as an explanation for code smells.

The quest for global design principles - PHP Benelux 2016

The quest for global design principles - PHP Benelux 2016

The quest for global design principles - PHP Benelux 2016

Matthias Noback

With many great tools available for sharing packages of PHP code, it is now up to you as a developer to design these packages well. You have to decide what to put in a package, when to split a package and on what other packages you can safely depend. You will learn how to make good decisions about your package design and release reliable, highly usable and therefore highly esteemed packages of PHP code.

Principles of Package Design FOSDEM 2015

Principles of Package Design FOSDEM 2015

Principles of Package Design FOSDEM 2015

Matthias Noback

The PHP world is spinning quite fast these days. There’s a lot to keep up with. You can’t be an expert in all subjects, so you need a way to find out what’s relevant for you and your team. Which approaches to software development would be useful? Which programming paradigms could help you write better code? And which architectural styles will help your application to survive in this quickly changing world? In this talk I’ll help you answer these questions by taking a bird’s-eye view. I will quickly guide you along some of the most fascinating topics in modern PHP development: DDD, BDD, TDD, hexagonal architecture, CQRS, event sourcing and micro-services. We’ll see how these things are related to each other, and how understanding and applying them can help you improve your software projects in many ways.

All the cool kids....

All the cool kids....

All the cool kids....

Matthias Noback

Of course, you should read all you can about SOLID, Design patterns, Patterns of Enterprise Application Architecture, etc. Once you have a basic understanding of these topics you still have to write that code though, and write it well too! What is good code? Are there some guidelines, or rules of thumb, which you can follow while making your everyday coding decisions? In this talk I’ll cover many of these coding guidelines, which aren’t usually covered by patterns or principles books. They should help you write better code and give you a richer vocabulary for reviewing other people’s code. Some of the subjects that we’ll discuss are: state, mutability, CQS, one-method objects, domain-first, API-driven, functional programming influences, object boundaries, (de)serialization, and many more!

Beyond design patterns and principles - writing good OO code

Beyond design patterns and principles - writing good OO code

Beyond design patterns and principles - writing good OO code

Matthias Noback

In our world there are two kinds of people: developers and managers. The people who don’t earn nearly enough money, given the incredible amount of mind-bending work they do all day, and the people who get way too much money for talking all day (and sending emails of course). Nevertheless, developers and managers - slightly irritated by each other’s presence and radically opposing life goals - need to work together productively, in order to satisfy someone known as “the customer”. Having been a “developer” for years, now I’ve become a “manager” myself. Instead of hating it, I’m slowly embracing it. I’m in a unique position to oversee and (partly) understand what’s going on. I’ll share with you everything I know that will be of vital importance to improve your relationship with any manager nearby. Trying to understand each other (including the omnipotent “customer”) will be key to your personal process of becoming the dev that’s worth their own weight in gold.

Please understand me

Please understand me

Please understand me

Matthias Noback

Commands, events, queries - three types of messages that travel through your application. Some originate from the web, some from the command-line. Your application sends some of them to a database, or a message queue. What is the ideal infrastructure for an application to support this on-going stream of messages? What kind of architectural design fits best? This talk provides answers to these questions: we take the *hexagonal* approach to software architecture. We look at messages, how they cross boundaries and how you can make steady communication lines between your application and other systems, like web browsers, terminals, databases and message queues. You will learn how to separate the technical aspects of these connections from the core behavior of your application by implementing design patterns like the *command bus*, and design principles like *dependency inversion*.

Hexagonal architecture - message-oriented software design

Hexagonal architecture - message-oriented software design

Hexagonal architecture - message-oriented software design

Matthias Noback

If you’re a programmer you make design decisions every second. Statements, functions, classes, packages, applications, even entire systems: you need to think, and often think hard, about everything. Luckily there are many useful design principles, patterns and best practices that you can apply. But some of them merely expose code smells. Others only help you design your classes. And some are applicable to packages only. Wouldn’t it be nice to have some more general, always useful, invariably applicable, foundational design principles? In this talk we’ll look at software from many different perspectives, and while we’re zooming in and out, we’ll discover some of the deeper principles that lie beneath proper object-oriented design. They are the foundation of many of the well-known design patterns and they may even serve as an explanation for code smells.

The Quest for Global Design Principles

The Quest for Global Design Principles

The Quest for Global Design Principles

Matthias Noback

If you’re a programmer you make design decisions every second. You need to think, and often think hard, about everything. Luckily there are many useful design principles and patterns that you can apply. But some of them merely expose code smells. Others only help you design your classes. And some are applicable to packages only. Wouldn’t it be nice to have some more general, always useful, invariably applicable, foundational design principles? In this talk we’ll look at software from many different perspectives, and while we’re zooming in and out, we’ll discover some of the deeper principles that form the basis of proper object-oriented design. After attending this talk you will be able to make better design decisions by reflecting on the stream of messages that is flowing from object to object, and from application to application.

The quest for global design principles (SymfonyLive Berlin 2015)

The quest for global design principles (SymfonyLive Berlin 2015)

The quest for global design principles (SymfonyLive Berlin 2015)

Matthias Noback

Before Symfony was spelled with a capital “S” there was another symfony, the first version of the framework. It already meant a lot to me at the time. But with the arrival of Symfony 2 it became clear that something very important was happening in the world of PHP programming. It appears that this framework is able to turn amateur website makers (like I used to be) into actual software developers. What is the secret? What makes Symfony so special? And why am I still hooked? We’ll look at pieces of code, the Symfony ecosystem, the people behind it, the things that have been written about it, and the experience that I have with it. We’ll take a trip down memory lane, collecting pieces for our Symfony scrapbook, while we try to construct an answer to these questions.

How Symfony changed my life (#SfPot, Paris, 19th November 2015)

How Symfony changed my life (#SfPot, Paris, 19th November 2015)

How Symfony changed my life (#SfPot, Paris, 19th November 2015)

Matthias Noback

Commands, events, queries - three types of messages that travel through your application. Some originate from the web, some from the command-line. Your application sends some of them to a database, or a message queue. What is the ideal infrastructure for an application to support this on-going stream of messages? What kind of architectural design fits best? This talk provides answers to these questions: we take the *hexagonal* approach to software architecture. We look at messages, how they cross boundaries and how you can make steady communication lines between your application and other systems, like web browsers, terminals, databases and message queues. You will learn how to separate the technical aspects of these connections from the core behavior of your application by implementing design patterns like the *command bus*, and design principles like *dependency inversion*.

Hexagonal architecture message-oriented software design

Hexagonal architecture message-oriented software design

Hexagonal architecture message-oriented software design

Matthias Noback

With many great tools available for sharing packages of PHP code, it is now up to you as a developer to design these packages well. You have to decide what to put in a package, when to split a package and on what other packages you can safely depend. You will learn how to make good decisions about your package design and release reliable, highly usable and therefore highly esteemed packages of PHP code.

Principles of Package Design (PHPCon Poland 2015)

Principles of Package Design (PHPCon Poland 2015)

Principles of Package Design (PHPCon Poland 2015)

Matthias Noback

Fisica

Trabajo de ingles

Trabajo de ingles

Trabajo de ingles

Viewers also liked (19)

Dutch PHP Conference 2015 - The quest for global design principles

Dutch PHP Conference 2015 - The quest for global design principles

Dutch PHP Conference 2015 - The quest for global design principles

The journey behind a child of mine

The journey behind a child of mine

The journey behind a child of mine

A Series of Fortunate Events - PHP Benelux Conference 2015

A Series of Fortunate Events - PHP Benelux Conference 2015

A Series of Fortunate Events - PHP Benelux Conference 2015

Blooming shibazakura flowers in japan

Blooming shibazakura flowers in japan

Blooming shibazakura flowers in japan

The Naked Bundle - Symfony Live London 2014

The Naked Bundle - Symfony Live London 2014

The Naked Bundle - Symfony Live London 2014

Causes of delay and cost overruns in construction of groundwater projects in ...

Causes of delay and cost overruns in construction of groundwater projects in ...

Causes of delay and cost overruns in construction of groundwater projects in ...

The quest for global design principles - PHP Benelux 2016

The quest for global design principles - PHP Benelux 2016

The quest for global design principles - PHP Benelux 2016

Principles of Package Design FOSDEM 2015

Principles of Package Design FOSDEM 2015

Principles of Package Design FOSDEM 2015

All the cool kids....

All the cool kids....

All the cool kids....

Beyond design patterns and principles - writing good OO code

Beyond design patterns and principles - writing good OO code

Beyond design patterns and principles - writing good OO code

Please understand me

Please understand me

Please understand me

Hexagonal architecture - message-oriented software design

Hexagonal architecture - message-oriented software design

Hexagonal architecture - message-oriented software design

The Quest for Global Design Principles

The Quest for Global Design Principles

The Quest for Global Design Principles

The quest for global design principles (SymfonyLive Berlin 2015)

The quest for global design principles (SymfonyLive Berlin 2015)

The quest for global design principles (SymfonyLive Berlin 2015)

How Symfony changed my life (#SfPot, Paris, 19th November 2015)

How Symfony changed my life (#SfPot, Paris, 19th November 2015)

How Symfony changed my life (#SfPot, Paris, 19th November 2015)

Hexagonal architecture message-oriented software design

Hexagonal architecture message-oriented software design

Hexagonal architecture message-oriented software design

Principles of Package Design (PHPCon Poland 2015)

Principles of Package Design (PHPCon Poland 2015)

Principles of Package Design (PHPCon Poland 2015)

Fisica

Trabajo de ingles

Trabajo de ingles

Trabajo de ingles

Forms

1. forms TNS PhotoGraphics

4. 07080531b 44

5. 07081360cw 55

6. 080526a15c3 66

7. C080428-91cw3 77

8. 07080558b 88

9. 07080571BcD 99

10. 05061229b 1010

11. 070424a5 1111

12. 07080573b 1212

13. 080712219w 1313

14. 080714-10e 1414

15. 080712274q 1515

16. 07081363C2bCQ 1616

17. 080410151c 1717

18. 07081355RQC 1818

19. 080406C-79w 1919

20. 07081371w 2020

21. 07042818www 2121

22. 080712275qRC 2222

23. 080714-03PQ 2323

24. 07081365Cq 2424

25. 07042831qw0 2525

26. C080425127wq 2626

27. 07080586Q 2727

28. 06081140Zw 2828

29. 07042487zQs 2929

30. 010111-005q 3030

31. 04101753RCQCQmq 3131

32. 07031712CQZ 3232

33. 05061316q 3333

34. 845418S2-anC2NQC 3434

35. 07082332C 3535

36. 07082314Cq 3636

37. 07012736zq 3737

38. 06070819zRCQ 3838

39. 05101056q 3939