Trisha Gee
Gradle
Trisha is a software engineer, Java Champion and author. Trisha has developed Java applications for a range of industries of all sizes, including finance, manufacturing and non-profit, and she's a lead developer advocate at Gradle. She has expertise in Java high-performance systems and dabbles with Open Source development.Trisha’s exceptionally passionate about sharing things that help real developers. That might be: getting them up to speed on the latest version of Java; teaching them tips and tricks to improve their productivity; or promoting healthy technical communities across the globe. Trisha values helping all developers level up their career and skills at every step of their journey.Read more from Trisha in the books “Head First Java”, “Getting to Know IntelliJ IDEA”, “97 Things Every Java Developer Should Know” and “What to Look for in a Code Review”.
It may surprise you to learn that we developers are a patient, tolerant species. People pay us to do what we enjoy - write code and create working applications. In return, we will put up with all sorts of blockages and toil that get in the way of this - long build times, flaky tests, hard-to-debug toolchain failures and so on.
Is this truly the price we need to pay? Could there be a better world, where the build is as fast as it could possibly be? A world where problems that affect many developers are quickly identified, and fixed?
Welcome to the world of Developer Productivity Engineering, where we can get computers to do what they’re good at (automation) to make developers’ lives easier, and make us more effective at our jobs. And while developer joy may be a difficult thing to sell to decision makers, effective developers who are making the best use of their time, and their hardware, have a direct impact on an organization’s ROI. What’s not to love?
In this talk, Trisha will explore what DPE is, give you some practical ways to get started, and discuss ways to help the leaders in your organisation to understand the enormous value DPE could unlock.
More Is this truly the price we need to pay? Could there be a better world, where the build is as fast as it could possibly be? A world where problems that affect many developers are quickly identified, and fixed?
Welcome to the world of Developer Productivity Engineering, where we can get computers to do what they’re good at (automation) to make developers’ lives easier, and make us more effective at our jobs. And while developer joy may be a difficult thing to sell to decision makers, effective developers who are making the best use of their time, and their hardware, have a direct impact on an organization’s ROI. What’s not to love?
In this talk, Trisha will explore what DPE is, give you some practical ways to get started, and discuss ways to help the leaders in your organisation to understand the enormous value DPE could unlock.
Java programmers have a lot on their minds. The codebase, the JDK, Java, JavaScript, build and deploy scripts, code in other JVM languages, frameworks, unit tests, testing approaches, programming techniques, IDEs, tools, development process, deadlines, meetings, software architecture, design patterns, team dynamics, code, requirements, bugs, code quality... and more. A lot.
The 97 Things Every Java Programmer Should Know project has collected together the wisdom of the crowd to offer a distilled snapshot of what every Java programmer should know, from code to people, from Java to other JVM languages, from inside the JVM to the outside world. Presented by the two editors of the book, this talk draws from this collection to present some highlights and useful advice.
More The 97 Things Every Java Programmer Should Know project has collected together the wisdom of the crowd to offer a distilled snapshot of what every Java programmer should know, from code to people, from Java to other JVM languages, from inside the JVM to the outside world. Presented by the two editors of the book, this talk draws from this collection to present some highlights and useful advice.
What is the happy path, for developers? It’s less boredom, and more play.
Developer satisfaction, developer joy, and business results are strongly correlated. And yet - many of our jobs are frustrating, filled with friction, and free of joy. What’s going on? How do we fix that? Is annoying waste inevitable? Can developer performance be tuned? Are productivity measurements helping or hurting us? How do we deal with fear at work? Will AI take our jobs? Finally, how can you persuade management to invest in boredom?
Holly is an expert on play at work, unwise automations, and polar bears. Trisha is an expert on performance tuning, tooling and productivity. Come to this talk to find out what these topics have in common.
More Developer satisfaction, developer joy, and business results are strongly correlated. And yet - many of our jobs are frustrating, filled with friction, and free of joy. What’s going on? How do we fix that? Is annoying waste inevitable? Can developer performance be tuned? Are productivity measurements helping or hurting us? How do we deal with fear at work? Will AI take our jobs? Finally, how can you persuade management to invest in boredom?
Holly is an expert on play at work, unwise automations, and polar bears. Trisha is an expert on performance tuning, tooling and productivity. Come to this talk to find out what these topics have in common.
When something goes wrong during your build, do you:
1) Know immediately how to fix it
2) Spend minutes or hours digging around different places to figure out what went wrong
3) Ask The Build Expert to take a look
Yes, there are times when it's obvious what went wrong. But even if you only have issues with the build every so often, it usually takes a lot of digging around, experimenting, asking and answering questions, waiting for people to get back to you, before you realise some rogue dependency or tiny line of code in the build script caused all the problems.
In this session, Trisha will show you how to use the free Build Scan service to identify build and test issues, and share the details of a broken build (or even a successful one) to get help with troubleshooting.
More 1) Know immediately how to fix it
2) Spend minutes or hours digging around different places to figure out what went wrong
3) Ask The Build Expert to take a look
Yes, there are times when it's obvious what went wrong. But even if you only have issues with the build every so often, it usually takes a lot of digging around, experimenting, asking and answering questions, waiting for people to get back to you, before you realise some rogue dependency or tiny line of code in the build script caused all the problems.
In this session, Trisha will show you how to use the free Build Scan service to identify build and test issues, and share the details of a broken build (or even a successful one) to get help with troubleshooting.
