Well said. If Matthias, a person who programs Python scripts for stress testing machines, and can navigate the hideous UI/UX of some digital oscilloscope, is not "computure-savvy"...
Give any of us a tired morning without coffee and a mis-click, and many of us could be in the same predicament.
It's awful that only a privileged subset of hacked users may get enough public attention to have Google give special treatment.
But I hope Matthias gets his channel back. I'm a long-time subscriber to both of his channels. Hopefully my comment adds into the pile and brings more notice to him :)
I used to be so pleased with CenturyLink myself. symmetric 1Gbps as well, and it was dreamy.
Then I began to exhibit packet loss. For gaming/discord, it's a death knell. I isolated the source of packet loss to be within the CenturyLink network, basically between me and the first traceroute hop. (Also retroactively verified by switching ISPs)
CenturyLink as an _offering_ is great, but their company operations and customer support is... kafkaesque and absurd. They are beyond incompetent and seem to have neither the capacity nor desire to fix any real problems.
When talking with some of the technicians and support people, the insight into their world was sad and disappointing. What a ramshackle company.
I really hope nothing ever goes wrong in your network segment :)
You are right, CenturyLink support is apparently non-existent these days. My aunt recently had issues for weeks before finally giving up trying to get any real engineering support, and eventually it resolved itself, presuming some monkey noticed a rampant trend for problems in the area. Cox wasn't much better at times unless you knew exactly how to deal with support (I for a time ran part of their engineering and do), but it's still volumes better than the worse than nothing you get with CenturyLink now.
That said I've been lucky, in the 6-7 years I've been on CL moving from Cox I've had 0 problems with my DSL, where I'll say there's something to be said for the old legacy 2-wire stuff. At least every 3-4 years, I'd have to have cox out to fix my cable terminations for suck-out (center conductor eventually contracts itself to lose contact with hot/cold over time) with the extreme heat in Phoenix, so it's been almost a nice change.
About a year ago I took off maybe 5 months to create a ephemeral voice messaging mobile app (Android + iOS)
Stack:
- React Native + Expo
- Typescript
- Supabase
- Vercel
- Some Vercel/nextJS-ish lamda functions so I could avoid AWS (Supabase didn't have that kind of offering yet)
For me, it was _very_ pleasant to work in. I was able to ship features via OTA updates from idea to live in literally minutes.. sometimes even under a minute.
After things were live, my migrations would be backward compatible. It's also possible to organize your tables where most of your data is in private schemas, and public views serve as your apis and versioning. Anything in a public view must be treated as a long-lived API until clients can be phased out.
My userbase was in the dozens at most, so pushing out a version OTA usually was effective to get things moving along.
Worst case, I had some code to check if the client version was too old and would shut it down until they updated.
As per models, what kind of details are you asking?
Personally, I've found node-pg-migrate works well for a Node stack and Postgres migrations in Supabase. Then, I primarily interact with the database using the Supabase GraphQL API + RLS.
Author here. I am sure there are many articles about this already. I just wrote this nugget to be as quick and to the point on the issue, since it's a peeve of mine.
It's not about people not handling being wrong, but about introspecting on how we deliver feedback. If people cannot take feedback or accept flaws in their work, that certainly is a problem. But this article is just asking us to think about the human relationships in our work, and to hold back on knee-jerk feedback.
