"PHP Code Avengers: Structuring, Refactoring, and Superhero Practices", Vladyslav Sikailo

•

0 gostou•182 visualizações

In the world of PHP development, we often find ourselves facing the challenge of dealing with bloated, monolithic classes that hinder testability, extensibility, and maintainability. This talk aims to guide PHP developers through the process of overcoming the problem of unwieldy classes by employing effective structuring, refactoring techniques, and industry best practices.

Tecnologia

1. Realize the problems
2. Understand what to do and how to do
3. Celebrate success 🍻

Problems
- They do too much
God classes
- They hold too much
- Difficult to read, maintain and extend
- Responsibility is too wide
- Violates SRP

Problems
- They do too much
Long functions
- They hold too much
- Difficult to read, maintain and extend
- Responsibility is too wide
- Violates SRP

Problems
- Familiar parts of code in several places
Code duplication
- Need to apply the changes in several places
- Forged to apply somewhere - inconsistent system
- Leads to bugs

Problems
- No standards for a structure
Poor structure
- Difficulty in Understanding
- Maintenance Challenges
- Reinvent the wheel

Problems
- No documentation
Bad documentation
- Outdated documentation
- Difficult to understanding the system
- Onboarding Challenges
- Maintainability issues

Problems
- Difficult to understand
Lack of modularity
- Difficult to extend
- Difficult to maintain

Software Development Costs: Bugfixing
https://blog.pdark.de/2012/07/21/software-development-costs-bugfixing/

4. Make it platform agnostic
2. Understand responsibilities
3. Split by purpose
6. Documentation
1. Follow Coding Standards
5. Apply Design Patterns
List of approaches
7. Cover it by Tests

4. Copy Paste Detector (phpcpd)
2. PSR-1, PSR-2, PSR-12
3. PHPStan, Psalm
6. CI/CD is a must
1. PHP Code Style (phpcs)
5. PHP Mess Detector (phpmd)
Must use
7. Rector, PHP CS Fixer
8. …

4. Low coupling, high cohesion!
2. What is the role of the class?
3. KISS 💋 (and focused)
1. What does the class do?
Think about

1. Easy to read
2. Easy to maintain
3. Easy to reuse
4. Easy to test
Benefits of focused components

- Entity
- Value Object
- Repository
- DTO
Most used types
- Validator
- Data Provider
- Mapper
- Service

4. Unaware of context
2. Stateless Operations
3. Сover one domain use-case
1. Domain-Focused Logic
Service

1. Difficult to replace framework
2. Difficult to replace environment
3. Difficult to split by module
4. Code lives as long as framework
Problems

https://codeopinion.com/design-patterns-who-gives-a/
Patterns
usage

4. Use proper naming
2. Think twice before use
3. Focus on commonly used patterns
1. Be careful!
5. Anti-Patterns
Patterns

- Docs near the code
2. Docs as Code
- Docs under version control
1. Avoid meaningless PHPDocs
3. Document interaction with integrations
Documentation
4. Architecture Decision Record

4. Think as a test
2. Tests are the part of documentation
3. Safe refactoring
1. Early find problems
Tests

2. Component tests
3. Integration tests
1. Unit tests
Commonly used tests types

2. Easy to read and understand
3. Reduced Bugs and Errors
1. Maintainability
4. Scalability
Pros

2. Learning
3. Over-Engineering
1. Initial Overhead
4. Initial Investment in Tooling
Cons

Recomendados

Code smells quality of code

Hasan Al Mamun

How to guarantee your change is integrated to Moodle core

Dan Poltawski

What's the "right" PHP Framework?

Barry Jones

Pull request review

Ketan Ghumatkar

sitHVR - The Hitchhikers Guide to the Legacy

Laurens van Rijn

Reading Notes : the practice of programming

Juggernaut Liu

sitBRU - The Hitchhikers Guide to the Legacy

Laurens van Rijn

Dev Ops for systems of record - Talk at Agile Australia 2015

Mirco Hering

Php traits

Shaun Morrow

Traits in PHP allow for sharing of methods among classes without instantiation. They provide a way to reuse code and reduce duplication. Traits are included using the 'use' keyword and resolve at compile time, making them highly coupled and difficult to test in isolation. While traits can achieve multiple inheritance, their inflexibility means other patterns like dependency injection are often preferable. Traits should be used sparingly to share simple functionality rather than as a primary means of code organization.

Surviving the technical interview

Eric Brooke

Technical interviews often do not reflect the actual day-to-day work of a job and require a unique set of skills. The document provides advice on preparing for technical interviews, which may involve coding challenges, algorithms, data structures, frameworks and languages. It recommends practicing core skills, gaining interview experience through mock interviews, and learning from every interview. The goal is to be able to think through problems and code solutions calmly under pressure.

Performance testing presentation

Belatrix Software

1.2 Evaluation of PLs.ppt

meenabairagi1

This document discusses several factors that influence the cost of developing software in different programming languages. It addresses criteria for evaluating languages, including readability, writability, simplicity, reliability, and expressive power. These criteria impact total software costs through their effects on training time, development time, compilation/execution time, maintenance needs, and reliability. The document also examines how language features like abstraction, orthogonality, structured control, and type checking can improve readability, writability and reliability.

Functional Solid, Aleksandr Sugak

Sigma Software

The document discusses applying SOLID principles to functional programming (FP). It argues that SOLID is often interpreted as being about object-oriented programming (OOP), but its goals of encapsulation, separation of concerns, and low coupling can also be achieved in FP. Extreme application of SOLID in OOP can result in many small, single-method classes and interfaces along with pervasive use of decorators, but FP approaches this through functions, function composition, and type signatures, leading to simpler code. An example message store implementation in F# demonstrates how SOLID is realized through types and pure functions in a functional style.

Functional solid

Alexandr Sugak

The document discusses applying SOLID principles to functional programming (FP). It argues that SOLID is often interpreted as being about object-oriented programming (OOP), but its goals of encapsulation, separation of concerns, and low coupling can also be achieved in FP. Extreme application of SOLID in OOP can result in many small, single-method classes and interfaces along with pervasive use of decorators, but FP approaches this through functions, function composition, and type signatures, leading to simpler code. An example message store implementation in F# demonstrates how FP facilitates applying SOLID principles through types and composition.

scale_perf_best_practices

webuploader

The document discusses best practices for scalability and performance when developing PHP applications. Some key points include profiling and optimizing early, cooperating between development and operations teams, testing on production-like data, caching frequently accessed data, avoiding overuse of hard-to-scale resources, and using compiler caching and query optimization. Decoupling applications, caching, data federation, and replication are also presented as techniques for improving scalability.

Guide to Destroying Codebases The Demise of Clever Code

Gabor Varadi

Optimizing your development process with Adobe Commerce

Rafael Corrêa Gomes

7 steps to migrate from SAP PI to PO/PRO

Daniel Graversen

ITARC15 Workshop - Architecting a Large Software Project - Lessons Learned

João Pedro Martins

11 scripting languages

cherrybear2014

This document discusses scripting languages and their key characteristics. Scripting languages are generally interpreted rather than compiled, allowing for rapid development and changes. They have built-in support for high-level structures and libraries. Python uses a combination of compilation and interpretation through bytecode. Scripting languages are often used to combine the functionality of other programs by acting as an intermediary between them. They can also extend their functionality by binding existing programs. Many scripting languages support dynamic typing, automatic memory management, object-oriented structures, dynamic code creation, and built-in data structures like associative arrays and lists.

Software development fundamentals

Alfred Jett Grandeza

DevOps Days Vancouver 2014 Slides

Alex Cruise

Speaker: Alex Cruise (Dir. Architecture, Metafor Software) Abstract: The rise of the DevOps movement has brought into welcome focus something that is often learned only through painful experience and expense: the success of a software product critically depends not only on its implementation, maintenance and enhancement, but also on how it’s deployed and operated. Distributed systems are hard, but you can’t escape them: you need to scale out, but wrapping proxy interfaces around remote resources so they look local is a recipe for a fragile system. Plus, as the complexity of components and services increases, local systems aren’t actually as reliable as we think! Concurrency is hard, but you can’t escape it: whether you’re using threads in a single process, or multiple processes on a single machine, you still need to synchronize state between them somehow. Fault tolerance is hard, but you can’t escape it: parts will fail, you need to cope without rebooting the whole application. Correctness is hard, but you can’t escape it: whether through laborious testing or a Sufficiently Advanced Compiler, you need to have some assurance that the software will work as intended. Let’s talk about a set of architectural patterns (and, yes, frameworks) that can really help us achieve the goals of concurrency, fault tolerance and correctness, while affording us the flexibility we need to scale our deployments when we achieve terrifying success.

InterConPHP 2014 - Scaling PHP

Lucas Arruda

Browser Fuzzing with a Twist (and a Shake) -- ZeroNights 2015

Jeremy Brown

The web client is critical software to secure from any perspective. No matter if you're an organization or a casual client, you're typically just as vulnerable as anyone else. OSes are often supplemented with hardening toolsets or built-in mitigations as an extra measure to avoid compromise, but as with all things, they aren't completely solid either. Thus the need for systems that break systems, some of which deploy fuzzing and almost all of them work to find implementation bugs. Browser fuzzing has been explored and improved in many different ways over the past several years. In this presentation, we'll be primarily talking about a mutation engine that provides a somewhat novel technique for finding bugs in a still-ripe attack surface: the browser's rendering engine. This technique has the flexibility to be applied even more broadly than browsers, for example, there's initial support for fuzzing PDF readers. We'll also be discussing the tooling and infrastructure areas of the process, detailing what's needed to build a system that will scale and enable your fuzzing strategies to be successful. Finally, we can conclude the talk with some incubation results and how you can start making use of these fuzzing techniques today to find the bugs you need to exploit browsers or identify and fix the code responsible for each vulnerability.

Writing code for others

Amol Pujari

The document discusses best practices for writing code that is easy for others to read and understand. It recommends writing code with short, clearly named methods; consistent formatting; necessary but not redundant comments; and avoiding issues like deeply nested code, long methods, and unnecessary complexity. The goal is to write code that other programmers can easily and enjoy reading to understand the program's logic and functionality.

10 clues showing that you are doing OSGi in the wrong manner - Jerome Moliere

mfrancis

Good code

Om Vikram Thapa

The document discusses principles for writing good code. It emphasizes that code is a collaborative effort that needs to last a long time and be understood by others. It stresses the importance of writing code that is readable, consistent, avoids complexity, is robust with few side effects, uses proper data types, carefully manages scope, takes a pragmatic approach considering the big picture and platform, and follows principles like error handling, exceptions, avoiding re-invention, and keeping code maintainable according to the boy scout rule. Suggested further reading on the topic is also provided.

NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund

Karel Zikmund

"What I learned through reverse engineering", Yuri Artiukh

Fwdays

"Impact of front-end architecture on development cost", Viktor Turskyi

Fwdays

I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.

Mais conteúdo relacionado

Semelhante a "PHP Code Avengers: Structuring, Refactoring, and Superhero Practices", Vladyslav Sikailo

Php traits

Shaun Morrow

Surviving the technical interview

Eric Brooke

Performance testing presentation

Belatrix Software

1.2 Evaluation of PLs.ppt

meenabairagi1

Functional Solid, Aleksandr Sugak

Sigma Software

Functional solid

Alexandr Sugak

The document discusses applying SOLID principles to functional programming (FP). It argues that SOLID is often interpreted as being about object-oriented programming (OOP), but its goals of encapsulation, separation of concerns, and low coupling can also be achieved in FP. Extreme application of SOLID in OOP can result in many small, single-method classes and interfaces along with pervasive use of decorators, but FP approaches this through functions, function composition, and type signatures, leading to simpler code. An example message store implementation in F# demonstrates how FP facilitates applying SOLID principles through types and composition.

scale_perf_best_practices

webuploader

Guide to Destroying Codebases The Demise of Clever Code

Gabor Varadi

Optimizing your development process with Adobe Commerce

Rafael Corrêa Gomes

7 steps to migrate from SAP PI to PO/PRO

Daniel Graversen

ITARC15 Workshop - Architecting a Large Software Project - Lessons Learned

João Pedro Martins

11 scripting languages

cherrybear2014

Software development fundamentals

Alfred Jett Grandeza

DevOps Days Vancouver 2014 Slides

Alex Cruise

InterConPHP 2014 - Scaling PHP

Lucas Arruda

Browser Fuzzing with a Twist (and a Shake) -- ZeroNights 2015

Jeremy Brown

Writing code for others

Amol Pujari

10 clues showing that you are doing OSGi in the wrong manner - Jerome Moliere

mfrancis

Good code

Om Vikram Thapa

NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund

Karel Zikmund

Semelhante a "PHP Code Avengers: Structuring, Refactoring, and Superhero Practices", Vladyslav Sikailo (20)

Php traits

Surviving the technical interview

Performance testing presentation

1.2 Evaluation of PLs.ppt

Functional Solid, Aleksandr Sugak

Functional solid

scale_perf_best_practices

Guide to Destroying Codebases The Demise of Clever Code

Optimizing your development process with Adobe Commerce

7 steps to migrate from SAP PI to PO/PRO

ITARC15 Workshop - Architecting a Large Software Project - Lessons Learned

11 scripting languages

Software development fundamentals

DevOps Days Vancouver 2014 Slides

InterConPHP 2014 - Scaling PHP

Browser Fuzzing with a Twist (and a Shake) -- ZeroNights 2015

Writing code for others

10 clues showing that you are doing OSGi in the wrong manner - Jerome Moliere

Good code

NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund

Mais de Fwdays

"What I learned through reverse engineering", Yuri Artiukh

Fwdays

"Impact of front-end architecture on development cost", Viktor Turskyi

Fwdays

"Micro frontends: Unbelievably true life story", Dmytro Pavlov

Fwdays

"Objects validation and comparison using runtime types (io-ts)", Oleksandr Suhak

Fwdays

"JavaScript. Standard evolution, when nobody cares", Roman Savitskyi

Fwdays

"How Preply reduced ML model development time from 1 month to 1 day",Yevhen Y...

Fwdays

"GenAI Apps: Our Journey from Ideas to Production Excellence",Danil Topchii

Fwdays

In my talk, I will tell about the world of GenAI services beyond GPT-wrappers and how we developed and scaled GenAI-centric applications. I'll share personal experiences about the obstacles, lessons, and strategic tools and methodologies that were key in taking GenAI applications from 0 to 1. I'll talk about the challenges we faced when launching LLM-based and image generative applications and delivering them to end users, and what conclusions and solutions were made.

"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...

Fwdays

Python engineers are introduced to the transformative potential of Large Language Models (LLMs) in the realm of advanced data analysis and the application of Semantic Kernel techniques. We will talk about how LLMs like ChatGPT can be integrated into Python environments to automate data processing, enhance predictive modeling, and unlock deeper insights from complex datasets. The session will delve into practical strategies for embedding Semantic Kernel methods within Python projects, illustrating how these advanced techniques can refine the accuracy of machine learning models by embedding domain-specific knowledge directly into the analysis process. Attendees will leave with a clear roadmap for leveraging the combined power of LLMs and Semantic Kernels, equipped with actionable knowledge to drive innovation in their data analysis projects and beyond, marking a significant leap forward in the evolution of Python engineering practices.

"Federated learning: out of reach no matter how close",Oleksandr Lapshyn

Fwdays

"What is a RAG system and how to build it",Dmytro Spodarets

Fwdays

"Debugging python applications inside k8s environment", Andrii Soldatenko

Fwdays

"ML in Production",Oleksandr Bagan

Fwdays

"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack

Fwdays

Ever seen a code base where understanding a simple method meant jumping through tangled class hierarchies? We all have! And while "Favor composition over inheritance!" is almost as old as object-oriented programming, strictly avoiding all types of subclassing leads to verbose, un-Pythonic code. So, what to do? The discussion on composition vs. inheritance is so frustrating because far-reaching design decisions like this can only be made with the ecosystem in mind – and because there's more than one type of subclassing! Let's take a dogma-free stroll through the types of subclassing through a Pythonic lens and untangle some patterns and trade-offs together. By the end, you'll be more confident in deciding when subclassing will make your code more Pythonic and when composition will improve its clarity.

"Distributed graphs and microservices in Prom.ua", Maksym Kindritskyi

Fwdays

The current architecture of Prom.ua is built on microservices and GraphQL API, but it was not always like that. In this talk, I'll tell you how far we've come and how we've made using graphs in a microservice architecture convenient and simple. I will talk about the problems we faced and how we overcame them, made our development process more accessible, deployments faster, and the remains of the monolith less loaded.

"Rethinking the existing data loading and processing process as an ETL exampl...

Fwdays

ETL stands for extract, transform, load. It's a process that combines data from different sources into a single repository for further processing, analysis, and utilization. This talk provides an example of how pandas can be used to solve ETL tasks as a stage in the evolution of the data intake component. This involves preliminary validation, filtering, and conversion of data according to a set of business rules and internal representation, with intermediate combination with other sources.

"How Ukrainian IT specialist can go on vacation abroad without crossing the T...

Fwdays

I’m confident that many IT professionals are currently facing the same situation I was in a few months ago. Mobilization, uncertainty. How can I be maximally beneficial to the country with my experience and continue professional development in such circumstances? Since the onset of the full-scale invasion, I've been actively volunteering and assisting the army. Mobilization became the next logical step. I want to share: My journey in IT, volunteering, and the beginning of my service in the Armed Forces Impressions from the first few months Which Soft Skills are helpful in this context I aim to dispel myths about the mobilization process and projects of the Armed Forces. Address your questions And yes, military personnel can travel abroad during their leave.

"The Strength of Being Vulnerable: the experience from CIA, Tesla and Uber", ...

Fwdays

The leader must be strong all the time. The leader cannot afford to make mistakes, let alone fail in front of their team. Is that really true? Nick Gicinto, a cybersecurity leader with over 25 years of experience, who has worked for the CIA and has built security systems from scratch at Tesla and Uber, fully hiring teams for these projects, will talk about the importance of being vulnerable to build trust within a team.

"[QUICK TALK] Radical candor: how to achieve results faster thanks to a cultu...

Fwdays

Sharing open feedback can be difficult because it equals much work on yourself. However, feedback needs attention and a special place in the corporate culture. It helps to grow dynamically, build a team of like-minded people and achieve powerful results. In the presentation, I will talk about: The ability to work with feedback as a soft, solid skill in developing technical specialists. A list of difficulties that prevent quality work with feedback. The 4A Framework is a tool for successful giving and receiving feedback. I will also help specialists learn the following: Form constructive feedback and understand how and when to give it. Work analytically with the received feedback. Feel free to share your thoughts and be heard.

"[QUICK TALK] PDP Plan, the only one door to raise your salary and boost care...

Fwdays

Will discuss: Current communication challenges, including mishaps and toxic versus productive interactions. Ever wondered about PDP? It’s likely because its relevance to career planning, even outside your current company, hasn’t been fully spotlighted. Exploring how PDP functions within career planning, applicable even if you’re eyeing an exit. “Who do I aspire to become?” Summarizing key points with a reference to a practical form you can download to use.

"4 horsemen of the apocalypse of working relationships (+ antidotes to them)"...

Fwdays

This talk will reveal four destructive communication patterns that can undermine team spirit, reduce productivity and cause conflict, and offer effective strategies for neutralizing them. Let's start with exciting storytelling about a fictional team of developers working on Scrum. You will learn about situations that their team member noticed during team meetings. Next, we will analyze "The Gottman Four Horsemen" model, which describes the four "horsemen of the apocalypse" of work relationships: criticism, defensiveness, contempt, and stonewalling. For each of these patterns, specific "antidotes" will be offered that allow you to build healthier and more productive relationships in the team. Finally, we'll look at why this topic is critical to team productivity, drawing on Google's "Project Aristotle" research. Special attention will be paid to the concept of psychological safety, which is a key factor in the success of high-performance teams. This talk will not only provide valuable insights and tools for improving communication and management in Tech teams, but will also help each member better understand their own contribution to the overall success of the team.

Mais de Fwdays (20)