Thread by @patio11

15 years of being a professional software engineer: can *almost* publish static HTML to my blog with the same likelihood as HTTP 200 that I had when doing my Warcraft 2 fan site in middle school on AOL.

*Almost.* (Freaking toolchains.)

How do folks learning now survive?!

I'm trying to think how I would explain this process to a newer professional:

"So what was the problem?"
"OK so I named a new type of content for the site with numbers."
"OK."
"And that worked with Jekyll."
"OK."
"So I deployed."
"OK."
"And everything broke because Nginx."
"Wat"

"Yeah that sometimes happens."
"So what did you do?"
"Oh I changed the template for my configuration file to add a regular expression specifying try_files for a particular subdirectory and then rebooted the server. You know, as one does."
"And that worked?"
"Not the first time."

"What happened the first time?"
"Well the files that were 404ing started 200ing but the files which were 200ing started 500ing."
"That means?"
"That's bad."
"OK."
"So I tried another thing and it fixed that but it broke the HTTP version of my site because of a tooling issue."

"The HTTP version?"
"Yes; the insecure one."
"You have an insecure one."
"Yes good you're paying attention."
"Why do you have an insecure one?"
"To point people to the secure one."
"Can you not have that?"
"Well theoretically if you set the right headers but SEO concerns mean..."