This document provides an overview of getting started with Puppet. It discusses setting goals for Puppet implementation, understanding key concepts and vocabulary, developing modules, testing code, and sharing modules. The document emphasizes keeping implementations simple, safe, secure and scalable through practices like loose coupling, orthogonal design, and experimentation. It also recommends focusing on quality, testing, and avoiding duplication and complexity when developing Puppet code and modules.
OpenStack Summit Vancouver: Lessons learned on upgradesFrédéric Lepied
Deploying OpenStack in production at any scale, upgrade support is one of the requirements to have a successful deployment. Without upgrade management, adeployment will have bugs and security issues from day 1. Also in longer term, it will miss the latest features that OpenStack offers.
CAPS: What's best for deploying and managing OpenStack? Chef vs. Ansible vs. ...Daniel Krook
Presentation at the OpenStack Summit in Tokyo, Japan on October 29, 2015.
http://sched.co/49vI
This talk will cover the pros and cons of four different OpenStack deployment mechanisms. Puppet, Chef, Ansible, and Salt for OpenStack all claim to make it much easier to configure and maintain hundreds of OpenStack deployment resources. With the advent of large-scale, highly available OpenStack deployments spread across multiple global regions, the choice of which deployment methodology to use has become more and more relevant.
Beyond the initial day-one deployment, when it comes to the day-two and beyond questions of updating and upgrading existing OpenStack deployments, it becomes all the more important choose the right tool.
Come join the Bluebox and IBM team to discuss the pros and cons of these approaches. We look at each of these four tools in depth, explore their design and function, and determine which scores higher than others to address your particular deployment needs.
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Paul Czarkowski - Cloud Engineer at Blue Box, an IBM company
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Learn how to use Continuous Delivery for Puppet Enterprise (CD4PE) in an interactive workshop with hands-on labs. What's CD4PE? CD4PE is the continuous delivery add-on to Puppet Enterprise, aimed at accelerating the speed at which you can get Puppet code changes deployed into production safely. CD4PE facilitates code collaboration across teams, and dramatically improves the release management process for teams that own & maintain individual Puppet modules. CD4PE integrates with both Puppet Enterprise as well as your version control system of choice.
After completing the workshop, you will be able to use CD4PE to perform common code management tasks on your Puppet control repo and modules.
OpenStack Summit Vancouver: Lessons learned on upgradesFrédéric Lepied
Deploying OpenStack in production at any scale, upgrade support is one of the requirements to have a successful deployment. Without upgrade management, adeployment will have bugs and security issues from day 1. Also in longer term, it will miss the latest features that OpenStack offers.
CAPS: What's best for deploying and managing OpenStack? Chef vs. Ansible vs. ...Daniel Krook
Presentation at the OpenStack Summit in Tokyo, Japan on October 29, 2015.
http://sched.co/49vI
This talk will cover the pros and cons of four different OpenStack deployment mechanisms. Puppet, Chef, Ansible, and Salt for OpenStack all claim to make it much easier to configure and maintain hundreds of OpenStack deployment resources. With the advent of large-scale, highly available OpenStack deployments spread across multiple global regions, the choice of which deployment methodology to use has become more and more relevant.
Beyond the initial day-one deployment, when it comes to the day-two and beyond questions of updating and upgrading existing OpenStack deployments, it becomes all the more important choose the right tool.
Come join the Bluebox and IBM team to discuss the pros and cons of these approaches. We look at each of these four tools in depth, explore their design and function, and determine which scores higher than others to address your particular deployment needs.
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Paul Czarkowski - Cloud Engineer at Blue Box, an IBM company
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Learn how to use Continuous Delivery for Puppet Enterprise (CD4PE) in an interactive workshop with hands-on labs. What's CD4PE? CD4PE is the continuous delivery add-on to Puppet Enterprise, aimed at accelerating the speed at which you can get Puppet code changes deployed into production safely. CD4PE facilitates code collaboration across teams, and dramatically improves the release management process for teams that own & maintain individual Puppet modules. CD4PE integrates with both Puppet Enterprise as well as your version control system of choice.
After completing the workshop, you will be able to use CD4PE to perform common code management tasks on your Puppet control repo and modules.
Gradle is an open source build automation system that builds upon the concepts of Apache Ant and Apache Maven and introduces a Groovy-based domain-specific language (DSL) instead of the XML form used by Apache Maven for declaring the project configuration.
Using Puppet - Real World Configuration ManagementJames Turnbull
Configuration management is the oft-misunderstood (and possibly black) art of managing your IT environment, infrastructure, and costs. Done well it can reduce operational errors and outages, simplify your environment, and help maintain the sanity of your IT staff.
Puppet is part of the bright future of configuration management for heterogeneous Unix systems. It combines automation, a powerful abstraction language, and uses a client-server model that can scale to suit enterprise-size environments. Puppet is written in Ruby and authored by recovering system administrator-turned-developer Luke Kanies.
This session explains why configuration management is important, the benefits configuration management will deliver, and how all of this can be achieved using Puppet. The session also explains emerging best practices in configuration management and addresses:
* What is configuration management? Or why am I here?
* Benefits, risks, and challenges: build fire resistant infrastructure rather than fight fires
* Best practice: how do we do this configuration management magic right?
* Where does Puppet fit in and why should management pay for its implementation?
* Why using Puppet will save you money and help staff retention (although is unlikely to stop world hunger)
* Real world configuration management using Puppet: code, examples, explanations, and using Puppet in anger
* Measuring the results and pocketing the returns
* Where to from here: some ideas about the future (may include wild-arse guesses)
[KubeCon NA 2018] Telepresence Deep Dive Session - Rafael Schloming & Luke Sh...Ambassador Labs
One of the challenges facing Telepresence is growing the contributor community. It’s a complex application that requires a good understanding of OS networking, VPNs, Kubernetes, and everything in between. We’ll kick off this meeting with a general architectural overview of Telepresence. We’ll talk about how we’ve managed the project to date, and our investments to make it easier. We want to then turn it over for an interactive discussion with participants to see what we can do to make it easier to contribute and grow the Telepresence community.
Chef is an open source configuration management and service integration automation tool that has been integral to a number of large successful OpenStack deployments. This talk will provide a brief introduction to Chef and why it frequently the configuration tool of choice for large deployments and discuss the use of Chef within the OpenStack ecosystem (development, testing, deploying and managing the installation). Chef also provides the ability to manage the instances running on top of Nova through the knife-openstack plugin.
Monitoring as an entry point for collaborationJulien Pivotto
In the last years, we have been building complex stacks, made from lots of components. All of this backed by multiple teams. This talk will present how you can use monitoring to look at the business side and have everyone looking at the same dashboards, making cooperation a reality.
Arquillian is an innovative and highly extensible testing platform for the JVM that enables developers to easily create automated integration, functional and acceptance tests for Java middleware, from Java EE and beyond.
For years we’ve been exploring how to layer and separate our code to test in isolation on the unit level. We’ve kept integration and functional testing as a big ball of mud; jumping straight from unit to full system testing. But can we apply some of the same lessons learned from unit to integration testing?
Speaker Bio:
Arquillian project lead, Aslak Knutsen, is a Senior Software Engineer at Red Hat where he is working on projects such as Arquillian and ShrinkWrap, one of the founders of the JBoss Testing initiative and a speaker at major industry conferences including JavaOne, Devoxx, Jazoon, JFokus, Geecon, JUDCon and JBoss World.
Leonid Vasilyev "Building, deploying and running production code at Dropbox"IT Event
Reproducible builds, fast and safe deployment process together with self-healing services form the basis of stable and maintainable infrastructure. In this talk I’d like to cover, from the Site Reliability Engineering (SRE) perspective, how Dropbox addresses above challenges, what technologies are used and what lessons were learnt during implementation process.
Roman Shaposhnik of Cloudera and the Apache Software Foundation talks on "Delopying Hadoop-Based Bigdata Environments: [Tall] Tales from the Frontier" at Puppet Camp Silicon Valley 2012.
In a rare mash-up, DevOps is increasingly blending the work of both application and network security professionals. In a quest to move faster, organizations can end up creating security vulnerabilities using the tools and products meant to protect them. Both Chris Gates (carnal0wnage) and Ken Johnson (cktricky) will share their collaborative research into the technology driving DevOps as well as share their stories of what happens when these tools are used insecurely as well as when the tools are just insecure.
Technologies discussed will encompass AWS Technology, Chef, Puppet, Hudson/Jenkins, Vagrant, Kickstart and much, much more. Everything from common misconfigurations to remote code execution will be presented. This is research to bring awareness to those responsible for securing a DevOps environment.
An introduction to SBT and how it works internally.
Talk from September 2013 Slovak Scala User Group meet-up, http://www.meetup.com/slovak-scala/events/133327122/
Gradle is an open source build automation system that builds upon the concepts of Apache Ant and Apache Maven and introduces a Groovy-based domain-specific language (DSL) instead of the XML form used by Apache Maven for declaring the project configuration.
Using Puppet - Real World Configuration ManagementJames Turnbull
Configuration management is the oft-misunderstood (and possibly black) art of managing your IT environment, infrastructure, and costs. Done well it can reduce operational errors and outages, simplify your environment, and help maintain the sanity of your IT staff.
Puppet is part of the bright future of configuration management for heterogeneous Unix systems. It combines automation, a powerful abstraction language, and uses a client-server model that can scale to suit enterprise-size environments. Puppet is written in Ruby and authored by recovering system administrator-turned-developer Luke Kanies.
This session explains why configuration management is important, the benefits configuration management will deliver, and how all of this can be achieved using Puppet. The session also explains emerging best practices in configuration management and addresses:
* What is configuration management? Or why am I here?
* Benefits, risks, and challenges: build fire resistant infrastructure rather than fight fires
* Best practice: how do we do this configuration management magic right?
* Where does Puppet fit in and why should management pay for its implementation?
* Why using Puppet will save you money and help staff retention (although is unlikely to stop world hunger)
* Real world configuration management using Puppet: code, examples, explanations, and using Puppet in anger
* Measuring the results and pocketing the returns
* Where to from here: some ideas about the future (may include wild-arse guesses)
[KubeCon NA 2018] Telepresence Deep Dive Session - Rafael Schloming & Luke Sh...Ambassador Labs
One of the challenges facing Telepresence is growing the contributor community. It’s a complex application that requires a good understanding of OS networking, VPNs, Kubernetes, and everything in between. We’ll kick off this meeting with a general architectural overview of Telepresence. We’ll talk about how we’ve managed the project to date, and our investments to make it easier. We want to then turn it over for an interactive discussion with participants to see what we can do to make it easier to contribute and grow the Telepresence community.
Chef is an open source configuration management and service integration automation tool that has been integral to a number of large successful OpenStack deployments. This talk will provide a brief introduction to Chef and why it frequently the configuration tool of choice for large deployments and discuss the use of Chef within the OpenStack ecosystem (development, testing, deploying and managing the installation). Chef also provides the ability to manage the instances running on top of Nova through the knife-openstack plugin.
Monitoring as an entry point for collaborationJulien Pivotto
In the last years, we have been building complex stacks, made from lots of components. All of this backed by multiple teams. This talk will present how you can use monitoring to look at the business side and have everyone looking at the same dashboards, making cooperation a reality.
Arquillian is an innovative and highly extensible testing platform for the JVM that enables developers to easily create automated integration, functional and acceptance tests for Java middleware, from Java EE and beyond.
For years we’ve been exploring how to layer and separate our code to test in isolation on the unit level. We’ve kept integration and functional testing as a big ball of mud; jumping straight from unit to full system testing. But can we apply some of the same lessons learned from unit to integration testing?
Speaker Bio:
Arquillian project lead, Aslak Knutsen, is a Senior Software Engineer at Red Hat where he is working on projects such as Arquillian and ShrinkWrap, one of the founders of the JBoss Testing initiative and a speaker at major industry conferences including JavaOne, Devoxx, Jazoon, JFokus, Geecon, JUDCon and JBoss World.
Leonid Vasilyev "Building, deploying and running production code at Dropbox"IT Event
Reproducible builds, fast and safe deployment process together with self-healing services form the basis of stable and maintainable infrastructure. In this talk I’d like to cover, from the Site Reliability Engineering (SRE) perspective, how Dropbox addresses above challenges, what technologies are used and what lessons were learnt during implementation process.
Roman Shaposhnik of Cloudera and the Apache Software Foundation talks on "Delopying Hadoop-Based Bigdata Environments: [Tall] Tales from the Frontier" at Puppet Camp Silicon Valley 2012.
In a rare mash-up, DevOps is increasingly blending the work of both application and network security professionals. In a quest to move faster, organizations can end up creating security vulnerabilities using the tools and products meant to protect them. Both Chris Gates (carnal0wnage) and Ken Johnson (cktricky) will share their collaborative research into the technology driving DevOps as well as share their stories of what happens when these tools are used insecurely as well as when the tools are just insecure.
Technologies discussed will encompass AWS Technology, Chef, Puppet, Hudson/Jenkins, Vagrant, Kickstart and much, much more. Everything from common misconfigurations to remote code execution will be presented. This is research to bring awareness to those responsible for securing a DevOps environment.
An introduction to SBT and how it works internally.
Talk from September 2013 Slovak Scala User Group meet-up, http://www.meetup.com/slovak-scala/events/133327122/
Reducing inertia in organizations is the key to a successful DevOps transitionJoep Piscaer
Looking at your organizational structure is key to removing inertia in the organization around a agile/scrum initiative. In this presentation we'll look at an ideal 'fairytale' as a dot on the horizon.
DevOpsDaysRiga 2018: Joep Piscaer - Reducing inertia with Public Cloud and Op...DevOpsDays Riga
"I have a strategy to solve the DevOps transitional challenge. It is called reducing inertia that can be seen on daily basis in finances, team behavior and tech stacks. Reducing the friction in these areas is key to successfully move to the DevOps way of work. For me, ‘inertia’ is a good way of making value flow visible and I’ve been using it as the principle underlying my work. This approach can be applied especially successfully in more complex environments, such as enterprises."
Joep Piscaer is a technologist with team building skills. He likes all things infrastructure (cloud, storage, virtualization), but really shines when it comes to DevOps and Infra-as-Code. Currently, Joep is building the Jumbo Tech Campus. It is the second biggest supermarket in the Netherlands and the fastest growing online supermarket there.
Clan code is extremely essential to build scalable application which can be maintained quite easily and improved further
Slide was prepared with contribution to my colleague
and i thank them for the help!
”In general programmers are pretty smart people. Smart people sometimes like to show off their smarts by demonstrating their mental juggling abilities. One difference between a smart programmer and a professional programmer is that the professional understands that clarity is king. Professionals use their powers for good and write code that others can understand.”
In this presentation we will see a brief introduction to design patterns, their origin and why we should learn them, Then we will spend most of the presentation to transform a real code sample by extracting some of the most common used patterns.
Second "code school lesson" for Eurosport's developers.
1. Refactoring : when? why? how?
2. Single Responsability
3. Practical case : clean architecture.
A short introduction to the more advanced python and programming in general. Intended for users that has already learned the basic coding skills but want to have a rapid tour of more in-depth capacities offered by Python and some general programming background.
Execrices are available at: https://github.com/chiffa/Intermediate_Python_programming
Skills that are adequate to build a small system will not suffice to build a larger system. This slidedeck was used in a talk where the differences were highlighted and methods and techniques to build large systems recommended.
Automating it management with Puppet + ServiceNowPuppet
As the leading IT Service Management and IT Operations Management platform in the marketplace, ServiceNow is used by many organizations to address everything from self service IT requests to Change, Incident and Problem Management. The strength of the platform is in the workflows and processes that are built around the shared data model, represented in the CMDB. This provides the ‘single source of truth’ for the organization.
Puppet Enterprise is a leading automation platform focused on the IT Configuration Management and Compliance space. Puppet Enterprise has a unique perspective on the state of systems being managed, constantly being updated and kept accurate as part of the regular Puppet operation. Puppet Enterprise is the automation engine ensuring that the environment stays consistent and in compliance.
In this webinar, we will explore how to maximize the value of both solutions, with Puppet Enterprise automating the actions required to drive a change, and ServiceNow governing the process around that change, from definition to approval. We will introduce and demonstrate several published integration points between the two solutions, in the areas of Self-Service Infrastructure, Enriched Change Management and Automated Incident Registration.
Simplified Patch Management with Puppet - Oct. 2020Puppet
Does your company struggle with patching systems? If so, you’re not alone — most organizations have attempted to solve this issue by cobbling together multiple tools, processes, and different teams, which can make an already complicated issue worse.
Puppet helps keep hosts healthy, secure and compliant by replacing time-consuming and error prone patching processes with Puppet’s automated patching solution.
Join this webinar to learn how to do the following with Puppet:
Eliminate manual patching processes with pre-built patching automation for Windows and Linux systems.
Gain visibility into patching status across your estate regardless of OS with new patching solution from the PE console.
Ensure your systems are compliant and patched in a healthy state
How Puppet Enterprise makes patch management easy across your Windows and Linux operating systems.
Presented by: Margaret Lee, Product Manager, Puppet, and Ajay Sridhar, Sr. Sales Engineer, Puppet.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
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.
Top 7 Unique WhatsApp API Benefits | Saudi ArabiaYara Milbes
Discover the transformative power of the WhatsApp API in our latest SlideShare presentation, "Top 7 Unique WhatsApp API Benefits." In today's fast-paced digital era, effective communication is crucial for both personal and professional success. Whether you're a small business looking to enhance customer interactions or an individual seeking seamless communication with loved ones, the WhatsApp API offers robust capabilities that can significantly elevate your experience.
In this presentation, we delve into the top 7 distinctive benefits of the WhatsApp API, provided by the leading WhatsApp API service provider in Saudi Arabia. Learn how to streamline customer support, automate notifications, leverage rich media messaging, run scalable marketing campaigns, integrate secure payments, synchronize with CRM systems, and ensure enhanced security and privacy.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
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.
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.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
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.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
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.
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
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.
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).
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.
Launch Your Streaming Platforms in MinutesRoshan Dwivedi
The claim of launching a streaming platform in minutes might be a bit of an exaggeration, but there are services that can significantly streamline the process. Here's a breakdown:
Pros of Speedy Streaming Platform Launch Services:
No coding required: These services often use drag-and-drop interfaces or pre-built templates, eliminating the need for programming knowledge.
Faster setup: Compared to building from scratch, these platforms can get you up and running much quicker.
All-in-one solutions: Many services offer features like content management systems (CMS), video players, and monetization tools, reducing the need for multiple integrations.
Things to Consider:
Limited customization: These platforms may offer less flexibility in design and functionality compared to custom-built solutions.
Scalability: As your audience grows, you might need to upgrade to a more robust platform or encounter limitations with the "quick launch" option.
Features: Carefully evaluate which features are included and if they meet your specific needs (e.g., live streaming, subscription options).
Examples of Services for Launching Streaming Platforms:
Muvi [muvi com]
Uscreen [usencreen tv]
Alternatives to Consider:
Existing Streaming platforms: Platforms like YouTube or Twitch might be suitable for basic streaming needs, though monetization options might be limited.
Custom Development: While more time-consuming, custom development offers the most control and flexibility for your platform.
Overall, launching a streaming platform in minutes might not be entirely realistic, but these services can significantly speed up the process compared to building from scratch. Carefully consider your needs and budget when choosing the best option for you.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
5. How
I
got
Started
• Oracle
*.*
• Enterprise
Linux
• Needed
a
way
to
not
waste
every
Monday
and
every
day
I
needed
to
refresh/clone
• Kill
technical
debt
• “Classic
Enterprise..”
@byron_miller
5
6. Vocabulary
• Convergence
–
stabilize
over
[me
• Idempotent
–
unchanged
element
when
operated
on
by
itself
• Orchestra[on
–
Coordina[on
&
Management
of
complex
systems
• Puppet
–
The
ecosystem
• Manifests
&
Modules
–
The
code
@byron_miller
6
7. More
Vocabulary
• ENC
–
External
Node
Classifier
• Mcollec[ve
–
orchestra[on
tool
set
• Hiera
–
key
value
lookup
system
• Node
–
Server/VM
• Facter
–
node
facts
• Types
&
Providers
–
Built
in
resources
you
declare
in
puppet
manifests
@byron_miller
7
9. Begin
by
thinking
• Puppet
has
a
learning
curve
but
making
it
work
for
your
organiza[on
is
up
to
how
you
define
“ge#ng
things
done”
and
your
future
• The
“vocabulary”
and
“Verbiage”
of
puppet
is
well
documented
&
simple
with
a
liele
prac[ce
• Think
about
your
work
• Think
about
your
future
@byron_miller
9
11. Ge#ng
Started
–
Set
Goals
• What
is
your
goal(s)?
• How
do
you
measure
success
or
failure?
• What
is
your
Intent?
Know
the
theory
of
your
desired
state
@byron_miller
11
12. How
do
you
work?
• Is
your
organiza[on
highly
constrained
&
highly
ordered?
• Do
you
strive
for
self-‐regula[ng
systems?
• Is
your
goal
compliance?
• Stability?
• Agility?
@byron_miller
12
13. Define
Workflow
• Simple
– Easy
to
install
&
Maintain
• Safe
– Version
Control
-‐
“Git
workflow”
• Secure
– SSH
/
SSL
/
Accountability
• Scalable
– Handle
1000s
of
nodes
@byron_miller
13
19. Style
• Make
quality
a
requirement
• Know
when
to
stop
(don’t
over
op[mize)
20. DRY
–
Don’t
repeat
yourself
• Imposed
Duplica/on
–
Apparent
lack
of
choice
• Inadvertent
Duplica/on
–
Not
realize
that
they’re
duplica[ng
informa[on
• Impa/ent
Duplica[on
–
lazy
/
duplicate
because
it
seems
easier
• Interdeveloper
Duplica/on
–
Mul[ple
people
on
teams
/
mul[ple
teams.
21. Code
• Keep
low
level
knowledge
in
code
• Reserve
Comments
for
high
level
expecta[ons
• Foster
an
environment
where
it’s
easier
to
find
and
reuse
exis[ng
stuff
than
to
write
it
yourself.
22. Scope
&
Avoid
Global
data
• Every
[me
you
reference
global
data
it
[es
you
to
the
other
components
that
share
data
• Use
Scoping
23. Manage
Complexity
Complexity
is
generally
used
to
characterize
something
with
many
parts
where
those
parts
interact
with
each
other
in
mul[ple
ways.
24. Orthogonal
-‐
Safe
to
Fail
• Independent
/
lightly
coupled
systems
– Eliminates
effects
of
unrelated
things
– Design
self
contained
things
• Increased
produc[vity
&
contained
risk
25. Prototype
(experiment)
• Architecture
• New
func[onality
in
exis[ng
systems
• Structure
or
contents
of
external
data
• Third
party
tools
or
components
• Performance
issues
• User
interface
/
experience
/
design
26. Experiments
• Worry
less
about
correctness,
completeness,
robustness
and
style.
• Focus
on
design
/
defini[on
• Is
coupling
minimized?
• Can
you
iden[fy
poten[al
sources
of
duplica[on?
28. Test
• Loosely
coupled
systems
easier
to
test
–
interac[ons
between
components
are
limited.
– Unit
tes[ng
is
easier
– Test
in
CI
pipeline
• Beaker
/
rspec
/
puppet
lint
29. Refactor
• Avoid
code
rot.
Don’t
let
bad
code
fester
and
turn
all
your
code
into
abandonware
• Code
rot
will
keep
you
from
staying
current,
maintaining
your
skills
and
generally
cause
people
to
shy
away
from
platorm
for
new
shiny
thing..
30. It’s
code
• Version
control
• Test
• Refactor
• Share.
• forge
31. Module
Template
• “puppet
module
generate”
–
use
the
boiler
plate
scaffolding
• Use
Garethr’s
boiler
plate
–
nice
&
updated
heps://github.com/garethr/puppet-‐module-‐
skeleton
32. Data
Separa[on
• Hiera
– Yaml,
Mysql,
GPG
etc..
• ENC
– Puppet
PE
– Foreman
– Homemade
– ?
• Single
source
of
truth..
Anyone
have
any?
J
33. Parameterized
Classes
• Great
for
ENCs
• Easy
to
set
default
values
• Portable
/
Shareable
• Just
do
it..
34. Class
Inheritance
• Use
within
a
module
to
reduce
repe[[on
(DRY)
• Inheri[ng
from
other
modules
decreases
modularity,
but
hard
to
avoid
– ENC
confusion
35. Code
Defensively
• Catch
unexpected
events
before
they
break
things
–
gracefully
bow
out
if
you
don’t
support
platorm
– Default
case
fail
on
unsupported
platorms
• Plan
for
Puppet
Future
parser
– Some
changes
/
restric[ons
– Expressions,
Lambdas,
Itera[ons
&
more
heps://docs.puppetlabs.com/puppet/latest/
reference/experiments_future.html
36. It’s
code
but…
• Don’t
think
of
it
as
“object
oriented”
from
a
programmers
perspec[ve
• It’s
a
“Domain
Specific
Language”
(DSL)
used
to
describe
a
desired
state.
@byron_miller
36
37. Prac[ce
• Vagrant
/
VM
instances
– Build
/
test
/
deploy
– Pull
modules
from
forge
• Read
• Test
• Deploy
• experiment
@byron_miller
37
41. Simple
Domain
• Start
with
what
you
know
• Relieve
pain
points
• Remove
constraints
• “Cause
–
effect”
rela[onships
–
you
can
codify
this
@byron_miller
41
43. Simple
-‐>
Chaos
• When
simple
breaks
– All
hell
breaks
loose.
@byron_miller
43
44. Infrastructure
• as
code..
Bus[ng
out
some
Deming..
“As
a
System
of
profound
knowledge”
A. Apprecia[on
for
a
system
B. Theory
of
Varia[on
C. Theory
of
Knowledge
D. Psychology
@byron_miller
44
45. Systems
Approach
Taking
a
systems
approach
results
in
viewing
the
organiza[on
in
terms
of
many
internal
and
external
interrelated
connec[ons
and
interac[ons
as
opposed
to
discrete
and
independent
departments
or
processes
governed
by
various
chains
of
command.
Apprecia[on
for
a
system..
@byron_miller
45
46. Varia[on
Why
did
something
go
wrong?
How
can
we
repeat
success?
Common
Cause
–
predictable
varia[on
within
a
system
Special
Cause
–
unique
event
outside
the
system
@byron_miller
46
47. Knowledge
• Theory,
Experimenta[on,
Sta[s[cal
analysis,
conveyed
meaning,
processes.
“Informa)on
is
not
knowledge”
-‐Deming
@byron_miller
47
49. Management
Is..
• Predic[on
• Theory
– What
causes
posi[ve
interac[ons?
– What
removes
conflict?
• Understanding
&
Conveying
meaning
of
a
system
• People..
@byron_miller
49
51. The
system
Intent..
• What
causes
behaviors
outside
the
system?
“The
obliga[on
of
any
component
is
to
contribute
its
best
to
the
system
but
it
will
not
do
that
unless
the
system
is
managed”
@byron_miller
51
53. Where
we
want
to
be
Future
Backwards:
Perspec[ves
of
people
within
an
organiza[on
give
them
a
limited
view
of
the
present,
and
such
entrained
paeerns
of
past
percep[on
can
determine
its
future.
@byron_miller
53
54. Your
future
Ge#ng
there..
• Flow
• Measure
• Retrospec[ves
• Involve
Stakeholders
• Sense
-‐>
Categorize
-‐>
Respond
“Bias
against
crea)vity
is
fueled
by
uncertainty”
-‐Deming
@byron_miller
54
55. Puppet
Opera[ons
• Develop
your
“System”
to
allow
experimenta[on,
upkeep,
maintenance
and
opera[onal
agility.
• Keep
it
Simple
• Grow
&
Learn
• Prac[ce
all
the
[me
• Prac[ce
More
@byron_miller
55
56. Ops
Pipeline
• Build
Build
Build
– Just
like
code
rot,
don’t
have
server
rot
CI
• Puppet
Lint
• Beaker/Rspec/ServerSpec
• Rubocop
@byron_miller
56
57. Keep
it
simple
• Decouple!
– Use
Roles
&
Profiles
(the
one
“paeern”
I’ll
always
recommend)
– Hiera
is
your
friend,
but
don’t
go
too
nuts
– Keep
your
ENC
simple
-‐
categoriza[on
@byron_miller
57
58. Use
the
feedback
loops
• Pay
aeen[on
to
pipeline
– Don’t
let
things
rot
– Seek
out
improvements
– Share
lessons
learned
– Get
feedback
• Puppet
Reports..
• Puppet
Dashboard..
• Event
Inspector
(PE)..
(and
other
tools)
@byron_miller
58
59. Don’t
stop
Thinking
• Maintain
a
consistency
of
understanding
and
effort
• Don’t
focus
on
local
op[mums
• Quality
starts
here
• Quality
starts
with
intent
• No
system
whatever
the
effort
put
in
will
be
free
from
accident/incident/error
@byron_miller
59
60. Enable
People
• Puppet
enables
me
to
codify
to
“my
future”
• Puppet
enables
me
to
know
my
past
@byron_miller
60
61. Prac[ce
• Test
Upgrades
• Test
new
forge
modules
• “Safe
to
fail”
experimenta[on
• Serverspec..
Beaker..
@byron_miller
61
62. Keep
trying
• Look
at
logs
• puppet
-‐-‐debug
–verbose
• Talk
to
community
• Use
the
dashboard
• puppet
-‐-‐help
@byron_miller
62
63. Community
• Google
Groups
• Twieer
• “Ask”
puppetlabs
• Online
Documenta[on
• IRC
• User
Groups!!
• Sh*t
Gary
Says
-‐
hep://garylarizza.com/
@byron_miller
63
64. Ques[ons?
“Organiza)ons
which
design
systems…
are
constrained
to
produce
designs
which
are
copies
of
the
communica)on
structures
of
these
organiza)ons.”
-‐
M.
Conway
@byron_miller
64