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.

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.

I do not know why these two concepts are so frequently conflated and misunderstood, but they absolutely are.

Thanks for the solid clarification. At-will and RTW are two very different concepts, and off the top of my head, forty-nine of the fifty states are at-will. The 50th state isn’t all that different (MT), just a bit nuanced: “Montana defaults to a probationary period, after which termination is only lawful if for good cause”

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…

Seems like it would be a nightmare to purify. Perhaps useful for agricultural applications, but for drinking and household use…. Most water supplies don’t have e.g., human bodies floating in them.

Not a scientist, happy to be proven wrong here, but that’s my gut.

Are you seeing a family doctor, or a sleep specialist? You want the latter, and a sleep study.

The classes of drugs that might help are imperfect at best, I’d be partial to a benzo before e.g., Ambien or related, given the inherent risks of sleepwalking and worse with those drugs.

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.

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.

Have made numerous mockups for devs, as a PM, that way.

When you have one style sheet for users and admins, you get creative.

At the time, building it wasn’t my problem. Explaining what needed to be built was, and the devs in question were not native speakers of same language I was.

Show, not tell, works quite well IFF you recognize immediately when it’s needed.

Copy the thing you want from where it is, paste it where it needs to be, and tweak the (easily recognisable by any human, cmon) verbiage.

I’m not a particularly visual person, so dev tools was quite useful for that. “${foreach} state, ${foreach} county, ${foreach} postal code,” here is the expected UI both expanded and not, beats hell out of trying to spec out what amounts to the better part of an RFC, especially when I am not the one actually writing the code and also not the one who came up with the straight up crazy schema.

Schema created years ago, and there’s only money to add this UI to replace an UPDATE WHERE that the boss decided he didn’t like because he didn’t “get it” and couldn’t personally do it if ever needed (literally no world where it would be needed, and boss didn’t understand the geo that made the whole thing necessary, but…. That’s life.)

(Edit: created, not ‘creates’, and FreeMarker is brutal. Things that binary work/do not work belong in code, not templates. Templates should be as tolerant as is sane given a use case. Boss wouldn’t know HTML or a variable if I whacked him over the head with a variable (length walking staff))

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.

Some of this - and I speak exclusively from a layman standpoint of having worked extensively with quite a few Indian colleagues - has to do with whether an education system (or culture) prioritizes rote memorization vs critical thinking. India tends towards the former, the West mostly tends towards the latter.

Much simpler to persist the practice across many years when the majority of folks are explicitly taught to accept what they are told and not to actually consider it.

Context, I’m an American working for a large public company whose execs appear to have actually realized they got too aggressive with offshoring in recent years and are actually reversing the practice to a relatively sensible degree.

There is shareholder value in workers who come from e.g., a caste system, but there is also a significant risk to shareholder value when too many levels of decision-making are sent to places where that mindset is common.

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.

I realized in fairly early adulthood that I have traits that would have gotten me an Asperger’s diagnosis pre DSM changes so I relate.

Spent years making quarterly trips from outside Indy to upstate NY - somehow the boss thought it was good for morale or something.

What it was good for was reminding me how much I disliked that individual as a human being in general, and why I needed to GTFO there.

Appreciate you pointing out those examples - while one could argue errors in judgement, going with what one knows allows for getting stuff done NOW.

Have to say, FB and G examples resonate most with me because while Java is hardly “rapid,” given a well-defined objective I can bang out PHP or Python to accomplish it quickly, and then iterate efficiently.

That was doable long before the idea of iterating quickly / failing big / etc entered the public consciousness. Just not in Java…

Nailed it. Debt paid down in your twenties is gone.

Debt you barely service until your forties…. Never goes away.

Are they based out of the PNW? Now that I think about it, I may actually have interviewed with them at one point.

ETA: Yeah, pretty sure it was them, they’re PT and have a 425 DID for sales, and the company name is wholly unrelated to the product. Had forgotten about them entirely, and would have had the same reaction as OP to getting that email now.

And it probably is the sw product the email was referencing, since Bartender is capitalized.

Boxes that physically live in my home are mostly Manjaro. They’re also not externally accessible from the internet.

Anything in the cloud I standardize on Debian. Two distros and consistency makes maintenance much easier.

Anything in a container runs whatever it was built on because porting a docker compose file from, say, Alpine to anything else is just not worth the time and energy.

Yes. Both.

Also not a medic, but always understood alcohol to be a blood thinner. Not the cause of it’s direct negative effects afaik but would seem to explain difference in bruising while drunk vs sober.

ETA: one of the things I miss from the other site is the chance to ask (claimed) actual doctors and lawyers hypo questions. And pharmacists. Not bc I want advice but bc once I form a proper question, i genuinely want an answer. Sure, I can navigate pubmed and LII at a lay level, but that doesn’t mean I can efficiently translate question into query with the correct verbiage to get useful and valid results - much less definitively and efficiently parse the meaningful bits of journal articles and disregard the rest.

That expertise in sussing out the actual meat of both question and answer was damned useful, damned interesting, and not practical to acquire as a working professional in an unrelated field.