Get an update about our two DVCS repository manager Bitbucket and Stash and learn the difference. See what we recently added to Confluence and get a sneak peak on what's coming next.
This session shows you how we do Kick-@$$ software development at Atlassian and actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Hear how we: use pull-requests for better code quality; collaborate fast to develop ideas; avoid meetings; tighten feedback loops to fail fast; shorten release cycles and work together happily on different continents. Sound like paradise? It is!
How effective feedback can improve your softwareSven Peters
Getting early feedback back into your development is essential for quality and acceptance of your application. Stop talking about what your software can do and start listening more to your customers, testers and stakeholder. This way you can find if you’re gonna ship the next killer feature or a dud. Let your customers decide what ideas would be awesome to implement and what features you should remove again to avoid feature creep.
Learn how we at Atlassian captures effectively feedback and incorporate it into our software development process. Find out how we use Innovation Games to collect ideas from users and try them out by building prototypes in just 24 hours. See how we use our cloud based services to test the adoption of new features before we role them out to all our customers. Stop endless discussions and reach out to your users!
Atlassian was founded 10 years ago. Today the Australien company has a $100 Million revenue and over 500 employees. After 10 years Atlassian still feels fresh and is one of the most popular employers for software developer. What are the Aussies doing differently?
This session shows Atlassians values and gives an inside view on how we work. I will discuss topics like:
* open and honest discussions
* what Agile means for us
* how we support innovations
* developer, developer, developer... and the rest
* how we capture feedback
We have fun developing awesome products. Other companies should have the same fun doing productive, transparent and honest software development. Find out how Atlassian works and get ideas how to improve your team and company.
Devcon Tel Aviv - How to do Kick-ass Software DevelopmentDavid Bonilla
How Atlassian tries to build kick-ass software. All the techniques, tips and hints condensed -from our special Continous Integration to our customized testing procedures- in a 30 minutes talk.
Get an update about our two DVCS repository manager Bitbucket and Stash and learn the difference. See what we recently added to Confluence and get a sneak peak on what's coming next.
This session shows you how we do Kick-@$$ software development at Atlassian and actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Hear how we: use pull-requests for better code quality; collaborate fast to develop ideas; avoid meetings; tighten feedback loops to fail fast; shorten release cycles and work together happily on different continents. Sound like paradise? It is!
How effective feedback can improve your softwareSven Peters
Getting early feedback back into your development is essential for quality and acceptance of your application. Stop talking about what your software can do and start listening more to your customers, testers and stakeholder. This way you can find if you’re gonna ship the next killer feature or a dud. Let your customers decide what ideas would be awesome to implement and what features you should remove again to avoid feature creep.
Learn how we at Atlassian captures effectively feedback and incorporate it into our software development process. Find out how we use Innovation Games to collect ideas from users and try them out by building prototypes in just 24 hours. See how we use our cloud based services to test the adoption of new features before we role them out to all our customers. Stop endless discussions and reach out to your users!
Atlassian was founded 10 years ago. Today the Australien company has a $100 Million revenue and over 500 employees. After 10 years Atlassian still feels fresh and is one of the most popular employers for software developer. What are the Aussies doing differently?
This session shows Atlassians values and gives an inside view on how we work. I will discuss topics like:
* open and honest discussions
* what Agile means for us
* how we support innovations
* developer, developer, developer... and the rest
* how we capture feedback
We have fun developing awesome products. Other companies should have the same fun doing productive, transparent and honest software development. Find out how Atlassian works and get ideas how to improve your team and company.
Devcon Tel Aviv - How to do Kick-ass Software DevelopmentDavid Bonilla
How Atlassian tries to build kick-ass software. All the techniques, tips and hints condensed -from our special Continous Integration to our customized testing procedures- in a 30 minutes talk.
Coding is simple and great if it's just you working on the code. It is getting much more complex when a whole team or even several teams are working on the code base. You want to be sure, that everybody knows about code changes, the quality is the same all over the code base and a merge shouldn't stop the whole team from working. Atlassian's tools can help you out.
This presentation shows how you can use Stash and Bamboo to happily code together in a team. You don't have to worry about broken builds on your master branch or that your graduate accidentally merges his changes that get automatic deployed. Everybody understands each part of the code base and the code got reviewed before it hits your master branch.
So you want to go Git, but other stakeholders in your organization aren't quite convinced it's worth the effort? This talk will explain why migrating to Git is a win for the whole business – not just developers. We'll give you the ammunition you need to convince your team that the switch to Git is a no-brainer.
How To Do Kick-Ass Software DevelopmentSven Peters
With Kick-Ass Software Development you actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Less mangers managing, less testers testing and less IT-operators operating. The developers take the power back, making them much happier. Sound like paradise? It is! This session will show you how we do Kick-Ass Software Development at Atlassian.
I talk about how we: use pull requests for better code quality; collaborate fast to develop ideas; avoid meetings to get more stuff done; tighten our feedback loops to fail faster; shorten our release cycles; and work together happily on different continents. It's a great way to develop software and we think it can work in your company, too.
Watch the video if this talk: http://vimeo.com/70102926
Achieving Technical Excellence in Your Software Teams - from Devternity Peter Gfader
Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers.
Great software engineer teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions.
Why would a company like to be "agile"?
How can a company achieve that?
How can you achieve Technical Excellence in your software teams?
What developer skills are more important than languages, methods or frameworks?
This will be an interactive session with a Q&A at the end.
London Atlassian User Group - February 2014Steve Smith
Continuous deployment is causing organisations to rethink how they build and release software. Atlassian Bamboo is rapidly adding features to help with automating deployment, but there are a lot of other practical and organisational issues that need to be addressed when adopting this development model. The Atlassian business-platforms team has been dealing with these issues over the last few months as we transition our order system to continuous deployment. This talk will cover why we adopted this model, some of challenges we encountered, and the approaches and tools we used to overcome them.
My 'Phoenix Project'—One Developer's Evolutionary JourneyBurr Sutter
What do Gene Kim and his apparent doppelgänger Burr Sutter have in common beyond strikingly similar goatees? DevOps. Building on Kim's iconic tech novel 'The Phoenix Project,' this lightning talk for All Things Open (with opensource.com) highlights Sutter's own 'Phoenix Project' DevOps experience earlier in his career. "We quickly understood that the only way out was forward—together—devs, ops, DBAs, and our business people—the whole team. We hero'ed up, worked in a fundamentally new way, and succeeded at the the impossible." Follow Burr on Twitter @BurrSutter
Teaching Elephants to Dance (and Fly!) A Developer's Journey to Digital Trans...Burr Sutter
We can be brilliant developers, but we won’t succeed—and won’t lead our organizations to succeed—without a new perspective (if you will) and new assumptions about the components of the “technology ecosystem” that are fundamentally critical to our success. This includes the operators, QA team, DBAs, security folks, and even the pure business contingent—in most cases, each of these individuals and groups plays a critical role in the success of what we create and give birth to as developers. What we do in isolation might be genius, but if we insulate ourselves—especially with arrogance—from these colleagues, neither our code nor our organizations will realize their full potential, and most will fail. The bottom line is that our old ways are no longer viable, and as the elite within our industry, we will be the leaders and heroes who discard old assumptions and adopt a new perspective in this exciting journey to digital transformation—where the impossible can become reality.
Fixing security by fixing software developmentNick Galbreath
Fixing Security by Fixing Software Development Using Continuous Deployment
Do you have an effective release cycle? Is your process long and archaic? Long release cycle are typically based on assumptions we haven't seen since the 1980s and require very mature organizations to implement successfully. They can also disenfranchise developers from caring or even knowing about security or operational issues. Attend this session to learn more about an alternative approach to managing deployments through Continuous Deployment, otherwise known as Continuous Delivery. Find out how small, but frequent changes to the production environment can transform an organization’s development process to truly integrate security. Learn how to get started with continuous deployment and what tools and process are needed to make implementation within your organization a (security) success.
The talk from DevOps Days Silicon Valley 2015 conference which describes the signs of having or being a single point of failure expert on your system, and the ways to solve the problem
DOES SFO 2016 - Greg Padak - Default to OpenGene Kim
Large enterprises have hierarchical organizations to define areas of responsibility and drive better accountability. Those structures often block cross-team interactions and knowledge sharing that slow innovation and agility. We will discuss strategies that use open platforms to drive meaningful development outcomes through collaboration and productivity across the enterprise.
Teaching Elephants to Dance (and Fly!): A Developer's Journey to Digital Tran...Burr Sutter
We can be brilliant developers, but we won’t succeed—and won’t lead our organizations to succeed—without a new perspective (if you will) and new assumptions about the components of the “technology ecosystem” that are fundamentally critical to our success. This includes the operators, QA team, DBAs, security folks, and even the pure business contingent—in most cases, each of these individuals and groups plays a critical role in the success of what we create and give birth to as developers. What we do in isolation might be genius, but if we insulate ourselves—especially with arrogance—from these colleagues, neither our code nor our organizations will realize their full potential, and most will fail. The bottom line is that our old ways are no longer viable, and as the elite within our industry, we will be the leaders and heroes who discard old assumptions and adopt a new perspective in this exciting journey to digital transformation—where the impossible can become reality.
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
Software development is a social challenge. We should design our workflows so that everybody knows what's going on: From coining an idea to running the software on servers in production.
Let me share with you how we at Atlassian are working with a highly transparent workflow and how we have build that directly into our tools - to build software better together!
Are you using Subversion or CVS? That’s great, whatever you do, don’t migrate to Git! Git makes you work overtime, confuses developers with too many options, destroys the social interaction with your co-workers and much more. Git has unnecessary features like offline commits and cherry picking that nobody needs at his day job. Your code is the most important thing for your software development and you should use a mature technology for storing it. Let the kids play around with Git.
In this ironic lightning talk I will give you 5 reasons, why you shouldn’t use Git always with a twinkle in the eye. So create a new branch in SVN and come to my session while you checkout the branch.
Coding is simple and great if it's just you working on the code. It is getting much more complex when a whole team or even several teams are working on the code base. You want to be sure, that everybody knows about code changes, the quality is the same all over the code base and a merge shouldn't stop the whole team from working. Atlassian's tools can help you out.
This presentation shows how you can use Stash and Bamboo to happily code together in a team. You don't have to worry about broken builds on your master branch or that your graduate accidentally merges his changes that get automatic deployed. Everybody understands each part of the code base and the code got reviewed before it hits your master branch.
So you want to go Git, but other stakeholders in your organization aren't quite convinced it's worth the effort? This talk will explain why migrating to Git is a win for the whole business – not just developers. We'll give you the ammunition you need to convince your team that the switch to Git is a no-brainer.
How To Do Kick-Ass Software DevelopmentSven Peters
With Kick-Ass Software Development you actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Less mangers managing, less testers testing and less IT-operators operating. The developers take the power back, making them much happier. Sound like paradise? It is! This session will show you how we do Kick-Ass Software Development at Atlassian.
I talk about how we: use pull requests for better code quality; collaborate fast to develop ideas; avoid meetings to get more stuff done; tighten our feedback loops to fail faster; shorten our release cycles; and work together happily on different continents. It's a great way to develop software and we think it can work in your company, too.
Watch the video if this talk: http://vimeo.com/70102926
Achieving Technical Excellence in Your Software Teams - from Devternity Peter Gfader
Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers.
Great software engineer teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions.
Why would a company like to be "agile"?
How can a company achieve that?
How can you achieve Technical Excellence in your software teams?
What developer skills are more important than languages, methods or frameworks?
This will be an interactive session with a Q&A at the end.
London Atlassian User Group - February 2014Steve Smith
Continuous deployment is causing organisations to rethink how they build and release software. Atlassian Bamboo is rapidly adding features to help with automating deployment, but there are a lot of other practical and organisational issues that need to be addressed when adopting this development model. The Atlassian business-platforms team has been dealing with these issues over the last few months as we transition our order system to continuous deployment. This talk will cover why we adopted this model, some of challenges we encountered, and the approaches and tools we used to overcome them.
My 'Phoenix Project'—One Developer's Evolutionary JourneyBurr Sutter
What do Gene Kim and his apparent doppelgänger Burr Sutter have in common beyond strikingly similar goatees? DevOps. Building on Kim's iconic tech novel 'The Phoenix Project,' this lightning talk for All Things Open (with opensource.com) highlights Sutter's own 'Phoenix Project' DevOps experience earlier in his career. "We quickly understood that the only way out was forward—together—devs, ops, DBAs, and our business people—the whole team. We hero'ed up, worked in a fundamentally new way, and succeeded at the the impossible." Follow Burr on Twitter @BurrSutter
Teaching Elephants to Dance (and Fly!) A Developer's Journey to Digital Trans...Burr Sutter
We can be brilliant developers, but we won’t succeed—and won’t lead our organizations to succeed—without a new perspective (if you will) and new assumptions about the components of the “technology ecosystem” that are fundamentally critical to our success. This includes the operators, QA team, DBAs, security folks, and even the pure business contingent—in most cases, each of these individuals and groups plays a critical role in the success of what we create and give birth to as developers. What we do in isolation might be genius, but if we insulate ourselves—especially with arrogance—from these colleagues, neither our code nor our organizations will realize their full potential, and most will fail. The bottom line is that our old ways are no longer viable, and as the elite within our industry, we will be the leaders and heroes who discard old assumptions and adopt a new perspective in this exciting journey to digital transformation—where the impossible can become reality.
Fixing security by fixing software developmentNick Galbreath
Fixing Security by Fixing Software Development Using Continuous Deployment
Do you have an effective release cycle? Is your process long and archaic? Long release cycle are typically based on assumptions we haven't seen since the 1980s and require very mature organizations to implement successfully. They can also disenfranchise developers from caring or even knowing about security or operational issues. Attend this session to learn more about an alternative approach to managing deployments through Continuous Deployment, otherwise known as Continuous Delivery. Find out how small, but frequent changes to the production environment can transform an organization’s development process to truly integrate security. Learn how to get started with continuous deployment and what tools and process are needed to make implementation within your organization a (security) success.
The talk from DevOps Days Silicon Valley 2015 conference which describes the signs of having or being a single point of failure expert on your system, and the ways to solve the problem
DOES SFO 2016 - Greg Padak - Default to OpenGene Kim
Large enterprises have hierarchical organizations to define areas of responsibility and drive better accountability. Those structures often block cross-team interactions and knowledge sharing that slow innovation and agility. We will discuss strategies that use open platforms to drive meaningful development outcomes through collaboration and productivity across the enterprise.
Teaching Elephants to Dance (and Fly!): A Developer's Journey to Digital Tran...Burr Sutter
We can be brilliant developers, but we won’t succeed—and won’t lead our organizations to succeed—without a new perspective (if you will) and new assumptions about the components of the “technology ecosystem” that are fundamentally critical to our success. This includes the operators, QA team, DBAs, security folks, and even the pure business contingent—in most cases, each of these individuals and groups plays a critical role in the success of what we create and give birth to as developers. What we do in isolation might be genius, but if we insulate ourselves—especially with arrogance—from these colleagues, neither our code nor our organizations will realize their full potential, and most will fail. The bottom line is that our old ways are no longer viable, and as the elite within our industry, we will be the leaders and heroes who discard old assumptions and adopt a new perspective in this exciting journey to digital transformation—where the impossible can become reality.
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
Software development is a social challenge. We should design our workflows so that everybody knows what's going on: From coining an idea to running the software on servers in production.
Let me share with you how we at Atlassian are working with a highly transparent workflow and how we have build that directly into our tools - to build software better together!
Are you using Subversion or CVS? That’s great, whatever you do, don’t migrate to Git! Git makes you work overtime, confuses developers with too many options, destroys the social interaction with your co-workers and much more. Git has unnecessary features like offline commits and cherry picking that nobody needs at his day job. Your code is the most important thing for your software development and you should use a mature technology for storing it. Let the kids play around with Git.
In this ironic lightning talk I will give you 5 reasons, why you shouldn’t use Git always with a twinkle in the eye. So create a new branch in SVN and come to my session while you checkout the branch.
Confluence - From Wiki to Collaboration PlatformSven Peters
A retrospective on the last 2 years (2011 to 2013). Confluence has developed a lot! This presentation shows how Atlassian has added a ton of features to help people to get their work done faster and collaborate better together.
Git is not just a version control system. Git can change the way you interact with your team members. Lot’s of teams don’t think about reflecting their development workflow in Git and just use it out-of-the-box. Git, however, can be much more powerful, giving your team a boost in productivity, protecting your delivery pipeline and helping you to work better together.
In this session we will start with a central workflow that is used by a lot of Subversion teams. You will learn how to practically integrate ALM solutions like continuous deployment, code reviews, change tracking and much more into your individual workflow. You will find out how to protect your master branch from accidental commits, broken builds and unreviewed code. This presentation will help you discover the best way to work together as a team – whether you’re yet to migrate to Git or even an experienced Git user.
It's the culture, but not as you know itSven Peters
People often start companies with a smart team and great product ideas. But as companies grows, some leaders tend to forget that it's not the product and services that made them successful – it's the culture. Culture may actually be harder to build than any product, but your organization can benefit in every way if you end up with a great one.
Sven works for Atlassian, an Australian software company that grew from 8 to 800 people in the last 10 years. He will share successes – and struggles – with bringing new people into a strong company culture, how culture is upheld in distributed teams, how your team can maintain its core culture, and why innovation and fun should be part of every company's culture.
One day we woke up and realized that our days are filled with all kind of stuff unrelated to code or product, that our goals are driven by product owners, and that our code design is dictated by architects trying to tell us how we should solve problems. A strong coding culture gives the power back to the developer to concentrate on one thing: Create awesome stuff!
Imagine a culture where the input of the whole organization turns an individual idea into a user story in just a couple of hours; where everybody's goal is to make the customer awesome, and where you work on stuff you love instead stuff you loathe. A great coding culture concentrates on making developers productive and happy by removing unnecessary overhead, bringing autonomous teams together, helping the individual programmer to innovate, and raising the awareness among the developers to create better code.
I will talk about how to establish and foster a strong engineering-focused culture that scales from a small team to a huge organization with hundreds of developers. I'll give lots of examples from our experience at Atlassian to show that once you're working in a great coding culture, you won't want to work anywhere else.
You can find a video version of the talk here: https://www.youtube.com/watch?v=rRc0FEg46kw
Moving to Git opens up a whole new level of agility for software teams. Freed from the clunky code freezes and monolithic mega-merges that plague centralized version control, developers can isolate work in progress and build in narrow vertical slices with ease. Branching is so painless with Git that many teams are making new branches for each user story or bug fix they implement. This model is quickly becoming the new gold standard for agile teams – and for good reason!
Bamboo is a continuous integrations server from Atlassian. But Bamboo is much more than that. See, how a modern CI-Server goes further with automated building, testing, deploying, and releasing of your software.
We work together in teams, across divisions and with different companies. A lot of our productive work time is lost because information is kept in departments, on file servers or in peoples heads. With the trend to distributed organizations we need to communicate more effective.
This sessions shows how companies like Atlassian and Hubspot have encouraged their employees to live and breath a collaborative culture. I will talk about 4 things that helped us work happily together like building a great work environment, focusing on people instead of roles, using tools to communicate faster and more transparently and staying away from a command & control mentality. Collaboration creates greater value, enhances achievement, and produces sustainable business models. It’s time to move from the industrial age to the information age and start the collaboration revolution!
Developing a product over years is a tough job. It is hard for the team to stay excited on a day to day basis. So how can you improve motivation and innovation of agile teams and still keep the focus on building a great product? I want to share with you how we at Atlassian used an agile approach to become one of the most successful developer tool companies in the world. This talk will cover topics like FedEx days, 20-percent time, keeping distraction away from developers, lunchtime talks, dogfooding and much more.
Keeping Your DevOps Transformation From Crushing Your Ops Capacity Rundeck
Presentation by Damon Edwards, co-founder of Rundeck, at DevOps Enterprise Summit in San Francisco, November 13, 2017
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
Container Soup for Your Soul: The Microservice Edition, Building Deployment ...Amazon Web Services
The talk is the story of a Clever's journey to effectively use a container orchestration system (ECS) and a walk through decisions to create a simple and effective deployment pipeline. We will go through various aspects of building application deployment pipelines for microservices. Clever is an education technology company and we do hundreds of deployments of tens of thousands of containers every week to serve over 50% of K-12 public and private school districts in the US. Learn More: https://aws.amazon.com/government-education/
Microservices, Microfrontends and Feature TeamsGiulio Roggero
Quali sono le buone pratiche per progettare un'architettura in stile Microservices?
Come rendere evolutiva un'applicazione Frontend senza che invecchi dopo poco tempo?
Come organizzare più team che lavorano su una Piattaforma che ha centinaia di Microservices e decine di Frontend?
A queste tre domande risponderò durante il talk con esempi pratici e casi di vita vissuta.
Scaling Up Lookout was originally presented at Lookout's Scaling for Mobile event on July 25, 2013. R. Tyler Croy is a Senior Software Engineer at Lookout, Inc. Lookout has grown immensely in the last year. We've doubled the size of the company—added more than 80 engineers to the team, support 45+ million users, have over 1000 machines in production, see over 125,000 QPS and more than 2.6 billion requests/month. Our analysts use Hadoop, Hive, and MySQL to interactively manipulate multibillion row tables. With that, there are bound to be some growing pains and lessons learned.
The most critical step in the agile transformation and DevOps adoption process is identifying the bottlenecks in the product delivery cycle. So, how do you go about finding and eliminating those dreaded bottlenecks? Tanya Kravtsov shares her experiences along with tools and methods that facilitate the discovery process while encouraging innovative thinking among team members. Join Tanya to explore ways you can use Mind Maps, Innovation Games (Speed Boat, Buy a Feature, and more), Stick Figure Process Flows, and Team Collaboration to identify, prioritize, and resolve bottlenecks. Learn ways to deal with the most common bottlenecks that cripple development progress—data generation, test environment setup, test execution, and results analysis. Automating these manual processes ensures the quality of the product by testing continuously and giving us more time for exploratory testing. This in turn helps improve developer productivity, reduces delivery cycle time, and adheres to agile principles of responding to change quickly while delivering quality software to customers. Leave with a new understanding of development bottlenecks and the tools you need to stamp them out.
This slide is translated version. Originally it was written in Korean. (http://www.slideshare.net/saltynut/how-do-we-drive-tech-changes )
It describes how do we drive technical changes onto our organizations had used old-fashioned java combinations(Java 1.6+Spring 3.x+MyBatis) and monolithic architecture.
Key point is what we need to do to drive changes, and I'll discuss what we did during Phase1 and what we are doing at Phase 2 for architecture, frontend, backend, methodologies/process.
Phase1
- Architecture : Frontend / Backend Separation
- Frontend : Angular.js, Grunt, Bower
- Backend : Java 1.7/Spring4, ORM
- Methodology/Process : Scrum, Git
Phase2
- Architecture : Micro-Service Architecture(MSA)
- Frontend : Content Router, E2E Test
- Backend : Polyglot, Multi-Framework
- Methodology/Process : Scrum+JIRA, Git Branch Policy, Pair Programming, Code Workshop
DevOps @ Scania - Trust and some code - NFI Testforum 2015Anders Lundsgård
Presentation about the DevOps movement at Scania by Anders Lundsgård and Mattias Järnhäll. The presentation was held in Stockholm the 15th of April on NFI Testforum 2015.
Similar to Atlassian - Software For Every Team (20)
✊ Join the DEV-olution: A culture of empowered developersSven Peters
Engineering leaders say their organizations struggle with productivity, collaboration, and tracking progress against goals. Some try to fix it by adding more dashboards, making strict rules, and asking for more reports. But just doing more doesn't solve the real issues developers face.
Let’s build a culture that empowers developers to do the right things and starts a dev-olution. Join Sven and hear how empowered teams build trustful relationships, work asynchronously and synchronously, use data smartly, care about outcomes, stay curious, and always try new things. More importantly, you will learn how to establish such a culture evolutionarily.
Empowering your engineers will amplify developer joy and supercharge your development effectiveness.
Team Shaping - Building a shared understandingSven Peters
Teamwork is tough, and it’s not getting easier. As more teams switch to remote or hybrid work models, building and maintaining a sense of connection and shared purpose among team members is becoming increasingly challenging. If we're going to get our teams healthy, we need to hit the teamwork gym!
Learn how to build a healthy team! We'll develop a shared understanding of responsibilities, team goals, how you work together, and our relationship with other teams. With just four simple exercises, you can bring your team in shape to become more productive and innovative. So let's pump...you up!
Developer Joy - How great teams get s%*t doneSven Peters
Join Sven and learn how great software teams measure and improve their developer experience, coordinate work across teams, run autonomous but highly aligned teams, and create a healthy and joyful engineering culture. Always backed up by data (not driven) instead of opinions.
The talk will demonstrate how great teams faced development challenges, reinvented themselves, and created new ways of working to get s%*t done. Without losing sight of what makes this craft fun for engineers.
We all know it and hate it — the dreaded “status meeting.” They’re great when it’s a small team, but they don’t scale and become a waste of time. In this session, we’ll show how to use Confluence and Atlas to keep teams in sync, async, while empowering them to continue using the apps that let them thrive.
The Hitchhiker's Guide to a Great Developer CareerSven Peters
As developers, our job is to write great code, test code, deploy code, fix code, and even delete code, but nobody told us that there is much more to it if we want to have a great developer career.
In this talk, Sven and Helen will share their successes and failures during their 20-year careers to date working for various technology companies. You’ll learn about growing your personal brand (what is it good for?), the trials and tribulations of different roles (so many choices), becoming a manager (or not), mentoring and sponsoring (they are not the same thing), how to care for yourself (prevent burnout), and lots more career advice.
You'll hear about their inevitable bumps in the road (or downright failures), as well as their successes. As it turns out, having a great developer career is not all about the technology and the code; it's also about you and the people around you!
The Effective Developer - Work Smarter, not HarderSven Peters
We’re agile, we’re doing DevOps, we work in cross-functional teams, and we use the latest developer pipeline tooling. With all those methodologies and technologies we should be highly effective, right? Probably not. Most of us still struggle with balancing coding speed and quality, working on the stuff that really makes a difference, and feeling constantly stressed by all the things we should learn.
Effective developers don’t just write clean, simple, and robust code. They also have a strong understanding of the entire development process and the problem that needs to be solved. They take time to learn, practice, and play.
Learn how those developers build effective coding habits, think about the outcome first, reserve time for deep work, and much more. You’ll walk away from this talk with lots of ideas on how to work smarter, not harder.
With all conferences going virtual this year, it's easier than ever to give a presentation: no travel days and no hotel costs. So how do you convince the organizers of an event that you're the right person with the right topic?
MongoDB veteran speakers Lauren Schaefer and Sven Peters have spoken at over 300 events and will share their tips and tricks and how to avoid pitfalls when submitting a proposal to speak at a conference.
In this workshop, you'll learn how to identify a topic that is perfect for both you and the conference, create a compelling title, and write a convincing abstract. And don't worry—you don't need to have tons of experience in public speaking to land your first gig.
The Effective Developer - Work Smarter, Not HarderSven Peters
We’re agile, we’re doing DevOps, we work in cross-functional teams, and we use the latest developer pipeline tooling. With all those methodologies and technologies we should be highly effective, right? Probably not. Most of us still struggle with balancing coding speed and quality, working on the stuff that really makes a difference, and feeling constantly stressed by all the things we should learn.
Effective developers don't just write clean, simple, and robust code. They also have a strong understanding of the entire development process and the problem that needs to be solved. They take time to learn, practice, and play.
Learn how those developers build effective coding habits, think about the outcome first, reserve time for deep work, and much more. You’ll walk away from this talk with lots of ideas on how to work smarter, not harder.
Remote work is offering lots of great benefits: access to a larger talent pool, freedom, working in pyjamas, and much more. So why are so many companies failing with remote work or hesitate to give it a try?
Sven works remotely for more than 7 years and will share 5 things how you and your distributed team can be more productive, happier, and feel more fulfilled while working remotely. You'll hear about practices like code review etiquettes, video conference rules, share-it-or-it-didn’t-happen guidelines, and much more. Learn how to best set up your office, how to keep connections with co-workers, and which tools works best in order to rock remote work.
Whether you’re just starting out in Confluence, or working in it every day, join Sven to discover the “hacks” that will maximize your productivity and make work flow more seamlessly.
Transform your content and learn the keyboard shortcuts, layout tricks, automation, and customizations that will make creating beautiful spaces and pages a breeze.
Less Process, more Guidance with a Team PlaybookSven Peters
Teams are different, projects are different, problems are different. Why are we still trying to squeeze teamwork into department processes, adding bureaucracy, and having organizational layers that makes it harder and much slower to get work done?
Join Sven Peters, former lead evangelist at Atlassian now K15t, as he talks about creating a Team Playbook by collecting practices from all teams in an organizations. No end-to-end process, no strict development rules, just some guidelines. You’ll learn tons of plays like goal setting with OKRs, decision making with DACIs, team improvements with health monitors, finding risks with premortem’s, and many more.
This talk will teach you how to utilize a playbook for more autonomy by providing teams with the freedom to pick what works in their environment.
Every software team writes code, but some teams produce fewer bugs than others. Every software team creates new features, but some teams develop them faster than others. What do high performance teams do differently, and why are team members more focused, satisfied and relaxed? They truly work together. No 10x rockstar programmer can achieve what a well rounded, enthusiastic team can.
Sven examines how the best software teams set and follow goals, integrate new members fast, ensure diversity, monitor and continually improve team health, embrace transparency, use a playbook to guide them through every phase of development and much more. He shares techniques including: bugfix rotations, OKRs, feature buddies, open demos, focus days and many more that help teams and team members to work more effectively together, and produce awesome results.
Rise of the Machines - Automate your DevelopmentSven Peters
When we talk about automation in software development, we immediately think of automated builds and deployments. We may also be using scripts to help make our daily work easier. But this is really just the beginning of the rise of the machines.
I show you how leading developers in our industry are using open source and commercial tools for automating much more. They've got "robots" for monitoring production servers, updating issues, supporting customers, reviewing code, setting up laptops, doing development reporting, conducting customer feedback -- even automating daily standups. In what instances is it useful to automate? In what cases does it not make sense? Automation prevents us from having to do the same thing twice, helps us to work better together, reduces workflow errors and frees up time to write production code. Plus, as it turns out, spending time on automation is fun! Don't be afraid of robots in software development, embrace them! Even if I save you just half an hour a week, this talk will be a beneficial investment of your time.
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.
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
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
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.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
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.
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/
7. Atlassian Q U O T E
Supporting Your J2EE World
ABN: 54 522 913 409
Level 3, 342 Kent St
Sydney, NSW 2000
Australia
Phone: (+612) 9290 1088
Fax: (+612) 9290 1343
QUOTE # KPN-003
DATE: 7/Jun/02
QUOTE DETAILS (ONSITE CODE REVIEW)
Forty hours onsite code review over 5 days from the 17
th
to 21
st
June inclusive. The option for a second week is available
at the same rates.
Code review to cover:
- Scalability and Performance
- Clustering
- EJB (CMT, CMP, BMP, DAO, JDBC)
- Security
- Review of design choices and suggestion of valid design patterns
- MVC and Workflow tool suggestions
- Coding conventions and documentation
- Other areas as advised.
QUANTITY DESCRIPTION UNIT
PRICE
AMOUNT
1 Airfare & Transfers $USD 1600 $USD 1600
7 Accommodation $USD 100 $USD 700
40 Onsite code review $USD 65 $USD 2600
SUBTOTAL $USD 4900
TAX
SHIPPING & HANDLING
TOTAL DUE $USD 4900
If you have any questions concerning this quote, contact Scott Farquhar, +61 414 884 583, scott@atlassian.com
12. The Old Way The Atlassian Way
Hard to try and deploy Do-it-yourself software
Expensive to buy Fits any budget
Top down Bottoms up
Offline business model E-commerce business model
89. Should we plan „mobile search“ for the next
sprint?
Ben Naftzger
3:15 AM
Paul Blackwell No, the mobile team just told that the platform is
not ready yet.
3:16 AM
Ben Naftzger Alright, good to know 3:16 AM
90. Should we plan „mobile search“ for the next
sprint?
Ben Naftzger
Paul Blackwell No, the mobile team just told that the platform is
not ready yet.
Ben Naftzger Alright, good to know
3:15 AM
3:16 AM
3:16 AM
Sven Peters Good Night! Apr-12 10:15 PM
Sven Peters Good Morning! 8:45 AM
92. Has anyone seen that stack trace?!
javax.servlet.ServletException: Something bad happened!
at com.example.myproject.OpenSessionInViewFilter.doFilter(OpenSessionInViewFilter.java:60)!
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)!
at com.example.myproject.ExceptionHandlerFilter.doFilter(ExceptionHandlerFilter.java:28)!
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)!
at com.example.myproject.OutputBufferFilter.doFilter(OutputBufferFilter.java:33)!
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)!
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)!
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
Sven Peters
Thomas Yes, looks like you’re using a wrong parameter
Sven Peters Thx!
Daphne Crane No, but @Thomas knows jetty pretty well@Thomas
110. Celebration designed by Scott Lewis
History designed by Ema Dimitrova
Bug designed by Matt Crum
Crown designed by Alex Auda Samora
Cleat designed by david fauveau
!
http://www.flickr.com/photos/19516393@N00/3510302818
http://www.flickr.com/photos/80641068@N07/14307438641
http://www.flickr.com/photos/22526198@N07/10920980315
https://www.flickr.com/photos/45468830@N07/6073151084/
https://www.flickr.com/photos/43322231@N07/5366609719
https://www.flickr.com/photos/45787223@N00/9309095892/
https://www.flickr.com/photos/15923063@N00/34596578
!
Thanks!
Photo credits