Tuesday, May 10, 2022
Tale has it that Gmail, AdSense, Google News have all started as a 20% individual projects.
At ScyllaDB R&D over the last 2 years we have been allowing R&D members to spend up to 20% on their individual projects and consider it a huge success.
In this talk I'll share our story of launching the 20% individual project and what guidelines we provide. I'll also share the frameworks we have set to track it and what changes we have done to enable its full potential.
Walking away from this talk you should consider is this right for my team?
As your team scale and grows, so do your practices of managing it. Every aspect of the team will be affected. Some can be fixed along the way - such as the processes of work. Others need to be planned from the first day to support scale - mainly culture. And of course, you, from time management to expectations and management style, must also evolve.
This talk will cover all of the above, with examples and stories, reviewing how a (fast) growing team affects culture, processes, technology, and yourself, hoping you will have a better experience managing the growth pains.
Building and maintaining robust CI/CD solutions for modern day SaaS applications is an ever increasing challenge. Catering to a diverse array of microservices, technologies, and the developers behind them is a huge undertaking that is usually backed by a small number of individuals in the R&D.
In this session we will talk about how we can overcome these challenges by creating a culture which places the responsibility back in the hands of the developers. We'll discuss what types of practices and tools exist to help us build democratic CI/CD pipelines and infrastructure. And finally, we'll examine our case study and the transition we’ve made.
DevOps is often implemented by embedding Ops team members in engineering, with the hope of increasing speed of work, creating camaraderie between teams and eliminating the “us vs. them” mentality. Unfortunately, this strategy doesn’t scale well and can often exacerbate issues of miscommunication as Ops team members start to feel siloed. Lucid’s VP of Infrastructure and IT, David Torgerson, has instead taken the opposite approach with his department, embedding engineers from every team into his Ops team. In this session, David will discuss how he’s implemented this change over the last several years, the lessons he’s learned, and how he believes this practice of “Actual DevOps” fosters empowerment within engineering and enables them to execute faster, while also holding engineers more accountable during production.
Architecture is often defined as the layout and usage of components based on external and internal constraints. Devops and SRE Teams are built around any number of services, but as services and the organizational landscape changes, team architecture can and should change to find the right fit based on the external and internal forces.
This is a vital topic as organizations evaluate their team architectures, shift priorities and add or consolidate teams in movement towards CloudNative. This session is applicable to experienced team leads as well as managers and architects that run teams and are looking for optimal team architectures.
This session is a conceptual session discussing architecture team patterns, yet technical topics will be covered encompassing Devops and SRE responsibilities and tooling. The format for this talk is a discussion covering about general constraints and then improvements that can be made in using or enhancing the patterns identified.
Key takeaways from this session will be the different types of Devops and SRE team architecture patterns that can be utilized for teams under varying external and internal constraints.
Any company doing business on the internet needs to authenticate their users. As the number of online accounts that each user needs to access has increased, the pains of password based authentication have reached a tipping point.
Passwords create problems both from a user experience perspective and a security perspective. From a user experience perspective, it is cumbersome to manage dozens if not hundreds of passwords for various accounts. From a security perspective, users end up cutting corners and reusing the same passwords across many of their online accounts. When one of those passwords is breached, then every other account using that same password is susceptible to an account takeover attack.
Passwordless authentication enables frictionless user experiences and an increased security posture, but navigating which of the myriad different authentication options to go with can be incredibly confusing. Passwordless can mean so many different things, such as email based verification like a magic link, SMS one time passcodes, biometrics, hardware keys, and SSO.
This session would discuss how to navigate the transition to a passwordless future. The session would discuss:
-Why passwords have to go.
-How to simultaneously increase conversion and decrease security risks.
-How to match your business needs to passwordless authentication options.
-When to choose email magic links, SMS one-time passcodes, WebAuthn (TouchID/FaceID and YubiKey support), OAuth, and multifactor flows, or use a combination of these methods.
-The present (and future) of biometric authentication.
The need to include an IT review during M&A due diligence is more significant than ever on both sides of a transaction. VC/PE firms, on the buy side, are looking to maximize the value of their investment. Tech companies, on the sell side, are eager to maximize their valuations.
Execs and Tech Leads in startups, however, usually participate in only a few transactions in their careers and are unprepared for the process. This talk aims to help them in their journey: we will start with a thorough analysis of the technical Due Diligence process for tech companies from the first introduction to the final DPA (Definitive Purchase Agreement).
We'll do a deep dive on each core pillar: Strategy, System Architecture, Product, People, Process&Workflows & IT/Governance. Then, we'll see "why" we look at these topics, the most common questions and the necessary document disclosures.
We'll look at strategies how to maximize the value and minimize the time spent in DD.
In the last section, we'll see how to do "dry runs" to identify any possible issues before starting a major funding round.
Three years into my software engineering career (that I was loving), a freight train hit me. I was promoted to dev team lead. This is a common trend in the engineering world - where many times the sole paths to success for excellent engineers are through management paths. However, the skills that make great developers do not always translate to great management. In fact, it’s usually quite the opposite, they often hold us back from succeeding in leadership roles, and I, unfortunately, learned this the hard way.
This talk will expose some of the surprises and common mistakes that developers transitioning into leadership roles often face. Over the years I have compiled a list of 8 tips that I wish my engineering lead would have shared with me before I took the job. This talk will focus on things like the “superhuman mode” fallacy and knowing your limitations, how to be data-driven without being a performance tyrant, and other mistakes I myself have made in my engineering leadership roles.
Developers, if you are considering pursuing a management role, this talk will help you understand what it takes to be successful. If you are already a team lead, after this talk you’ll walk away with my personal playbook and all of my best tips for becoming a more effective leader. CTOs, VPs, and Directors of Engineering will learn how to set up new managers for success as they transition from individual contributors to team leads.
The tech industry resignations rank among the highest with a 4.5% increase in departures compared to 2020 (HBR). Yet, the last two years have seen unprecedented growth across nearly every technology-driven industry. High growth and turnover compounded make for even more go-to-market challenges. How can we solve for this as leaders? We found that developers rank “opportunities to learn” in the top three reasons they stay with an organization or decide to move on. In this talk, Ben Matthews will discuss how cultivating agile thinking and learning can transform teams built for high-performance.
When I was a VP of Engineering, I would show up to the CEO's staff meeting every week and get the same question, "how can we accelerate project XYZ?" Answering this question was one of the most important aspects of my job. And yet I failed to answer it accurately most of the time.
In order to answer the question, first, we need to know:
- What is the current status of XYZ? And I'm not talking about "in progress" :)
- Which developers/teams are working on XYZ?
- What else are those developers/teams working on that are competing?
- Do we have any bottlenecks slowing us down?
There's no place we can go to get the answers to these questions. Jira doesn't have it. Our dev leads don't have it. Without this data, we can't have rationale negotiations as priorities shift and we can align engineering to business.
Through trial and error, I found processes and technology that improved my communication with the business. In this presentation, I'm sharing:
- How I correlate real developer work from GitHub with our Jira projects to provide highly accurate project delivery updates.
- How I visualize what our teams are working on so everyone in the business can see which projects are getting attention.
- Which metrics I share with the business every month to demonstrate engineering performance and improvement.
- How to implement the same process and technology in your organization.
This talk will highlight how an Intelligent Event Data Platform, with easy data consumption, low-code data transformation capabilities, and reliable, efficient data distribution, enables organizations to accelerate innovation and deliver game-changing, real-time applications to market faster, while significantly reducing the cost of software development and ongoing operations.
As data has become the currency of competitive advantage, Data Wrangling is a requisite for event driven architectures. Data Streams often require transformation and enrichment for optimized and often hyper-personalized, data delivery to a potentially millions of Web/Mobile/IoT applications. Rich data wrangling capabilities are needed in an event-driven architecture to deliver upon modernization and digital transformation goals. Data wrangling can be the most challenging and time-intensive aspect of application development. Architects are seeking low-code intelligent data platforms to address their data modeling requirements to accelerate application development and bring solutions to market faster.
You wouldn't build a house without a blueprint. Why build APIs without a plan? But you also can't build a house without the proper infrastructure. It'll take work to get your organization ready to shift left into a design-first API strategy. Learn how to prepare your organization to create a winning API program. We'll answer why organizations are turning to APIs in droves, what is holding organizations back, and why a design-first approach to your API design matters.
Building trust within your team is not only critical to employee engagement, happiness, and retention—it's what ultimately determines whether your company will succeed. Shay will discuss critical elements for new and experienced dev managers to begin implementing as they build, maintain, and scale high-performing teams. During his time at ActiveCampaign, Shay has been instrumental in leading teams across product, design, and engineering—helping the company grow sixfold in just three years and through its $240M Series C round earlier this year. From tackling difficult conversations to key decision-making, Shay will share best practices to identify and address employee struggles and drive improvements in performance. Attendees will learn strategies to foster growth, create alignment with organization goals, and build a culture of meaningful engagement—resulting in world-class product teams driven to optimize the product life cycle.
TOPIC: DEV LEADERSHIP
What are the major challenges in modern engineering organizations: Maintaining current/legacy products & code? Prototyping new products? Attracting and maintaining talent?
Wednesday, May 11, 2022
xLabs is an advanced development program in VMware’s Office of the CTO that focuses on designing, launching, and exiting highly strategically aligned technology projects that are 1-3 years ahead of the business’s roadmap. We operate a little bit like an incubator, a little bit like a VC portfolio, and we run our teams like startups that need to build in an iterable, agile fashion, learning and failing and pivoting fast to drive the best outcome. Our goal is to be the best place in the world to launch your new idea into meaningful product, accelerating participants’ careers. This talk will go over how we run the program and teams to drive results, and our lessons learned along the way as we bootstrapped, found success, and began to scale.
The effectiveness of working in a DevOps way and be able to progressively deliver software and gain insights comes from having a diverse group of people who, together, have a lot of wisdom and knowledge. You would expect that all this knowledge and all the feedback from progressively delivery software will be put to use co-creating and to design a model. In reality, we don’t actually listen to all the available input and perspectives due to cognitive biases and ranking. Because not everything that needs to be said has been said, we will end up with building sub-optimal software. Even worse, people don’t feel part of the solution and don’t commit to it. Good software needs all the insights and perception. If you are not aware, cognitive biases and ranking kills those insights and wisdom and kills the effectiveness of your DevOps culture!
Join us in this talk where we will explore how we can improve our facilitation skills and focus on neuro-inclusiveness. We will let you leave with the knowledge on how to observe sabotage behaviour, battle oppression, and to create safety in exploring alternative perceptions. We will show you how you can really let the group say what needs to be said and take a collective autocratic decision in creating software.
What makes a good engineering leader? What skills and experiences does a software engineer or lead developer require to move into engineering management and beyond?
KEYNOTE: Mattermost - How to Accelerate Hiring and Retention of Software Engineers through Developer-Friendly Workplace PR
How to accelerate hiring and retention of software engineers through developer-friendly workplace practices
Can’t hire developers? Losing the ones you have? Take a closer look at your collaboration tools--are they attracting or repelling your talent?
In a remote world, employee experience is digital experience.
Without offices, catered lunches, and fancy meeting rooms, the quality of a workplace comes down to online tools you use to communicate and get work done. HR and facilities can’t help. Nor can any other C-suite exec. It's up to CIOs and technology leaders to make the single most important decision affecting workplace satisfaction:
Will you centralize the selection of collaboration tools to save on cost--or will you give business units and departments the freedom to make their own choices, at the risk of sprawl?
Most importantly, do your IT and finance leaders understand the impact of these decisions on your organization’s ability to attract and retain software developers?
In this talk we'll discuss needs from an array of leading development organizations--from fast growing startups to tech giants to the world's largest banks--and what worked and didn't work in building a digital workplace that developers love.
Organizations are becoming mired in DevOps transformations that are stuck in a middle ground according to the latest Puppet State of DevOps Report (2021). Value stream management aims to kick these organizations on by applying the necessary cultural and lean changes required, and by applying the principles directly to ITSM, we can add new efficiencies to team workflows and incident resolution. This session will demonstrate why applying Value Stream Management to Incident Management is as important as its application to Software Delivery and how that can be achieved through a Digital Operations Platform
DevSecOps is an inclusive term yet most security teams argue they remain left out of the effort to automate deployment processes. While DevOps teams and their tools are progressing along the automation curve, security teams are left to manual hand-offs from DevOps. As a result, DevOps and security teams struggle to collaborate as their organizations modernize and adopt cloud-native technologies.
Using the resources we already possess, is it possible for cybersecurity to gather speed and collaborate with DevOps? In this session, I will cover the current automation challenges faced by cybersecurity, namely a lack in collaborative when it comes to automation with DevOps. I will show how security tools can be used in DevSecOps pipelines to automate routine security tasks including: adding infrastructure-as-code security scanning before deploying Kubernetes clusters, scanning Kubernetes deployed on cloud infrastructure against the CIS K8s benchmark , and even performing remediation with Kubernetes in real-world DevSecvOps pipelines.
Cybersecurity is a growing field but the gap between DevOps and cybersecurity is widening. The faster we make DevSecOps a reality, the quicker we can enable cybersecurity teams to truly contribute in a collaborative approach with DevOps with cloud-native technologies.
Google the phrase “Tech hiring is broken” and you’ll find roughly 21 million results. You’ll walk away from those articles with more questions than answers. Does whiteboarding really evaluate a candidate’s practical skills? How do you respect a candidate’s time? How do you avoid being exclusionary to minority groups? How do you hire junior candidates? How do you _really_ hire for culture fit? I’ve spent significant time shaping the interview process at the companies I’ve worked for, and I have learned some valuable lessons, You’ll learn about crafting an inclusive hiring process, efficiently evaluating technical skills, patterns in candidate submissions, and how your code is a reflection of culture.
Remote teams are here to stay and now is the time to figure out how to manage them effectively. The first hurdle is understanding that what normally works in the office is not going to be effective across time zones (and especially continents). Managing remote teams requires a focus on over communicating, over planning, and over empathizing. It requires a different type of management style and skill set that relies on our tools and our emotional intelligence more than ever. This talk will draw on years of experience building and managing a remotely distributed team that delivered great code reliably, and give you the tools you need to do the same.