That's what I do, combined with a 64-thread/128GB build machine.
In fact, I'm so happy with my discontinued HP UltraSlim docks mounted vertically on the side of my desk/divider that I went to IT and special-ordered the last model that fit those docks. My new laptop is five years old. Worth it! :)
Do you have a physical build machine? Or in the cloud? And did you build it or order it from somewhere?
It's a Threadripper-something, 128GB RAM, and nvme disks totaling 9-10 TB (plus a sata SSD for the OS, and maybe a big HDD for the mirror). I use btrfs' raid to join the repo disks, while others use other solutions (e.g. ext4 on top of mdraid). I also run btrfs compression, which saves a lot of space for very little cost (iirc, something like 1% extra time for a full Android build, but ymmv).
Most of us share the build machine with 1-3 other engineers, which is fine because we rarely need to make (big) builds at the same time. Android is not small, and having multiple copies of the complete history for multiple people would be impractical, so we have a custom git/repo mirroring solution that keeps our various checkouts from growing out of hand.
People use whatever tool they like to connect to the machine. I've seen remote desktop of some sort, xpra, mosh... Personally, I'm using ssh and screen, with some ssh_config aliases for quick access to specific product branches.
When it's time to flash a build to a device, rsync is great. I believe AOSP aims for hermetic/reproducible builds, which enables big speedups from rsync.
I have not needed one in years, power, peripherals, and networking all go through the single usb-c connection.
Elevate & decoupled! Raise the screen. Use a Bluetooth keyboard. Stop staring down!
Ideally one can rig up a way to get the keyboard under the laptop. That's rough though, not always easy (some soda cans & cardboard... Where there's a will!). Often I end up with my laptop on my adventure pack and the keyboard in front (or on my lap). I used to just use tablet style 2-in-1's, which rock: the Tryone gooseneck arm (or many others) let's you hover the screen in really nice position, wherever you want.
I was pretty fine having a decently hidpi 11-12 inch screen positioned close in, but I have really wanted a bigger 2-in-1 I could work with. I miss 2013 when there was the bigger bigger bigger push for tablets: we are creeping back up, but the bold 18.4 beasts of that age were I hope only a bit too soon.
It all comea down to!:
> Improve your coding environment
Downsides: - Looking sideways is bad for your neck. - Looking from the one to the other and refocusing probably takes more time than using a shortcut key to switch between virtual desktops or something similar. - Consumes additional space, energy and money.
Upsides: - Looks cool and professional, I guess. - ??
I have my main monitor centered and my second off to the side. My browser mostly lives on my second monitor while my IDE lives on my main. I spend a large majority of my time looking at my center monitor, as I put my IDE there and also move my browser there when I need to look at it for any extended period of time.