Documentation is all well and good, but also having people who can solve domain problems rather than just describe them ought to be a priority among many to have a mix in the organization. Less capable people can document what someone more skilled solved if they're not great communicators (I knew several people exactly like this). Having all documenters doesn't necessarily allow tackling hard problems but could risk reducing the bar to who can communicate in-lieu of doing hard things. There is a finite supply of hard problem solvers and even fewer far who can communicate well. It may or may not be cheaper to hire one who can't communicate and a technical writer or junior staffer rather than an all-in-one unicorn who can do everything.
Pretty soon, Apple will tell you what the name of your app will be and what it should be about. Oh and nothing older than X years will be allowed to run. Tighten the screws until users repurchase hardware. Take that, hackintoshes and virtualized desktops. Verboten!
Extremely dangerous idea down the rabbit hole towards annihilation of open society. Reprehensible, but not imminently-dangerous, speech must be allowed because that is, unfortunately, the price (tradeoff) of an open and free society. Otherwise, it becomes a more closed, fascist society with thoughtpolicing and political correctness enforced by law by the fashions of those with power. F that!
Speaking of being gaslit, is everyone who applies to the Triplebyte told they received "among the highest score ever?" I know I'm adequately good but not a poet-ninja-pirate of software dev. So, it seemed like obvious BS that added to the red flags that led me to ignore them in-spite of potential $180k-ish opportunities because I just didn't trust them.
The timeless advice of Warren Buffett "no matter how good it seems now, you can never get a good deal with a shark."
The MIC will find a way to make a flying car/moon rocket that fires Hellfires and a gatling railgun. Let's call it a multi-program total cost of $40 terabucks that could've given every American a nice home (household assets are $130T but this counts both impoverished and wealthy persons) and UBI; but no: self-serving, subsidized wealth transfer to the Cheney's and the Erik Prince's comes first.
This seems like another signal of an overall trend. Post-sj, Cupertino seems to be getting progressively laxer about testing, quality, usability, and overall excellence in software and hardware. It's a shame. :'(
I don't think there's a one-sized-fits-all solution without something custom and extremely expensive ($15k+). Maybe a Lenovo T480 for most purposes and a dedicated second screen for color correctness? I had a Dell Studio XPS 1645 with an RGBLED screen with an insane gamut. It begs the question: Why aren't such screens widely available?
What about getting a T480 and replacing the screen itself? You can find a decent one for ~$400 USD, and a 1080p or WQHD screen for another $100.
As for screen availability, I think it's more to do with the fact that these are business computers. Lenovo only recently started blurring the line between their premium and business class devices.
I think every post-Haswell ThinkPad comes with a 720p screen in it's default configuration. At least up until Tx90/5 series.
Politics is a realm the average person has no power in, yet many adhere to tribal, cargo cult fashions and canards that divide-and-conquer people into atomized groups of one. Is that political or apolitical? ¯\_(ツ)_/¯
Throw politics out the window and get behind policies individually.
Argh! Package dependency hell of the second kind: mandatory requirements. It could be A Good Thing™ parts are being rewritten in Rust, but the costs, performance, and modularity of maintaining vs. ditching cairo needs to be weighed. Having two SVG rendering engines would have advantages (choices) and disadvantages (compatibility, security, code bloat).
Consumer-oriented novelty obsession (new == better + secure) and code churn "job security." If something works and is quality for what it does, it works. Does "ls" really need to be perpetually maintained with minor, inconsequential refactorings if it already works perfectly?
If something has bugs or lacks features, then it needs maintenance. "Maintenance" for pushing out versions to fulfill expectations of "maintained" is pointless.
