Blog

Posted on

IDE tips to save you from disaster

5 Features to save you from Disaster

I'm working on creating a training course for IntelliJ IDEA (I've been working on it for a while now, I don't really want to talk to much about it because I'm not sure when I'll actually deliver it). Anyway, as I was thinking through Features You Really Need To Know, I realised that it's not really about code completion and code generation, it's about those features that will get you out of a big, deep hole that you've dug yourself into.

So, I put together my top five features that have saved my bacon, and recorded a video for the Continuous Delivery channel. I have asked around and these features should work for all JetBrains IDEs, not just IntelliJ IDEA.

As usual, I have included the transcript below so you can skim it and skip to the bits that interest you.

Continue reading "IDE tips to save you from disaster"
Posted on

Staying Relevant in the Tech Industry

Thumbnail image for the video "Staying Relevant in Tech"

My latest video for the Continuous Delivery YouTube channel is about staying up to date in tech. For the last couple of years, all anyone can talk about is AI, and it can make you feel like you're becoming irrelevant if you're not learning or using AI. Don't worry, this is a feeling that is pretty much constant in tech, and is not specifically related to the hype around AI. So I dusted off an old talk, which was based on an older blog post, about how to stay up to date in technology, and condensed it to a twelve-minute YouTube video (transcript below, if you prefer to read). Enjoy.

Continue reading "Staying Relevant in the Tech Industry"
Posted on

Getting Started with Presenting

Martin Thompson and Trisha Gee

Context and Background

It's currently 2024, and I was looking for some "Getting Started with DevRel" content from my blog. All my posts are in a GitHub repo/IntelliJ IDEA Project first, and then ported into WordPress at some point. Searching my IntelliJ project I found this post, which apparently I wrote in 2020 and never published! What's more confusing is that it's based off something I wrote in 2014, so it was written 10 years ago and then I failed to publish it twice.

So, with that in mind I'm going to publish it as-is and hope that there are some useful bits and pieces in there for someone. Better than having it stuck in my drafts folder forever.

Welcome to 2020, all over again...

I have loads of advice for aspiring speakers, which is lucky because I get asked about how to get started (or how I got started) all the time. I found an email I sent to someone absolutely years ago (2014) and thought it useful enough to dust off and post. It's interesting to see my mindset back then because now I've largely forgotten what it was like in the early days.

The timing is not great, since in these Coronavirus times no-one's going to or presenting at conferences, but I firmly believe that with all these virtual events and conferences there's a much lower barrier to entry to speaking, and that now is exactly the right time to start presenting if it's something you've ever had on your wish list.

"I was hoping I could get some advice off you as I'm starting to look at ways to get out and speak a little bit more at events. Would you have some insights from how you started?"

Continue reading "Getting Started with Presenting"

Posted on

Reading Code Is Hard, and tips to improve

We spend more time reading code than writing it

This week's video for Dave Farley's Continuous Delivery YouTube channel is me ranting about why reading code sucks, and offering some advice on how to improve.

"Every programmer occasionally, when nobody’s home, turns off the lights, pours a glass of scotch, puts on some light German electronica, and opens up a file on their computer. They read over the lines, and weep at their beauty…."

https://www.stilldrinking.org/programming-sucks

The original idea for this video is from my presentation Reading Code Is Harder Than Writing It, and from my blog post Reading Code is a Skill, an older post which has only become more relevant in the modern age of AI.

Continue reading "Reading Code Is Hard, and tips to improve"
Posted on

Flaky Fashion

From left to right: Baruch, Trisha and Brian, wearing "F*ck Flaky Tests" t-shirts.

During the last four weeks, I've been to a few conferences. Sick of wearing the same t-shirts and jeans, I've been experimenting with different outfits. By far the most successful t-shirt (yes, I know, I said I was sick of wearing t-shirts) was a new one I designed for the Develocity Developer Advocates showing our disdain for intermittently-failing tests.

Continue reading "Flaky Fashion"
Posted on

Are Developer Productivity and Developer Joy opposites?

A few glasses of fizzy were consumed during the JetBrains party at Devoxx Belgium last year:

Holly: You do presentations about productivity, and about developer happiness, and I do presentations about developer joy. We should do a presentation together!

Me: Yes! What a fantastic idea! Two titans of the London Java Community co-presenting on a topic that excites us both!

This is the story of how that went

Continue reading "Are Developer Productivity and Developer Joy opposites?"
Posted on

Flaky tests are poisoning your productivity

Picture of Trisha's face frowning and the title "Flaky Tests"

I freaking HATE flaky tests.

The first time I worked in an environment that had real Continuous Integration with Actual Automated Tests that Actually Ran, it was like... freedom. We literally got the green light that our new code was working as expected, and that any changes we made hadn't broken anything. And refactoring... before then, I don't think I had ever really refactored anything. Even a simple rename was fraught with danger, you never knew if reflection or some sort of odd log-file parsing was dependent upon specific class or method names. With a comprehensive suite of unit, acceptance and performance tests, we had this blissful safety net that would tell us "Everything Is OK" after we'd done simple or extensive refactoring.

Except.

Continue reading "Flaky tests are poisoning your productivity"