Feel ya, no job is perfect. My giant employer is great about WFH for those hired as such during a particular period of time, but they’ve outsourced HR entirely to a third party - a simple inquiry becomes a three day saga, abd if I’m talking in real time to HR, voluntarily, it’s because I’ve a concern of some immediacy.

WFH plus great benefits > downsides, but it’s always a balancing act of priorities for sure.

Content? Hardly.

Disinformation. Lies. Etc.

Wasn’t sure I’d agree when I started reading, but I like the way you think.

I should have marked mine more clearly as a “first pass” from the start.

Worked with too many hotshot folks to trust future/past humans quite that much.

Once in a while, I’ve even been that hotshot guy. Definitely not excluding my own “oh that was prod…” adventures when I worry about humans, didn’t mean to come off like I think I might have.

But interesting, and certainly worth kicking around.

In green fields projects, this makes a fair bit of sense at initial reading, tentatively.

But new code becomes old code, and then builds on the quality / discipline / cowboy status of the last person to touch the code, in a complex and interlocking way.

I can’t say I’d be excited to find a partially converted existing codebase of this. But in fairness, I’m on my couch on a Sunday and haven’t actually worked through your examples (or read the original paper). I see the benefit to having both types of extensibility, obviously. Just not sure it outweighs the real world risk once actual humans start getting involved.

I don’t know a single person who can’t say they’ve never taken a single “good enough” shortcut at work, ever, and it seems this only works (efficiently) if it’s properly and fully implemented.

I distinctly remember that, and the associated horror. Not to mention the risk of fatigue, health issues, and a thousand other scenarios.

Right there with you on “just works,” as well as the simple fact that the config snippets you need are readily available - either in the repo of whatever you’re putting behind the proxy, or elsewhere on the internet.

I consistently keep in mind that it’s ultimately an RU product, of course. But since it’s open source and changes relatively infrequently, that’s mitigated to a large degree from where I sit.

Nothing against Caddy, though Apache gets heavy quickly from a maintenance standpoint, IMHO. But nginx has been my go to for many, many years per the above. It drops into oddball environments without having to rip and tear existing systems out by the roots, and it doesn’t care what’s behind it.

Ages ago, I had a Tomcat app that happened to be supported indirectly by an embedded Jetty (?) app that didn’t properly support SSL certs in a sane way on its own.

That was just fine to nginx and certbot, the little-but-important Jetty app just lived off to the side and functionally didn’t matter because with nginx and certbot, nothing else gave a crap - including the browser clients and the arcane build system that depended on that random Jetty app.

Haven’t seen RTFM casually dropped in conversation online in… um… a while…

You’ve been hanging out on the intartoobz at least as long as I have. Circa the paleolithic era, or so…

Entirely valid question, that as a USian, I might just be qual to answer. The ratio between them varies by individual, but it boils down to a core American exceptionalism that’s taught actively from very young; some ridiculous blather about how having founding docs / written constitution makes our rights safer even in context of significant social change; and my personal least fave, the idea that if one didn’t directly and proximately earn something through capital or wage slavery, they just aren’t working hard enough and therefore shouldn’t have it.

Those things are at the core of a very large group of American voters’ opinions, and all are fatally flawed.

Of course, as a child of the very early eighties, growing up it was still (at least conceptually) possible to buy a house and a car on one income, within relatively recent history. As it absolutely should be.

Kicking that exceptionalism thought process is quite the struggle (as is the rest), even for those motivated to do it.

Civilised world has mostly lower paid docs (relative to us) but also mostly some sort of universal care. I’d gladly accept NHS-level wait times, if it meant that I could take the $2k a month that my emp and I together now pay for insurance (just 2 adults) - even if taxed to support that sort of system, that is real money.

Things are bettter than they were in my lifetime, even though ObamaCare was basically a typical American “personal responsibility” solution, just with subsidies to avoid actively excluding only the less financially well off.

Used to be that you had to have continuous coverage in order to get a new cost, or pre existing conditions weren’t covered under a newer policy even if one could buy one privately (you really couldn’t, practically).

Healthcare before ACA was a sanctioned and mostly very profitable betting operation for large carriers because the risk pool for each individual policy was large, and there were max amounts and sometimes lifetime total limits that could be paid.

By comparison, what we have is pretty great for folks who lived thru that era, but… Hot garbage compared to many other developed nations.

We’re a nation full of people literally trained to think our system is the best in the world. Helluva barrier to overcome, all the more so when the ACA did actually make things better.

Mild sidetrack but the only reason to assume by default our system might be better is the education (indoctrination) we receive early and often, and consistently.

Always appreciate a comment that makes me question why/how I made some assumption.

sed harbors no demon beasts, in my experience.

On the other hand, by default using sed -i is where the demons come in.

No, sed, NOT in place. Not the first time. Show me what you want to do based on the instructions I gave you, and then we’ll talk about letting you play with the real data.

Things are no better stateside. To get social security disability takes years, and a lawyer who will take a portion of your back pay settlement when finally awarded.

And of course one can’t be earning money during the process.

Even with private short term disability coverage through employer, while it was more efficient than that, I still barely had the strength to get through it just to get partially paid for 10 hrs a week for a few months, in hopes that I can regroup, get things back together, and be able to make it through forty hour weeks.

Since that’s an external company, and our HR and payroll is a different external company, now I have to stay on the latter to make sure a) they get the memo and b) I actually get the pay in question.

As part of a much larger project that was all-in on Java to begin with, I’ve used Tomcat to serve pages and PDFs/office doc formats rendered based on a postgres backend and FreeMarker templates.

For these purposes, you don’t want that level of complexity (or Java) but the general premise and template libs should be available in nearly any sane web programming language.

What was said internally is absolutely brutal.

How many others lack the energy, strength, or (bs) “social skills” to work through this?

Might actually result in change.

My own lived experience is that the blind/deaf orgs who pursue these things should be a model for other orgs serving folks w/ other disabilities.

Thank you for the TL;dw. Sincerely appreciated.

A hard timeline on commit strikes me as less than ideal.

People are people. They have issues, they screw up, but they still write good code.

Seems like a brutal metric that encourages minimal commits without real change.

Used it in a pinch once, and realized how incredibly awesome it is. Now, it’s my go-to.

Haven’t tried data and files on same stick, but…. Now I want to.

That source is garbage.

Seems to be based on what amounts to a single “does not currently appear that the procedure itself killed him” statement from MGH, which is generally respected.

I will wait for the actual journal article that (I sincerely hope) is yet to come.

Five years, and an additional two months following consent from a highly experimental and unique procedure that he appears to have given informed consent for because he would otherwise have died sooner beats the hell out of five years without the two months.

I could make a hell of a lot of amends in sixty days, knowing it was all I had, that I’ve had trouble making in four plus decades…. Which would make the end exponentially more peaceful and pleasant.

Anything that gives me that much time is a net positive. Not going to bother with some of the usual surgical recovery stuff if I am fully informed at that point but… Don’t want to die wishing I had had time to make that one phone call or txt that I didn’t quite get to make because we don’t get to choose the moment.

Ten yrs from now hewill be a hero for undergoing the procedure that leads to real progress.

On one hand, I’m a fan of the ESP32 as a challenge.

OTOH, sometimes you actually need a full fledged computer for your semi embedded task, and sometimes you just don’t want to (or can’t be seen to, from PR standpoint) support Beijing.

While arguments can be made either way about the prior para, from a biz POV, it’s pretty binary.

Would love to find similar platforms that don’t involve those concerns and might theoretically be commercializable by hackers, but I’m not aware of many.

Not aware of a FOSS 1:1, but that sounds like Ghost or your blogging platform of choice.

Except WP, if self hosting, IMHO. Wordpress == PHP == trouble and risk. I don’t mean to malign WP specifically, but if you’re a noob, you want to avoid exposing PHP to the public internet - especially if there’s any possibility you’ll eventually forget about maintaining and upgrading.

Just too damn easy for some threat actor to come along and exploit a vuln you missed, in the software or the web server or WP.

That said, years of WP taught me that, roughly, you want “pages” linking to “posts” ( == chapters). In theory, the former is a permanent reference and the latter is dynamic to some degree.

In reality, the existence of search engines before enshittification means the two have been conflated frequently.

Pages would often get links in a sidebar or menu. Posts might get buried much farther down, but can also be linked to. They’re often, but not always, time—specific.

“2023 NY [financial product] Guide” (page) might well link to a years-old post about subrogation regarding an attempted BBQ of a random wild animal that went wrong and caused a fire, because it’s a positively classic example of the same that makes a great deal of sense to most people, even if they don’t understand terms like subrogation.

Post/page are distinctions that WP makes, but are abstractly relevant to setting up abs any CMS (which is what you want, Content Management System) so that you (ideally) never have to figure out how or where to link something, its just native. Changing the structure means changing the URLs which is annoying at best, and fraught with peril at worst.

Above 2023 xxxx Guide page, would be https://example.org/NY-Xxxx-Guide and that way you DGAF about the sidebar links, for instance. Link it once, and then you only have to update 50 posts with the year and/or some change in the data, which can be done programmatically in the db as a trivial exercise. “UPDATE page SET title = (SELECT title FROM… WHERE ‘2022’ in title TO ‘2023’;”

Disclaimer: do not run that query as copypasta, it’s meant to illustrate a point and not to exhibit valid SQL on any db (Not least because I intentionally left out at least one closing paren and simplified a bit. I’m a PG guy, and I am 100% certain it would fail as written, but fully expect anything approaching the standard to reject it. But you get the idea, update 50 states at once with a fairly simple query, once a year.

Lots going on here, but go for a modern CMS and repeatable updates, not a legacy product with a bunch of tech debt accumulated. Build it clean, plan it out first, and know whatever DB is backing it fairly well.

Migadu has been amazing. It “”just works,”and there’s no reason to deal with any of the crap that comes with hosting email.

They are affordable, and provide exactly what they claim to provide.

Email is not - IMHO - worth the trouble to self host. There are too many hard stops where email is required as login, etc to bother.

I enjoy hosting and using a variety of services. But I’ve no desire to bother with something I can ship out to folks who live and breathe that particular service.