DevExec World + DevLead Conference
Monday, February 7, 2022
“Quality”… velocity, productivity, and efficiency? Improved performance? Few or no bugs? Meets stakeholder requirements? “Done”… we did what we planned? Fits business objectives? Coded, tested, documented, and deployable?
Remember our customers? The people paying our salaries? Their satisfaction is supposed to be our *highest* priority. But we fall in love with assumptions about users. We burn weeks coding, testing, merging, and releasing product guesses. We move to the next project, and are interrupted later when we learn that customers aren’t finding much value or quality in that last release. Guessing, assuming, and being reactive aren’t Agile or Lean. Six Sigma would be ashamed of you.
“Architecting for customers’ needs and tasks” and “being Agile” shouldn’t be the polar opposites they often are now. No matter what an Agile coach, scrum master, or stakeholder declares, the customer decides what is “quality,” “done,” and “good enough.”
Learn how to change processes to improve agility, eliminate some Lean waste, and produce better customer outcomes.
Tuesday, February 8, 2022
Context switching between your IDE, GitHub repo, JIRA, Terminal and Slack is no way to optimize developer collaboration and it results in countless hours of distraction and lack of focus, hurting code quality. Team alignment and productivity depend on just the right mix of collaboration and staying in the zone. At the same time, developers are hindered by lack of visibility into the performance of applications across the entire tech stack. In the future, development teams must be able to troubleshoot their tools in context, integrate telemetry and observability as part of the workflow, and work with engineers on debugging as part of the collaboration. Here we will discuss how such an integration should happen, and we will spell out the benefits that accrue to the individual developer, the team and the organization.
Once seen as a far off idea, the metaverse today is lauded as the future, discussed daily in the media, and prominent in the public discourse — anything but ignored. Many experts have hypothesized what this will look like, and companies across industries and around the world are starting to come forth with their plans for their presence in this next stage of the digital age. For Dan Sturman, there’s one concept that’s central to this vision of the future online — human co-experience. In this session, Dan will outline the five key pillars of creating an ecosystem for human co-experience — fully user generated, persistent identity, universal availability, immediate teleportation, shared fabric — and dive into the latest technologies available for developers within each, including open source software, storage enhancements, Luau programming language advancements, avatar tech, search and discovery, authentication, and more. He will also spotlight how developers across platforms are leveraging technology and advancing what is possible both today and in the future. Furthermore, he will share Roblox’s vision of what will become the foundation of an accessible, safe, creative, and civil human co-experience.
Conversation Intelligence (CI) APIs enables to build applications that go beyond basic speech to text, creating a new array of sophisticated AI-driven experiences and functionalities. Basic speech recognition is designed to recognize or respond to explicit words and phrases, while conversation intelligence is capable of contextual comprehension of any human conversations to effectively extract key insights, identify user intent, surface actionable insights, detect sentiment, and more.
Conversation Intelligence has given a rise to a new generation of AI driven applications and platforms across various verticals such as revenue intelligence, tele-health, call centers and customer support, collaboration and productivity platforms and more…
In DevOps everyone performs security work, whether they like it or not. With a ratio of 100/10/1 for Development, Operations, and Security, it’s impossible for the security team alone to get it all done. We must build security into each of “the three ways”; automating and/or improving efficiency of all security activities, speeding up feedback loops for security related activities, and providing continuous learning opportunities in relation to security. While it may sound like the security team needs to learn to sprint, give feedback, and teach at the same time, the real challenge is creating a culture that embodies the mindset that security is everybody's job.
Developers are under increasing pressure to build and ship applications quickly and then add new features consistently to boost user engagement and grow competitive advantage. Moving fast always comes with risks but since moving slow isn’t a popular option, how can development teams ship code with speed whilst strategically managing the risks?
Progressive delivery is a modern way of developing, testing, and deploying code, which allows development teams to make data-driven decisions throughout the software delivery lifecycle, from pre-production to production.
Join Ivan Diaz, Manager of Solutions Engineering at Bugsnag, a SmartBear company, to discuss how development teams should be thinking about progressive delivery.
Register for the session to learn more and ask questions!
Necessity is the mother of invention. It’s a well-known proverb and means that the primary driving force for most new inventions is a need. When it comes to product innovation, those needs or ‘pain points’ are most easily identified when people in different roles tell you about them. You then follow a well-defined product innovation and development roadmap to create a solution to the problem.
But how do you solve a problem users don’t know is there? Steve Jobs famously said “people don’t know what they want until you show it to them”. With the ever-increasing pace of tech innovation and its ability to continually disrupt established ways of working, his statement has never been more true. So what is the trigger? How can you identify a ‘problem’ by convincing users that there’s a better way to do something when the current way of doing it works just fine.
Join Sanjeev Mervana, Vice President of Product Management for Cisco’s Emerging Technologies & Incubation team, as he details how to identify, generate, screen, and manage new innovation and incubation ideas that ultimately fuel growth.
“I really want to develop a tool that aggregates user interactions!”, said no developer ever.
Product-Led Growth (PLG) has stormed into our lives over the past few years. Concepts like usage-based pricing, seamless onboarding, built-in security, and product analytics are now taking a toll on developers. Companies are investing more and more engineering resources on developing self-service features that are shifting the focus from building innovative code for your product’s core technology.
From the product side, this surely looks innovative and unique. However, from the development side, it adds another variable into the equation, which already includes bugs, security issues, never-ending product feedback loops, and other things that stop developers from building exceptional code.
But while investing resources in creating a seamless product experience is crucial, isn’t the core value of the product more important? How can developers build self-service features, while achieving their innovative selves?
In this talk, we will be discussing the application side of the story for PLG success. This will be a practical demonstration of how developers can integrate self-service and data-driven by-design capabilities, while ensuring speed, flexibility, and full user observability, without sacrificing innovation.
A healthy development team is critical to the success of any technology-led organization. Companies around the globe are not only dealing with a competitive talent landscape but also a technology skills gap that has worsened since the start of the COVID-19 pandemic. But once you find the right talent, how do you nurture, retain, and keep them successful? Lilac Mohr shares key learnings on what a healthy team looks like and teaches best practices to find opportunities and areas of improvements to keep your team healthy, productive, and successful.
Design Sprints have become an increasingly common tool in Design, Technology, and Business in recent years – teams rely on them to make decisions that are core to their product. When covid appeared in 2020 and many teams went remote-first overnight, this meant that designers everywhere were taking a crash course in facilitating remote collaboration.
In this talk, Eugenia will speak about adapting the Google Sprint Process (and other processes / methods) to the new remote-first world, and will share unique insights gathered from online classroom studio collaborations, serving diverse learning needs. The material was developed in collaboration with Rachel Simpson, and they explain how to run a design sprint or collaborative workshop with remote participants (with suggested tools), unpack common challenges that facilitators may face, and discuss how to pick and choose methods to become a more flexible advanced facilitator.
There are no shortage of API metrics you could track, but how do you aligned to business outcomes. This workshop takes a deep dive on how to align metrics to three key goals: Adoption, Engagement, and Retention. Then, we'll discuss changes you can make to your developer experience for improving these areas.
As companies migrate to more resilient cloud infrastructures, threat actors continue to turn their attention to the application landscape as the new entry point for compromising systems.
Despite cyberattacks happening at a pace of every 39 seconds, only 3% of U.S. bachelor's degree graduates have cybersecurity-related skills. While several factors play into this, the most glaring is that faculty just don't know about the security field, leading to gaps between academia and industry. Unfortunately the gap has gotten wider due to constant changes and growing toolchains in software development.
This is compounded by a consistent lack of employee training in secure coding principles and how it applies to the software development life cycle, causing new entrants into software development to be ill-prepared to build secure systems.
In order to continue to defend critical assets and infrastructure in rapidly evolving cloud-centric environments, secure coding principles need to be adopted not only within corporate environments but in the classroom, ensuring that the next generation of developers can build experiences that are not only engaging but also secure.
This session will delve into:
The growing security challenges developers face today
The current perceptions of “security” within the developer community
The need for secure coding education at the university level
Opportunities for learning secure coding in educational and corporate environments
Testing in production used to be a joke. In fact, it was a popular "Most interesting man in the world" meme. But as life often imitates art, this meme has become reality. As it turns out, the best tests to learn from are the ones that match production. So when looking for feature flag solutions, developers and software delivery teams find themselves looking for ways to test their code and deployments in prod!
In this talk we will dip our toes into the world of feature flags. We'll begin with an overview of what feature flags are, how to think about them, and why both engineers and business users find them valuable. In addition, you’ll also learn about how to get started with feature flags, and the key things to look out for once you "Do it live!" .
In case you haven't heard, relational databases are the new hotness. Why? Distributed SQL. Wait, distributed what now?
Distributed SQL databases are relational databases engineered with a distributed architecture to scale out on commodity hardware, on premises or in the cloud…without any trade-offs. These databases retain standard SQL, ACID transactions and strong consistency while adding unprecedented levels of scalability. But that's only the tip of the iceberg.
In this session, you'll gain an understanding of the fundamental concepts of distributed SQL and get a quick look at MariaDB's new distributed SQL implementation, Xpand. Using MariaDB Xpand we'll take a more pragmatic look at how distributed SQL takes database elasticity, scale and high availability to the next level. Then, diving deeper, you'll be introduced to the novel concept of MariaDB's columnar indexing with distributed SQL, and how it can be used to dramatically improve the execution speed of analytical queries on massive datasets.
High performing distributed/remote teams require a concerted effort to remain productive, healthy and happy while continuing to operate with excellence. In this talk, we will talk about how to set the right metrics to measure productivity and refactor team design, day-to-day work, onboarding process with a goal to stay nimble through constant changes to work environments, needs of the customer and a rapidly growing cloud native distributed software stack.
2021 has been a breakthrough year for the crypto industry, reaching 100 million+ global users and a multi-trillion dollar market cap. In this session, Lewis will discuss what it takes to lead engineering teams building blockchain-powered products to keep up with skyrocketing mainstream demand. From implementing effective hiring methods to strategizing team roles and responsibilities, Lewis will share how technical leaders can hire and inspire high-impact teams to build industry-leading products. He will integrate key lessons learned while scaling the engineering team at Blockchain.com, increasing technical headcount over 1000% and helping the company achieve a $5 billion-plus valuation.
Policies, norms, and practices are an integral part of software development practices and undeniably important for delivering scalable and robust systems at high quality. Yet, they can simultaneously be a blocker to fast, iterative development processes which are vital to creating a culture of continuous innovation across the organization.
Even cloud developers who are striving to build bleeding-edge systems are often restricted in delivering value at their optimal personal speed. Handcuffs are being imposed on them by important, yet cumbersome cloud approval processes, as well as unnecessarily long wait times during deployment and testing stages within their cloud infrastructure.
In this talk we will shed some light on common inefficiencies and roadblocks that cloud developers face when developing against public clouds. We will discuss how to give back control and autonomy to developers over their own dev environments and tools with local and hybrid cloud development patterns, to foster innovation and fast feedback loops. Most importantly, we will highlight how the same concepts which give full autonomy to individual developers can also be leveraged to substantially improve team collaboration and feedback loops across team borders, for the best possible developer engagement across all stages of the CI/CD pipeline.
If you feel like you are not getting the full potential out of your cloud team, join me in this thought provoking session and let’s discuss strategies on how to free your development teams from their handcuffs - while embracing security, quality, and compliance.
No matter where you are, at some point your work is going to have to be demonstrated to other people. Instead of having your BA or QA or even PO demo it, wouldn't it be easier to just demo it yourself? But, having to present in front of people is a little scary. Indeed it is but there are some tips and tricks that you could learn to very easily put into practice to help you be able to eliminate that fear and be a demoing machine.
In this session, we are going to go over the basics on how to run a good demo. Tips and tricks on what to show and how to show off what you've done, and even some hints as to how to run a demo in different ways depending on your audience.
It's never going to be easy to give a demo but with a few tips and tricks, we can work on making any demo more successful
SRE (site reliability engineering) depends on orchestration and improvisation. To develop a great SRE practice means a deep understanding of the technical infrastructure but also the confidence to trust your instincts and just start jamming. I run a weekly continuous learning session at Blameless that takes its title from the traditional Indonesian orchestra: the Gamelan (pronounced ""gah-meh-lahn""). A key element of gamelan is that the music is written by the group as it is practiced, with the belief that music should grow and change.
What we've created at Blameless is an opportunity for learning and a time to come together in a collaborative way to share mental models and tell stories about different areas of the system in a safe and unpressurized way so we can carry learning forward. This way, incidents are also merely another time we can apply our powers of intuition, because we've put techniques for addressing them into practice. More precisely, we call this The Practice of Practice, which is the experience we absorb when we actually do our craft, i.e. improvisation, production, incidents. In my talk, I'll show you how we do Gamelan on the infra team. I'd like to get the audience engaged, and show them how we create an open environment for sharing and learning.
So you’re ready to hire someone to help with user experience. You’ve identified usability issues with your sites, apps, or other software products, and need someone to help fix them, a single usability professional to “do UX”—whatever that means. I’m sorry to tell you, this person does not exist. And, if you try to foist all of your usability problems onto one professional, you will not get the rainbow-filled success you’re hoping for.
While UX professionals might be pretty magical beings, no one person can juggle all of the areas of expertise needed for top-tier user experience. Having a full, well-rounded usability team is always ideal. But we don’t live in a world of unicorns or ideals. You may only be able to get the budget, resources, or go-ahead for one UX hire.
If that’s where you’re at, not all is lost. You can still create more useful, usable sites and apps with a single, strategic UX hire. To make this work, you’ll need to focus less on one person to do all things UX and more on how your lone UX pro will fit into the team and skillsets you already have.
Attendees will walk away being able to:
1. Make an honest assessment of their team’s strengths and weaknesses.
2. Understand the value of embedding UX in their existing team structure.
3. Take concrete steps towards happier users and improved success online.
Learn how developers can use Synopsys® Code Sight™ plug-in to quickly find and fix security defects in source code, open source dependencies, IaC and more, without leaving the IDE. It’s easy to try, and provides quick time to value. It helps them write better code, fix issues before code commit, and avoid costly rework caused by issues not found until downstream testing.
With testing and new releases, errors are going to creep through the cracks and new debugging approaches are needed. Nick Hodges, Developer Advocate at Rollbar, will uncover the 4 main insights that are transforming the ways we approach debugging to help return more productive time to developers.
We are beginning to see a shift in the way developers want to be interviewed, and in turn, the prospective jobs they are most drawn to. They are less intrigued by job opportunities that utilize traditional algorithm interview challenges and instead are more attracted toward those that explore real-world problems, challenges and projects.
This session will unpack the history of technical interviews, starting with trends that have since fallen out of fashion — "How many golf balls fit inside a 747?" — and landing on our current world, one that's steeped in skill-based interview challenges. As the competition for tech talent heats up globally, there's never been more at stake in hiring the right talent with the right skills.
With that in mind, the session will also look to the future of technical interviewing and the potential shifts we will see in technologies, interview structure and overall focus. As more real-world scenarios and challenges become popular, hiring companies will adapt to keep up with demand for developers.
The sad reality of our industry is that many sites and services are woefully inaccessible, and the teams behind them may not have the prior knowledge or motivation to become accessible. Making your product accessible is likely to be at least as much of a political battle as it is a technical. This talk will guide you through being firm but collaborative in both of those struggles.
We'll start with the common ways of speaking to your coworkers' motivations and positioning product accessibility to fit them. We'll then cover how to built it into your team practices. We'll end with an overview of the automations you can put in place to make sure your product and people become accessible and stay that way.
How do you launch a product with a bare-bones team working remotely in the middle of a pandemic?
In June 2020, I was tasked with taking an idea to launch in just eight weeks with nine engineers. I’d never met this team, and wouldn’t for almost two years: the pandemic had just locked everyone down.
But the investments had been made, and a date was set. I had to create a long-term vision with moments to spare and weeks to deliver.
There’s a saying: Take the leap, and build your wings on the way down. So that’s what we did.
But before you wonder how many 24-hour days the engineers put in? Not many. How frantically decisions were made? Not at all. How did the time crunch inform our tech stack? (Hint: we love Python, but Go was faster). And how does one cobble this all together, anyway?
The key to building and launching a product against outlandish technical constraints isn’t by grinding a small team into dust by making them row the boat until they can’t move. It’s by building that boat smartly, beginning with the end in mind, so you can build as you row with thoughtfully selected parts that move and scale with you from the get go.
The audience will learn:
How to replicate - or modify for themselves - my unique approach to tripling our remote team around the world in just two months
How to structure their organization for optimum collaboration, management, and conflict resolution during incredibly tight release schedules
Create 24/7 workflows without working your teams 24/7
How to choose the right tech stack for the project to get a massive project to market in a competitive timeline – without churning engineers or running into multiple dead-ends and refactors due to hasty decisions.
Roughly 60% of stream processing is spent doing mundane transformation tasks like format unification for ML workloads, filtering for privacy, simple enrichments like geo-ip translations, etc.
In this session, we will show you how easy it can be to do streaming data transformations while also eliminating data ping-ponging between storage and compute — thanks to Redpanda’s built-in support for WebAssembly (WASM). We’ll share best practices for data transforms using Redpanda, our Kafka API-compatible streaming data platform.
We will also cover:
- Overview of Redpanda and our WASM architecture
- Example use cases for data transforms
- Live demo of data transforms
The temptation to fix people problems (or product problems!) is usually to add something new. A new pizza party, a new feature, a new recurring well intended meeting…
But what if the answer lives in not adding but removing?
In this session we’ll confront our loss aversion and look for opportunities to improve culture, solve talent challenges and build systems around the truism that less is more.
As burnout and distractions rise for leaders and teams alike, the ability to remove and simplify has never been more important or more difficult.
Attendees of this session will walk away knowing how to:
Cut out the unnecessary and improve on the essential including fewer and better meetings
Map your values to your day to day patterns
Use anti-goals to clarify and remove distractions
Identify culture waste and avoid culture debt
With the explosion of various developer tools and services in recent years, it's tempting to think that we've entered a golden age for software development productivity. However, contrary to popular belief, developer productivity is in fact declining, and this phenomenon risks bringing modern software development to a grinding halt in many organizations. In this talk, Nnamdi Iregbulem, Partner at Lightspeed Venture Partners, reveals a framework for thinking about developer productivity and charts a path toward reversing this dire trend.
Human health is complex - it's not something we can buy; it's something we have to earn! This exact approach goes for open source projects and their communities. A truly dedicated and loyal fanbase cannot be bought; it has to be nurtured. But what do we mean when we call a community and the open source project "healthy"? This question is what we are trying to answer at Facebook!
In this talk, we will look at the approach that the Facebook Open Source team takes to measure the current state of Facebook open source projects, and how we use these metrics to prioritize and to direct our DevRel focus. Ultimately, we aim to show how by looking at information about your open source communities, your team can concentrate on the quality of the projects instead of only the quantity of repositories that you make public.
As web performance and user experience across both mobile and desktop devices continue to increase in importance, so do progressive web apps (PWAs). PWAs are becoming more popular because they have lots of enhancements that help your application perform better and they make apps accessible even to users with limited internet connection. In this talk, you are going to learn the advantages of using PWAs and how to turn your web application into a PWA.
Wednesday, February 9, 2022
We observe bad Developer Experiences across industries and in a variety of organisations and products. A common result of bad DX is a high cognitive load for development teams: long waiting times lead to a high amount of context switches and ultimately to a degrading momentum. Still some technical products and platforms struggle due to a lack of empathy with the user, the developer.A good Developer Experience on the other hand gets your features into production fast, reliable and safe. Whether you are managing an organisation or building a product for developers, it is time to research your developer users’ experience and invest in it.Based on our experience building a cloud and an IoT platform used by developers, we will highlight the business benefits of a good developer experience and take a closer look at indicators that help identify the right opportunities to invest in.
KEYNOTE: CircleCI -- What We Learned about Hiring Engineers after 6,000 Technical Interviews in One Year
Last year, CircleCI hit hyper-growth and needed to hire more engineers quickly. But the process was taking too long, so we had to figure out how to improve it.
We tried many things, including outsourcing technical interviews to a third party. When we still weren’t moving fast enough or finding the right talent, we iterated on our process again and again.
After conducting more than 6,000 engineering interviews in one year, Michael Stahnke, VP of Platform at CircleCI, shares what our engineering organization learned about how to scale the technical interview process and find top tech talent for growing startups.
True developers would agree: solving complex problems and coming up with innovative software solutions is every developer’s holy grail. But often developers are faced with the impossible: 25% of their time is spent on debugging, 25% is lost on meetings and security, and 20% on code maintenance. Innovation is lost in a space of unoriginality. But as the software world is heading towards a what’s known as “bottom-up” approach, developers can have a true impact on the development process, and help companies reach better dev decisions. In this session we will talk about key insights and trends from our Dev Innovation report, addressing the developer impact, what is holding it back, and what can drive it for growth.
Qt is widely recognized as a premier development framework for native, cross-platform applications and devices. But do you know what else is cross-platform? The web! Join us to see how the latest version of Qt supports the WebAssembly standard.
While the age-old choice between native vs. HTML5 development solutions will never be straightforward, we’ll show you how there can be overlap. We’ll also take a look at how you can leverage the latest Qt enhancements to expedite cross-platform deployment.
Over the last ten years the role of a software engineer has evolved drastically. Software continues to reach unprecedented scale and complexity. Organizations from all industries are now becoming software companies and with the pandemic everyone is feeling the effects of burnout. Creating an industry with healthy productivity is paramount but too much of a focus on “going faster,” without addressing burnout, is a recipe for failure. Engineering managers need to constantly balance both and as we move increasingly remote, these problems are even more acute. Ravs Kaur, CTO of Uplevel will share insights on how today’s engineering managers can ensure an efficient pipeline while making sure engineers are happy and healthy.
Enterprise blockchain is a team sport. The technology serves as shared de facto infrastructure for stakeholders across and between organizations. Community-built DLTs serve as the foundation for decentralizing critical processes and creating transparent operations with trust built in at the core.
Increasingly, enterprises are looking to deploy blockchain platforms in larger systems and more complex solutions. This means integrating with other systems and even other blockchains. The open source development model is now delivering on a new generation of tools and technologies to make deployments simpler, to help networks interoperate and more.
In this talk, David Boswell, Senior Director of Community Architecture at the Hyperledger Foundation, will sit down with Hart Montgomery of Fujitsu and Peter Somogyvari
from Accenture, two long-time leaders in the Hyperledger developer community, to talk about how development happens in the open source community and the latest developments in the current enterprise blockchain ecosystem. Hart and Peter are contributors to Hyperledger Cactus, a blockchain integration tool designed to allow users to securely integrate different blockchains. They are also members of the Hyperledger Technical Steering committee. The discussion will cover:
- Business and technical drivers for expanding blockchain networks into extensible multiparty systems capable of exchanging data in secure, transparent ways across a mix of platforms
- The growing pipeline of technologies for cross chain, off chain and legacy system interoperability
- The value of an open ecosystem in driving innovation and trusted software
- The opportunities to get involved in the community of communities developing and deploying the increasingly diverse technologies in the enterprise blockchain space
Software testing requires development skills in terms of automation and CI/CD. Social skills as well. There are though responsibilities like release management. It looks like we have to be supermen holding all these qualifications. But we are human beings. It is okay to make mistakes. It is okay not to be okay.
When I refresh my memory and consider my whole testing life, I again realize that life is full of lessons. Whenever I think about this, I come up with a saying by John W. Gardner: “Life is the art of drawing without an eraser.” We are all making mistakes and it is not possible to manage each single piece of processes perfectly. Still; what we can remember is, with additional brush strokes, those mistakes can evolve into nice colors inside the big picture. Besides, in the next run, we may take precautions against possible mistakes.
In short, after the quick review of my career, I decided that I can collect the required soft skills for a tester. Of course, I do not claim to be the super person who carries all those, but at least they are the ones which I realized to be the most prominent from my experiences.
What I will talk about is:
• What I learnt from my very early testing time: As a junior tester, what I faced? Which ways to act I learnt from those experiences.
• What I learnt from switching projects/products frequently.
• How did I survive in different environments?
• What other aspects did I experience after I was a team leader?
• What were the difficulties stemming from working in global studies?
Sometimes testing is underestimated and the responsibility is not understood well. To be able to survive in the next generation testing positions, we as testers have to hold both technical and social skills.
In this talk, I collected 25 soft skills that I decided a tester should have from my personal story. But I am pretty sure all testers face these situations. The presentation aims to wrap several skills from different perspectives like communication, agility, problem solving, efficiency and others.