The document discusses techniques for writing better code through minimizing what is written. It begins with an agenda that includes discussing principles over prescriptions. It then explains that writing less code saves both time and money. Several figurative techniques are presented for writing less code, such as YAGNI (You aren't gonna need it) and KISS (Keep it simple stupid). Literal techniques like test-driven development and acceptance test-driven development are also discussed. The document emphasizes writing code only for demonstrated needs and verifying requirements with stakeholders.
Short history of Spartez and information whom we want to hire and why.
Extra bonus: my aspirational thinking about how juniors differ to senior and principal developers.
This slidedeck was presented by me during Spartez Open Day on March 13th 2015.
Software Developer Career Unplugged - GeeCon 2013Wojciech Seliga
This is my quite subjective take on various less technical aspects of a software developer career. I delivered this presentation and GeeCon 2013 (video hopefully coming soon) and quite compressed/abridged version at InfoSHARE.
Ten lessons I painfully learnt while moving from software developer to entrep...Wojciech Seliga
My presentation from Devoxx Poland 2016 conference - the newest, slightly revised version.
For many years I was a software developer. I would concentrate on the code, software projects and the interactions with my closes team and the users. I was sure that Agile solves all world’s problems. I would laugh over Scott Adam’s Dilbert comics with his Point Hair Boss. Life was simple, life was good. Now for 8+ years I have been running a software company, not a small one anymore. I became myself a full-time boss who only codes sometimes at home or during hackathons.
This session is about sharing with you those critical lessons which I painfully learnt when trying to grow into this new role - transitioning from being a software engineer into being an entrepreneur and top manager. Wheres not all of the lessons may or will (if you dream about your own startup) apply to your case, being aware of them may save you tons of time, energy, money or even help you to avoid the total disaster - burying your own company or dreams. And after all, sharing war stories from the past is fun … when these stories are the past.
Cosa abbiamo scoperto in questi 20 anni? Che cercare di cambiare il mondo focalizzandoci su un singolo aspetto, il processo, il TDD, il clean code, non porta da nessuna parte. I veri cambiamenti avvengono quando scopriamo le reali interazioni tra le parti, quando lasciamo la specializzazione e cominciamo a vedere il vero quadro d'insieme.
In questo talk vedremo come scelte architetturali apparentemente innocue, finiscano per impattare il processo, ed in generale di come processi, pratiche, architetture, persone e scelte di business non possano essere considerate come elementi disaccoppiati tra loro.
Ten lessons I painfully learnt while moving from software developer to entrep...Wojciech Seliga
My presentation from InfoShare 2016 conference.
For many years I was a software developer. I would concentrate on the code, software projects and the interactions with my closes team and the users. I was sure that Agile solves all world’s problems. I would laugh over Scott Adam’s Dilbert comics with his Point Hair Boss. Life was simple, life was good. Now for 8+ years I have been running a software company, not a small one anymore. I became myself a full-time boss who only codes sometimes at home or during hackathons.
This session is about sharing with you those critical lessons which I painfully learnt when trying to grow into this new role - transitioning from being a software engineer into being an entrepreneur and top manager. Wheres not all of the lessons may or will (if you dream about your own startup) apply to your case, being aware of them may save you tons of time, energy, money or even help you to avoid the total disaster - burying your own company or dreams. And after all, sharing war stories from the past is fun … when these stories are the past.
I've spent the last years modelling complex businesses and Software Architectures with EventStorming. The original recipe evolved a lot from the initial one. This is EventStorming state of the art.
Short history of Spartez and information whom we want to hire and why.
Extra bonus: my aspirational thinking about how juniors differ to senior and principal developers.
This slidedeck was presented by me during Spartez Open Day on March 13th 2015.
Software Developer Career Unplugged - GeeCon 2013Wojciech Seliga
This is my quite subjective take on various less technical aspects of a software developer career. I delivered this presentation and GeeCon 2013 (video hopefully coming soon) and quite compressed/abridged version at InfoSHARE.
Ten lessons I painfully learnt while moving from software developer to entrep...Wojciech Seliga
My presentation from Devoxx Poland 2016 conference - the newest, slightly revised version.
For many years I was a software developer. I would concentrate on the code, software projects and the interactions with my closes team and the users. I was sure that Agile solves all world’s problems. I would laugh over Scott Adam’s Dilbert comics with his Point Hair Boss. Life was simple, life was good. Now for 8+ years I have been running a software company, not a small one anymore. I became myself a full-time boss who only codes sometimes at home or during hackathons.
This session is about sharing with you those critical lessons which I painfully learnt when trying to grow into this new role - transitioning from being a software engineer into being an entrepreneur and top manager. Wheres not all of the lessons may or will (if you dream about your own startup) apply to your case, being aware of them may save you tons of time, energy, money or even help you to avoid the total disaster - burying your own company or dreams. And after all, sharing war stories from the past is fun … when these stories are the past.
Cosa abbiamo scoperto in questi 20 anni? Che cercare di cambiare il mondo focalizzandoci su un singolo aspetto, il processo, il TDD, il clean code, non porta da nessuna parte. I veri cambiamenti avvengono quando scopriamo le reali interazioni tra le parti, quando lasciamo la specializzazione e cominciamo a vedere il vero quadro d'insieme.
In questo talk vedremo come scelte architetturali apparentemente innocue, finiscano per impattare il processo, ed in generale di come processi, pratiche, architetture, persone e scelte di business non possano essere considerate come elementi disaccoppiati tra loro.
Ten lessons I painfully learnt while moving from software developer to entrep...Wojciech Seliga
My presentation from InfoShare 2016 conference.
For many years I was a software developer. I would concentrate on the code, software projects and the interactions with my closes team and the users. I was sure that Agile solves all world’s problems. I would laugh over Scott Adam’s Dilbert comics with his Point Hair Boss. Life was simple, life was good. Now for 8+ years I have been running a software company, not a small one anymore. I became myself a full-time boss who only codes sometimes at home or during hackathons.
This session is about sharing with you those critical lessons which I painfully learnt when trying to grow into this new role - transitioning from being a software engineer into being an entrepreneur and top manager. Wheres not all of the lessons may or will (if you dream about your own startup) apply to your case, being aware of them may save you tons of time, energy, money or even help you to avoid the total disaster - burying your own company or dreams. And after all, sharing war stories from the past is fun … when these stories are the past.
I've spent the last years modelling complex businesses and Software Architectures with EventStorming. The original recipe evolved a lot from the initial one. This is EventStorming state of the art.
5-10-15 years of Java developer career - Warszawa JUG 2015Wojciech Seliga
English slides from my talk (delivered in Polish) on 1st of December 2015 at Warsaw Java User Group.
This is slightly changed and extended version of the talk I delivered at Devoxx Poland 2015
Technical Debt has become a catch-all phrase for any code that needs to be re-worked. Much like Refactoring has become a catch-all phrase for any activity that involves changing code. These fundamental misunderstandings and comfortable yet mis-applied metaphors have resulted in a plethora of poor decisions. What is technical debt? What is not technical debt? Why should we care? What is the cost of misunderstanding? What do we do about it? Doc discusses the origins of the metaphor, what it means today, and how we properly identify and manage technical debt.
Can software architecture affect the culture and emotions in the workplace? In this talk I look to some ways architectural choices shape collaboration and survivability in the workplace.
Can we write successful enterprise software without challenging assumptions? Agile doesn't happen in a vacuum. Here's what I discovered using EventStorming as a blade to cut through business, software and organisation dysfunctions. From XP2017 Cologne.
Software Craftsmanship and Agile Code GamesMike Clement
Join us to talk about what it means to be a software craftsman, how the Software Craftsmanship Manifesto (http://manifesto.softwarecraftsmanship.org/) provides a framework for us to improve.
A large part of being a software craftsman is practice. Using different "code games" we can have a full toolbelt of activities that will help us (and those around us) become better at our craft.
Agile software development promises the ability to deliver value quickly. But this isn’t just a matter of process. Uncle Bob says "the only way to go fast is to go well." But how do we go well? As software developers, we can only deliver features as fast as the code base and our skills allow us. Unfortunately the quality of our code base is directly related to our skill in the past.
Musicians and athletes spend most of their time practicing, not performing. As software developers (aspiring craftsmen) we must have practice sessions that allow us to improve our skills and develop better “code sense”. We’ll look at some different “agile code games” that will help us improve our craft.
The technical debt metaphor is useful in capturing the long-term impacts of
tradeoffs taken during software maintenance between productivity (getting
something done sooner) and maintainability (degradation of the code's
quality over time). This webinar on Technical Debt will present
techniques and insights that help software engineers to identify and track
technical debt in their projects. We will outline how business and product
quality goals should affect the choice of approaches (and combinations of
approaches) for managing technical debt. More specifically, we will discuss
a set of automated approaches based on static code analysis that are likely
to spot problems in source code that have real impact on productivity and
defect proneness. Based on previous empirical studies, we will give further
advice on which types of debt can be found by these tools, and which types
are not yet detectable.
Play to Learn: Agile Games with Cards and DiceMike Clement
Play is a powerful method to learn! Come and play some simple agile games that use playing cards, index cards and dice to explore the different values that are at the foundation of Agile and Lean development practices. In addition to your own insights, you may be able to take these game back to work to share with your co-workers.
This is a hands-on session so come prepared to have some fun!
There is no "right" answer to what you're "supposed to" learn from a game, so come ready to discover your own insights into software development processes and teamwork.
Software development is not one size fits all. Domain-Driven Design is significant where there's high complexity and high value. In these areas different tools might be needed. EventStorming is the best way I know to gather requirements in a complex environment, and also maps with CQRS/ES architecture perfectly.
As a Salesforce Developer I will... 7 Ground Rules for Success, Robert SösemannCzechDreamin
After a decade of working as a developer, consultant, and architect in the Salesforce ecosystem, I believe that it takes more than deep technical skills to be successful. Over and over I have seen a handful of meta-skills separate the rock stars from the crowd. Ground Rules have made Salesforce developers like me more effective in their work, more flexible towards changes, and more composed when the stress levels are high.
In this session, I will share the 7 Ground Rules – with practical examples and tools you can use next sprint – that will aid you and your team to success.
10 bezcennych lekcji dla software developera stającego się szefem firmyWojciech Seliga
[Originally Polish lecture with English slides - with a few exceptions]
Przez wiele lat byłem software developerem. Koncentrowałem się na kodzie, projektach software'owych oraz interakcjach w moim zespole i z klientami. Byłem pewny, że Agile rozwiązuje wszystkie problemy tego świata. Śmiałem się z komiksów Scotta Adamsa i stworzonej przez niego karykatury szefa (PHB). Życie było proste i piękne...
Teraz od ponad 8 lat prowadzę firmę software'ową, którą przy blisko 90 osobach trudno już nazwać maleństwem. Sam stałem się "szefem" na pełen etat.
Podczas prezentacji podzielę się z Wami różnymi doświadczeniami oraz naukami (nieraz bolesnymi) jakie wyniosłem w ostatnich latach podczas mojej stopniowej przemiany z developera/inżyniera w przedsiębiorcę i szefa firmy. O ile zapewne nie wszystkie sytuacje i wnioski mają lub mogą mieć (o ile marzysz o własnym startupie czy zespole) zastosowanie w Twoim życiu, same sobie ich uświadomienie może oszczędzić Ci w przyszłości straty mnóstwa czasu, energii i pieniędzy oraz uniknąć przykrych rozczarowań.
Building In Quality: The Beauty Of Behavior Driven Development (BDD)Synerzip
Behavior Driven Development (BDD) began as a means of helping developers practice Test Driven Development (TDD).
In this it was successful, but it quickly proved its value in many other ways. In this presentation, Larry Apke quotes heavily from the work of Uncle Bob Martin to make the case for TDD and then explains how developers can use BDD to take advantage of this excellent software development practice.
Larry also talks about his “Ten Reasons BDD Changes Everything” along with some easy ways to begin implementation of BDD in your software development organization immediately and what the corresponding future steps would be to take full advantage of this technique.
Code quality directly impacts how easy or hard your job is. The higher the quality, the easier it is for anyone (including you) to quickly jump in and get to work. Where do you start? In this session, Tonya Mork will empower you to simplify your code while dramatically increasing its code quality.
It's all about building <human code>, code that is highly human readable and understandable.
This slide deck is from a session I gave for WPSessions. https://wpsessions.com/sessions/code-quality-makes-jobs-easier/
WordCamp Nashville: Clean Code for WordPressmtoppa
Slides from my talk at WordCamp Nashville, including notes. Covers why clean code is important, and provides 10 tips to make your code cleaner, for WordPress and beyond
Agile Development Overview (with a bit about builds)David Benjamin
I gave this presentation to our dev team when i started at Hannan IT back in October. Its a quick run through the Agile basics, with a bit of extra discussion on continuous integration.
I experimented here with scripting in two tangential sections in the hopes that it would avoid many more spontaneous tangents. It worked!
Architecting Solutions and Systems – Randy’s Secrets to SuccessRandy Williams
This session will provide background and guidance on how Randy has architected software solutions for the past 20+ years. This will cover a range of mostly technical topics, including infrastructure planning, trade-off considerations, performance and scalability, and separation of tiers. Expect to hear plenty of stories from real projects over his career, along with numerous tips on his secrets to success.
OSDC 2019 | Feature Branching considered Evil by Thierry de PauwNETWAYS
With DVCSs, branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what’s evil about feature branches, which is not necessarily the problems they introduce – but rather, the real reasons why teams are using them. After the session, you’ll understand a different branching strategy and how it relates to CI/CD.
Unicorn or Rhino? Agility in the Data Realm?Daniel Davis
What is that uniquely horned creature over there? Unicorn? Rhino? Our Data? As the world of “Data” is growing more and more, so are the technologies and tools around it continuing to advance and improve. Inevitably this also means the struggles and problems around it are also going to increase as well though. Thankfully these are usually not completely new and in fact tend to be very similar to other scenarios we’ve seen and solved for in the past. In this session we’ll explore the adoption of agile, lean & craft processes/practices within our data realms to seek solution to these new and growing concerns.
5-10-15 years of Java developer career - Warszawa JUG 2015Wojciech Seliga
English slides from my talk (delivered in Polish) on 1st of December 2015 at Warsaw Java User Group.
This is slightly changed and extended version of the talk I delivered at Devoxx Poland 2015
Technical Debt has become a catch-all phrase for any code that needs to be re-worked. Much like Refactoring has become a catch-all phrase for any activity that involves changing code. These fundamental misunderstandings and comfortable yet mis-applied metaphors have resulted in a plethora of poor decisions. What is technical debt? What is not technical debt? Why should we care? What is the cost of misunderstanding? What do we do about it? Doc discusses the origins of the metaphor, what it means today, and how we properly identify and manage technical debt.
Can software architecture affect the culture and emotions in the workplace? In this talk I look to some ways architectural choices shape collaboration and survivability in the workplace.
Can we write successful enterprise software without challenging assumptions? Agile doesn't happen in a vacuum. Here's what I discovered using EventStorming as a blade to cut through business, software and organisation dysfunctions. From XP2017 Cologne.
Software Craftsmanship and Agile Code GamesMike Clement
Join us to talk about what it means to be a software craftsman, how the Software Craftsmanship Manifesto (http://manifesto.softwarecraftsmanship.org/) provides a framework for us to improve.
A large part of being a software craftsman is practice. Using different "code games" we can have a full toolbelt of activities that will help us (and those around us) become better at our craft.
Agile software development promises the ability to deliver value quickly. But this isn’t just a matter of process. Uncle Bob says "the only way to go fast is to go well." But how do we go well? As software developers, we can only deliver features as fast as the code base and our skills allow us. Unfortunately the quality of our code base is directly related to our skill in the past.
Musicians and athletes spend most of their time practicing, not performing. As software developers (aspiring craftsmen) we must have practice sessions that allow us to improve our skills and develop better “code sense”. We’ll look at some different “agile code games” that will help us improve our craft.
The technical debt metaphor is useful in capturing the long-term impacts of
tradeoffs taken during software maintenance between productivity (getting
something done sooner) and maintainability (degradation of the code's
quality over time). This webinar on Technical Debt will present
techniques and insights that help software engineers to identify and track
technical debt in their projects. We will outline how business and product
quality goals should affect the choice of approaches (and combinations of
approaches) for managing technical debt. More specifically, we will discuss
a set of automated approaches based on static code analysis that are likely
to spot problems in source code that have real impact on productivity and
defect proneness. Based on previous empirical studies, we will give further
advice on which types of debt can be found by these tools, and which types
are not yet detectable.
Play to Learn: Agile Games with Cards and DiceMike Clement
Play is a powerful method to learn! Come and play some simple agile games that use playing cards, index cards and dice to explore the different values that are at the foundation of Agile and Lean development practices. In addition to your own insights, you may be able to take these game back to work to share with your co-workers.
This is a hands-on session so come prepared to have some fun!
There is no "right" answer to what you're "supposed to" learn from a game, so come ready to discover your own insights into software development processes and teamwork.
Software development is not one size fits all. Domain-Driven Design is significant where there's high complexity and high value. In these areas different tools might be needed. EventStorming is the best way I know to gather requirements in a complex environment, and also maps with CQRS/ES architecture perfectly.
As a Salesforce Developer I will... 7 Ground Rules for Success, Robert SösemannCzechDreamin
After a decade of working as a developer, consultant, and architect in the Salesforce ecosystem, I believe that it takes more than deep technical skills to be successful. Over and over I have seen a handful of meta-skills separate the rock stars from the crowd. Ground Rules have made Salesforce developers like me more effective in their work, more flexible towards changes, and more composed when the stress levels are high.
In this session, I will share the 7 Ground Rules – with practical examples and tools you can use next sprint – that will aid you and your team to success.
10 bezcennych lekcji dla software developera stającego się szefem firmyWojciech Seliga
[Originally Polish lecture with English slides - with a few exceptions]
Przez wiele lat byłem software developerem. Koncentrowałem się na kodzie, projektach software'owych oraz interakcjach w moim zespole i z klientami. Byłem pewny, że Agile rozwiązuje wszystkie problemy tego świata. Śmiałem się z komiksów Scotta Adamsa i stworzonej przez niego karykatury szefa (PHB). Życie było proste i piękne...
Teraz od ponad 8 lat prowadzę firmę software'ową, którą przy blisko 90 osobach trudno już nazwać maleństwem. Sam stałem się "szefem" na pełen etat.
Podczas prezentacji podzielę się z Wami różnymi doświadczeniami oraz naukami (nieraz bolesnymi) jakie wyniosłem w ostatnich latach podczas mojej stopniowej przemiany z developera/inżyniera w przedsiębiorcę i szefa firmy. O ile zapewne nie wszystkie sytuacje i wnioski mają lub mogą mieć (o ile marzysz o własnym startupie czy zespole) zastosowanie w Twoim życiu, same sobie ich uświadomienie może oszczędzić Ci w przyszłości straty mnóstwa czasu, energii i pieniędzy oraz uniknąć przykrych rozczarowań.
Building In Quality: The Beauty Of Behavior Driven Development (BDD)Synerzip
Behavior Driven Development (BDD) began as a means of helping developers practice Test Driven Development (TDD).
In this it was successful, but it quickly proved its value in many other ways. In this presentation, Larry Apke quotes heavily from the work of Uncle Bob Martin to make the case for TDD and then explains how developers can use BDD to take advantage of this excellent software development practice.
Larry also talks about his “Ten Reasons BDD Changes Everything” along with some easy ways to begin implementation of BDD in your software development organization immediately and what the corresponding future steps would be to take full advantage of this technique.
Code quality directly impacts how easy or hard your job is. The higher the quality, the easier it is for anyone (including you) to quickly jump in and get to work. Where do you start? In this session, Tonya Mork will empower you to simplify your code while dramatically increasing its code quality.
It's all about building <human code>, code that is highly human readable and understandable.
This slide deck is from a session I gave for WPSessions. https://wpsessions.com/sessions/code-quality-makes-jobs-easier/
WordCamp Nashville: Clean Code for WordPressmtoppa
Slides from my talk at WordCamp Nashville, including notes. Covers why clean code is important, and provides 10 tips to make your code cleaner, for WordPress and beyond
Agile Development Overview (with a bit about builds)David Benjamin
I gave this presentation to our dev team when i started at Hannan IT back in October. Its a quick run through the Agile basics, with a bit of extra discussion on continuous integration.
I experimented here with scripting in two tangential sections in the hopes that it would avoid many more spontaneous tangents. It worked!
Architecting Solutions and Systems – Randy’s Secrets to SuccessRandy Williams
This session will provide background and guidance on how Randy has architected software solutions for the past 20+ years. This will cover a range of mostly technical topics, including infrastructure planning, trade-off considerations, performance and scalability, and separation of tiers. Expect to hear plenty of stories from real projects over his career, along with numerous tips on his secrets to success.
OSDC 2019 | Feature Branching considered Evil by Thierry de PauwNETWAYS
With DVCSs, branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what’s evil about feature branches, which is not necessarily the problems they introduce – but rather, the real reasons why teams are using them. After the session, you’ll understand a different branching strategy and how it relates to CI/CD.
Unicorn or Rhino? Agility in the Data Realm?Daniel Davis
What is that uniquely horned creature over there? Unicorn? Rhino? Our Data? As the world of “Data” is growing more and more, so are the technologies and tools around it continuing to advance and improve. Inevitably this also means the struggles and problems around it are also going to increase as well though. Thankfully these are usually not completely new and in fact tend to be very similar to other scenarios we’ve seen and solved for in the past. In this session we’ll explore the adoption of agile, lean & craft processes/practices within our data realms to seek solution to these new and growing concerns.
TDD vs. ATDD - What, Why, Which, When & WhereDaniel Davis
This is a slide deck for a discussion about Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD) and starting to explore the differences between them. Get some insight into why we use them and the advantages and disadvantages of both, as well as, get a better understanding of which should be used where and when. By the end of the session you should be well along the path to TDD vs. ATDD enlightenment.
Top 10 Things To Do If You Want To Get Fired Over A WordPress ProjectWilliam Bergmann
A rundown of 10 of the most common ways to wreck a WordPress project, along with tips to avoid them for Project Managers on both the Client and Agency side.
Common Characteristics of the Greatest DevelopersDaniel Davis
This slide deck takes a deep dive exploration into the common characteristics of the greatest developers of last century. As well as learning who the best of the best are. You can expect to cover a wide range of topics, from old school habits, to new school tricks, from wacky hacks, to vetted practices. Plan to leave with some new found insight into aspects you can put directly into your own work, all in hopes that you too can become one of the all time greats.
Do your unit tests feel like a chore to maintain? Are they sometimes useful but come with a high maintenance cost? Do you secretly believe you’d work faster without them there? A great test suite should help speed up your development process, not slow you down. This talk highlights some techniques you can use to improve the front-end unit tests you write.
How to successfully engage enterprise software vendors – software selectionJohn Cachat
It All Starts With The Sales Team
It Doesn’t Do What We Want
Vendors Tiers And Costs
Finding The Right Tier
Contract Language
SaaS Alternative
johncachat@hotmail.com
www.peproso.com
Similar to the best code, is code never written (20)
Safely Calling BS Against Teams & LeadershipDaniel Davis
We've all been in the situation where you know things just aren't right. Whether its a sense that comes from your brain, your gut or your heart, it's for sure a feeling that is actively setting off the BS radar. In this session we'll discuss some safe and trusted techniques for approaching and handling it with your teams and leadership. We'll also explore some better practices we can personally embrace to limit the amount of BS we ourselves spread.
When it comes to software these days coding is becoming more and more the easy part. Just think of all the options you have when it comes to languages, tools, and sites to visit for learning or questions. In this talk we'll take a deep dive into exploring the human characteristics behind software development and learn how we can better support them, both from within ourselves and our organizations for improved future success.
not BEYOND agile, but rather BEHIND itDaniel Davis
Since long before the manifesto, Agile approaches have proven time and time again to be very successful at delivering business value for organizations. Along with those approaches come defined processes and practices, but is that all it takes? Often agile is referred to not as a "methodology", but rather a "mindset". Well then, what are the other things not process or practice specific that we need to be mindful of to ensure we deliver on the business value expected? In this session we'll take a deeper dive into exploring the human characteristics behind agile and learn how we may better support them both within ourselves and our organizations for improved future success.
assert(false) agile.healthy == agile.easyDaniel Davis
Any organization that has attempted to shift toward more of an agile approach knows that it isn’t easy. In this slide deck we take a mock testing approach to review the top characteristics of healthy agile teams and look at what they did to get there.
A Family That Hacks Together, Interacts Together!Daniel Davis
Everyone's heard the old saying "A family thats plays together, stays together", right? Well this session is going to kick that up a notch and talk about getting the family to "hack" together. It starts out discussing the different forms of hacking a family might embrace. Along the way it highlights what supplies & equipment you might need, as well as suggesting the overall costs that one might expect to incur. It then takes a brief focus on safety and proper use of that equipment. The session finishes off with some tips and tricks that may help with both the hacks themselves, as well as getting the family to actually interact by joining in on the fun.
The 3 Fs Equation : Failure - Fear = FreedomDaniel Davis
Failure with the absence of fear leads to freedom. From this freedom comes the ability to be more creative, more innovative, more courageous and even more adventurous. Join this session to get an in-depth look into how fear is a predominant factor in the perception of failure. Then by exploring the practices that can help identify fear, as well as gaining a thorough understanding of the methods that can help combat it, expect to gain a new found freedom to fail, without having to go all "Braveheart" when you get back to work!
In this presentation we'll take a high level view of that messy thing most of us call a career in this ever evolving technological world. We'll more deeply explore how Agile fits into the the mix, whether for better or for worse, and drive out what we can do about it to help us achieve the goals we have set before us.
What the heck is DevOps and why do we need it?Daniel Davis
During this presentation we explore what DevOps is and the different flavors. We learn what some of the better practices and tools are and get a high level understanding of how they can be used to improve your organizations delivery of business value.
We've all caught some of the hype around "agile" and most have at least heard (if not directly seen) its benefits. In this presentation, we are going to dive deep into one key aspect - Continual Learning. We'll discuss how it has become a staple for our modern day technical careers; how if you aren't growing, adapting, and evolving, then you're stagnating and how eventually you won't outgrow your job - it will outgrow you. We'll then investigate the factors of Learning Agility and explore ways that we can use it to help us not just survive, but thrive in our current environments.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
Into the Box Keynote Day 2: Unveiling amazing updates and announcements for modern CFML developers! Get ready for exciting releases and updates on Ortus tools and products. Stay tuned for cutting-edge innovations designed to boost your productivity.
Strategies for Successful Data Migration Tools.pptxvarshanayak241
Data migration is a complex but essential task for organizations aiming to modernize their IT infrastructure and leverage new technologies. By understanding common challenges and implementing these strategies, businesses can achieve a successful migration with minimal disruption. Data Migration Tool like Ask On Data play a pivotal role in this journey, offering features that streamline the process, ensure data integrity, and maintain security. With the right approach and tools, organizations can turn the challenge of data migration into an opportunity for growth and innovation.
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
Advanced Flow Concepts Every Developer Should KnowPeter Caitens
Tim Combridge from Sensible Giraffe and Salesforce Ben presents some important tips that all developers should know when dealing with Flows in Salesforce.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
2. the best code, is code never written
@daniel_davis
• Brief Intro
• Focus For The Session
• Why Is It Important
• Figurative Techniques
• Literal Techniques
• Recap
• Q & A
Agenda
2
3. the best code, is code never written
@daniel_davis
• Founder/Lead Consultant at Elev8
• Business Improvement Consultant
• Developer & Technical Coach
• Innovator, Life Hacker, Maker
• Pro Snowboard Instructor
• Parent of 3 + 2
Brief Intro
3
4. the best code, is code never written
@daniel_davis
• Discussion over Presentation
• Principles over Prescription
Focus For The Session
4
5. the best code, is code never written
@daniel_davis
Global cost of code is
hard to narrow down.
However, I did find that in
2018, in the US alone the
cost for poor quality code
was $2,840,000,000,000.
Why Is It Important
5
6. the best code, is code never written
@daniel_davis
Code Is Expensive -
- Hard To Write
- Cost Of Delay
- Complicated To Maintain
We Are Expensive - (prefer to keep it so)
- Smart / Talented / Rare
- Specialized Skillsets
- Dedicated & Committed Mindset
Why Is It Important
6
7. the best code, is code never written
@daniel_davis
Pizza Delivery Service Voice App that was solved by a
simple 1-(800) phone number that already existed.
YAGNI - (You Aren’t Gonna Need It)
- Lines of code are a liability, don’t look at it as the "number of
lines produced”, but rather the “number of lines spent”.
- More explicitly, lines of code saved is directly correlated to
dollars we didn’t spend.
- Minimizes waste.
Figurative Techniques
7
8. the best code, is code never written
@daniel_davis
NIH - (Not Invented Here)
- Beg (to use it)
- Borrow (if already written don’t reinvent it)
- Steal (note ‘stealing’ to learn is far different from stealing for profit)
- Cheat To Win (it’s was bad when we were kids, it’s cool now)
There is a fine line when it comes to relying on others code.
Make sure the source is trusted and reliable and
test protect it as if it was your own.
Figurative Techniques
8
9. the best code, is code never written
@daniel_davis
FITYMI - (Fake It Till You Make It)
- Mock, Fake, Stub, Etc… don’t make the actual thing it until
you know you absolutely need it.
- “It” is far better suited to your emotions, ie. confidence, pride,
etc… than it is actual skills.
Figurative Techniques
9
“The cheapest, fastest, and most reliable components of a
computer system are those that aren’t there.”
- Gordon Bell
10. the best code, is code never written
@daniel_davis
Not all your thoughts on the solution should turn into code.
In fact most shouldn’t. Be aggressively de-selective.
KISS - (Keep It Stupid Simple)
- What's the simplest thing that could possibly work?
(Beck/Cunningham)
- ST2CPWAKYO2HRJOM (The Simplest Thing That Could Possibly
Work And Keep You Out Of Human Resources, Jail, Or Morgue)
- Simple is subjective, it’s really just focusing on “one thing”
Figurative Techniques
10
11. the best code, is code never written
@daniel_davis
“A complex system that works is inevitably found to have
evolved from a simple system that works.”
- John Gall
ED - (Emergent Design or Evolutionary Design)
- Primitive Whole, which builds in sophistication over time.
- Pursue high-value and high-risk items early.
- Follow Scientific Method
- Give it time to learn, but don’t be afraid to fail fast.
Figurative Techniques
11
12. the best code, is code never written
@daniel_davis
MVP -
Figurative Techniques
12
13. the best code, is code never written
@daniel_davis
Pretotyping -
- Avoid “Can we build it?” or “Will it work?” Instead focus on
“Should we build it at all?” or “If we build it, will people buy it?”
- Pretotypes make it possible to make a go/no-go decision at a
fraction of the cost of prototypes: hours or days instead of
weeks or months, and pennies instead of dollars.
Literal Techniques
13
“Design until you feel you understand the problem.
Write code until you realize you don’t.”
- Software Engineering Conference, 1968
14. the best code, is code never written
@daniel_davis
Literal Techniques
ATDD & TDD Visualized -
- The shared practice of - Red - Green - Refactor
14
15. the best code, is code never written
@daniel_davis
The biggest advantage TDD (Design) provides is the
ability to protect you from yourself.
TDD - (Test Driven Design/Development)
- Writing a tests before code helps assure only necessary code is
written.
- Doing so inherently makes the code simple and clear.
- Ensures the individual units of the system are built correctly.
Literal Techniques
15
16. the best code, is code never written
@daniel_davis
The biggest advantage ATDD provides is the ability to
protect the business from themselves.
ATDD - (Acceptance Test Driven Design/Dev)
- Same approach as TDD, however these tests are generally
written from a business/stakeholders perspective.
- Helps devs identify the appropriate code to write, that is, code
that reflects the outcomes desired.
- Meant to ensure the business value of the system is being met.
Literal Techniques
16
17. the best code, is code never written
@daniel_davis
“The single biggest problem with communication
is the illusion that it has taken place.”
- George Bernard Shaw
WWAC - (Well Written Acceptance Criteria)
- Acceptance Criteria that has real and legit content and context
to the business value that is being requested.
- Understandable by any and all team members.
- Realistic and Achievable.
Literal Techniques
17
18. the best code, is code never written
@daniel_davis
Rules are meant to be broken. Make sure they are
manageable and have some kind of ranking and/or priority.
DoR & DoD - (Definition of Ready & Done)
- Driven more from a team standards approach.
- Still also Realistic and Achievable.
- Meet the need and ONLY the need.
- Don’t over-complicate them.
Literal Techniques
18
19. the best code, is code never written
@daniel_davis
Figurative
• YAGNI
• NIH
• FITYMI
• KISS
• ED
Recap
Literal
• Pretotyping
• TDD
• ATDD
• WWAC
• DoR & DoD
19
20. the best code, is code never written
@daniel_davis
Resources
• https://www.it-cisq.org/the-cost-of-poor-quality-software-in-the-us-a-2018-
report/The-Cost-of-Poor-Quality-Software-in-the-US-2018-Report.pdf
• https://www.artima.com/intv/simplest.html
• https://insights.dice.com/2018/07/05/tech-pros-steal-code-good-idea-bad/
• https://www.pretotyping.org/uploads/1/4/0/9/14099067/
pretotype_it_2nd_pretotype_edition-2.pdf
• https://github.com/northofnormal/ConferenceTalks/blob/master/
qualityvsquantity.pdf
• https://docs.google.com/document/d/
1A1sLe2R-9XhRpOiAZfKii2944PM5tUKS17EgaiGCnLE/export?format=pdf
20
21. the best code, is code never written
@daniel_davis
Q & A
21
22. the best code, is code never written
@daniel_davis
Now, go unto the world
& not write some code!
22
23. the best code, is code never written
@daniel_davis
Thank you!
Daniel Davis
dan@elev8.services
@daniel_davis
linkedin.com/in/davisdaniel
23