AT&T Fiber in Round Rock, TX (Austin metro area)
940 down; 939 up - per Speednet's macOS app via Ethernet directly to AT&T's supplied router.
Unfortunately, I'm paying $80.42/mo. as I'm well past all the offers they're willing to give. Still - overall pretty reliable, except when we have a power outage (not AT&T's fault) and it takes (on average) 15-20 minutes to get back online.
I worked for a company a full year that always prioritized new features over bug fixes, or even QA. This was a sales-driven company. For various reasons, it was a toxic environment and I left.
The next company I worked for prioritized good engineering over shipping a product. This was an engineering-oriented company. It's funding was running low ('cause - well, no product!) and I got caught up in a layoff.
Company #1 - for 5 months of that year, I was the only QA person (with 13 devs). Literally no time to automate regression - there was always the "next feature we need to close a sale to customer 'X'". I told my boss that inevitably I (or my occasional comrades) would miss something and the company would be liable. Sure enough, within 18 months of my exit, they were hit with 3 different lawsuits.
Company #2 - absolutely delightful environment, except for the non-technical CEO. Understandably, he wanted to return value to the investors, but he kept making short-term decisions about direction that, while intending to make money, ended up accelerating the cash burn. I was promoted to be a technical lead of about 8 people on a side-project that was supposed to leverage technology from a company whose name is a homophone of 1 × 10¹⁰⁰. No surprise, mega-company changed the rules and our potential product was DOA. The entire team (including me) was let go.
TL;DR - quality is engineered in, and everyone owns quality. If a genuine defect exists, determine its severity and likelihood of emergence with customers to determine priority. Don't ship/push to production any code that will cause customers to lose data or their ability to run their businesses. If you have to make a choice, choose bug fixes over new features.
I stuck to Mojave for essentially the same reason. Then I found out you could provision another volume, install Mojave on it, and treat the Mac like a dual-boot machine. When I need to run any of my 32-bit apps (mostly games, but there are others), I change the startup disk to that volume. I switch back to run in Monterey (still deciding on Ventura).
I, too, have used Typora for years whilst in Beta. I appreciated it's approach and features enough that I've paid for it.
Alternately, there's a free editor called MarkText that is maybe 85% there as compared to Typora. I use this on my work Windows machine, which is pretty locked down due to corporate policies.
My wife was at a meeting, and a friend's kid spilled water all over the table they were sitting at (her phone was sitting on the table). Same thing - Pixel 4a indicated it wouldn't use the USB-C port until water or debris was removed. I used a Q-tip a few hours after the fact (she had cleaned it to the best of her ability), and that seemed to do the trick.
I grew up in SoCal (NW Orange County - in between Seal Beach & Los Alamitos), but my mom's family hailed from near Texarkana, TX. I can still recall one of my second cousins asking me, in a very Southern accent: "Gregory Lee - whaay dew yew tokk so fuunny?" It was the first time it occurred to me that I had an accent. I've reconnected with her on social media and talked to her a couple of times. Her accent has flattened out, but I still get a chuckle about that exchange.
> It was the first time it occurred to me that I had an accent.
As a non-native speaker, it's funny to me that some people think they don't have an accent. An accent is just the way you talk, if you speak, you have an accent.
What everyone seems to think an accent is, is "this person has a different accent from mine, therefore they have an accent".
It's like seeing a blond person for the first time in your life and saying "it never occurred to me I had a hair color".
Absolutely! I found this post via my RSS feed for Hacker News.
I really like the https://feeder.co/ extension, and even pay for the Pro license. There are a few minor bugs, but overall it works extremely well for me. I don't often use the account Reader feature, but the extension has a nice way to organize various feeds into categories/folders. You can stay on the free tier forever if you'd like, but to sync across multiple machines you'll need to pay.
FWIW, the Chrome extension is named 'RSS Feed Reader' if you want to search for it. For Firefox, Edge, and iOS, it's just named 'Feeder'; Android - "Feeder.co"
As an SDET, I'm always looking for quicker/easier ways to get selectors that are non-brittle. The trick is to analyze either the CSS or XPath selector and optimize it so it's neither brittle nor a mile long. This is something I've learned to do by hand, but optimizing as I've indicated doesn't seem to be a part of the tools I've seen.
Also of note: Selenium was really designed for "Web 1.x" and doesn't assume the dynamic DOMs of today. Modern frameworks like Playwright are built with the understanding that the DOM is dynamic and are more robust. So - consider Playwright (or something like it - although I think it's "best of breed") vs. Selenium.
Unfortunately, I'm paying $80.42/mo. as I'm well past all the offers they're willing to give. Still - overall pretty reliable, except when we have a power outage (not AT&T's fault) and it takes (on average) 15-20 minutes to get back online.