xionon
Joined 18 years ago
Joined 18 years ago
I'm in my 40s. Both my parents are alive, and have a house full of stuff. I live in a different house, 3.5 hours away at highway speeds, full of different stuff. It doesn't really matter to me if my parent's dining room table is a nicely crafted table - I have a nice table, and I don't need two dining room tables. Getting it to my house is a tremendous hassle. Picking between them is a tremendous hassle. And then I still have all the other stuff - the hutch, the chairs, the couches, the beds - and only one sibling to split them with.
"Rampant, commoditization consumerism" didn't cause this, longevity, freedom of movement, and independent living caused this, and I wouldn't trade those away for an heirloom table.
Grades don’t show your ability relative to others, they show your mastery of a set of knowledge and skills. You mastering something doesn’t prevent your neighbor from also mastering it.
It wasn't like constantly monitoring your private residence, more like setting up a breathalyzer checkpoint on the way to the freeway.
I am now 99% sure it was Spacecraft 2000 - 2100 AD. Thank you so much for posting the name and helping me solve this mystery.
The art looks unique, detailed, and dynamic.
The default is 12px. The max appears to be 30px.
Changing font size only appears to change the UI font, not the message fonts, but it does appear to change all UI sections I tested. I saw increased font in the 5 major UI sections and the Settings section.
When setting size to 30px, the the email panes looks mediocre, but usable. The icons do not increase in size, but the bounding boxes for text areas do, so things lay out approximately correct. It's clear this is not yet fully supported.
The Address Book looks like garbage, and clearly has a layout bug. In the list of contacts, the selectable boxes around different contacts do not scale appropriately, and the text from one sits over the text from its neighbors. It functions properly, and the individual contact view is usable, so this may not be a deal breaker until its fixed.
The other sections I use (calendar & tasks) look fine. I do not have any chat accounts set up, so I cannot test that section.
Overall, I would rate it as a usable first step, but hopefully they do not consider it finished. As a minimum, icons need to scale with font sizes, and the padding between elements at high font size needs to scale, or at least have some breakpoints.
This hasn't been a serious problem in a decade.
> We also had no typing then, so every bug was a runtime bug. Hopefully it's improved in the years since...
The ecosystem has been introducing gradual typing, but even at high scale, types were not remotely the most common type of problem I ever ran into, and certainly not "every" bug.
(ex-Braintree engineer, we processed billions of requests on Rails)
Or rather, is it actually too nuanced to think the ends don’t justify the means?
A meager defense follows. I've worked both "midwest design shop" and FAANG-adjacent jobs, from junior to staff to manager.
The main thing is supply and demand. The supply of engineers willing to work at a FAANG, in a region that FAANG is willing & able to support, and are willing and able to go through the technical hazing process called a "hiring panel," is very much short of demand. On the other side, profits per employee are phenomenal at scale, so making hires at these rates still makes sense financially.
But to answer your real question: it's less about the complexity of the code on a day to day basis, and more about the complexity of the system you have to work within, both technical and political, and the expectations of scale. A microservice system has both network and political boundaries to work through, whether making changes or RPC calls.
Then, while a small scale system might see a one-in-a-million event once per year, a large system will see it many times per hour, or even per minute. Managing simple things like changes to a database becomes a multi-step process, involving tools and stakeholders, instead of just a quick 2 minutes of scheduled downtime. Engineers need to be capable of thinking through those sorts of things. Stuff gets real weird at scale.
As a result, of both the above, engineers frequently find themselves doing highly specialized work, which is even harder to hire for. The guy who knows scaling properties of Postgres inside and out hasn't written production web code in a decade; his skills are almost worthless outside of FAANG-scale problems. Amazon has folks working for years on all sorts of niche network optimizations, because microseconds matter to them, but good luck transferring those skills back to fullstack web dev.
Last, a not insignificant number of engineers at FAANG are doing fantastically easy work on the same pay scale. Someone has to manage the wordpress (or whatever) installation for the docs site, or some backend process written in Django just for six important people. They often still get an engineer title and pay scale. So, it frequently is harder, but certainly not always.
Looking forward to trying out For All Mankind, See, Macbeth, and Invasion; the first two seem especially well liked by friends.
Bounced off Physical and Dickinson, but that had nothing to do with the quality of the shows; they're well made and have excellent acting.
The wide variety of stories and genres are lacking, but I think the quality of the average Apple TV+ show is quite a bit higher than the average Netflix show, on par with most of HBO.
herdr is very flexible, but it shines when you are working with multiple projects, with multiple worktrees, and multiple agents within those projects.
1. herdr uses workspaces to help organize tabs. Conceptually, a workspace probably maps to a project, but it doesn't have to.
2. herdr has native worktree support, and can create a nested workspace per worktree with a keyboard or CLI command. It can check out worktrees for you
3. herdr identifies agents across tabs and workspaces and pulls them out into an extra navigational pane. It shows the status of those agents (e.g. idle, working, waiting, done), and can play a sound when they change state. This helps you track multiple agents across multiple projects and quickly switch to them when they need help without needing to remember "claude is running in space 2, tab 3"
4. herdr integrates with your agents, which can control herdr's UI and rename tabs based on their status.
5. All this is scriptable via the herdr CLI, and agents are very good at it. But it also has full mouse support, if you're new to multiplexers its very easy to start interacting with it.