Change Project Colour

5 Tips for Your JetBrains IDE Interface

When I started this blog post, I was targeting ways to configure the so-called “New UI”, but as it turns out, not all my tips are related to that, so sit back, relax and see if something appeals to you!

Back in the old days, several of us devised ways to configure the old UI to make it more efficient for our workflow and to remove aspects that cluttered the interface. The so-called “New UI” is much kinder on the eye and easier to work with, but I still have some tips and recommendations for increasing your productivity. That’s the last time I will call it the “New UI” since it’s not so new anymore!

1. Learn tool window shortcuts

One of the biggest criticisms I am aware of was the decision to remove numbers from the tool window icons. I’m going to say it, please don’t hate me, but try and learn the shortcuts. The ones for the tool windows all take the same form, that is:

macOS
Cmd+<number>

Windows
Alt+<number>

You might be reading this thinking, “I can’t learn all 10!”; you don’t need to! Here are the common ones:

Cmd+1 / Alt+1 Project 
Cmd+4 / Alt+4 Run
Cmd+9 / Alt+9 VCS

I also use Cmd+8 / Alt+8 for the Services tool window a fair bit, too, but start with your Project, Run and VCS, that’s the basics and only three shortcuts – or just the number 149. You got this!

If you’re still not convinced, you can always head into your Settings, search for “tool windows”, and select the checkbox that says Show tool window names. It’s even better than numbers, if a little less pretty, in my opinion, but it is there if that works better for you:

JetBrains Interface with toolbar buttons

2. Don’t use editor tabs

I might horrify you with this one – you can turn off the tabs in the editor and still find everything you need quickly. Head into your Settings again and search for “editor tabs”. You’ll find what you’re looking for under Editor | General | Editor Tabs.

From the Tab placement drop-down, select “None”. Now, instead of having that space consumed at the top of your editor, you have more real estate for coding tranquillity. Before you start to worry about how to get to your files, add a new shortcut to your repertoire:

Recent Files
Cmd+E / Ctrl+E  

Recent Files is a mouse-free way of moving around the files that you have open. If you add a Shift into the shortcut, you get Recent Locations, which is arguably even more helpful: 

Recent Locations
Cmd+Shift+E / Ctrl+Shift+E 

You can think of Recent Files/Locations as your working context, so you don’t need Editor Tabs to show you that anymore:

Recent Locations in JetBrains IDE

If you want to learn more about working with a tabless UI check out this tip in our JetBrains Guide.

3. Turn the navigation bar off

The status bar is now in the navigation bar itself. How you configure this depends on the language you’re working in and how you like your IDE to look, but for me, I like the status bar on and the navigation bar off.

You can turn the navigation bar off with View | Appearance | Navigation Bar | Don’t Show:

Navigation Bar Don't Show in JetBrains IDE

This should mean that your status bar runs along the bottom uninterrupted (unless other settings are at play). You can click a status message to open it in the notifications tool window.

If the navigation bar is part of your workflow and you want it back, I suggest putting it at the top of your file instead of in the status bar.

4. Show virtual space 

Here’s a lesser-known option if, like me, you dislike working at the bottom of your screen. There’s a lesser-known option in your Settings (Cmd+, / Ctrl+Alt+S) called Show virtual space at the bottom of the file:

You can now work where your eyes are comfortable without adding white space to VCS! 

5. Change your project colour

Lastly, this one is great if you’re constantly flicking across multiple projects. You can now colour-code your projects to give your eyes a visual hint of what’s where. Right-click on your project name and choose Change Project Color:

Change Project Colour

Naturally, you can customise the colour as well.

Summary

To recap, the five tips that I recommend are:

  1. Learn tool window shortcuts
  2. Don’t use editor tabs
  3. Turn the navigation bar off
  4. Show virtual white space
  5. Change your project colour

Happy coding, and let me know what your top tips are in the comments!

The Great Resignation – So good I did it twice

Three months ago I left JetBrains because I took an opportunity at MongoDB as a Keynote Storyteller. Today I am returning to JetBrains as a Java Developer Advocate.

But that’s what a probation period is for, right? It’s a chance for the company to check out if you’re a good fit for them and more importantly, for you to check out if they’re a good fit for you. The probation period is a chance to test theories, form hypotheses and have new experiences.

In the last few weeks, while in my probation period at MongoDB, I realised two things. Firstly that it wasn’t a good fit for me, and secondly that I missed the work I was doing at JetBrains and the people I was doing that work with. Plus, life is short; we all have to find our own way.

I consider myself very fortunate, and I’m grateful to my colleagues for welcoming me back to a role where I know I can add value and work with the diverse and talented Java community once again.

I’m looking forward to continuing work on the IntelliJ IDEA Guide, creating videos for our YouTube channel, as well as getting to know the amazing Java community better. Trisha Gee and I are also busy on our book Getting to Know IntelliJ IDEA! I’ll share more updates once I’m re-settled and up to speed!

Let’s do this!

It’s My Last Day at JetBrains

I’m leaving my role as a Java Developer Advocate at JetBrains today, Friday 3rd December 2021. I start my next adventure soon, but before I do, I want to recognise those I’ve worked with as well as my achievements!

My Team

First and most importantly, my team. Trisha Gee leads the team and is my sponsor, mentor and friend. I have learned an incredible amount from her, including being kinder to myself and how to prioritise my efforts. Trisha also steered me towards public speaking and has been my biggest cheerleader in that department. Working alongside Trisha has been an incredible opportunity and privilege that I’ll cherish forever.

I can remember being incredibly excited when I first met Mala Gupta. I was totally in awe of her, and I still am. Mala embraced what I brought to the table; the skills and the fears. Mala challenged me on several occasions in the kindest way possible. I’m forever thankful to her for that. It’s because of what Mala has taught me and the feedback she’s given me that I push myself even further out of my comfort zone, repeatedly!

Dalia Abo Sheasha helped me to recognise that it wasn’t just me who struggled with code at times – everyone does. She also taught me how to walk away and come back to something troubling me, something I have often struggled with. Dalia always treated me as her equal on the Java front, despite my lack of real-world experience. She always let me find my own way when we were solving a problem and patiently listened to all my thoughts. Dalia is the reason I’m more confident writing code than I’ve ever been.

Community

The Java community have been incredibly helpful and supportive throughout my time at JetBrains. If you’ve read any of my blogs, watched any of my videos or tuned in to a live stream – thank you!

To those of you who collaborated with me on projects, are lurking in my Twitter inbox, sent me some messages of support and encouragement, gave me a platform, supported me through a new process, offered me opportunities, chatted with me in any number of Slack organisations(!), or connected me with even more amazing people – thank you!

Achievements

I’ve done a lot at JetBrains; here’s a whirlwind tour! Of course, I can’t list everything, but I’ve hand-picked my favourite highlights from my time at JetBrains.

  • Straight after I started in August-September I wrote ten blogs for the JetBrains Technology day for Java.

JetBrains Technology Day for Java

foojay Multiple Carets Blog

  • December is not only Christmas, but I also crafted this 3 Ways to Refactor Your Code in IntelliJ IDEA, one of my favourite blogs. December also was home to this screencast on the New Project Wizard in IntelliJ IDEA – my top-performing video!
  • Phew, here comes January! I stepped back from the public content creation and focussed on creating content for the IntelliJ Guide. I also started drafting my new talk Writing Code is Easy, Being a Great Developer is Hard.
  • In February, we held our IntelliJ IDEA Conference to celebrate IntelliJ IDEA turning 20!

IntelliJ IDEA Guide

JLove Conference

  • July was home to was more talk preparation and conference efforts, including being part of the program committee for Devoxx UK.
  • As I look at August I’m reminded that for the past year I’ve produced the vast majority of the tip tweets you see on the IntelliJ IDEA Twitter handle – that’s me!
  • In September, I hosted one of our Coffee Club episodes – Staying Ahead of the Curve and I started crafting what has become Helen’s Take On videos.
  • I’m not sure what happened in October, but mostly it was more video recording and conferences!
  • I spoke at Devoxx UK in early November.

Devoxx UK Conference

And since then, I’ve been wrapping up my time at JetBrains, culminating in the blog post that you’re now reading!

Summary

I’m very fond of the 16 months I spent at JetBrains, and I’m honoured to have worked with some of the smartest people I know. Beyond my immediate team, I got to work in the broader team full of talented developer advocates who never hesitated to help me or answer my endless questions.

To name check but a few… Marco – thank you for all the Spring and Spring Boot help, I learned so much from you. Paul – thank you for listening to me as I brought the IntelliJ IDEA Guide to life, I could not have done it without you (and I’m sorry for beating on Gatsby so much). Maarten for bailing me out of my Git holes on more than one occasion and generally being an all round sane voice! Rachel for teaching me some fundamentals that had totally passed me by and also for being a lovely friendly person to chat to right from the start. Nafiul for teaching me more about audio than I thought there was to know and demoing it. Shengyou for helping me to understand our broader audiences and for working so tirelessly on translations. Khalid for helping me on my website and co-authoring a blog with me. Matt for being my buddy in the UK when a rant was required about something country-specific! Yann for helping me to understand aspects of the plugin ecosystem. And finally, Hadi, firstly because he’ll be upset if I don’t mention him, but more importantly, for being super supportive at all times. I haven’t name-checked everyone (sorry), but in summary, you’re all awesome and I’ve loved working with you!

It’s been a really enjoyable time, and as I move on to my next adventure, I have great memories of this role and for all those I interacted with directly and indirectly.