If I were starting from scratch, and really had a function-key-centric workflow, I'd probably make the number keys (and - and + for F11 and F12 respectively) be tap-and-hold for that function key input.
1,702 karma · joined February 1, 2009
* Location: Pittsburgh, PA
* Web/Résumé: https://jake.achee.com
* Bio: Network-Engineer-turned-Linux-Admin-turned-SRE, Platform agnostic, not-quite-entrepreneurial. Also: I like python and awk.
* I literally grew up between a trailer park and the landfill. I know my privilege got me out. What's yours gotten you?
If I were starting from scratch, and really had a function-key-centric workflow, I'd probably make the number keys (and - and + for F11 and F12 respectively) be tap-and-hold for that function key input.
The Overview button helps get an idea of where to go.
See, e.g.: https://www.theatlantic.com/technology/archive/2025/03/libge...
I tried again this week, and CoPilot Plan Mode read the same 5-line markdown file 18 times over the course of 5 minutes of churning on a simple request, then provided zero value over what I posed in the request itself, and hallucinated things about my terraform repo that were just flat-out wrong.
As an Infrastructure/Cloud engineer, I’m far from worried about AI coming for my job.
Pick any two.
And a management failure should not result in unpaid (slave) labor.
Those are exceedingly difficult to solve via technology.
It’s happened scores of times. No company is as loyal to its labor as it expects labor to be to it.
Failures of management’s planning are imposed as emergencies on the devs.
No need for an algorithm to decide what is worth seeing.
Seems everything old is new again.