OOP - Back to Basic

•Transferir como PPT, PDF•

0 gostou•664 visualizações

G

OOP – Back to Basic! Gøran Hansen Seniorkonsulent, Capgemini http://blog.goeran.no [email_address] Twitter.com/goeran

[object Object]

[object Object],.NET VB.NET C# Ruby Python Silverlight Flash Java ASP.NET MVC Ruby on Rails WPF Azure

[object Object]

[object Object]

[object Object]

[object Object]

[object Object]

[object Object],[object Object]

[object Object],[object Object],[object Object],[object Object]

[object Object],[object Object],[object Object]

[object Object],[object Object],[object Object]

[object Object]

[object Object]

[object Object]

[object Object],[object Object],[object Object],[object Object]

OOP – Back to Basic! Gøran Hansen Seniorkonsulent, Capgemini http://blog.goeran.no [email_address] Twitter.com/goeran

Mais conteúdo relacionado

Semelhante a OOP - Back to Basic

OSCon - Performance vs Scalability

OSCon - Performance vs Scalability

OSCon - Performance vs Scalability

Solid principle

Solid principle

Solid principle

muhammadali0014

Solid

Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)

Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)

Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)

Solid principes

Solid principes

Solid principes

Functional Solid, Aleksandr Sugak

Functional Solid, Aleksandr Sugak

Functional Solid, Aleksandr Sugak

Functional solid

Functional solid

Functional solid

Abstract: SOLID is a mnemonic acronym coined by Robert C. Martin (aka Uncle Bob) referring to a collection of design principles of object-oriented programming and design. By using these principles, developers are much more likely to create a system that more maintainable and extensible. SOLID can be used to remove code smells by refactoring. In this session, you will learn about the following SOLID principles with code examples demonstrating the corresponding refactoring. S – Single Responsibility Principle – An Object should have only one reason to change. O – Open/Closed Principle – A software entity(module, library, routine) should be closed to any modification but be open to extension L – Liskov Substitution Principle – Derived classes should be substitutable for the base classes I – Interface Segregation Principle – Having more fine grained interfaces over fat interfaces D – Dependency Inversion Principle – Depending on abstractions, not concrete implementations.

SOLID Principles of Refactoring Presentation - Inland Empire User Group

SOLID Principles of Refactoring Presentation - Inland Empire User Group

SOLID Principles of Refactoring Presentation - Inland Empire User Group

Object Oriented Programming Ch3 SRP, DIP, ISP

Object Oriented Programming Ch3 SRP, DIP, ISP

Object Oriented Programming Ch3 SRP, DIP, ISP

Developer Job in Practice

Developer Job in Practice

Developer Job in Practice

S.O.L.I.D. Principles for Software Architects

S.O.L.I.D. Principles for Software Architects

S.O.L.I.D. Principles for Software Architects

Ricardo Wilkins

OO Design Principles

OO Design Principles

OO Design Principles

Anju Kanjirathingal

SOLID principles-Present

SOLID principles-Present

SOLID principles-Present

Solid as OOP abstraction

Solid as OOP abstraction

Solid as OOP abstraction

Common design principles and design patterns in automation testing

Common design principles and design patterns in automation testing

Common design principles and design patterns in automation testing

Solid principles

Solid principles

Solid principles

Kumaresh Chandra Baruri

S.O.L.I.D. principles of software development

S.O.L.I.D. principles of software development

S.O.L.I.D. principles of software development

Design poo my_jug_en_ppt

Design poo my_jug_en_ppt

Design poo my_jug_en_ppt

PHPConf Asia 2018 Workshop by Junade Ali It’s no secret that software is often written poorly. In commercial environments, developers will regularly find themselves facing technical debt and find that the ability to refactor code is an essential skill to master. As Martin Fowler famously wrote: "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." Due to bad design in software, delivering value to the client can become ever more difficult and stressful until bad software design decisions are rectified. For developers working on badly designed projects, making repayments on technical debt, whilst also delivering value is a key skill – this session will explain how it is possible to square-the-circle and both deliver value whilst paying down technical debt. Unfortunately far too many developers consider refactoring as a risky task filled with code that’s ridden with var_dumps and debug breakpoints. This session seeks to teach attendees that refactoring can be a safe, everyday task during normal software development and that it is indeed healthy to refactor software mercilessly, especially when operating in an Agile environment with changing software requirements. This session will feature a hands-on demonstration of how to refactor a legacy app through a combination of automated testing, faster releases and merciless refactoring. Practical experience in automated software testing and continuous integration are vital learning outcomes and this session seeks to expose attendees to tools like Docker, PHPUnit, Selenium and PHP Mess Detector. Beyond testing, we’ll cover the Code Smells that help developers weed out where the problematic code is. Gaining a firm grounding in Object-Oriented Programming when refactoring PHP is invaluable and as such, this session will take a deep-dive into Polymorphism, SOLID principles and anti-patterns. After nailing down Object-Orientation, we’ll discuss how we can move legacy software architecture to suitable Design Patterns. Extreme Programming practices will be presented as a key discussion point on how developers can help achieve these goals.

Workshop: Refactoring Legacy PHP: The Complete Guide

Workshop: Refactoring Legacy PHP: The Complete Guide

Workshop: Refactoring Legacy PHP: The Complete Guide

SOLID Principles

SOLID Principles

SOLID Principles

Semelhante a OOP - Back to Basic (20)

OSCon - Performance vs Scalability

OSCon - Performance vs Scalability

OSCon - Performance vs Scalability

Solid principle

Solid principle

Solid principle

Solid

Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)

Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)

Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)

Solid principes

Solid principes

Solid principes

Functional Solid, Aleksandr Sugak

Functional Solid, Aleksandr Sugak

Functional Solid, Aleksandr Sugak

Functional solid

Functional solid

Functional solid

SOLID Principles of Refactoring Presentation - Inland Empire User Group

SOLID Principles of Refactoring Presentation - Inland Empire User Group

SOLID Principles of Refactoring Presentation - Inland Empire User Group

Object Oriented Programming Ch3 SRP, DIP, ISP

Object Oriented Programming Ch3 SRP, DIP, ISP

Object Oriented Programming Ch3 SRP, DIP, ISP

Developer Job in Practice

Developer Job in Practice

Developer Job in Practice

S.O.L.I.D. Principles for Software Architects

S.O.L.I.D. Principles for Software Architects

S.O.L.I.D. Principles for Software Architects

OO Design Principles

OO Design Principles

OO Design Principles

SOLID principles-Present

SOLID principles-Present

SOLID principles-Present

Solid as OOP abstraction

Solid as OOP abstraction

Solid as OOP abstraction

Common design principles and design patterns in automation testing

Common design principles and design patterns in automation testing

Common design principles and design patterns in automation testing

Solid principles

Solid principles

Solid principles

S.O.L.I.D. principles of software development

S.O.L.I.D. principles of software development

S.O.L.I.D. principles of software development

Design poo my_jug_en_ppt

Design poo my_jug_en_ppt

Design poo my_jug_en_ppt

Workshop: Refactoring Legacy PHP: The Complete Guide

Workshop: Refactoring Legacy PHP: The Complete Guide

Workshop: Refactoring Legacy PHP: The Complete Guide

SOLID Principles

SOLID Principles

SOLID Principles

Mais de goeran

Intro til windows 8

Intro til windows 8

Intro til windows 8

Silverlight 4 @ MSDN Live

Silverlight 4 @ MSDN Live

Silverlight 4 @ MSDN Live

The Software Craftsman (2nd edition)

The Software Craftsman (2nd edition)

The Software Craftsman (2nd edition)

The Software Craftsman

The Software Craftsman

The Software Craftsman

Software Craftsmanship @ Ntnu

Software Craftsmanship @ Ntnu

Software Craftsmanship @ Ntnu

MSDN Live: Silverlight 2

MSDN Live: Silverlight 2

MSDN Live: Silverlight 2

MSDN Live: Windows Presentation Foundations Line of Business Apps

MSDN Live: Windows Presentation Foundations Line of Business Apps

MSDN Live: Windows Presentation Foundations Line of Business Apps

Mais de goeran (7)

Intro til windows 8

Intro til windows 8

Intro til windows 8

Silverlight 4 @ MSDN Live

Silverlight 4 @ MSDN Live

Silverlight 4 @ MSDN Live

The Software Craftsman (2nd edition)

The Software Craftsman (2nd edition)

The Software Craftsman (2nd edition)

The Software Craftsman

The Software Craftsman

The Software Craftsman

Software Craftsmanship @ Ntnu

Software Craftsmanship @ Ntnu

Software Craftsmanship @ Ntnu

MSDN Live: Silverlight 2

MSDN Live: Silverlight 2

MSDN Live: Silverlight 2

MSDN Live: Windows Presentation Foundations Line of Business Apps

MSDN Live: Windows Presentation Foundations Line of Business Apps

MSDN Live: Windows Presentation Foundations Line of Business Apps

OOP - Back to Basic

1. OOP – Back to Basic! Gøran Hansen Seniorkonsulent, Capgemini http://blog.goeran.no [email_address] Twitter.com/goeran

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.

16.

17.

18.

19.

20.

21.

22.

23.

24.

25.

26.

27. OOP – Back to Basic! Gøran Hansen Seniorkonsulent, Capgemini http://blog.goeran.no [email_address] Twitter.com/goeran