Creating change from within - DevReach 2012

•

0 likes•557 views

This document discusses how an Agile developer introduced improvements to his team's practices. It describes how he started by analyzing their test code and fixing 40% of the tests. He then set up a continuous integration server to run tests on each commit. He educated the team through various communication methods like code reviews and pair programming. Some immediate improvements included using MSTest and writing tests before fixing bugs. The developer emphasizes that change happens gradually through small incremental steps and passion is needed to convince others.

Technology

Create change from within –
the Agile Developer’s story

Dror Helper | Better Place

About.Me
• Software Developer 9+ years

• Team’s technical lead

• TDD/Unit testing enthusiast

• Some SCRUM/Kanban background

• Blogger – http://blog.drorhelper.com

www.devreach.com

The problem with Agile

We don’t have time
It would never
work in this I don’t want to do this!
project

www.devreach.com

What can one person do?

www.devreach.com

My team 2010
• One manager + 3 developers

• Unit tests – more or less
• Iteration tracking ?
• Manual deployment
• Code reviews

www.devreach.com

My 1st week on the job

www.devreach.com

Step #1 - Analysis
• Took two days to fix 40% of tests

• Find what are the main issues – and focus on them
– Not readable
– Using logic inside test
– Testing too much
– Hand rolled mocks
– Scenarios hiding as unit tests
– Highly coupled code

www.devreach.com

Step #2 – CI Server
Build Server

What’s new?

Commit
There you go

Source Control

www.devreach.com Build Agents

Step #3 - Teach the team

www.devreach.com

Communicate!
• Email
• Phone call
• Face to face
• Presentation
• Code reviews
• Pair programming
• Daily meetings

www.devreach.com

Immediate steps
• MSTest

• Write new test before fixing bug

• Fix existing tests when implementing new features

• Delete obsolete tests

www.devreach.com

Change is iterative
• Hard to perform big changes overnight

• Small incremental changes

www.devreach.com

Today
• More than 5000 tests

• Good code coverage

• Most features are developed using TDD

• CI server run all tests on commit

• Nightly builds

• Change code without fear

www.devreach.com

DECIDING WHAT TO CHANGE

www.devreach.com

Passion is a must!
• Become champion

• Need to convince co-workers

• Survive the road

www.devreach.com

The cost of change
Participants

Maintenance Effort (Time)

Cost of
Change
Emotional
Cost (Money)
Value

Previous
investment

www.devreach.com

Demonstration > Discussion

www.devreach.com

Individual task boards

www.devreach.com

Be pragmatic
• Every action should have a purpose
• If it doesn’t work – change it!
• Names are not important – just what
you do
• Practices can be adapted for the team

Know where to draw the
line
www.devreach.com

TFS + Work item manager

www.devreach.com

What to when change fails?

Understand why it failed
Wait and see
Choose a different path
Cut your losses
www.devreach.com

The right attitude
• Be positive

• Don’t tell them what to so - suggest
improvements

• Don’t force – convince

• Be ready to change if proven wrong

www.devreach.com

Enlist help
Because You cannot do it all by yourself

www.devreach.com

Journey not a destination

www.devreach.com

Thank you!
@dhelper
http://blog.drorhelper.com/
http://www.linkedin.com/in/drorhelper

Dror Helper | Better Place

This document summarizes a presentation about getting the most value from Microsoft's Team Foundation Server (TFS). The presentation covers how TFS can be used for more than just .NET development, including using it for version control of any file type and size. It demonstrates using TFS for work item tracking, linking related items, and using Excel for reporting. The presentation also discusses using TFS for build automation and testing, and leveraging the new "fire and forget" user licensing. It concludes by discussing upcoming improvements to TFS like hierarchical work items and improved branching capabilities.

Kanban in 4 easy steps

Shore Labs

Kanban stand-up meetings

Miroslav Bajtoš

Kanban is a lean methodology for managing workflow. Its core practices include visualizing workflow using a kanban board with columns for different states, limiting work-in-progress to avoid bottlenecks, making policies explicit, and implementing feedback loops to continuously improve. Kanban focuses on managing flow rather than fixed processes, and emphasizes finishing work rather than starting new work. Kanban stand-ups differ from Scrum in that the focus is on identifying impediments rather than commitments.

Automated testing DrupalCamp in Asheville

Promet Source

Promet Solutions specializes in developing complex web applications using open source technologies. They have over 30 solutions architects and have been in business for 10 years, contributing to over 32 open source projects. They have offices in Chicago and San Jose and have developed over 10 mobile apps in the past 12 months. They are presenting on their experience with automated testing for Drupal applications using tools like Selenium and PHPUnit.

Getting Business Exec Buy-in for Architecture Change

Dominica DeGrandis

Front End page speed performance improvements for Drupal

Andy Kucharski

If you are a developer or business manager with responsibilities over your website, then check out this deck.. What will you learn? The webinar, created by our Founder and CEO, Andy Kucharski, is a highly accessible, information-rich review on the ways Drupal site performance can be radically improved. Some of the main topics we will cover include: What is slow site speed? What tools to use to diagnose it. Plus six key improvements to make Drupal “run fast!” And if that’s not already enough, we will also share some best practices monitoring tips for making sure you know how the Drupal server is performing 24/7.

HCM Scrum Breakfast – The real life of Scrumban team

Scrum Breakfast Vietnam

In the general view, Scrum is the best Agile method for building a product and developing projects. However, when we have projects that include production support, we should be advised to combine with Kanban. This provides some ideas about Scrumban. On the one hand, it has the Agile of Scrum, on the other hand it encourages teams to continuously improve their processes along with Kanban. Scrumban is a solution favored by the service industry, and a great project management tool for teams that deal with product development and its maintenance together. In this Scrum Breakfast, we would like to share our real life of Scrumban team that we applied to work with our customers. Topic: The real life of Scrumban team Speaker: Ms. Anh Thu – Scrum Master at Axon Active Vietnam Time: Saturday – 25th Feb, 2016 | 9:00 AM – 11:00AM Venue: Trung Nguyên Cafe, 264A Nam Kỳ Khởi Nghĩa, Ho Chi Minh #scrum #scrumbreakfast #agile #scrumban #AxonActiveVietnam

This document discusses 7 SQL Agent jobs that should be running to monitor a SQL Server environment. It provides background on the presenter, Mike Hillwig, and introduces the topic of using SQL Agent to automate monitoring processes. Example monitoring jobs discussed include checking for auto shrink being enabled, verifying backups are running successfully, and alerting on failed SQL Agent jobs. The presentation aims to provide both introductory information on SQL Agent and specific monitoring jobs and scripts that can be implemented.

Devops down-under

Robert Postill

The document summarizes the speaker's experience with developing and improving the architecture for a Ruby on Rails application hosted on a customer's VMware infrastructure. It describes initial flaws with logging and database issues. It then discusses efforts to improve the architecture using tools like Chef but facing challenges, and moving to a model of customizing VMs using Capistrano scripts. Key lessons learned include the importance of monitoring performance, being aware of virtualization impacts, and hiring strong technical staff.

Kanban Basics for Beginners Revised

Zsolt Fabok

Kanban is a method for visualizing and limiting work in progress to improve flow and productivity. It involves mapping workflows, restricting work items in each stage, and measuring cycle times, lead times and throughput. Kanban boards are used to visualize workflows and work items moving through each stage. Implementing Kanban principles like continuous improvement and making policies explicit can help organizations become better and faster.

From Scrum to Scrumban

John Peltier

This document summarizes John Peltier's experience transitioning from Scrum to Scrumban for product development. Some key points: - Retrospectives revealed their team was taking on too many stories at once and planning was draining. - They adopted elements of Kanban like just-in-time planning and work-in-progress limits, while keeping Scrum elements like iterations, standups, and retrospectives. - This "Scrumban" approach resulted in a 20% increase in productivity and improved morale. It released more control to developers and relieved pressure on product managers serving as product owners.

Kanban Methodology

Sudhanva Ramesh

Kanban is a lean methodology for managing workflow. It uses visual signals like cards to limit work-in-progress and optimize flow. Software teams can implement Kanban virtually with boards and cards to visualize work, standardize workflows, and identify blockers. Key benefits include planning flexibility, shortened cycle times from overlapping skills, fewer bottlenecks from limiting work-in-progress, and support for continuous delivery of value. Teams use metrics like control charts and cumulative flow diagrams to continually improve efficiency.

Agile Network India | "Make Work Visible" - Expose the time thieves to optimi...

AgileNetwork

The document discusses how to identify and address five "time thieves" - too much work-in-progress, conflicting priorities, unknown dependencies, unplanned work, and neglected work - that can stall workflow optimization. It recommends making all work visible using tools like Kanban boards, setting work-in-progress limits, exposing dependencies between teams, prioritizing work, and tracking aging tasks to create transparency and accountability that will optimize the flow of work.

Get responsive in 30 minutes (WordCamp Sofia)

Nickolay Ninarski

9 Productive Tips to Work Faster

Shore Labs

Scrum refresh

Scrum Breakfast Vietnam

Cloud tools

John McCaffrey

John McCaffrey gives a presentation on cloud tools for development. He discusses terminology related to hosting and deploying applications. Some hosting options he covers include self-hosting, Amazon Web Services, EngineYard, Heroku, and AppHarbor. John then demonstrates deploying applications to Heroku and monitoring tools. He finishes by discussing collaboration tools like email, chat, screen sharing, and code repositories on services like GitHub.

ScrumBan Evolution - What is you next step?

Sebastian Radics

Kanban presentation

Bijo Joseph

Kanban is a lean manufacturing process that uses visual signals to control inventory and work flow. It was developed by Toyota based on pull production principles from supermarkets. A kanban system uses cards or bins to signal when more inventory is needed to be produced. The document then provides an example of how a kanban system would work with a board to limit work-in-progress at each stage and reveal bottlenecks in the production process. It describes the different types of kanbans for raw materials, work-in-progress, and finished goods.

Ciklum net sat12112011-vladimir gorshunov -scrum and kanban in action

Ciklum Ukraine

Vladimir Gorshunov is a technical consultant and Agile coach with over 8 years of software development experience. He helps distributed teams implement efficient Agile practices like Scrum and Kanban to deliver business value on time and on target. While Scrum and Kanban each have their uses, Vladimir advocates using a hybrid approach that combines the two for projects with short timelines, limited resources, or other constraints that prevent strict adherence to a single methodology. He works with teams to visualize their workflow, limit work in progress, and continuously optimize processes.

Denver ACE March Remote Transition Tips

denveraug

The document summarizes the Denver Atlassian Community Meeting held on March 25th, 2020. It provided information about virtual events and guidelines for participating remotely. It introduced speakers and covered topics for upcoming meetings. It also provided information about the free Remote Summit 2020 virtual event on April 1-2 and an Adaptavist Live Q&A session on March 31. Tips for remote work were shared, including maintaining routines, setting up a home office, structuring the day, staying connected, and using the time for learning. Recent product updates from Atlassian were briefly outlined.

ScrumBan [R]Evolution - Are #NoEstimate and #NoSprints your next steps

Sebastian Radics

The document discusses Scrumban, which combines elements of Scrum and Kanban. It outlines 5 guiding questions about value, flow, quality, joy, and continuous improvement. It then describes 5 steps of evolution away from sprints and toward continuous flow. This includes slicing stories properly based on size and forecasting using throughput. It recommends focusing on predictability and fitness for purpose over estimates. Various metrics for measuring flow and progress are presented, like cumulative flow diagrams and scatterplots. Finally, recommended resources on Scrumban and related topics are listed.

Responsive, adaptive and responsible - keynote at NebraskaJS

Christian Heilmann

This document discusses challenges facing web developers and proposes ways to address them in a responsible manner. It notes that web principles of maintainability, accessibility, and flexibility are often challenged by a focus on visuals over content and a belief that things should look the same everywhere. It argues that developers internalize these challenges too much by releasing things too quickly without proper crafting. The document calls on developers to be more responsible for their work by always questioning authority and avoiding blind faith in new technologies or browser innovations. It stresses the importance of focusing on users over other priorities and addressing issues through love rather than punishment.

An Introduction to Kanban

Camille Bell

Kanban is an Lean practice that focuses on completing work. Used alone Kanban provides an evolutionary approach to agile development and better fits many SW development teams (like maintenance or sysadmin) that don't have an iterative cadence. Used in combination with agile processes like Scrum or Extreme Programming, Kanban practices like WIP limits and Service Level swim lanes solve issues real teams and companies encounter every day. Project managers should pay special attention to Kanban Lead Time metric.

Debugging WooCommerce - WooConf Talk

Andrew Wikel

This document provides tips for debugging issues with a WooCommerce site. It recommends remaining calm when a site whitescreens, asking questions to identify when and how the problem occurred, and using tools like the System Status Report and browser developer tools to look for errors or outdated plugins/themes. The tips suggest fixing issues on a staging site with backups, deactivating all plugins except the problem one to troubleshoot in a vacuum, and googling or contacting support if the issue cannot be resolved.

Make Work Visible - Unmask Capacity Killing WIP

Dominica DeGrandis

[Da Nang Scrum Breakfast] Dealing with Technical Debt

Scrum Breakfast Vietnam

Software developers use the term “Technical Debt” as a metaphor to convey the compromise between hitting the release date to meet the deadline and cleaning your code to ensure the quality. This could relate to financial debt when you could get money in a quicker and easier way but it comes with the duty of paying interest. In software development, incurring “Technical Debt” comes with extra work in the future and some other consequences.

Creating change from within - Agile Practitioners 2012

Dror Helper

Faced with management that do not care about "being agile" what can a single developer do? Quite a lot! Every developer has the power to improve the organization he works in in small iterative steps – and I can show you how. If you want to make the change and don't know where to start – look no further, in this session I'll share my experience and show a few tips and tricks I learnt. As well as discuss the do and don'ts that can make all the. - How to be agile developer in a waterfall company. - Influencing people without formal authority. - Using the right practices that makes the difference - How to avoid alienating people - Discovering your allies - Know when to fight and when to "retreat" and cut your losses - Making a change without disrupting the daily routine - What being an agile evangelist is all about

Good behaviors

Rawin Windygallery

This document provides advice for developers at different levels and in working with various roles. It discusses that a developer is someone who writes software and outlines junior and senior developer levels. It also lists important skills and advises developers to work well with customers by listening to feedback, with marketing by clearly explaining concepts, and with QA by engaging in clear communication and defensive coding. The document emphasizes the importance of collaboration, continuous learning, and focus.

What's hot

Seven Jobs You Should Be Running #sqlsat126

Mike Hillwig

Devops down-under

Robert Postill

Kanban Basics for Beginners Revised

Zsolt Fabok

From Scrum to Scrumban

John Peltier

Kanban Methodology

Sudhanva Ramesh

Agile Network India | "Make Work Visible" - Expose the time thieves to optimi...

AgileNetwork

Get responsive in 30 minutes (WordCamp Sofia)

Nickolay Ninarski

9 Productive Tips to Work Faster

Shore Labs

Scrum refresh

Scrum Breakfast Vietnam

Cloud tools

John McCaffrey

ScrumBan Evolution - What is you next step?

Sebastian Radics

Kanban presentation

Bijo Joseph

Ciklum net sat12112011-vladimir gorshunov -scrum and kanban in action

Ciklum Ukraine

Denver ACE March Remote Transition Tips

denveraug

ScrumBan [R]Evolution - Are #NoEstimate and #NoSprints your next steps

Sebastian Radics

Responsive, adaptive and responsible - keynote at NebraskaJS

Christian Heilmann

An Introduction to Kanban

Camille Bell

Debugging WooCommerce - WooConf Talk

Andrew Wikel

Make Work Visible - Unmask Capacity Killing WIP

Dominica DeGrandis

[Da Nang Scrum Breakfast] Dealing with Technical Debt

Scrum Breakfast Vietnam

What's hot (20)

Seven Jobs You Should Be Running #sqlsat126

Devops down-under

Kanban Basics for Beginners Revised

From Scrum to Scrumban

Kanban Methodology

Agile Network India | "Make Work Visible" - Expose the time thieves to optimi...

Get responsive in 30 minutes (WordCamp Sofia)

9 Productive Tips to Work Faster

Scrum refresh

Cloud tools

ScrumBan Evolution - What is you next step?

Kanban presentation

Ciklum net sat12112011-vladimir gorshunov -scrum and kanban in action

Denver ACE March Remote Transition Tips

ScrumBan [R]Evolution - Are #NoEstimate and #NoSprints your next steps

Responsive, adaptive and responsible - keynote at NebraskaJS

An Introduction to Kanban

Debugging WooCommerce - WooConf Talk

Make Work Visible - Unmask Capacity Killing WIP

[Da Nang Scrum Breakfast] Dealing with Technical Debt

Similar to Creating change from within - DevReach 2012

Creating change from within - Agile Practitioners 2012

Dror Helper

Good behaviors

Rawin Windygallery

Building a Startup in .NET

Marcelo Calbucci

DevDay 2013 - Building Startups and Minimum Viable Products

Ben Hall

BTD2015 - Your Place In DevTOps is Finding Solutions - Not Just Bugs!

Andreas Grabner

This is about leveling-up and REVOLUTIONIZING Testing as part of your Agile/DevOps Transformation. You can contribute more than testing functionality. You need to Level-Up your skill set by understanding the apps you are testing. # Images, # JS Files, # SQL Statements, Connection Pool Utilization and Garbage Collection Activity have to be added to your portfolio. Check these metrics when you do your functional testing and report regressions to your engineers even though the functionality is still good. But you just uncovered an Architectural regression that will lead to a scalabilty and performance problem. Finding these problems early will eliminate a lot of wasted and unplanned time later on in the lifecycle. that is your contribution to delivering software faster with better quality

Completely Test-Driven

Ian Truslove

Refactoring Applications using SOLID Principles

Steven Smith

We’ve all heard about well-designed software projects, where things aren’t (yet) a big ball of mud that’s painful to work with, but many of us aren’t lucky enough to work on these. Nor is it an option for us to get to start a brand new “greenfield” project, where we can leave behind the legacy of spaghetti code and technical debt our current project might have. But there is hope! By applying refactoring steps based on SOLID principles of object oriented design, we can reduce the technical debt of our existing application, improve our code quality, and hopefully make our application more enjoyable and productive to work with. In this session, we’ll briefly introduce the SOLID principles and several design patterns, and then we’ll apply these principles and patterns by improving the design of an existing application through several refactoring steps.

WTF: Where To Focus when you take over a Drupal project

Symetris

Jumping into pre-built Drupal projects sometimes requires a leap of faith as much for clients as for developers. The client is usually coming out of a bad previous business relationship and the code is not always structured according to your standards. During this talk, Symetris will share its experience and provide tips on how to navigate these often uncharted waters. Our goal is to help you convert an uncertain client into a long term partner and have a checklist of what to look out for as developers.

Extreme Programming (XP): Revisted

Mike Harris

In his recent book, Clean Agile, Robert C "Uncle Bob" Martin chooses Extreme Programming (XP) for the basis of his explanation of Agile because "of all the Agile processes, XP is the best defined, the most complete, and the least muddled." So why is it that in my professional life I only hear us speaking about Agile in terms of Scrum, Sprints, and possibly Kanban? Often I mention XP and people are not sure what I mean. Am I sure myself? Coined in 1999 by Kent Beck and Ward Cunningham, XP has been with us for twenty years, but may of its practices have been with us for much longer. Many of them will be familar to you, but did you know they came from XP? This talk aims to take us back to what XP is, how it fits in the Agile world, how it sits alongside other methodologies, and why, like Uncle Bob, I believe it is the best defined methodology, and what we should all be talking about. The talk is based on a heavily refactored talk that Mike gave previously at Agile on the Beach conference, updated for 2020. Given at Ox:Agile Meetup on February 11th 2020: https://www.meetup.com/OXAGILE/events/nxrdmrybcdbpb/

Technical Excellence Doesn't Just Happen--Igniting a Craftsmanship Culture

Allison Pollard

This document discusses igniting a culture of craftsmanship in software development. It argues that technical excellence is necessary for agility, as ignoring technical debt and quality will eventually slow a project. The document outlines some common causes of technical debt, such as cutting corners and overengineering. It also discusses how paying down technical debt through refactoring can improve both internal code quality and external customer outcomes. Overall, the document advocates for continuous attention to technical practices, automated testing, refactoring and simple designs in order to sustain agility in software development.

A modern architecturereview–usingcodereviewtools-ver-3.5

SSW

Test Driven Development: More Development Than Ever

Kiryl Baranoshnik

Flexing your Agile Muscle - Agile Technical Concepts Explained

Sandy Mamoli

Continuous integration, acceptance test driven development (ATDD), specification by example and continuous deployment: The list of have-to-know concepts is growing and you have this nagging feeling that you should really get started so you won’t miss out on the fun. Learn what basic Agile technical concepts mean, understand how you can benefit from using them and get ideas for how you might get started. Also, you will be able to explain to your boss or project manager why Agile technical concepts are well worth the investment. This session will keep things on a strictly conceptual level - so whether you’re a developer or an interested manager please come along.

Driving application development through behavior driven development

Einar Ingebrigtsen

This document discusses Behavior Driven Development (BDD) and how it can be used to drive application development. It introduces BDD, focusing on behaviors of the system rather than tests. It discusses key aspects of BDD like Gherkin, units, test doubles, writing testable code, frameworks like SpecFlow and recommended reading. The overall message is that BDD changes the way software is developed by shifting the focus to behaviors and improving collaboration.

The View - Lotusscript coding best practices

Bill Buchan

This document discusses best practices for LotusScript coding. It covers topics like code structure, using short logical functions, defensive programming, variable naming conventions, and ensuring variables only exist as long as needed. The goal is to write code that is maintainable, reusable, and robust. Testing practices like test-driven development and separating development, testing, and production environments are also recommended to improve quality.

Jax Devops 2017 Succeeding in the Cloud – the guidebook of Fail

Steve Poole

Many have gone before you along this path. Many have failed. A few have succeeded. All have scars. Although the journey is different for everyone there are common aspects to them all. In this talk we will cover our experiences in moving applications into the Cloud. What you must do. What you must not. What matters, what doesn’t. In moving to the cloud there is no try. In this talk: * We’ll cover the core aspects of how the cloud differs from local data centers in terms of application design, runtime characteristics and operational considerations. * We’ll explain through various real life examples where things worked and where they didnt * We end with a summary of the key elements to success and the major pitfalls to avoid.

Advanced dev ops governance with terraform

James Counts

Jim Counts specializes in helping enterprises transition to cloud-native architectures. He focuses on making infrastructure management repeatable, reliable and sustainable through automation with Terraform. Large organizations face challenges of "DevOps project sprawl" as they have many teams with different responsibilities. This can lead to overuse of shared credentials and resources if not properly governed. Jim discusses how to establish "launch pads" and "landing zones" using Terraform to automate the management of environments, projects, credentials and other resources to bring order to this "sprawl" and make governance scalable.

Leandro Melendez - Switching Performance Left & Right

Neotys_Partner

Since its beginning, the Performance Advisory Council aims to promote engagement between various experts from around the world, to create relevant, value-added content sharing between members. For Neotys, to strengthen our position as a thought leader in load & performance testing. During this event, 12 participants convened in Chamonix (France) exploring several topics on the minds of today’s performance tester such as DevOps, Shift Left/Right, Test Automation, Blockchain and Artificial Intelligence.

Code stock

Erin Page

Software Bootcamp graduates (and other Junior Programmers) are entering the technology market with a brief understanding of CRUD actions and web development in general. After a whirlwind of learning in school, graduates are often left asking: what do I learn next? My first professional project was to create a microservices app from scratch. Previously, I had made extremely simple apps with only a few models, a couple of controllers, and some basic CRUD actions. Oh, and static web pages. I made plenty of those. This talk covers some of the key technical concepts encountered when first going beyond a basic crud app: * State Machines * Decorators * Database Normalization This talk will also discuss some of the soft skills that are necessary to participate on a software development team, including: * Code Reviews * User Stories * Pair Programming Bootcamps are a clear line from civilian to Junior Programmer. Less clear is the line from Junior to Mid-level. Armed with basic CRUD and MVC knowledge, Junior Programmers can begin to dive into other programming concepts. Programmers are also expected to participate in collaborative development on projects that require soft skills in addition to technical skills.

Picnic Software - Developing a flexible and scalable application

Nick Josevski

Similar to Creating change from within - DevReach 2012 (20)

Creating change from within - Agile Practitioners 2012

Good behaviors

Building a Startup in .NET

DevDay 2013 - Building Startups and Minimum Viable Products

BTD2015 - Your Place In DevTOps is Finding Solutions - Not Just Bugs!

Completely Test-Driven

Refactoring Applications using SOLID Principles

WTF: Where To Focus when you take over a Drupal project

Extreme Programming (XP): Revisted

Technical Excellence Doesn't Just Happen--Igniting a Craftsmanship Culture

A modern architecturereview–usingcodereviewtools-ver-3.5

Test Driven Development: More Development Than Ever

Flexing your Agile Muscle - Agile Technical Concepts Explained

Driving application development through behavior driven development

The View - Lotusscript coding best practices

Jax Devops 2017 Succeeding in the Cloud – the guidebook of Fail

Advanced dev ops governance with terraform

Leandro Melendez - Switching Performance Left & Right

Code stock

Picnic Software - Developing a flexible and scalable application

More from Dror Helper

Unit testing patterns for concurrent code

Dror Helper

Getting started with unit testing is not hard, the only problem is that most programs are more than a simple calculator with two parameters and a returns value that is easy to verify. Writing unit tests for multi-threaded code is harder still. Over the years I discovered useful patterns that helped me to test multi-threaded and asynchronous code and enabled the creation of deterministic, simple and robust unit tests. Come learn how to test code that uses concurrency and parallelism – so that the excuses of not writing unit tests for such code would become as obsolete as a single core processors.

The secret unit testing tools no one ever told you about

Dror Helper

There are more to unit testing than using a unit testing framework - in order to succeed you want to use the right tools for the job. There are a few tools that almost no one talks about - some enabling creating of top-notch, robust unit tests. Some will help you run your tests better and faster. In this session I'll explain about the inevitable maintainability problems developers face when writing and maintaining huge unit testing suits and how unit level BDD, AutoMocking, and Continuous Execution can help take control over your tests.

Debugging with visual studio beyond 'F5'

Dror Helper

Debugging is part of any development process, but unfortunately it’s never planned or expected. On top of that, it’s rarely approached in a structured way, and while many modern IDEs have powerful debugging tools – most developers are not aware of how they can be used to reduce the time and pain of debugging. The whole act of debugging is done as an ad-hoc, time consuming activity, which is considered less interesting then developing new features or investigating the latest and greatest technology. But while there are many articles and productivity tools aimed at writing better code – faster, it seems as though it’s impossible to find resources that teach you how to effectively debug your code. In this lecture, we will discuss how to approach a debugging session, and show the latest power debugging capabilities Visual Studio has to offer. These will help you save time and pain by first understanding the problem and then fixing the bug that caused it.

From clever code to better code

Dror Helper

Every software developer enjoys finding new and clever ways to solve problems. Writing code using his/her wits, intelligent and creativity. However, sometimes being too clever can lead to hard to track bugs, maintainability issues and impossible to understand code. Is all cleverly written code good code, or is it a problem just waiting to happen? In this session, I will show you real world examples of cleverly written code. And show you how we can use clean code principles, refactoring and design patterns, to transform that code from clever code to good code – one that your peers and future self would thank you for writing.

From clever code to better code

Dror Helper

Part of the software developer job is to find new and better ways to solve problems. Writing code using his/her wits, intelligent and creativity. However, sometimes being too clever can lead to hard to track bugs, maintainability issues and impossible to understand code. Is all cleverly written code good code, or is it a problem just waiting to happen? In this session, I will show you real world examples of cleverly written code. And show you how we can use clean code principles, refactoring and design patterns, to transform that code from clever code to good code, code one that your peers - and future self - would thank you for writing.

A software developer guide to working with aws

Dror Helper

This document provides guidance for software developers working with AWS. It begins by recommending steps for getting started with AWS, including creating an AWS account and user, and not using the root account for security. It then discusses considerations for deciding on compute types, networking configurations, architecture for high availability, storage and database options, and how to test services locally before deploying to AWS. The document demonstrates calling AWS services from code and provides resources for learning more about AWS services and costs.

The secret unit testing tools no one has ever told you about

Dror Helper

The role of the architect in agile

Dror Helper

In Agile development, architects still play an important role by setting constraints and principles to provide guidance and boundaries for development teams. While Agile values working software over documentation, architects can document architecture decisions and provide guidance through code examples. On Agile teams, the architect acts as an owner who facilitates architectural decisions, explores new technologies, and evolves the architecture over time based on learnings. The architect also helps align development across teams when needed.

Harnessing the power of aws using dot net core

Dror Helper

In the past AWS and C# seemed to belong to two different eco-systems. One was a leading cloud platform while the other a widely used, powerful programming platform. Does it mean that a developer that needs to provide a solution in the cloud must choose between the two? Not anymore. In this talk, I will show how to write C# code that runs in a dockerized container in the cloud or as an AWS Lambda and harness, the popular AWS services.

Developing multi-platform microservices using .NET core

Dror Helper

Harnessing the power of aws using dot net

Dror Helper

Secret unit testing tools no one ever told you about

Dror Helper

There are more to unit testing than using a unit testing framework – in order to succeed you want to use the right tools for the job. There are a few tools that almost no one talks about – some enabling creating of top-notch, robust unit tests. Some will help you run your tests better and faster. In this session I’ll explain about the inevitable maintainability problems developers face when writing and maintaining huge unit testing suits and how unit level BDD, AutoMocking, and Continuous Execution can help take control over your tests.

C++ Unit testing - the good, the bad & the ugly

Dror Helper

C++ is a powerful language when used by a seasoned developer. It is being used everywhere from operating systems and compilers to cross platform mobile apps development. But this power comes with a cost - C++ programming is not simple nor easy – with memory leaks, stack overflows and strange exceptions, a software developer needs all of the power he can use. By harnessing the power of unit tests a software developer can find defects quickly, avoid regression and speed up development time. In this talk I’ll show how to use the right unit testing tools and practices available that will help you get your C++ code under control and even test legacy code which no one ever want to touch.

Working with c++ legacy code

Dror Helper

The document discusses strategies for working with legacy C++ code, including gaining control over legacy code through iterative refactoring while ensuring existing functionality is maintained. It emphasizes learning what the code does, making sure it continues functioning properly, and making gradual improvements. Specific techniques mentioned include writing tests, creating fake objects to inject into code under test instead of real dependencies, and using templates or friendship to fake classes that are otherwise difficult to mock.

Visual Studio tricks every dot net developer should know

Dror Helper

Debugging is hard - this is a fact of life. Unfortunately, it’s never planned nor expected. It takes too much time, time we could have spent doing cool stuff - like developing new features for our customers. But while there are many articles and productivity tools aimed at writing better code – faster, it seems as though it’s impossible to find resources that teach you how to effectively debug your code. In this talk we’ll explore Visual Studio’s more powerful but lesser known debugging capabilities. We’ll also showcase OzCode and explain how it helps finding and fixing bugs faster.

Secret unit testing tools

Dror Helper

There is more to unit testing than using a unit testing framework. In order to succeed you want to use the right tools for the job. There are a few tools that almost no one talks about – some enabling the creation of top-notch, robust unit tests; some will help you run your tests better and faster. In this session, Dror will explain about the inevitable maintainability problems developers face when writing and maintaining huge unit testing suits, and how unit level BDD, AutoMocking and Continuous Execution can help take control over your tests.

Electronics 101 for software developers

Dror Helper

These days it seems as if everybody talks about the internet of things (IoT). With a cheap Arduino, Raspberry PI (or another microcontroller) every developer has the power to control the real world. Suddenly confronted with resistors, digital inputs, analog interfaces and a weird bread board full of holes – a developer is reminded that the world of hardware can be confusing and sometimes downright frustrating.

Navigating the xDD Alphabet Soup

Dror Helper

TDD, BDD, ATDD are all methodologies that enable incremental design that is suitable for Agile environments. It seems that every day a new xDD methodology is born with the promise to be better than what came before. Should you use behaviour-driven tests or plain old unit tests? Which methodology is better? And how exactly would it benefit the development life cycle? In this session, Dror will help to sort out the various methodologies – explaining where they came from, the tools they use, and discussing how and when to use each one. Here we will once and for all answer the question as to whether or not there’s one “DD” to rule them all.

Building unit tests correctly

Dror Helper

This document discusses best practices for writing unit tests. It emphasizes that unit tests should be easy to understand, trustworthy, and robust. A good unit test only fails if a bug is introduced or requirements change. The document provides examples of well-written unit tests and discusses how to avoid common problems like fragile tests. It stresses the importance of testing only specified functionality, using isolation frameworks to mock dependencies, and not putting test logic in the test. Overall, the document promotes writing "clean tests" to avoid brittle tests and minimize maintenance overhead.

Who’s afraid of WinDbg

Dror Helper

This document introduces WinDbg, a debugger tool that can be used for post mortem crash analysis, memory leak detection, and deadlock discovery. It discusses how to load crash dumps and symbols, and provides an overview of basic commands like listing processes and threads. Crash analysis commands for .NET like !analyze, !printexception, and !clrstack are presented. Commands for investigating memory issues like !dumpheap and !gcroot are also highlighted. The document concludes with discussing deadlock detection using commands like !dlk and !mwaits.

More from Dror Helper (20)

Unit testing patterns for concurrent code

The secret unit testing tools no one ever told you about

Debugging with visual studio beyond 'F5'

From clever code to better code

A software developer guide to working with aws

The secret unit testing tools no one has ever told you about

The role of the architect in agile

Harnessing the power of aws using dot net core

Developing multi-platform microservices using .NET core

Harnessing the power of aws using dot net

Secret unit testing tools no one ever told you about

C++ Unit testing - the good, the bad & the ugly

Working with c++ legacy code

Visual Studio tricks every dot net developer should know

Secret unit testing tools

Electronics 101 for software developers

Navigating the xDD Alphabet Soup

Building unit tests correctly

Who’s afraid of WinDbg

Recently uploaded

inQuba Webinar Mastering Customer Journey Management with Dr Graham Hill

LizaNolte

HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable. In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed: Key Takeaways: Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement. Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers. Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Jason Yip

The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.

Astute Business Solutions | Oracle Cloud Partner |

AstuteBusiness

Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency

ScyllaDB

"What does it really mean for your system to be available, or how to define w...

Fwdays

Northern Engraving | Modern Metal Trim, Nameplates and Appliance Panels

Northern Engraving

Dandelion Hashtable: beyond billion requests per second on a commodity server

Antonios Katsarakis

This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).

Apps Break Data

Ivo Velitchkov

How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?

Day 2 - Intro to UiPath Studio Fundamentals

UiPathCommunity

In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project. 📕 Detailed agenda: Variables and Datatypes Workflow Layouts Arguments Control Flows and Loops Conditional Statements 💻 Extra training through UiPath Academy: Variables, Constants, and Arguments in Studio Control Flow in Studio

Session 1 - Intro to Robotic Process Automation.pdf

UiPathCommunity

👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program: https://bit.ly/Automation_Student_Kickstart In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC. 📕 Detailed agenda: What is RPA? Benefits of RPA? RPA Applications The UiPath End-to-End Automation Platform UiPath Studio CE Installation and Setup 💻 Extra training through UiPath Academy: Introduction to Automation UiPath Business Automation Platform Explore automation development with UiPath Studio 👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/

Christine's Product Research Presentation.pptx

christinelarrosa

Leveraging the Graph for Clinical Trials and Standards

Neo4j

Mutation Testing for Task-Oriented Chatbots

Pablo Gómez Abajo

Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots. To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.

Essentials of Automations: Exploring Attributes & Automation Parameters

Safe Software

Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they? Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality. You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.

Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors

DianaGray10

Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more. The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications. We’ll discuss and demo the benefits of UiPath Apps and connectors including: Creating a compelling user experience for any software, without the limitations of APIs. Accelerating the app creation process, saving time and effort Enjoying high-performance CRUD (create, read, update, delete) operations, for seamless data management. Speakers: Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP Charlie Greenberg, host

zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...

Alex Pruden

Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security. Paper Link: https://eprint.iacr.org/2024/257

AppSec PNW: Android and iOS Application Security with MobSF

Ajin Abraham

Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application. This talk covers: Using MobSF for static analysis of mobile applications. Interactive dynamic security assessment of Android and iOS applications. Solving Mobile app CTF challenges. Reverse engineering and runtime analysis of Mobile malware. How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.

GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph

Neo4j

Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians

Neo4j

What is an RPA CoE? Session 1 – CoE Vision

DianaGray10

Recently uploaded (20)

inQuba Webinar Mastering Customer Journey Management with Dr Graham Hill

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Astute Business Solutions | Oracle Cloud Partner |

Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency

"What does it really mean for your system to be available, or how to define w...

Northern Engraving | Modern Metal Trim, Nameplates and Appliance Panels

Dandelion Hashtable: beyond billion requests per second on a commodity server

Apps Break Data

Day 2 - Intro to UiPath Studio Fundamentals

Session 1 - Intro to Robotic Process Automation.pdf

Christine's Product Research Presentation.pptx

Leveraging the Graph for Clinical Trials and Standards

Mutation Testing for Task-Oriented Chatbots

Essentials of Automations: Exploring Attributes & Automation Parameters

Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors

zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...

AppSec PNW: Android and iOS Application Security with MobSF

GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph

Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians

What is an RPA CoE? Session 1 – CoE Vision

Creating change from within - DevReach 2012

1. Create change from within – the Agile Developer’s story Dror Helper | Better Place

2. About.Me • Software Developer 9+ years • Team’s technical lead • TDD/Unit testing enthusiast • Some SCRUM/Kanban background • Blogger – http://blog.drorhelper.com www.devreach.com

3. The problem with Agile We don’t have time It would never work in this I don’t want to do this! project www.devreach.com

4. What can one person do? www.devreach.com

5. My team 2010 • One manager + 3 developers • Unit tests – more or less • Iteration tracking ? • Manual deployment • Code reviews www.devreach.com

6. My 1st week on the job www.devreach.com

7. LET’S DO TDD! www.devreach.com

8. Step #1 - Analysis • Took two days to fix 40% of tests • Find what are the main issues – and focus on them – Not readable – Using logic inside test – Testing too much – Hand rolled mocks – Scenarios hiding as unit tests – Highly coupled code www.devreach.com

9. Step #2 – CI Server Build Server What’s new? Commit There you go Source Control www.devreach.com Build Agents

10. Step #3 - Teach the team www.devreach.com

11. Communicate! • Email • Phone call • Face to face • Presentation • Code reviews • Pair programming • Daily meetings www.devreach.com

12. The power of code reviews

13. Immediate steps • MSTest • Write new test before fixing bug • Fix existing tests when implementing new features • Delete obsolete tests www.devreach.com

14. Change is iterative • Hard to perform big changes overnight • Small incremental changes www.devreach.com

15. Today • More than 5000 tests • Good code coverage • Most features are developed using TDD • CI server run all tests on commit • Nightly builds • Change code without fear www.devreach.com

16. DECIDING WHAT TO CHANGE www.devreach.com

17. Passion is a must! • Become champion • Need to convince co-workers • Survive the road www.devreach.com

18. The cost of change Participants Maintenance Effort (Time) Cost of Change Emotional Cost (Money) Value Previous investment www.devreach.com

19. Create success record www.devreach.com

20. ITERATION TRACKING www.devreach.com

21. In the beginning…

22. Post it + wall www.devreach.com

23. Demonstration > Discussion www.devreach.com

24. Individual task boards www.devreach.com

25. Be pragmatic • Every action should have a purpose • If it doesn’t work – change it! • Names are not important – just what you do • Practices can be adapted for the team Know where to draw the line www.devreach.com

26. TFS + Work item manager www.devreach.com

27. What to when change fails? Understand why it failed Wait and see Choose a different path Cut your losses www.devreach.com

28. TIPS AND TRICKS www.devreach.com

29. The right attitude • Be positive • Don’t tell them what to so - suggest improvements • Don’t force – convince • Be ready to change if proven wrong www.devreach.com

30. Don’t be “that guy” www.devreach.com

31. Enlist help Because You cannot do it all by yourself www.devreach.com

32. Journey not a destination www.devreach.com

33. Thank you! @dhelper http://blog.drorhelper.com/ http://www.linkedin.com/in/drorhelper Dror Helper | Better Place

Editor's Notes

Teach best practices – in the right contextTrack progressFind common issuesAlso pair programming – although I found that managers are more likely to
Impossible to convince
We had nothing
Show then let them decideJust do it!

Creating change from within - DevReach 2012

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Creating change from within - DevReach 2012

Similar to Creating change from within - DevReach 2012 (20)

More from Dror Helper

More from Dror Helper (20)

Recently uploaded

Recently uploaded (20)

Creating change from within - DevReach 2012

Editor's Notes