Presentation: Develop Your Development Experience
Share this on:
Abstract
Developers don’t get paid to write code. We deliver working software in production. How does your team turn source code into running software? And how do you make sure it stays working? If it’s like my experiences, the process is too intricate for words. Instead, let’s code it. How quickly can we get from an idea to deployment? I can spin up a project, change a bit of code, then track that through tests, code review, and into production: give me ten minutes and a few button clicks. You’ll say, but my deployment process is unique. That’s OK: we’re developers, and we can code this. Build complete? How about a nice button for deployment. Oh wait it needs review? Enforce policies in code, not through training. Build failed? Here’s a DM in Slack that includes the error from the log. Forgot to format your code? Oh look I did that. It’s like adding a team member who looooves to update issue status and check on the status of that PR for you. Let’s scale up ourselves: with our software development machine, a team can take care of more software and still build new things. Have a new organizational best practice? Put that in code and roll it out to every existing repository in minutes. Atomist expands the range of development automation past what we have considered. Come to this session, and be the developer who makes a 10x team.
How you you describe the persona and level of the target audience?
Mid-to-senior developers, architects, and development managers. These are people who want to improve their teams, but the methods prescribed so far aren't doing enough for them.
What do you want “that” persona to walk away from your talk knowing that they might not have known 50 minutes before?
The key takeaway is: your team is more than the people on it. It's also our tools, the software between us and the production app. We can move some of our team's collaboration overhead and mental-model-maintenance work (collectively, the coherence penalty to growing a team) into the automated portion of the team. Instead of onboarding more developers, let's enhance and customize our tools.
What trend in the next 12 months would you recommend an early adopter/early majority SWE to pay particular attention to?
Prepare to allocate more time for each team to improve itself by customizing its tooling. Prepare to let each team work differently. Let go of the one-size-fits-all pipeline, and think about how task takes the path it must; aim for visibility into this, over orchestration of it. You may not be ready to adopt a DevEx (bigger than DevOps) platform yet, but start thinking about the coordination tasks that you could automate, when you have the tools.
Similar Talks
Tracks
-
Microservices/ Serverless: Patterns and Practices
Stories of success and failure building modern service and function-based applications, including event sourcing, reactive, decomposition, & more.
-
Distributed Stateful Systems
Architecting and leveraging NoSQL revisitied
-
Evolving Java and the JVM: Mobile, Micro and Modular
Although the Java language is holding strong as a developer favourite, new languages and paradigms are being embraced on JVM.
-
The Practice & Frontiers of AI
Learn about machine learning in practice and on the horizon
-
Operating Systems: LinuxKit, Unikernels, & Beyond
Applied, practical, & real-world deep-dive into industry adoption of OS, containers and virtualisation, including Linux on Windows, LinuxKit, and Unikernels
-
Stream Processing in the Modern Age
Compelling applications of stream processing & recent advances in the field
-
Leading Edge Backend Languages
Code the future! How cutting-edge programming languages and their more-established forerunners can help solve today and tomorrow’s server-side technical problems.
-
Modern CS in the Real World
Applied trends in Computer Science that are likely to affect Software Engineers today.
-
DevEx: The Next Evolution of DevOps
Removing friction from the developer experience.
-
Bare Knuckle Performance
Killing latency and getting the most out of your hardware
-
Tech Ethics in Action
Learning from the experiences of real-world companies driving technology decisions from ethics as much as technology.
-
Security: Red XOR Blue Team
Security from the defender's AND the attacker's point of view
-
Architecting for Failure
If you're not architecting for failure you're heading for failure
-
Architectures You've Always Wondered About
Topics like next-gen architecture mixed with applied use cases found in today's large-scale systems, self-driving cars, network routing, scale, robotics, cloud deployments, and more.
-
Observability: Logging, Alerting and Tracing
Observability in modern large distributed computer systems
-
Speaker AMAs (Ask Me Anything)
-
Building Great Engineering Cultures & Organizations
Stories of cultural change in organizations
-
Speaker AMAs (Ask Me Anything)