If hadoop did it, so can you. I'm talking about a project that stretched Java 8 to, and arguably beyond, its intended operational boundaries. Unlikely that you’re leaning on this boundary. It's Spring Boot upgrades that will be giving you troubles.
If you’re hiring for a UX / product hybrid, I’d welcome the opportunity to connect you with a candidate.
They operate fluently across user research, synthesis, and interaction design — but more importantly, they are disciplined about ensuring the team is solving the right problem before optimizing the solution. Strong conviction around first-principles framing, epistemic rigor, and problem selection as leverage.
Core strengths:
- Structured discovery and incisive problem definition
- Translating ambiguous signals into coherent product theses
- Systems-level thinking across UX, engineering, and business constraints
- Driving execution with clarity, precision, and accountability
A thinker who prizes discernment over velocity and correctness over noise.
If your team values intellectual honesty, strategic acuity, and taste, I’m happy to make an introduction.
People found this worked in the past and it gets copied around. There is no reason to disable some of this. Bridge will automatically disable LRO and find the common set of other offloads. TSO is not useful for a bridged guest.
This way, I have all the matches at hand. When I pick the one I need, I select the line and search for it, finding the next occurrence in the full man-page.
Checking sub-command section is trivial as well. Because the editor remembers the exact location of the cursor, you can always go back to it after scrolling up and down however you feel like.
For this scenario to work nicely, you have to have run the commands from a text editor. I use Acme [1], it’s optimized for this style of work and doesn’t shy away mice. (I think that the traditional TUI cannot be as smooth.)
would search for the L tag in the ls(1) man page, or there's
man -akO tag Ic=ulimit
to find whatever the ulimit thing is or for an even more general search a small wrapper along the lines of
#!/bin/sh
man -akO tag="$1" any="$1"
may help, unless you are not on OpenBSD, in which case you may wish for the droolsauce and energy waste that is AI because the documentation on your OS is probably some sort of evolving train wreck (man pages -> gun info -> README from 2003 -> web pages, increasingly bloated and behind the iron curtain of javascript -> ??? -> Singularity! Three hails for our Saint Kurzweil!!). Back when I supported Linux I might just run strace on the process because who knew if there was documentation (maybe?) or if it was accurate (sometimes?) and
function info { /usr/bin/info "$@" 2>/dev/null | $PAGER; }
is at least a ksh function for making info somewhat less terrible.
After a while you learn to be specific ' -a' (with space) or '-a,', but this requires that you know what you're looking for. Also n/N is easier to jump between matches than /<Enter>, one less keypress.
Another useful trick is filtering with &, &/-a will narrow it down, but you won't know about the sub-commands if there are many matches. I just tried &/hidden on rg and fd and it takes me straight to `-., --hidden` for rg and `-H, --hidden` for fd. And &/case shows all options related to case-sensitivity with the descriptions. Once you get the intuition for it it's not that bad.
Manuals are not perfect but I don't think I would want an AI. I'm frustrated enough when I don't find a flag the LLM insists is supposed to be there and it gaslights me even though I'm telling the stupid thing I have the manual open.
I had the same experience, I learned it early too. My thinking was, if I'm going to be typing my whole life, I might as well do it with the bee's knees.
I also swap ctrl+caps. That caps key real estate is just too good.
It's pretty wild, I can _ONLY_ touch type dvorak. I couldn't tell you which keys are which looking down at the keyboard. And I'm fast. I'm so fast I don't even need to vibecode.
I can push 130WPM with some serious warmup on QWERTY. Even still…I can feel its inadequacy. The semicolon sitting unused under my pinky is just such a massive waste. The period there instead would be a game-changer.
It still feels bad because you most often have to jump and aim your pinky to hit enter afterwards. I guess those who write minified JS are laughing straight to the bank though.
reply