When I updated the Darwin SDK and source releases in nixpkgs last year, I tried using the FreeBSD locale data. It worked in a technical sense, but it broke things that depended on the quirks in the Apple’s locale data. That statement about compatibility is unfortunately true.
I’m in my mid-40s. I’ve been practicing GTD for about a decade. My system used to be fairly elaborate in the beginning, but now it’s fairly simple. However, I don’t view it as an organizational system. It’s a tool for me to be confident that I’m doing the right thing right now.
For organizing reference material, I have a drawer with files for physical things and cloud storage and notes for digital things. I label it by topic as it seems appropriate/obvious. I review my reference material annually, deleting or destroying anything that’s not still needed.
In practice, I don’t actually engage with my system much. I review it weekly to clear out any next actions I did. It’s there as a backstop (i.e., I use deadlines as appropriate in OmniFocus) and to help keep me aware of my hard and soft landscapes.
(I lost my weekly review habit for a while, and that was bad for me and my system. I’m glad I’ve reestablished it.)
If (for example) I decide to hack on nixpkgs stuff tonight, I don’t need a task for that. I may capture one to resume later, but what’s important is that I know what I’m not doing, and I’m fine with that. If it turns out I’m not, then that’s a sign I need to renegotiate or delegate some of those things.
macOS also supports the APIs, but password manager developers don’t seem willing to implement them there.
I’ve used 1Password for a long time, but I’m probably going to drop it for Apple’s password manager because when users ask 1Password to add support, they are directed to use 1Password’s browser extension and universal autofill instead. Neither support passkeys in applications. I also find the browser extension buggy at times (especially with passkeys).
I'm aware of iOS' APIs because of Strongbox (iOS Keepass-compatible client), and someone also mentioned that macOS Strongbox does the same thing just fine. That is interesting that in this case it seems specifically a 1Password choice/disinterest.
Improving the interaction with language ecosystems was one of the motivating reasons for how I approached the [rework][1] of Darwin support in nixpkgs. A lot of Rust stuff was simply impossible to build due to their SDK needs and how hard it was to override the SDK correctly, but that’s fixed now (with a few remaining cases that will be fixed in the final staging cycle before 24.11). I expect other ecosystems to benefit similarly, especially since Darwin support looks more like a native toolchain while still being built and provided by nixpkgs.
For example, Zed and Wezterm (previously failing intermittently on x86_64-darwin) now build on Darwin. Someone even has [Firefox building from source][2]. PyTorch will be able to support MPS, and MoltenVK will be able to use Metal 3 features if your system supports them.
The bug probably wasn’t reproducing on Linux because the clang shipped with Xcode is from Apple’s fork. The version may say “15”, but it was closer to upstream LLVM’s clang 16. There are also changes that haven’t been upstreamed yet and probably some that may not ever be (if my experience updating libtapi in nixpkgs was anything to go by).
I’ve had good experiences with scrum. I was on a team that was empowered to own and refine its practice. We were able to halve our cycle time and improve sprint planning to the point where we rarely overcommitted. It was great, and it was credited with the successful delivery of a major project.
Unfortunately, our management changed, and we were no longer empowered. The new manager had his own ideas for how things should be done, and that resulted in a replacement process that was worse. We lost the ability to do effective capacity planning and iterate quickly. It was terrible.
That’s really my biggest issue with agile. There’s a big focus on process, but it’s about the people. If the people aren’t empowered, it won’t work. If you’re not iterating and communicating, it won’t work. If someone’s not on board with that, they can sabotage things (intentionally or otherwise).
That’s fair, and you’re right. I apologize for being unclear. Perhaps I should have quoted it to reflect that my issue is with what gets called “agile” rather than what the practice is supposed be (and the former seems unfortunately common).
The manager would tell people which ServiceNow tickets to work or what project work to do. We went from empowered to micromanaged. Maybe the kinks got worked out eventually, but I didn’t stick around and left after a few months.
> The traditional markers of financial success—from owning a home to snagging that corner office at work—are becoming not only less attainable but also less valuable for Gen Zers.
To be fair, those corner offices might not even exist anymore depending on the employer. From when I started working part-time in college in the early ’00s through today, those sorts of things have disappeared.
I remember how the programmers where I first worked in an entry-level position out of college had their own offices. I’m a staff engineer now, and I don’t even have my own desk (because it’s an open office with hoteling). I hate it.
The way I handle this on my home network is to advertise a ULA prefix in addition to the one delegated by my ISP. The ULA addresses are not routed. They’re just used for my network. My home DNS server advertises AAAA records using the stable, ULA addresses for those servers I want to advertise. For other machines (like computers, laptops, etc), I rely on mDNS.
You are not. At the very end of the article, right after "Happy emoji-ing!" I had to zoom in to see what they were. Previously, I could have seen them without issue due to the color variation. This is a step backwards.
Some of them seem specially hard to read. I mistook the phone emoji for a "missing character" symbol, the baby emoji for a hand and the dancing emoji for an Among Us crewmate with Elvis hair. The monkeys at the end also looked like some sort of ear at first glance. I like the idea, and most of the emojis featured in the article seem to be mostly fine at small sizes, but some of them don't really seem optimized enough to be recognizable at smaller text sizes.
