An updated and condense version of the recipe Atlassian uses to help migrate their teams to DVCS tooling.
This presentation was given in a Webinar by Clearvision http://www.clearvision-cm.com/
Simplified, Robust and Speedy Novell Identity Manager Implementation with Des...Novell
Novell Identity Manager tools for implementation and administration have always been the product's key differentiating factor. Recent changes have made Identity Manager implementations even more easy and efficient. Whether you are new to Identity Manager or are an existing user, attend this session to learn more about Designer, Analyzer and iManager.
For Designer, you will hear about Identity Manager staging, role-based entitlements, and key performance improvements such as working over VPN and an optimized import/deployment of your identity management project. The presenters will also offer insight into how well Designer supports the latest versions of Identity Manager and Novell Identity Manager Roles Based Provisioning Module with the new Rich Client Platform (RCP) Designer and the support it offers to Novell Compliance Management Platform. Finally, you'll hear about the Designer roadmap for the Identity Manager product line.
You will also hear about the data cleansing and massaging capabilities in Analyzer. For iManager, you will see new features such as war file deployment.
VMworld 2015: Monitoring and Managing Applications with vRealize Operations 6...VMworld
This year VMware vSphere 6 combined with vRealize Operations 6.1 (vR Ops 6) adds critical features to increase technical agility in the infrastructure, and reduce Mean time to Repair. With a new Automated remediation action framework in vR Ops, vSphere 6’s ability to vMotion Physical Raw Device mappings (RDMs), and a complete Management Pack Ecosystem for monitoring Infrastructure to applications, administrators have the tools needed to get to maintain 5 9’s uptime, shorten Mean Time to Repair (MTTR), and predict capacity requirements as and when the business requires.. This session will be a deep technical explanation, and live demonstration of these tools. It will give administrators a solid understanding of how they can use these tools to monitor and manage their application clusters, keep applications running during Infrastructure maintenance, and get deep holistic visibility into the entire Application ecosystem, from Storage to Networking.
How NBCUniversal is embracing DevOps to improve application delivery. Hear how they are using automation tools, like IBM UrbanCode to help standardize culture, speed time to market, integrate with existing tools, and deliver releases effectively. Learn more about UrbanCode here: http://ibm.biz/learnurbancode
Databases create a real challenge for automation and dealing with database deployments is a complex process. Databases contain our most valuable information, business data, which must be preserved and protected at all costs and yet the automation processes for database deployment are not widely adopted.
Application schema changes are incremental, cumulative, and painful - often reaping havoc on the Application Release Lifecycle. Using manual processes with SQL scripts are error-prone, as well as hard to track and troubleshoot. Learn release and deploy best practices for automating schema management using Datical and IBM UrbanCode Deploy. See how Datical extends the popular Liquibase Open Source project for enterprise use with a data model approach for previewing impact of change in production.
Simplified, Robust and Speedy Novell Identity Manager Implementation with Des...Novell
Novell Identity Manager tools for implementation and administration have always been the product's key differentiating factor. Recent changes have made Identity Manager implementations even more easy and efficient. Whether you are new to Identity Manager or are an existing user, attend this session to learn more about Designer, Analyzer and iManager.
For Designer, you will hear about Identity Manager staging, role-based entitlements, and key performance improvements such as working over VPN and an optimized import/deployment of your identity management project. The presenters will also offer insight into how well Designer supports the latest versions of Identity Manager and Novell Identity Manager Roles Based Provisioning Module with the new Rich Client Platform (RCP) Designer and the support it offers to Novell Compliance Management Platform. Finally, you'll hear about the Designer roadmap for the Identity Manager product line.
You will also hear about the data cleansing and massaging capabilities in Analyzer. For iManager, you will see new features such as war file deployment.
VMworld 2015: Monitoring and Managing Applications with vRealize Operations 6...VMworld
This year VMware vSphere 6 combined with vRealize Operations 6.1 (vR Ops 6) adds critical features to increase technical agility in the infrastructure, and reduce Mean time to Repair. With a new Automated remediation action framework in vR Ops, vSphere 6’s ability to vMotion Physical Raw Device mappings (RDMs), and a complete Management Pack Ecosystem for monitoring Infrastructure to applications, administrators have the tools needed to get to maintain 5 9’s uptime, shorten Mean Time to Repair (MTTR), and predict capacity requirements as and when the business requires.. This session will be a deep technical explanation, and live demonstration of these tools. It will give administrators a solid understanding of how they can use these tools to monitor and manage their application clusters, keep applications running during Infrastructure maintenance, and get deep holistic visibility into the entire Application ecosystem, from Storage to Networking.
How NBCUniversal is embracing DevOps to improve application delivery. Hear how they are using automation tools, like IBM UrbanCode to help standardize culture, speed time to market, integrate with existing tools, and deliver releases effectively. Learn more about UrbanCode here: http://ibm.biz/learnurbancode
Databases create a real challenge for automation and dealing with database deployments is a complex process. Databases contain our most valuable information, business data, which must be preserved and protected at all costs and yet the automation processes for database deployment are not widely adopted.
Application schema changes are incremental, cumulative, and painful - often reaping havoc on the Application Release Lifecycle. Using manual processes with SQL scripts are error-prone, as well as hard to track and troubleshoot. Learn release and deploy best practices for automating schema management using Datical and IBM UrbanCode Deploy. See how Datical extends the popular Liquibase Open Source project for enterprise use with a data model approach for previewing impact of change in production.
Introducing Serena Dimensions CM 14, Discussion and product demonstration (We...Serena Software
Watch the presentation of the new Serena Dimensions CM 14 release and its latest features - the most innovative and powerful version of Serena’s proven process-based software change and configuration management (SCCM) product in the last decade. Dimensions CM 14 eliminates the complexity of parallel development, while increasing development team collaboration and providing unique visibility into the health and quality of development deliverables, smoothing the transition to continuous delivery.
Presentation on dbMaestro TeamWork - a Database Change Management solution with the unique Database Change Policy enforcement and supports all development methods such as waterfall, agile and DevOps
IBM UrbanCode is a leader in deploying applications to multiple platforms in complex environments. And Docker is an open platform for developers and system administrators to build, ship, and run distributed applications.
Laurel Dickson-Bull, IBM UrbanCode Product Manager, and Mike Samano, IBM Lead Developer for UrbanCode Integrations, as they discuss how you can leverage UrbanCode to deploy Docker containers.
Database continuous integration, unit test and functional testHarry Zheng
Discuss continuous integration for database projects, including building project, deploying project to database, and executing unit tests and functional tests.
This presentation will also discuss database test standards, tips and tricks.
Deployment automation efforts tend to start with easier scenarios like moving builds of web applications to servers and getting them installed. However, some parts of our applications aren’t simple builds. They may be updated incrementally; changes may be non-repeatable; or they may be dependent on knowledge contained within some other tool or framework. When we fail to automate changes to these “tricky” parts of our application, errors and delays materialize.
Eric Minick from IBM, and Robert Reeves, database guru from Datical, discuss what makes certain things hard to deploy, and practical techniques and tools for deploying them. Topics covered include:
* What causes certain deployments to be trickier to automate than others
* Successful patterns for overcoming those challenges
* Application of those techniques to mainframe changes, WebSphere configuration and database schema updates
This presentation will introduce a new DevOps reference architecture published by IBM. This technology agnostic reference architecture was developed harvesting solution architectures from dozens of clients who have been successful in adopting DevOps at scale. The presentation will present the capabilities - across practices, tools, platforms and organizational considerations, that are required for large scale DevOps adoption in an enterprise.
Unified Deployment: Including the Mainframe in Enterprise DevOpsXebiaLabs
Compuware’s Mark Schettenhelm and XebiaLabs’ Tim Buntel demo and discuss how the integration between Compuware’s ISPW mainframe DevOps solution and XebiaLabs’ XL Release Continuous Delivery technology helps enterprises engage in cross-platform release orchestration and create business agility.
VMware and Puppet: How to Plan, Deploy & Manage Modern ApplicationsPuppet
Are you looking to better understand how to use Puppet with VMware to rapidly deploy applications?Join us to learn how to easily model and automate delivery of modern applications to private or public clouds. We will walk through how to use Application Director and Puppet together to build, deploy and configure standardized multi-tier applications within minutes. Once these applications are deployed, you’ll learn how best to provide ongoing management and maintenance. We will show you how to manage drift, roll out updates and ensure consistency in your applications to reduceoutages and unnecessary downtime. This session will include a demo of common use cases and customer case examples.
Speakers
Nigel Kersten
CTO, Puppet Labs
Nigel came to Puppet Labs from Google HQ in Mountain View, where he was responsible for the design and implementation of one of the largest Puppet deployments in the world. He’s been a sysadmin for Linux and Mac deployments for longer than he is entirely comfortable calculating.
Becky Smith
Product Line Manager, VMware
Becky Smith has 16 years of experience in IT and System Management space. As a Product Line Manager for VMware's Enterprise Management business unit, Becky is responsible for product direction for operational, security and regulatory configuration and compliance management across cloud, virtual and physical infrastructures and workloads. Becky Smith's technical background and expertise consists of cloud and virtualization infrastructure management, system administration and compliance.
Flintstones or Jetsons? Jump Start Your Virtual Test LabTechWell
The power of virtualization has made it easy and inexpensive to create multiple environments for testing. How you implement your virtualization strategy can boost not only the savings on physical gear and availability of test environments but also your testing productivity. Sharing his experience working through the evolution of Verisign’s virtual test lab, David Silk examines how a well-implemented virtual lab can push your testing productivity to new levels. Learn about the key practices to get a virtual test lab working like an advanced Jetson’s-style machine while avoiding the Flintstone's dinosaur approach. See how Verisign’s approach focuses on the whole environment—not just one virtual machine at a time. Learn where to start and how to build a virtual test lab that leverages the technology, ensures repeatability, and saves test engineers time and effort. Don’t be a Flintstone!
Early Draft: Service Mesh allows developers to focus on business logic while the crosscutting network data layer code is handled by the Service Mesh. This is a boon because this code can be tricky to implement and hard to test all of the edge cases. Service Mesh takes this a few steps further than AOP or Servlet Filters or custom language-specific frameworks because it works regardless of the underlying programming language being used which is great for polyglot development shops. Thus standardizing how these layers work, while allowing teams to pick the best tools or languages for the job at hand. Kubernetes and Istio Service Mesh automate best practices for DevSecOps needs like: failover, scale-out, scalability, health checks, circuit breakers, rate limiters, metrics, observability, avoiding cascading failure, disaster recovery, and traffic routing; supporting CI/CD and microservices architecture.
Istio’s ability to automate and maintaining zero trust networks is its most important feature. In the age of high-profile data breaches, security is paramount. Companies want to avoid major brand issues that impact the bottom line and shrink market capitalization in an instant. Istio allows a standard way to do mTLS and auto certificate rotation which helps prevent a breach and limits the blast radius if a breach occurs. Istio also takes the concern of mTLS from microservices deployments and makes it easy to use taking the burden off of application developers.
Introducing Serena Dimensions CM 14, Discussion and product demonstration (We...Serena Software
Watch the presentation of the new Serena Dimensions CM 14 release and its latest features - the most innovative and powerful version of Serena’s proven process-based software change and configuration management (SCCM) product in the last decade. Dimensions CM 14 eliminates the complexity of parallel development, while increasing development team collaboration and providing unique visibility into the health and quality of development deliverables, smoothing the transition to continuous delivery.
Presentation on dbMaestro TeamWork - a Database Change Management solution with the unique Database Change Policy enforcement and supports all development methods such as waterfall, agile and DevOps
IBM UrbanCode is a leader in deploying applications to multiple platforms in complex environments. And Docker is an open platform for developers and system administrators to build, ship, and run distributed applications.
Laurel Dickson-Bull, IBM UrbanCode Product Manager, and Mike Samano, IBM Lead Developer for UrbanCode Integrations, as they discuss how you can leverage UrbanCode to deploy Docker containers.
Database continuous integration, unit test and functional testHarry Zheng
Discuss continuous integration for database projects, including building project, deploying project to database, and executing unit tests and functional tests.
This presentation will also discuss database test standards, tips and tricks.
Deployment automation efforts tend to start with easier scenarios like moving builds of web applications to servers and getting them installed. However, some parts of our applications aren’t simple builds. They may be updated incrementally; changes may be non-repeatable; or they may be dependent on knowledge contained within some other tool or framework. When we fail to automate changes to these “tricky” parts of our application, errors and delays materialize.
Eric Minick from IBM, and Robert Reeves, database guru from Datical, discuss what makes certain things hard to deploy, and practical techniques and tools for deploying them. Topics covered include:
* What causes certain deployments to be trickier to automate than others
* Successful patterns for overcoming those challenges
* Application of those techniques to mainframe changes, WebSphere configuration and database schema updates
This presentation will introduce a new DevOps reference architecture published by IBM. This technology agnostic reference architecture was developed harvesting solution architectures from dozens of clients who have been successful in adopting DevOps at scale. The presentation will present the capabilities - across practices, tools, platforms and organizational considerations, that are required for large scale DevOps adoption in an enterprise.
Unified Deployment: Including the Mainframe in Enterprise DevOpsXebiaLabs
Compuware’s Mark Schettenhelm and XebiaLabs’ Tim Buntel demo and discuss how the integration between Compuware’s ISPW mainframe DevOps solution and XebiaLabs’ XL Release Continuous Delivery technology helps enterprises engage in cross-platform release orchestration and create business agility.
VMware and Puppet: How to Plan, Deploy & Manage Modern ApplicationsPuppet
Are you looking to better understand how to use Puppet with VMware to rapidly deploy applications?Join us to learn how to easily model and automate delivery of modern applications to private or public clouds. We will walk through how to use Application Director and Puppet together to build, deploy and configure standardized multi-tier applications within minutes. Once these applications are deployed, you’ll learn how best to provide ongoing management and maintenance. We will show you how to manage drift, roll out updates and ensure consistency in your applications to reduceoutages and unnecessary downtime. This session will include a demo of common use cases and customer case examples.
Speakers
Nigel Kersten
CTO, Puppet Labs
Nigel came to Puppet Labs from Google HQ in Mountain View, where he was responsible for the design and implementation of one of the largest Puppet deployments in the world. He’s been a sysadmin for Linux and Mac deployments for longer than he is entirely comfortable calculating.
Becky Smith
Product Line Manager, VMware
Becky Smith has 16 years of experience in IT and System Management space. As a Product Line Manager for VMware's Enterprise Management business unit, Becky is responsible for product direction for operational, security and regulatory configuration and compliance management across cloud, virtual and physical infrastructures and workloads. Becky Smith's technical background and expertise consists of cloud and virtualization infrastructure management, system administration and compliance.
Flintstones or Jetsons? Jump Start Your Virtual Test LabTechWell
The power of virtualization has made it easy and inexpensive to create multiple environments for testing. How you implement your virtualization strategy can boost not only the savings on physical gear and availability of test environments but also your testing productivity. Sharing his experience working through the evolution of Verisign’s virtual test lab, David Silk examines how a well-implemented virtual lab can push your testing productivity to new levels. Learn about the key practices to get a virtual test lab working like an advanced Jetson’s-style machine while avoiding the Flintstone's dinosaur approach. See how Verisign’s approach focuses on the whole environment—not just one virtual machine at a time. Learn where to start and how to build a virtual test lab that leverages the technology, ensures repeatability, and saves test engineers time and effort. Don’t be a Flintstone!
Early Draft: Service Mesh allows developers to focus on business logic while the crosscutting network data layer code is handled by the Service Mesh. This is a boon because this code can be tricky to implement and hard to test all of the edge cases. Service Mesh takes this a few steps further than AOP or Servlet Filters or custom language-specific frameworks because it works regardless of the underlying programming language being used which is great for polyglot development shops. Thus standardizing how these layers work, while allowing teams to pick the best tools or languages for the job at hand. Kubernetes and Istio Service Mesh automate best practices for DevSecOps needs like: failover, scale-out, scalability, health checks, circuit breakers, rate limiters, metrics, observability, avoiding cascading failure, disaster recovery, and traffic routing; supporting CI/CD and microservices architecture.
Istio’s ability to automate and maintaining zero trust networks is its most important feature. In the age of high-profile data breaches, security is paramount. Companies want to avoid major brand issues that impact the bottom line and shrink market capitalization in an instant. Istio allows a standard way to do mTLS and auto certificate rotation which helps prevent a breach and limits the blast radius if a breach occurs. Istio also takes the concern of mTLS from microservices deployments and makes it easy to use taking the burden off of application developers.
Presentation for the Londno Atlassian user group in February 2012.
Covers a brief intro to JIRA 5 new release, software development getting more social.
Also mentioning JIRA under the hood improvements to make it easier for developers to start with their own plugin development and have a stable platform for future develpment.
XP teams try to keep systems fully integrated at all times, and shorten the feedback cycle to minutes and hours instead of weeks or months. The sooner you know, the sooner you can adapt.
Watch our record for the webinar "Continuous Integration" to explore how Azure DevOps helps us in achieving continuous feedback using continuous integration.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
Continuous Integration as a Way of LifeMelissa Benua
Continuous integration (CI) is a buzzword in software development today. We know it means “run lots of builds,” but having a continuous integration pipeline opens up opportunities well beyond making sure your team's code compiles. What if this pipeline could improve everything from the quality of code reviews to how often and safely you deploy to production and how you monitor your product in the wild? What if CI could provide insights into how automated tests are performing and how to improve them? Melissa Benua describes how to set up a basic CI infrastructure and then transform it into a way of life for development and test teams. Using free or nearly free tools, Melissa walks through a practical approach to making sure your code works—all the time and at every stage of the release train. Come away with practical advice for creating builds and running automation on the fly without spending hundreds of hours or thousands of dollars.
[WSO2Con EU 2017] Continuous Integration, Delivery and Deployment: Accelerate...WSO2
Continuous integration, continuous delivery, and continuous deployment are essential practices adopted by agile organizations to meet the new demands of digital transformation. Ultimately, the goal is to accelerate development and test processes and get new code out to production fast. This slide deck focuses on sustainably flowing ideas into the hands of customers in the form of innovative digital capabilities and applications, and continuously improving the digital business with CI/CD.
Moving to the cloud isn’t easy, transforming your engineering team to adopt to the cloud and services lifestyle is therefore crucial. It all starts with creating a common understanding of the engineering and development principles which are important in the cloud, which are different then building regular applications. This session will take you on a road trip based on the presenters experience developing and more importantly operating Azure Active Directory, SQL Server Azure and most recently the Xbox Live Services to support Xbox One.
Atlassian Developers switch to DVCS - Unite London conferenceJohn Stevenson
Discussion of how Atlassian moved from subversion source code management to DVCS tools such as Git and Mercurial.
Covers a basic recipe for making the switch from the Atlassian experience and ideas as to why DVCS has become a competitive advantage to businesses.
Release software is no less important than activities that precede it.
The Continuous Delivery is a set of practices and methodologies that build an ecosystem for the software development lifecycle.
We will see how to build this ecosystem around the applications developed, for which this release activities becomes a low-risk, inexpensive, fast and predictable.
Marjorie M. K. Hlava, President, Chair of the Board, and Chief Scientist, Access Innovations, Inc.
During this annual highlight of the DHUG meetings, Margie will discuss the exciting new changes and additions to the Data Harmony software. She will be joined by some members of our software development team to talk about specific initiatives we have worked on over the past year.
Configuring and maintaining a continuous integration environment is quite a bit of work. It requires ongoing resources both in terms of manpower and hardware infrastructure. As an application evolves so does the number of ongoing projects. The challenge is creating a scalable continuous integration environment which does not impede development and can handle the complexities of Java EE testing. This session covers how to setup and configure a cloud-based continuous integration environment for Java EE applications.
The presentation will focus on demonstrating how to use Atlassian Bamboo running on AWS to build and test a Maven/Gradle Java EE project that uses Arquillian for testing. Topics that will be covered include creating a custom AWS VM for use with Bamboo, creating an Amazon VPC (Virtual Private Cloud) along with test database using Amazon RDS. The presentation will delve into the specifics of testing EJBs, WebSocket endpoints, RESTful web services, as well as performing load testing in this environment. Security, cost control, and build monitoring will be covered as well.
Using a revision control system that tracks changes in source code with ways to manage your code in separate branches and tag revisions as releases is a bare minimum for developers.
This presentation highlights the importance of using a version control system Subversion.
Similar to How Atlassian made the switch to DVCS (20)
Confessions of a developer community builderJohn Stevenson
Slides from my talk on building developer communities at London Software Craftsmanship conference 5th & 6th October.
I share my experiences of interacting with the software development community over the last 22 years.
Discussion includes what kinds of events you could run in your community and how to get your community started.
Progscon 2017: Taming the wild fronteer - Adventures in ClojurescriptJohn Stevenson
Progscon 2017 conference talk, introducing Clojurescript for a functional programming approach to building React.js apps.
Examples include using React.js directly and the Om Clojurescript library that closely follows the React.js API. Also cover a simpler approach to React with the Clojurescript libraries called Reagent and Rum.
Discussing the challenges of communication that affect us all and techniques to help you be more effective
- Six Thinking Hats
- Thinking Fast & Slow
- Cognitive bias / confirmation bias
This talk was last given at DevRelCon in London, December 2016.
Get into Functional Programming with ClojureJohn Stevenson
A brief guide on how to think in the way of Functional Programming, using Clojure as the example code.
Covers the main concepts and abstractions within Functional Programming & Clojure
Presented at several conferences and meetup events through 2016, with a video captured via GoPro at CeBIT Developer world 2016 on youtube at:
https://www.youtube.com/watch?v=mEfqULqChZs
Helping others learn Clojure can be a little different to how you learnt. What makes sense for one person may not make relate to another persons experiences. This presentation gives a brief introduction to guiding people into Clojure.
This presentation was first given at Clojure Remote 2016
Git and github - Verson Control for the Modern DeveloperJohn Stevenson
An introduction to Git and Github, tools for distributed version control that give an easy to use and highly collaborative approach to version code and configuration.
An overview of Functional Programming and Clojure, helping you understand the importance of minimising side effects and walking through examples of functional programming concepts.
Dreamforce14 Metadata Management with Git Version ControlJohn Stevenson
An introduction to using Git version control to manage changes in the metadata of your Salesforce Org as you develop your apps.
Your app is put into an unmanaged package, copied to your local machine with Force.com CLI and changes pushed to Github using Github for Mac/Windows client.
An introduction to Heroku, the Platform as a Service from Salesforce for all your customer facing applications.
Discover how to get going with the Heroku platform and additional services you can use to speed up the deployment of your custom application.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
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.
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.
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.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
How Atlassian made the switch to DVCS
1. Making the Switch to DVCS
How Atlassian teams moved from centralised to
distributed version control
John Stevenson
Developing the Atlassian UK Community
blog.jr0cket.co.uk
@jr0cket
1
5. Subversion issues
• Long lived branching
causing Merging hell
• <3 month release
cycles painful
• Fear of breaking the
build
• delayed commits lead
to more merging hell
6. Subversion issues
• Long lived branching
causing Merging hell
• <3 month release
cycles painful
• Fear of breaking the
build
• delayed commits lead
to more merging hell
41. Continuous Integration and
release management
• Run same builds against
subversion and git
• Continuous Validation
• Separate repos for integration
42. Continuous Integration and
release management
• Run same builds against
subversion and git
• Continuous Validation
• Separate repos for integration
43. Separate Repo for Building
Collaboration History of changes Multiple copies
44. Separate Repo for Building
Collaboration History of changes Multiple copies
45. Continuous Integration Stages
The "Gatekeeper"
• Merges changes from your
branch into the main line and
builds the result.
• Successful code is committed
and pushed
Automated branch detection
The "Build Updater"
Branch Plans automatically inherit • Merges the main line into the
master plan config changes branch, and builds the
combined code.
• Successful code is committed
& pushed to branch, ensuring
longer-living branches don't
stray far from trunk.
46. Branching and auto-merging
The "Gatekeeper"
• Merges changes from your
branch into the main line and
builds the result.
Automated branch detection • Successful code is committed
and pushed
Branch Plans automatically inherit
master plan config changes The "Build Updater"
• Merges the main line into the
branch, and builds the
combined code.
• Successful code is committed
& pushed to branch, ensuring
longer-living branches don't
stray far from trunk.
We want to share our experience of our move to DVCS\n- talking about why we did it, \n- how we did it and \n- what benefits we got from it.\n\n[Quick slide to make sure people are settled and know what they are about to hear]\n
Using Beef as a more colourful term for problem, to follow the UK theme of changing the guards (beefeaters)\n\n\n
With a centralised server, everyone shares the same resource. Its like going to a all you can eat buffet, anyone can go up to buffet at any time and make a change, but if two people want the last slice of peperoni pizza you have a conflict.\n\nIts not quite that bad for developers (we seem to have a never ending supply of pizza)\n\nIf two developers make a changes to the same part of the code they could create a conflict when they both attempt to save those changes back to the repository. The bigger they changes they make, the more risk of conflict they have with changes from one or more other developers.\n\nUsing a central model is how Atlassian teams used to work and it could make us all very angry nerds some times.\n\n\n
With a centralised server, everyone shares the same resource. Its like going to a all you can eat buffet, anyone can go up to buffet at any time and make a change, but if two people want the last slice of peperoni pizza you have a conflict.\n\nIts not quite that bad for developers (we seem to have a never ending supply of pizza)\n\nIf two developers make a changes to the same part of the code they could create a conflict when they both attempt to save those changes back to the repository. The bigger they changes they make, the more risk of conflict they have with changes from one or more other developers.\n\nUsing a central model is how Atlassian teams used to work and it could make us all very angry nerds some times.\n\n\n
Subversion is still used by a lot of developers, even though they regularly have issues with merging all the code together from each developer. As subversion only understands changes to individual files, it takes a lot of communication for a development team to not stand on each others toes when working on the same product.\n\nWhen using subversion, you have one server you connect with to save all your changes. All the changes have to be in sync with each other. If two developers work on the same code and want to commit their changes, considerable effort can be involved to merge all these changes into subversion.\n\nWhen you also have a continuous integration server attached to your subversion server, developers can become concerned about breaking the build and often delay checkin in code, making it harder to merge all these changes together.\n\nUsing DVCS, you encourage developers to commit their changes constantly.\n\n
The basics of how we have enhanced the way we develop software at Atlassian.\n\nA slide to just take a quick breath and see how people are doing...\n
Walk through the main idea of a central server - SVN style. Mention others - CVS, P4, ClearCase\n\nMost people are familiar with the centralized version controls of the world - SVN, P4, CVS\nDescribe centralized versions control with SVN (image of how it works)\nThis what Atlassian was doing across a majority of our product teams teams\n\n\n\n
Share the knowledge around the team\n\n\n
The way you work with DVCS commands (for both Git & Mercurial) are very similar to the subversion and CVS commands used. As DVCS has an additional remote repository (usually called the origin in Open Source projects) there is one extra optional step.\n\nIf you do not need to share your whole repository with anyone, there is no need to push your repository to another one.\n\nIf you want to submit a simple change, you can package it up as a pull request - a request to have your specific change pulled into someone elses repository. For example if you fork someones project on Bitbucket, making a copy that has a link back to the original repository, you can make changes to your copy of the code, commit them to your own repository and then create a pull request using the magic button on Bitbucket to send a message back to the owner of the repository. If the owner likes your change, it will be added into their repository and become officially part of the project.\n\n\n
Using a good tool you can start using the power of DVCS whist still having a subversion repository. Using things like GitSVN you can have local git repos that will push to a subversion.\n\nGive developers a chance to learn the tools well, so you are not slowing down the development process or making it too frustrating.\n\nDVCS is a new skill, so give your teams time to adopt.\n
Bring as much of the history from Subversion as you can, its an important record of your development.\n\nMake sure code is checked into the subversion, then make it read only\n
Bring as much of the history from Subversion as you can, its an important record of your development.\n\nMake sure code is checked into the subversion, then make it read only\n
\n
Every developer can create a copy of a DVCS repository on their own PC, this is called a clone. The cloned repository has the full history of the original repository and so you can trace back through all the changes that were ever done for that project.\n\nAs we are using change sets to record the change rather than individual file changes, then it is easier to manage many different branches (Forks), especially when using pull requests.\n\nPull requests give an opportunity for code review, integration testing and continuous integration builds to run.\n\n
DVCS and the rise of services like Bitbucket have helped evolve open source projects to a new level of social coding.\n\nDevelopers across the world can quickly share their code with everyone, anyone can take that code and change it, then send a message to say hey &#x201C;I found a bug in your code, here is a fix for it&#x201D;\n\nThis social coding is obviously great for open source project acceleration, as many hands get more work done. This is main reason why so many projects have switched. \n\nFor enterprises this sharing of code supports innovation and promotes collaboration within an organisation. With a private repository from Bitbucket, a team can share their code safely within the organisation and create high quality software products.\n
DVCS and the rise of services like Bitbucket have helped evolve open source projects to a new level of social coding.\n\nDevelopers across the world can quickly share their code with everyone, anyone can take that code and change it, then send a message to say hey &#x201C;I found a bug in your code, here is a fix for it&#x201D;\n\nThis social coding is obviously great for open source project acceleration, as many hands get more work done. This is main reason why so many projects have switched. \n\nFor enterprises this sharing of code supports innovation and promotes collaboration within an organisation. With a private repository from Bitbucket, a team can share their code safely within the organisation and create high quality software products.\n
Everything is on your own machine - don&#x2019;t be afraid to mess up, it is easy to get back into a stage where things are stable.\n
Be a coding ninja and commit all your changes early and often. Typically you write a failing unit test, then commit. Write some code to pass the tests and then commit. Think about refactoring and the start all over again.\n\nSome developers say the code is the documentation, but the code is just the present. By giving meaningful commit messages anyone can review the code and have a better understanding of how that code evolved.\n
Include a person of experience with DVCS in the team\nThe knowledge and experience spreads round the team\nMove people with DVCD experience around teams\n
\n
Naturally, as we use DVCS ourselves, all our products work with DVCS tools.\n
Share the knowledge around the team\n\n\n
Show how you write JIRA issue numbers in your commit statements to link up your commits with the issues in JIRA that commit addresses.\n\nThen cover how Crucible uses that JIRA number in commit to help you find the right review\n
Previously we showed the commands for git you enter on your operating system command line, you can uses visual tools like SourceTree from Atlassian to manage the whole workflow.\n\nIt seems the command line is like Marmite, you either love it or hate it. [Add your own opinion here if you wish]\n
Previously we showed the commands for git you enter on your operating system command line, you can uses visual tools like SourceTree from Atlassian to manage the whole workflow.\n\nIt seems the command line is like Marmite, you either love it or hate it. [Add your own opinion here if you wish]\n
Using SourceTree to help us work with our code in DVCS systems so we don&#x2019;t have to learn the command line.\n\n
Using SourceTree to help us work with our code in DVCS systems so we don&#x2019;t have to learn the command line.\n\n
View file history \nView authors/blame - BB or Stash\nSwitching/creating a branch - BB\n\n\n
View file history \nView authors/blame - BB or Stash\nSwitching/creating a branch - BB\nListing Tags\n\n
View file history \nView authors/blame - BB or Stash\nSwitching/creating a branch - BB\nListing Tags\n\n
\n
Show how you write JIRA issue numbers in your commit statements to link up your commits with the issues in JIRA that commit addresses.\n\nThen cover how Crucible uses that JIRA number in commit to help you find the right review\n
[Add stuff about crucible and DVCS]\n
\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
\n
\n
Share the knowledge around the team\n\n\n
I got the need, the need for SPEED (we like to drive fast)\n Common commands, just faster - status, log, commit, branch/merge are instantaneous\n The speed with which DVCS carries out common tasks lowers the bar and encourages developers in making use of those procedures. That, in turn, means that teams are using their version control system in more versatile and effective ways.\n Dev history without going over the network\nFast tool = Happy Developers\n No Servers bogging you down - push when you are ready\n Commit often\n Use the features instead of bypassing them bc they are slow\nCode without limitations\n Do "stuff" after the fact\n apply changes to a different branch <cmd>\n need more here....\n Jump between and modify branches\n need more here...\n \nAs stated in the previous slides, common commands become useful again. When commands are instantaneous that are used more often than not. Think back to any fuction in JIRA or Confluence...if they were not easily accesible you may not use them. Same with version control - if they take time or the commands are advanced you may not use the full power of the technology.\n\n\nYou will use the command line as its faster ???\n\n\nExample to give ambassadors context: Working without a network connection to your subversion repository is more than just committing the changes. If you make a mistake in a file or try a spike solution, and want to start over, you can&#x2019;t until the network returns. If you want to diff between previous versions to help find a problem, you can&#x2019;t until the network returns.\n\nDVCS allows you to utilize version control during your development without contaminating the team repository.\n
Developers have a clearer understanding of the impact of their work, both in the benefits they deliver to the customers and the potential problems if issues should arise.\n\nMore lessons learnt throughout the whole company. Small changes that build on each other are easier to absorb and get meaningful feedback, in a way that a big bang approach does not.\n\nFeeback from customers (dogfooding or OnDemand) make better products as Atlassian has a better understanding of the customer experience.\n
Instead of one big repository, the common approach is to split your code up into a more modular set of components or plugins - this is the way that Atlassian have been working for a while. In JIRA and Confluence, nearly everything is a plugin, even if it is a core part of the product.\n\nInstead of three month projects (97 days at Atlassian) a two week iteration is now running for development teams, allowing much quicker feedback from the rest of Atlassian. \n\nAs a developer you learn so much more the sooner you get feedback from your code. Code reviews are a great example of this, as are unit tests. However, there is no greater feedback than someone actually using your code day in day out. As we dogfood our products at Atlassian, any new features have over 400 eyes on them a few days after they were written and we can give feedback to the developers whilst they still remember clearly how they created those features.\n\nAn increased feedback cycle spawns more collaboration and innovation throughout Atlassian, as new features lead on to new ideas.\n\n
Now we are supporting developers directly and helping shape the future of code versioning with Bitbucket and SourceTree, a great pair of DVCS tools to help developers get work done.\n\nUsing these tools we improve the way developers manage all the changes around all of the projects they work on, from code, configurations, web artifacts, images, etc.\n\nI hope to show that using DVCS for your versioning provides real business benefit to your organisation and makes your developers happy nerds.\n