bevr1337

PBS and NPR don't have regional programming. They're national. Local, member stations provide regional content. You'd be comparing WETA to OETA.

I'm looking at your WETA TV guide and it is completely standard material. We've got kids cartoons, Bob Ross, some selections from BBC and Bloomberg, and Ask This Old House (one of my favorites). OETA has almost identical programming.

Where's the programming where they bully people about race and sex? Are you talking about that couple that give the good financial advice? Or maybe those cooks on America's Test Kitchen? I never did trust that Wishbone dog...

Podunk people are indigenous to present-day Connecticut. The Podunk were thought to live far away, so living in Podunk grew to mean living in a remote, uninteresting place.

Originally, it may not have been used kindly. I wonder if Podunk could be thought of as an Americanization of the Roman's barbarians. (The others.)

> For the rest of that decade, the only way Americans could access ISS was by purchasing tickets on Russian spacecraft.

Perhaps our coolest diplomacy program. I love that RU and USA have managed to cooperate in space through many decades of conflict.

You're very kind and generous to reply directly. Thank you.

Just keep an open mind that others are struggling there with you ;)

> But everyone else? You're voluntarily breaking yours. I need medication to feel what you could feel naturally if you stopped training your brain that effort gets you nowhere.

> I was born with this dysfunction. You're choosing it.

This ending is worse than a TV show revealing a dream sequence.

We get it, you're special, we're sheep, thank you for enlightening us.

I was truly enjoying it until the author decided to throw out a middle finger.

The person you're replying to said they maintained a homelab for 15 years. I'm sure they have the experience to correctly gauge the amount of effort required. What you're arguing is qualitative. There is _some_ maintenance, as you admitted, and the OP has other priorities.

I personally relate to the person you're replying to. I sleep better not worrying about HDD health or if my APs can reach their controller. Tried it - not for me.

Indeed, some professional software is now cheaper and more accessible to the individual consumer. Before Adobe went to the subscription model, I only had access through school programs and later through my newspaper's office. When Adobe inevitably released a new Photoshop version, my employer could easily swallow the price tag. It seems quaint thinking about how I drove across town to access software.

> I sometimes read some dubious content on MDN.

I couldn't agree more. MDN should expect to outlive userland libraries and frameworks.

I'm curious if Vercel will find a way to funnel MDN users right into their frameworks.

A little morbid, but have you considered setting up a beneficiary for the allocation or detailing this asset in a will? That's some special, virtual real estate you have there.

Mine engine brakes, but it's true that it wouldn't be smart enough to engine brake going downhill. This is my first automatic after a couple decades of manual. It would be really nice improvement for automatics.

There are _moments_ where I would like to exercise more control, like the long downhill example or maybe staying in a low gear in bad weather.

But, I'm still unconvinced that engine braking on a manual transmission in a consumer sedan for every stoplight is helpful. Cars weigh a lot, simply let off the gas a few seconds earlier.

I'm of the opinion that Erlang/Elixir are terrible for repeat tasks like a standard CRUD server over a SQL database. Because yes, it IS cumbersome! Behaviors and type hints only get so far, and it is exhaustingly slow to sit with epgsql in the REPL to figure out what a query actually returns.

I find them much better suited for specific tasks where there is little overlap or repetition.

Anecdotally, every car I've been in where the driver talks about engine braking is rode hard and put up wet. Humans seem pretty bad at downshifting/engine braking outside of vehicles designed for that purpose like big rigs. Cars have much fewer gears so it's harder to align the downshift.

Of course there's little use in having this conversation since we all think ourselves above average drivers. I've had acquaintances reply "I don't even need a clutch I can shift so smooth!" (Do not attempt.)

I wouldn't lump guards and typespecs together. Guards are a runtime feature of erlang/elixir's excellent pattern matching.

Typespec is an opt-in type hint for develop and build time.

> Isn't there some kind of optional typing in Elixir?

Sort-of. Developers provide typespec which is like a hint and use dialyzer to find issues before runtime.

This is venturing off-topic, but can you expand on "eliminating tasks." Is eliminating a task like setting up auto bill pay, or getting rid of items that I don't want to clean?

Thanks for linking that. Their rubric for ultra-processed is easy enough to grok that folks could use this at a grocery store. We're on a kick to remove "parameters" from tasks right now, so this definition is clearer than thoughts like "stick to the outside of the store."

I'll admit my experience in Django is only migrating customers off Django. Thanks for adding some interesting details about that ecosystem

> their mental model is all wrong.

Is it? In Postgres, all FK references must be to a column with a PK or unique constraint or part of another index. Additionally, Postgres and Maria (maybe all SQL?) automatically create indexes for PKs and unique constraints. There's a high likelihood that a foreign key is already indexed _in the other table_.

Generally, I agree with your statement. Adding a FK won't magically improve performance or create useful indices. But, the presence of a FK or refactoring to support a FK does (tangentially) point back to that index.

It was nice in my 20s when we traded labor for beer and weed. A style of collaboration and exchange is what I aimed to describe.

Now, all my peers have wisened up and can get the big bucks elsewhere. So definitely, if a student of any age has the money, they can get a tutor. But it's nice to find a young tutor who would gladly proof your work in exchange for tacos or help on their CS homework

I've got them under my thumb now, and thank you! I've managed to muddle through linear and develop an ECS and prove it's in linear space and enough discrete to be pleasantly surprised by Noam Chomsky's many lives.

I used them as examples of when I transitioned back to CS and had to learn what to learn before I could learn. So to speak.

Anything on your own learning journey you'd like to share?

Quite a bit! MIT and Harvard open courses are great for aligning self-guided learning and finding vetted resources. My regex compiler would not be functional without those lecture series.

> When you don't know what you don't know, having someone to efficiently guide you can save a ton of time, and for some topics, that mentor is a great textbook or teacher.

A bit of a self insert, but I think you described the reality so well that I wanted to offer my own anecdote.

I'm somewhere between formally educated and self-taught. I did not complete higher level undergrad maths like discrete or linear. Because of this, my vocabulary is lacking. I don't even know what to google, even if I could teach myself!

Some subjects really benefit from instruction and direction. It's actually hard to find a math tutor to proof your vector math program in your late 30s. My colleagues either forgot or are using that energy elsewhere.

> you just need to never rely on the constructor for parsing user input.

A rather large disadvantage in a programming language for developing user interfaces

Their handling of MDN has been disappointing. Laying off their staff, asking for unpaid contributors, and selling more advertising space was greedy business.

They're currently running a REDIS advertisement that looks like a critical error. The ad is a bright red toast!

_Speaking personally_, MDN is Mozilla's most valuable resource. It is the only resource I want to survive Moz's leadership.

Just my two pennies. Firefox is the best vendor for adhering to spec. In contrast, Webkit drags its feet while Chromium releases and deprecates experimental API willy nilly.

There has been one debugging niche where I've found Chromium preferable: Chrome sometimes gives better WebRTC signaling error messages than Firefox.

Although I'm partial to a SPROC, I do not deploy them because I understand my colleagues might throw me from a window. But without going full tilt DB-as-the-application,

The DB can make much stronger guarantees about transactions and updates the closer that logic happens to itself. In the world of cloud computing, this can be a cost savings for ingress/egress too.

> the data does not get to decide what happens next based on itself.

Then why bother with a relational database? Relations and schemas are business logic, and I'll take all the data integrity I can get.

> if you imagine a device has a 10 year lifespan, I would guess that making the provisioning hardware probably translates into at a minimum a full month of downtime over the lifespan of the device, with many devices being down for months or years at a time because no one can be bothered to figure out why.

Can you explain more about how you reached this conclusion? Why are devices offline for years now?

Oof, yes that's certainly a way QR codes can go wrong. Ideally manufacturers print the QR code on the device such that it lasts the device's lifetime.

It would be nice if technical users (installers) could reset the certificates or keys too. Besides losing the QR code, secondhand owners also want some assurances.

> Edit: One thing Matter adds that was not in Zigbee is Bluetooth provisioning, letting you use your phone to add a device to your network without QR codes or numbers to type in.

What follows are my two pennies as a developer working in home automation for 7 years. In this venue, readers may even have more knowledge regarding security, but I hope to speak to a common case.

I develop this exact feature though not for Ikea. Having made the sausage, some of these UX-first flows are worrisome.

Consider a lightbulb that factory resets given a rapid succession of power cycles. Most consumers won't have redundant power during a brownout, so there is an edge case where dirty power can mistakenly send the bulb to a reset state. (More plausibly, a child tugging at a light switch?) Now, any device in radio range has an opportunity to take over the bulb.

Provisioning is rare. Unless the owner enjoys tinkering, a residential IoT device is provisioned a handful of times in its life. I personally think it's a waste of time to optimize this flow if the improvements are also vulnerabilities.

Suppose I have a great new smart bulb. I'm ready for a larger market so I prepare a demonstration for Lowe's, hopeful for space in their lighting and rough electric aisles. Lowe's has seen this before. My bulb works fine but my users aren't technical. Lowe's replies, "we can't carry this. Users must deploy and control from a single app in 5 minutes." If I want my smart device to compete, my hand may even be forced to implement UX-first provisioning.

Companies like Lowe's and IKEA don't want to be in the tech support business. My bulb is a liability because their customers will call with complaints or questions.

I find QR codes to be a slick implementation. They don't even need electricity! Users can manage the system even when components go offline. Folks are trained on social security numbers and PINs for bank cards. It's easy to comprehend the QR code as a password.