TDD - Inevitable Challenge for Software Developers (phpkonf15 keynote)

Jul 28, 2015283 likes13,301 views

Lemi Orhan Ergin

These are the slides of my keynote talk on the second day of PHPKonf15 conference.

TDD - Inevitable Challenge for Software Developers (phpkonf15 keynote)

This document discusses how to improve motivation in agile work environments. It argues that money does not lead to engagement and that practices focusing on human relationships and professionalism are more effective. These include building trust, collaboration, mentorship, positive feedback, and ensuring teams have purpose and fun. Adopting a mindset of servant leadership and allowing people to invest in themselves can help foster motivation.

Trespassing The Forgotten and Abandoned: Ethics in Software DevelopmentLemi Orhan Ergin

Let me guess what you think. You think you are smart, you think you do a good job and you think you really love software development. You think you can program 24 hours a day if you are able to do so. You also think that software development is a profession and you are a member of such a huge great community. You feel proud of what you are belonging to. At this point I am sure that only a very few of you do your profession under the lights of ethics in software development. As in every professions, software development has a common set of ethical values, behaviors and rules. That might be the most forgotten and abandoned area in our profession and my main goal is to trespass it with this presentation. I presented the slides at Voxxed Days Istanbul 2015 Conference on 9th of May, 2015.

Build Features, Not AppsNatasha Murashev

Happy Developer's Guide to the Galaxy: Thinking About Motivation of DevelopersLemi Orhan Ergin

The document discusses how to motivate developers by creating an environment that improves passion, discipline and motivation. It suggests building human-centric practices like Lean, Craftsmanship and Agility that foster collaboration, continuous learning, trust and empowerment. Mindset is more important than tools, and managers must provide safe environments for trial and error to encourage innovation.

Java Exception Handling Best Practices - Improved Second VersionLemi Orhan Ergin

Git and Git Workflow Models as Catalysts of Software DevelopmentLemi Orhan Ergin

Unleashed Power Behind The Myths: Pair Programming (CraftSummit15)Lemi Orhan Ergin

Code Your Agility - Tips for Boosting Technical Agility in Your OrganizationLemi Orhan Ergin

Real world continuous deliverySeb Rose

In this session, I look at the challenges that real companies face when trying to adopt the good practices that fall under the banner of Continuous Delivery. To do this, we’ll start by extracting the core concepts described in the book Continuous Delivery by Jez Humble and Dave Farley, and look at how these map to the practices of typical organisations today. We’ll dig deep into the relationship between Agile and Continuous Delivery, how DevOps and infrastructure-as-code fit into the delivery process, and its impact on software development practices, especially version control.

A Beginners Guide to noSQLMike Crabb

Teoriden Pratiğe Mikroservisler - Özgür Web Teknolojileri Günü 2014Lemi Orhan Ergin

Fix Your Broken Windows With Code Reviews - phpist14Lemi Orhan Ergin

Best Practices in Exception HandlingLemi Orhan Ergin

Mobile-First SEO - The Marketers Edition #3XEDigitalAleyda Solís

Fear Driven DevelopmentRyan Kennedy

How Do You Build Software? Software Engineering Practices of an Agile DeveloperLemi Orhan Ergin

Global Day of Coderetreat'14 - Istanbul EventLemi Orhan Ergin

Professional Code of Ethics in Software EngineeringLemi Orhan Ergin

Coderetreat - Practice to Master Your CraftsLemi Orhan Ergin

The ProgrammerKevlin Henney

Keynote presented at SDD (12th May 2015) Somewhere in the heart of a development process, essential to the very being of a product's existence, are the people who write, consider and wrestle with code. What motivates and demotivates them? What are the intellectual challenges and rewards? What are the skills they have and need and cognitive biases and environment they work with and against? This talk by the editor of 97 Things Every Programmer Should Know considers the act of programming and those who do it and want to get better at it, from the perspective of development process to craft, from architecture to code.

Working With Big DataSeth Familian

This document outlines Seth Familian's presentation on working with big data. It discusses key concepts like what constitutes big data, popular tools for working with big data like Splunk and Segment, and techniques for building dashboards and inferring customer segments from large datasets. Specific examples are provided of automated data flows that extract, load, transform and analyze big data from various sources to generate insights and populate customized dashboards.

Creative Traction Methodology - For Early Stage StartupsTommaso Di Bartolo

The document discusses the Creative Traction Methodology (CTM) for gaining traction for new products and ideas. CTM has three parts: 1) The Idea Release Life Cycle which emphasizes validating ideas before development and engaging communities early. 2) Ransack Tools which means leveraging new growth hacking strategies and tools. 3) Act Creatively which involves lateral thinking with no biases to attract niche audiences and validate assumptions through experimentation. The document provides examples and case studies for applying each part of CTM.

Study: The Future of VR, AR and Self-Driving CarsLinkedIn

We asked LinkedIn members worldwide about their levels of interest in the latest wave of technology: whether they’re using wearables, and whether they intend to buy self-driving cars and VR headsets as they become available. We asked them too about their attitudes to technology and to the growing role of Artificial Intelligence (AI) in the devices that they use. The answers were fascinating – and in many cases, surprising. This SlideShare explores the full results of this study, including detailed market-by-market breakdowns of intention levels for each technology – and how attitudes change with age, location and seniority level. If you’re marketing a tech brand – or planning to use VR and wearables to reach a professional audience – then these are insights you won’t want to miss.

Clean Software Design: The Practices to Make The Design SimpleLemi Orhan Ergin

The document discusses principles for clean software design. It outlines 5 principles: 1) Tests should always pass to prove the system works as required; 2) Code should express intent through clear naming and avoiding generic names; 3) Keep methods and classes small in size; 4) Find and remove duplications in code and knowledge; 5) Align abstraction levels and avoid leaky abstractions that expose implementation details. It provides examples for each principle and cautions against anti-patterns like singletons and premature optimization. The document advocates code practices like refactoring, pair programming, and code reviews to achieve clean design.

Unwritten Manual for Pair ProgrammingLemi Orhan Ergin

This document discusses pair programming and provides guidance on how to effectively implement it. It begins by explaining the purpose of pair programming is to produce high quality software. It then discusses various pairing techniques like ping-pong pairing and mob programming. The document also identifies benefits like higher quality code and faster defect removal, as well as challenges like being tiring. Finally, it provides tips for making pairing work well such as starting with a defined task, switching roles frequently, and not forcing people who strongly dislike pairing.

10 Faulty Behaviors of Code Review - Developer Summit Istanbul 2018Lemi Orhan Ergin

The document outlines 10 faulty behaviors that can occur during the code review process and provides recommendations to address each one. The behaviors include having no standards for code reviews in the team, providing ambiguous content for review, selecting the wrong reviewers, requesting feedback too late in the process, not understanding what the code change is doing, treating the code as solely the author's work, trying to prove others are wrong instead of having constructive discussions, not being able to convince others with review comments, reviewers not providing feedback on pull requests, and prematurely merging pull requests before the review is finished. For each behavior, the document recommends actions like establishing review standards and processes, providing better context for reviews, selecting appropriate reviewers, reviewing code earlier, adding tests

More Related Content

Viewers also liked (19)

Java Exception Handling Best Practices - Improved Second VersionLemi Orhan Ergin

Git and Git Workflow Models as Catalysts of Software DevelopmentLemi Orhan Ergin

Unleashed Power Behind The Myths: Pair Programming (CraftSummit15)Lemi Orhan Ergin

Code Your Agility - Tips for Boosting Technical Agility in Your OrganizationLemi Orhan Ergin

Real world continuous deliverySeb Rose

A Beginners Guide to noSQLMike Crabb

Teoriden Pratiğe Mikroservisler - Özgür Web Teknolojileri Günü 2014Lemi Orhan Ergin

Fix Your Broken Windows With Code Reviews - phpist14Lemi Orhan Ergin

Best Practices in Exception HandlingLemi Orhan Ergin

Mobile-First SEO - The Marketers Edition #3XEDigitalAleyda Solís

Fear Driven DevelopmentRyan Kennedy

How Do You Build Software? Software Engineering Practices of an Agile DeveloperLemi Orhan Ergin

Global Day of Coderetreat'14 - Istanbul EventLemi Orhan Ergin

Professional Code of Ethics in Software EngineeringLemi Orhan Ergin

Coderetreat - Practice to Master Your CraftsLemi Orhan Ergin

The ProgrammerKevlin Henney

Working With Big DataSeth Familian

Creative Traction Methodology - For Early Stage StartupsTommaso Di Bartolo

Study: The Future of VR, AR and Self-Driving CarsLinkedIn

Java Exception Handling Best Practices - Improved Second VersionLemi Orhan Ergin

Git and Git Workflow Models as Catalysts of Software DevelopmentLemi Orhan Ergin

Unleashed Power Behind The Myths: Pair Programming (CraftSummit15)Lemi Orhan Ergin

Code Your Agility - Tips for Boosting Technical Agility in Your OrganizationLemi Orhan Ergin

Real world continuous deliverySeb Rose

A Beginners Guide to noSQLMike Crabb

Teoriden Pratiğe Mikroservisler - Özgür Web Teknolojileri Günü 2014Lemi Orhan Ergin

Fix Your Broken Windows With Code Reviews - phpist14Lemi Orhan Ergin

Best Practices in Exception HandlingLemi Orhan Ergin

Mobile-First SEO - The Marketers Edition #3XEDigitalAleyda Solís

Fear Driven DevelopmentRyan Kennedy

How Do You Build Software? Software Engineering Practices of an Agile DeveloperLemi Orhan Ergin

Global Day of Coderetreat'14 - Istanbul EventLemi Orhan Ergin

Professional Code of Ethics in Software EngineeringLemi Orhan Ergin

Coderetreat - Practice to Master Your CraftsLemi Orhan Ergin

The ProgrammerKevlin Henney

Working With Big DataSeth Familian

Creative Traction Methodology - For Early Stage StartupsTommaso Di Bartolo

Study: The Future of VR, AR and Self-Driving CarsLinkedIn

More from Lemi Orhan Ergin (17)

Clean Software Design: The Practices to Make The Design SimpleLemi Orhan Ergin

Unwritten Manual for Pair ProgrammingLemi Orhan Ergin

10 Faulty Behaviors of Code Review - Developer Summit Istanbul 2018Lemi Orhan Ergin

Yeni Nesil Yazılım Kültürü: Daha İyi Profesyoneller, Daha Kaliteli Yazılım, D...Lemi Orhan Ergin

Irresponsible Disclosure: Short Handbook of an Ethical DeveloperLemi Orhan Ergin

Ethics... It could be the most important and underrated topic in software industry. It is directly related with professionalism, craftsmanship and professional discipline. From time to time we have to jump into the discussions, however we never discuss it deeper. I have found himself in a huge blast of discussions when he tweeted about a **HUGE** security issue at the most popular operating system. Then I had deep thoughts about ethics and the behaviours of ethical developers. In this session I talk about the followings: * I refer to real-life stories of many good practices for professional ethics that are critical in the software development world. * I mention technical and non-technical aspects of being an ethical developer. * I deep dive into the arguments against the ethical controversies and the debate over the sharing of a major error in MacOS via Twitter.

Scrum Events and Artifacts in ActionLemi Orhan Ergin

DevOps & Technical Agility: From Theory to PracticeLemi Orhan Ergin

Fighting with Waste Driven Development - XP Days Ukraine 2017Lemi Orhan Ergin

This document discusses lean thinking for software developers. It begins by outlining some common mindsets in software development that lead to waste, such as being overconfident and not having enough time for testing and refactoring. It then discusses various types of waste found in software development processes. The document advocates adopting a lean mindset to maximize value for customers by removing waste through practices like test-driven development, refactoring continuously, and making codebases clean through frequent short releases. It concludes by discussing the need for changes in culture and mindset to fully embrace lean software development.

Git Anti Patterns - XP Days Ukraine 2017Lemi Orhan Ergin

1. The document discusses various good and bad practices for using Git, including committing early and often, squashing commits before merging, and avoiding long-lived topic branches. 2. It recommends splitting large features into small shippable tasks, committing changes early and often without worrying about compilation or CI, and rebasing regularly to integrate changes from the main branch. 3. Changes should be "perfected" later by squashing commits and making the history a single commit before merging back to the main branch when tests pass and code is reviewed.

Waste Driven Development - Agile Coaching Serbia MeetupLemi Orhan Ergin

This document discusses lean thinking and waste-driven development for software developers. It argues that traditional software development practices lead to a lot of waste, including defects, rework, slow development cycles, and lack of value delivery to customers. It promotes applying lean principles from manufacturing to software development, such as focusing on value delivery, eliminating waste, keeping codebases small and modular, automating everything, having high transparency, and challenging common paradigms. Documentation is identified as a particular type of waste.

Git Anti-Patterns - Extended Version With 28 Common Anti-Patterns) - SCTurkey...Lemi Orhan Ergin

This document discusses common Git anti-patterns and provides recommendations to avoid them. It begins by explaining how Git works under the hood in terms of files, folders, references, and objects. It then covers 15 specific anti-patterns to avoid, such as treating Git like Dropbox, having long-living topic branches, merging too late without validation, and being afraid to delete branches. For each anti-pattern, it provides alternatives and recommendations, such as splitting work into small tasks, committing early and often, rebasing rather than merging, and deleting merged branches. The overall message is how to use Git properly and cure common issues by following best practices.

Git Anti-Patterns: How To Mess Up With Git and Love it Again - DevoxxPL 2017Lemi Orhan Ergin

This document contains the slides from a presentation on best practices for using Git and avoiding common antipatterns. It discusses how Git works internally and the different objects it uses to store files, references, and commits. It then covers strategies for committing code early and often in small batches, rebasing regularly to integrate changes, squashing commits before merging back to the main branch, and using feature flags to disable unreleased features. The overall message is to leverage Git's power effectively while avoiding long-lived topic branches, loose commit histories, and other issues that can arise from not understanding Git's model.

Yazılım Geliştirme Kültürünün Kodları: Motivasyon, Teknik Mükemmellik ve İnov...Lemi Orhan Ergin

Bugünün acımasız rekabet ortamında hayatta kalabilmek için her şirketin bir yazılım şirketi olması gerekir. Bu çok büyük bir mücadele demek. Kaliteli yazlımcılar işe alınmalı, projeler doğru yönetilmeli ve proje teslim tarihleri belirlenmelidir. Ancak, gerçekte çok farklı bir tabloyla karşılaşıyoruz. Yüzlerce geliştiriciyle iş görüşmesi yapılıyor ancak bulunamıyor. Geliştiricilerden oluşan bir ekip oluşturulsa bile, motivasyonel sorunlar, sürekli artan teknik problemler, iletişim sorunları, inovasyon eksikliği ve işten ayrılmalar ile ediyoruz. Müşteriler, kaçırılan tarihler ve çıktının düşük kalitesi nedeniyle hayal kırıklığına uğruyor. Her yazılım geliştirme ekibi kendi dinamiklerini yaratır. Çalışanların davranışlarıyla ekiplerin gizli dinamiklerini toplandığımızda şirketteki yazılım geliştirme kültürünü oluşturuyoruz. Bu, bir yazılım geliştirme takımının ne kadar başarılı olabileceğini tanımlayan, en önemli faktörlerden biridir. Bu oturumda, motivasyon, teknik mükemmellik, işbirliği, yardımlaşma, yenilikçilik ve başarı sağlayan bir yazılım geliştirme kültürünün nasıl kurulacağından bahsedeceğim. Yazılım dünyasına girmiş ve ilgilenen herkes katılabilir. Bu sunum Dinamikler 2017 Kongresinde kullanılmıştır.

Git Anti-Patterns: How To Mess Up With Git and Love it AgainLemi Orhan Ergin

Git is one of the most powerful tool in developers' toolbox. If you use it correctly, it dramatically increases productivity of developers and eliminates the waste products continuously. Developers cultivate a development culture on top Git most of the time. It's powerful but its power is untamed. Many teams fall into several traps of misusing commands and therefore feel uncomfortable while using Git. We mess up Git history, the codebase and the whole preferred branching strategy in seconds. We use branches, merge/rebase strategies, creating commits in wrong ways. Even we never take committing paradigms into account while using Git. As a software craftsman, I've been using Git for years and I've already educated Git to hundreds of developers in all levels. I'm so lucky; I had a chance to experience huge amount of anti-patterns in time. In this talk, I will talk about what those anti-patterns are and what should we do in order not to fall into them.

Clean Software Design - DevNot Summit Istanbul 2017Lemi Orhan Ergin

Let The Elephants Leave The Room - Tips For Making Your Development Life LeanerLemi Orhan Ergin

A Gentle Introduction to Micro Services - From Theory into PracticeLemi Orhan Ergin