Git can be challenging for developers new to version control. This document outlines an introductory session on using Git that focuses on real world workflows. It discusses how solo developers and small teams can use branching strategies and decentralized workflows to collaborate more efficiently. The session helps attendees understand basic Git concepts and terminology without using the command line, and provides a chance for questions and discussion about challenges with version control.
You're organised, you love spreadsheets, you're a great cheerleader, you handle a backlog with superhero skills, and now you're faced with managing a Drupal project and everything just feels foreign. It's not you, it's Drupal. The mix of site building, front end development, backend development, and over 20,000 contributed modules makes project management for Drupal exceptionally frustrating for people who've not worked with Drupal before.
This session will cover:
- the basic Drupal development workflow (from a developer's perspective, but without using developer jargon)
writing useful tickets which developers can accomplish
- estimation tips for multi-discipline tickets (design / back end / front end)
- ideal team structures -- and what to do if you can't get them
Updated from DrupalCamp London to include the truisms I've learned about being a first-time project manager.
Many of the new fangled front end development efficiency tools require you to drop into the Command Line. For those who are accustomed to using a Graphical User Interface, this can be a frustrating and demoralizing experience. The Command Line User Experience (CLUE) may be archaic, but it is also a very efficient way to work.
This session will uncover some of the mysteries of the command line, and unpack the psychology behind your frustrations with it. We'll dive into details necessary to enhance your appreciation of this simple tool by touching on the following topics:
why you're right to hate the command line (and how you can get over your hatred and get on with your job)
the features of a well-written command line utility (so you can distinguish between the good ones and the ones that ought to make you curl your toes in frustration)
the benefits of working at the command line when things are going wrong (and why things are more likely to go *right* when working from the command line for certain kinds of tasks)
and finally, some simple tips to make your time at the command line more bearable
By the end of this session you should be equipped to tackle command line tasks. Specifically, you will be able to:
create a mental model of the tasks you need to complete while at the command line
locate the command line on your computer
complete tasks using relevant commands
identify and apply troubleshooting techniques if things go wrong
safely exit the command line when your tasks are complete
Yes, this is an introductory session. This is for people who feel shame that they don't know how to "just see Dee into yer root durrr" and get mad when people say "just diff me a patch" as if it's as easy as playing with a kitten. No, you don't have to have Git, or Grunt, or Sass installed to attend (you don't even need to know what they all are--bonus marks if you do though). You don't even need to know where the command line is on your computer.
Responsive design is forcing us to reevaluate our design and development practices. It's also forcing us to rethink how we communicate with our clients and what a project's deliverables might be. Pattern Lab helps bridge the gap by providing one tool that allows for the creation of modular systems as well as gives clients the tools review the work in the place it's going to be used: the browser.
This deck reviews some of the features of Pattern Lab. It also discusses how I feel it can fit into the overall workflow of a team. It doesn't cover the technical aspects of the tool but I'm happy to follow-up if anyone wants me to. Also, be sure to check out the documentation at http://pattern-lab.info/docs/
Fronteers 2009 Of Hamsters, Feature Creatures and Missed OpportunitiesChristian Heilmann
My presentation at Fronteers 2009 about the opportunity we have as developers to liberate ourselves from the fail that is browsers and write some nice code to mix data on the web.
You're organised, you love spreadsheets, you're a great cheerleader, you handle a backlog with superhero skills, and now you're faced with managing a Drupal project and everything just feels foreign. It's not you, it's Drupal. The mix of site building, front end development, backend development, and over 20,000 contributed modules makes project management for Drupal exceptionally frustrating for people who've not worked with Drupal before.
This session will cover:
- the basic Drupal development workflow (from a developer's perspective, but without using developer jargon)
writing useful tickets which developers can accomplish
- estimation tips for multi-discipline tickets (design / back end / front end)
- ideal team structures -- and what to do if you can't get them
Updated from DrupalCamp London to include the truisms I've learned about being a first-time project manager.
Many of the new fangled front end development efficiency tools require you to drop into the Command Line. For those who are accustomed to using a Graphical User Interface, this can be a frustrating and demoralizing experience. The Command Line User Experience (CLUE) may be archaic, but it is also a very efficient way to work.
This session will uncover some of the mysteries of the command line, and unpack the psychology behind your frustrations with it. We'll dive into details necessary to enhance your appreciation of this simple tool by touching on the following topics:
why you're right to hate the command line (and how you can get over your hatred and get on with your job)
the features of a well-written command line utility (so you can distinguish between the good ones and the ones that ought to make you curl your toes in frustration)
the benefits of working at the command line when things are going wrong (and why things are more likely to go *right* when working from the command line for certain kinds of tasks)
and finally, some simple tips to make your time at the command line more bearable
By the end of this session you should be equipped to tackle command line tasks. Specifically, you will be able to:
create a mental model of the tasks you need to complete while at the command line
locate the command line on your computer
complete tasks using relevant commands
identify and apply troubleshooting techniques if things go wrong
safely exit the command line when your tasks are complete
Yes, this is an introductory session. This is for people who feel shame that they don't know how to "just see Dee into yer root durrr" and get mad when people say "just diff me a patch" as if it's as easy as playing with a kitten. No, you don't have to have Git, or Grunt, or Sass installed to attend (you don't even need to know what they all are--bonus marks if you do though). You don't even need to know where the command line is on your computer.
Responsive design is forcing us to reevaluate our design and development practices. It's also forcing us to rethink how we communicate with our clients and what a project's deliverables might be. Pattern Lab helps bridge the gap by providing one tool that allows for the creation of modular systems as well as gives clients the tools review the work in the place it's going to be used: the browser.
This deck reviews some of the features of Pattern Lab. It also discusses how I feel it can fit into the overall workflow of a team. It doesn't cover the technical aspects of the tool but I'm happy to follow-up if anyone wants me to. Also, be sure to check out the documentation at http://pattern-lab.info/docs/
Fronteers 2009 Of Hamsters, Feature Creatures and Missed OpportunitiesChristian Heilmann
My presentation at Fronteers 2009 about the opportunity we have as developers to liberate ourselves from the fail that is browsers and write some nice code to mix data on the web.
A presentation on Web 2.0 communication tools by Ann Traecy and David Erickson at the Minnesota Council of Nonprofits Tech Tools 2.0: The Right Tools For Effective Communication conference on April 24, 2007.
Presentation for Triangle Drupal User's Group on March 17, 2010. Includes discussion of why version control is a good idea, how to deal with special Drupal issues (updating modules, core) and how to set up your file structure.
Ever find a module that does 98% of what you need it to do, and there's no way to make it do that last 2%? Ever need to fix a bug in a module you've run into, but you're the only one who's ever had this problem? You need a patch.
Phase 2 Senior Developer Joshua Turton will cover the hows and whys of patching a module. You will learn:
When is a patch appropriate?
How to edit the module's code and what branch to edit against
How to generate a patch with git, both on the command line and in a GUI
How to report an issue in the module issue queue
How to name your patch file according to drupal's standards
How to use drush make to apply your patch automatically.
What to do if your patch is accepted or rejected
And most importantly: Why you SHOULD contribute your patch, and not be shy!
This presentation is aimed right at the beginner level developer, who is interested in getting involved in Drupal's open-source community, but is intimidated by the complexities and scale of the issue queue and module building. Middle to advanced level developers should also find the session interesting, particularly if they have not gotten involved in the issue queues themselves.
Become a Better Developer with Debugging Techniques for Drupal (and more!)Acquia
What is debugging? How is it different from simply writing a program, and how can you get better at it? A structured debugging approach narrows down problems, rather than using random changes and guesses, and can help you identify and solve problems faster and more effectively.
In this webinar about debugging techniques for Drupal, we’ll cover:
-A general approach to debugging Drupal problems
Common sources of bugs
-A tour of useful debugging tools and techniques that can help you start to see into the inner workings of any version of Drupal
-The use of tools such as XDebug, the devel suite, and client side debugging such as Firebug, LiveHTTPHeaders, and javascript debugging
You are a clever and talented person. You create beautiful designs, or perhaps you can architect a system that even a cat could use. Your peers adore you. Your clients love you. But (until now) you haven't *&^#^ been able to make Git bend to your will. It makes you angry inside that you have to ask your co-worker, again, for that *&^#^ command to share your work.
It's not you. It's Git. Promise.
We'll kick off this session with an explanation of why Git is so freaking hard to learn. Then we'll flip the tables and make YOU (not Git) the centre of attention. You'll learn how to define, and sketch out how version control works, using terms and scenarios that make sense to you. Yup, sketch. On paper. (Tablets and other electronic devices will be allowed, as long as you promise not to get distracted choosing the perfect shade for rage.) To this diagram you'll layer on the common Git commands that are used regularly by efficient Git-using teams. It'll be the ultimate cheat sheet, and specific to your job. If you think this sounds complicated, it's not! Your fearless leader, Emma Jane, has been successfully teaching people how-to-tech for over a decade. She is well known for her non-technical metaphors which ease learners into complex, work-related topics that previously felt inaccessible.
Yes, this is an introductory session. No, you don't have to have Git installed to attend. You don't even need to know where the command line is on your computer. Yes, you should attend if you've been embarrassed to ask team-mates what Git command you used three weeks ago to upload your work...just in case you're supposed to remember.
If you're a super-human Git fanatic who is frustrated by people who don't just "git it", this session is also for you. You'll learn new ways to effectively communicate your ever-loving Git, and you may develop a deeper understanding of why your previous attempts to explain Git have failed.
A brownbag presentation at IPC media in London about the need to use libraries to make web development much less random and more professional. Get the audio at: http://www.archive.org/details/ProfessionalWebDevelopmentWithLibraries
Tek 2013 - Building Web Apps from a New Angle with AngularJSPablo Godel
AngularJS is a new JavaScript framework, backed by Google, for building powerful, complex and rich client-side web applications. We will go over the features and basics of building a web application with AngularJS and we will demonstrate how to communicate with a REST server built with PHP.
9 ways to get started with Agile in public servicesJosephBadman1
Agile is simple to understand, but lots of people we work with sometimes find it difficult to get started.
Here are some practices you can try to help you get started on your Agile journey. They range from simple things you can do as an individual, to more ambitious approaches that will involve your wider team.
Let us know how you get on at comms@basis.co.uk or on Twitter @WeAreBasis or @Dyn_Drwg for Joe.
Tools/Processes for serious android app developmentGaurav Lochan
I've managed a team that developed serious android apps, and ended up dabbling with tools out there and processes/systems. Here is a quick summary of the various things to think about if you're serious about android development, and in some cases, my recommendations.
This covers:
IDE
Build
Source Control
Bug/Task tracking
Crash reporting
Analytics
Test Automation
Continuous Integration
Device Matrix testing
Performance testing
Beta testing
A/B testing
Backend-as-a-Service
A presentation on Web 2.0 communication tools by Ann Traecy and David Erickson at the Minnesota Council of Nonprofits Tech Tools 2.0: The Right Tools For Effective Communication conference on April 24, 2007.
Presentation for Triangle Drupal User's Group on March 17, 2010. Includes discussion of why version control is a good idea, how to deal with special Drupal issues (updating modules, core) and how to set up your file structure.
Ever find a module that does 98% of what you need it to do, and there's no way to make it do that last 2%? Ever need to fix a bug in a module you've run into, but you're the only one who's ever had this problem? You need a patch.
Phase 2 Senior Developer Joshua Turton will cover the hows and whys of patching a module. You will learn:
When is a patch appropriate?
How to edit the module's code and what branch to edit against
How to generate a patch with git, both on the command line and in a GUI
How to report an issue in the module issue queue
How to name your patch file according to drupal's standards
How to use drush make to apply your patch automatically.
What to do if your patch is accepted or rejected
And most importantly: Why you SHOULD contribute your patch, and not be shy!
This presentation is aimed right at the beginner level developer, who is interested in getting involved in Drupal's open-source community, but is intimidated by the complexities and scale of the issue queue and module building. Middle to advanced level developers should also find the session interesting, particularly if they have not gotten involved in the issue queues themselves.
Become a Better Developer with Debugging Techniques for Drupal (and more!)Acquia
What is debugging? How is it different from simply writing a program, and how can you get better at it? A structured debugging approach narrows down problems, rather than using random changes and guesses, and can help you identify and solve problems faster and more effectively.
In this webinar about debugging techniques for Drupal, we’ll cover:
-A general approach to debugging Drupal problems
Common sources of bugs
-A tour of useful debugging tools and techniques that can help you start to see into the inner workings of any version of Drupal
-The use of tools such as XDebug, the devel suite, and client side debugging such as Firebug, LiveHTTPHeaders, and javascript debugging
You are a clever and talented person. You create beautiful designs, or perhaps you can architect a system that even a cat could use. Your peers adore you. Your clients love you. But (until now) you haven't *&^#^ been able to make Git bend to your will. It makes you angry inside that you have to ask your co-worker, again, for that *&^#^ command to share your work.
It's not you. It's Git. Promise.
We'll kick off this session with an explanation of why Git is so freaking hard to learn. Then we'll flip the tables and make YOU (not Git) the centre of attention. You'll learn how to define, and sketch out how version control works, using terms and scenarios that make sense to you. Yup, sketch. On paper. (Tablets and other electronic devices will be allowed, as long as you promise not to get distracted choosing the perfect shade for rage.) To this diagram you'll layer on the common Git commands that are used regularly by efficient Git-using teams. It'll be the ultimate cheat sheet, and specific to your job. If you think this sounds complicated, it's not! Your fearless leader, Emma Jane, has been successfully teaching people how-to-tech for over a decade. She is well known for her non-technical metaphors which ease learners into complex, work-related topics that previously felt inaccessible.
Yes, this is an introductory session. No, you don't have to have Git installed to attend. You don't even need to know where the command line is on your computer. Yes, you should attend if you've been embarrassed to ask team-mates what Git command you used three weeks ago to upload your work...just in case you're supposed to remember.
If you're a super-human Git fanatic who is frustrated by people who don't just "git it", this session is also for you. You'll learn new ways to effectively communicate your ever-loving Git, and you may develop a deeper understanding of why your previous attempts to explain Git have failed.
A brownbag presentation at IPC media in London about the need to use libraries to make web development much less random and more professional. Get the audio at: http://www.archive.org/details/ProfessionalWebDevelopmentWithLibraries
Tek 2013 - Building Web Apps from a New Angle with AngularJSPablo Godel
AngularJS is a new JavaScript framework, backed by Google, for building powerful, complex and rich client-side web applications. We will go over the features and basics of building a web application with AngularJS and we will demonstrate how to communicate with a REST server built with PHP.
9 ways to get started with Agile in public servicesJosephBadman1
Agile is simple to understand, but lots of people we work with sometimes find it difficult to get started.
Here are some practices you can try to help you get started on your Agile journey. They range from simple things you can do as an individual, to more ambitious approaches that will involve your wider team.
Let us know how you get on at comms@basis.co.uk or on Twitter @WeAreBasis or @Dyn_Drwg for Joe.
Tools/Processes for serious android app developmentGaurav Lochan
I've managed a team that developed serious android apps, and ended up dabbling with tools out there and processes/systems. Here is a quick summary of the various things to think about if you're serious about android development, and in some cases, my recommendations.
This covers:
IDE
Build
Source Control
Bug/Task tracking
Crash reporting
Analytics
Test Automation
Continuous Integration
Device Matrix testing
Performance testing
Beta testing
A/B testing
Backend-as-a-Service
Inventing The Next Business Programming LanguageRichard Green
written for Detroit Lambda Lounge
---
If you want to program a computer, use a computer programming language.
If you want to program a business process,
use a business programming language.
CocoaPods talk given at the RubyMotion Inspect 2013 conference.
There is another version that does not include speaker notes available at: https://www.slideshare.net/alloy020/ruby-motion-inspect-2013-without-notes-18676749
The videos that were shown on slide 5 and 6 are available at: https://vimeo.com/63891717 & https://vimeo.com/63891716.
Bug reports, standups, issue queues, retrospectives, pull requests, code reviews, flame-outs. We're constantly communicating and if we don't take the time to stop and think about what state of mind will be most productive, we can sometimes say things that put us further behind. Nothing disrupts flow like unproductive communication! In this session Emma Jane Hogbin Westby will show you a new way of thinking about how people behave in the workplace. She will walk you through three types of thinking strategies; and show you how to apply these strategies to create more productive interactions with your co-workers.
You've just been handed a gorgeous, static Photoshop file. By tomorrow it needs to be a flexible, extensible, and compatible Drupal theme for some Web site you've never seen. Oh and they said something about it needing to be responsive to 508 or something like that? *gulp* The problem with creating a Drupal theme is —once you know how—it becomes intuitive. Themers spontaneously transform design files into complete Drupal themes without realizing all of the little steps their brain takes to achieve the final solution. It's sort of like those “learn to draw a cat” books where it takes you from a basic circle to a cat with beautiful fur in four simple steps. It's never four complete simple steps though. It's two steps of making circles and then some kind of crazy artist voodoo that makes a complete cat by the last step. In this session Emma Jane Westby (of Front End Drupal fame) will walk you through the steps ... all the steps ... of converting a design into a theme.
Without missing any steps, Emma will walk you through:
the benefits of theming by component
what you need to have in place before you start
what's worth keeping from SMACSS (and what's just overhead)
how to refine her simple procedure so it works for your team, and with any version of Drupal
The bigger the company, the more likely you are to get dragged into meetings that waste your time, waste your talent, and waste your company's money. Sure, it's great to be included in the process, but wouldn't it be even nicer if the process didn't waste your time? In this session Emma Jane Hogbin show you five simple tips to make your time in meetings more efficient. Want to dig deeper? She'll explain why these five tips work and show you how to make more of your interactions with (difficult) people more efficient and enjoyable.
Does Git make you angry inside? In this workshop you will get a gentle introduction to working efficiently as a Web developer in small teams, or as a solo developer. We'll focus on real world examples you can actually use to make your work faster and more efficient. Windows? OSX? Linux? No problem, we'll get you up and running with Git, no matter what your system. Yes, this is an introductory session. This is for people who feel shame that they don't know how to "clone my github project", wish they too could "get the gist", and get mad when people say "just diff me a patch" as if it's something as easy as making a mai thai even though you have no rum. No, you don't have to have git installed to attend. You don't even need to know where the command line is on your computer.
Is your theme folder filled with files like this: page.old.2.bak.php? Does Git make you angry inside? Do you resent that everyone except you regularly visits the magical place referred to as "The Command Line"? Are you afraid of the vagrant who stole your puppet? In this workshop you will get a step-by-step introduction to working efficiently as a Drupal developer in small teams, or as a solo developer. We'll focus on real world examples you can actually use to make your work faster and more efficient.
Full workshop available at: http://designtotheme.com/workshops/work-flow-solo-developers-and-small-teams
The handout and video are also available for this presentation.
http://munich2012.drupal.org/program/sessions/evaluating-base-themes http://munich2012.drupal.org/sites/default/files/slides/basethemes-handout-munich_1.pdf
One of these themes is not like the other: Mothership, Zen, Omega, Bartik, Fusion. Since writing my first book, Front End Drupal, Drupal base themes have matured significantly. Some of these base themes have evolved to the point of having the learning curve of a theming engine rather than a set of preset markup defaults. In this session we'll explore the base theme ecosystem. You'll get a biased view of how I evaluate base themes and which themes come out on top for the "themer experience". You'll find out why there can be no single base theme to meet the needs of every themer and why the base theme you're using might not be right for you.
Bring your questions (and your flame thrower) as we romp through the valley of Drupal base themes.
The theme of your website has the capacity for beautiful, semantic markup...and also the hacky HTML soup. You can build a new theme by downloading a free theme and tearing out its guts--or you can learn how to become a theme surgeon.
In this session you will learn two key techniques needed to build a successful theme: crime scene investigation (identifying Drupal page elements in your design files) and power tools for copy-cat theming (things you need to recreate your design using Drupal). From start to finish we will transform a design file into a Drupal theme. With special attention given to your all-important questions: how do I save time with grid-based design? Should I use Panels? How do I make this bit of stuff appear next to that bit? Yah, but how do I start?
[This presentation was given at DrupalCon Chicago but the recording failed. Slides are available from http://www.slideshare.net/emmajane/forensic-theming-for-drupal]
About The Presenter
Emma Jane Hogbin is well known in the Drupal community for her engaging presentations and kickass theming book, Front End Drupal. She is currently working on her second book, Drupal: A user's guide which is due out shortly after DrupalCon. Through her training company, Design to Theme, emmajane has empowered thousands of people to create the Drupal site of their dreams.
Intended audience
Small business site builders who partner with graphic designers but have no idea how to make Drupal look like a design file. Intermediate themers who start with a free Drupal theme that looks "close" to the final site and then start hacking to make their theme. The audience currently does not use base themes and are frustrated at how complicated all of the code is. They are looking for shortcuts and some quick-fix solutions to make theming faster and more profitable.
Questions answered by this session
What are the key tools I need to use to make themeing Drupal easier?
How can I make Drupal markup less yucky?
Where should I start when building a new theme?
Yeah, but how do I theme *that thing*?
I want to see how you build a theme: show me!
Presented at: http://london2011.drupal.org/conference/sessions/forensic-theming-key-techniques-building-effective-drupal-themes
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Designing Great Products: The Power of Design and Leadership by Chief Designe...
Git Makes Me Angry Inside
1. Git Makes Me Angry Inside
Emma Jane Westby
Education Development Coordinator
Drupalize.Me
@emmajanehw
http://drupalize.me
Slides at: http://tinyurl.com/dcto13-git
Saturday, 13 July, 13
Problem: Developers face a steep learning curve when they choose to adopt version control.
Solution: There is a version control strategy to suit your workflow, even if you've always
thought it was too hard to bother.
Is your project folder filled with files like this: page.old.2.bak.php? Does Git make you angry
inside? Do you resent that everyone except you regularly visits the magical place referred to
as "The Command Line"? Are you afraid of the vagrant who stole your puppet? In this session
you will get a gentle introduction to working efficiently as a developer in small teams, or as a
solo developer. We'll focus on real world examples you can actually use to make your work
faster and more efficient.
Yes, this is an introductory session. This is for people who feel shame that they don't know
how to "just cd into yer root durrr" and get mad when people say "just diff me a patch" as if
it's something as easy as making a mai thai even though you have no rum. No, you don't have
to have git installed to attend. You don't even need to know where the command line is on
your computer.
2. Why Stick Around
• Learn how Git thinks, without being exposed to the command line.
• Learn how to structure your work flow to take advantage of Git.
• Learn how basic commands are applied to common work flow scenarios.
• Q&A / therapy session
Saturday, 13 July, 13
4. What are your tasks?
download
work
create
snapshot
share
work
Saturday, 13 July, 13
What are the tasks that your team work on?
For example: download work, make changes, upload work to a shared space.
6. What’s your branch management strategy?
Saturday, 13 July, 13
As your people are working together, they need to have private, and shared spaces to do
their work. This is where a branch management strategy gets layered in.
7. How do we make Git do that?
Git Shell, cross-platform
Saturday, 13 July, 13
We’re not going to talk about the specifics of how to run commands today. But these are a
few examples of the GUIs that are available for different platforms. (You don’t *have to be*
stuck on the command line if you don’t want to be.)
Before we get started: let’s take a second to find out who you are. Why are you here, and how
are you currently struggling with version control?
8. Git is 90% process and 10% technology.
• Git was written by kernel developers, for kernel developers. Chances are high
you’re not a kernel developer. Stop blaming yourself, and start blaming Git for
your struggles.
• Not all is lost! If you can diagram the problem you are trying to solve; you will
be able to find the right Git commands.
• Before we start drawing pictures, let’s take a look at some of the concepts
version control helps us with.
Saturday, 13 July, 13
Out of the box, Git does basically nothing for you. It’s your processes that will allow you to
apply the tools you need to make version control work for you.
Then go through each of the points listed.
Transition: let’s take a look at some of the terms you’ll run into when working with Git to give
us a shared language.
9. Version control (sort of) makes automation easier
• Backup and restore
• Synchronize across multiple platforms
• Short-term “undo” to test implications of changes
• Long-term “undo” to reverse bugs or regressions
• Track changes to see why/how software evolved
• Track ownership to give “credit” to change makers
• Sandbox code to test changes without affecting other people and systems
Saturday, 13 July, 13
There are a lot of valid reasons to use version control. The biggest gain bigger teams will see
is in automation of process. But you don’t need to automate things to take advantage of
version control.
Read through the list of things version control helps with.
10. Terminology: locations
• remote repository
• trunk or main
• head or tip
• local repository
• client
• working copy
Saturday, 13 July, 13
There are a lot of terms in version control. Creating a map of where things live can make the
documentation a lot easier to deal with.
Repo: database of changes to your files.
Server: computer storing the repo
Client: computer connecting to the repo
Working copy: local copy where changes are made
Trunk/main: The current, primary source for unchanged code
Head: the latest revision in a repository (tip: latest in a branch...HEAD moves, tip doesn’t).
11. Terminology: actions and tasks
Saturday, 13 July, 13
With our locations mapped out, let’s take a look at the common tasks or “actions” you can
take.
Basic actions:
adopt / download: clone, merge, fetch, checkout, pull/rebase
review: log, status
compare: diff HEAD, diff, diff --cached
reset: checkout, checkout HEAD, reset --hard (throw away in-between commits), revert (save
in-between commits)
save: add -u, commit, commit -a
distribute: push
12. Set the stage!
Before we can set our workflow we need to know who we’re dealing with and
what they’re supposed to be doing.
Saturday, 13 July, 13
People first. In this next section, we’ll start with the folks on your team (not the software).
13. Who’s on your code team?
Write down a list of all of the people on your code team. This list may
include:
• developers
• designers
• project managers
• clients
Saturday, 13 July, 13
Who are the folks on your team? Designer? Developer? Site builder?
14. Where do you fit in?
Maybe you do everything. Maybe you only do some things. Write a list of all
the tasks you are actually responsible for. This might include:
• Writing code.
• Reviewing code.
• Pushing tested code to the server.
• Fixing broken code.
Saturday, 13 July, 13
Slide is “as advertised”.
15. What are your tools and restraints?
Often there are other things we need to fit into our workflow. Create a third list
of any tools and restraints you are aware of. This list might include:
• Version control software (we’ll always assume Git)
• Code hosting system (Bitbucket, GitHub, self-hosted)
• Server ecosystem (dev / staging / live)
• Code editors & integrated developer environments (vim, Dreamweaver,
Sublime, PHPstorm)
• Automated testing systems or review “gates”
Saturday, 13 July, 13
Slide is “as advertised”.
16. What’s your workflow?
With the team members identified, it’s time to sketch out how these people
(ideally) work together.
Saturday, 13 July, 13
Now that we know the people, let’s talk about how they work together. There are lots of valid
ways of working together, let’s take a look at a few of them.
18. Partner workflow with no central server
Saturday, 13 July, 13
James starts a grocery list; Emma already had a grocery list started so she asks to see James’s
list. She adds her items to James’s list and hands it back.
19. Centralized workflow with no local commits
Saturday, 13 July, 13
the “old” style of version control has a single place where all work is checked into. Every time
work is saved, it’s uploaded to the shared space. You can implement this workflow with
distributed version control too, but you wouldn’t want to.
20. Decentralized with human gatekeeper
Saturday, 13 July, 13
This is pretty typical: it’s a decentralized workflow. The developers pull/clone. Do their work
locally and then ask their “gatekeeper” to check their work and merge it into the central repo.
Once the central repo has the changes, the devs grab a fresh copy and continue their work.
21. Decentralized with automated gatekeeper
Saturday, 13 July, 13
The decentralized with automated gatekeeper is almost the same, except it’s a computer
making the decision on whether or not code should be accepted. This is fine for quantitative
reviews, but shouldn’t be used for qualitative reviews...unless there are pre-merge peer
reviews also happening.
22. Sketch out your workflow
• Identify the roles on your team.
• Identify the relationships between the team members.
• Draw arrows to show how code flows between team members.
Saturday, 13 July, 13
Slide is “as advertised”.
23. How will you manage your branches?
With the workflow described, it’s time to look at how the code will be
segregated into different branches.
Saturday, 13 July, 13
This is where the fun starts! Managing branches in a distributed workflow.
25. Work flow and branch management
Saturday, 13 July, 13
26. Work flow and branch management
Saturday, 13 July, 13
27. Work flow and branch management
peer review
Saturday, 13 July, 13
28. Work flow and branch management
peer review
public / live
server
Saturday, 13 July, 13
29. Work flow and branch management
peer review
public / live
server
Saturday, 13 July, 13
30. Work flow and branch management
peer review
public / live
server
dev / testing
server
Saturday, 13 July, 13
31. Work flow and branch management
peer review
public / live
server
dev / testing
server
master
master
master
Saturday, 13 July, 13
32. Work flow and branch management
peer review
public / live
server
dev / testing
server
master
master
master
dev
dev
dev
Saturday, 13 July, 13
33. Work flow and branch management
feature feature
hotfix featur
peer review
public / live
server
dev / testing
server
master
master
master
dev
dev
dev
Saturday, 13 July, 13
34. Work flow and branch management
feature feature
hotfix featur
peer review
public / live
server
dev / testing
server
master
master
master
dev
dev
dev
Saturday, 13 July, 13
35. Sketch out your branch management strategy
• Identify the roles on your team.
• Identify the relationships between the team members.
• Draw arrows to show how code flows between team members.
• Time: 10 minutes
Saturday, 13 July, 13
37. You can make Git do what you want...
now that you know what you want.
@emmajanehw
http://drupalize.me
Slides: http://lb.com/dcto13-git
How to git: http://lb.cm/howto-git-videos
Saturday, 13 July, 13