utility classes are just a small step away from style attributes

por_que_no_los_dos.meme

files with 10k lines of code

oh my sweet summer child.

I was once charged with maintaining an application with a median line count of 40k. The largest file was 87kLOC with 2nd place going to a 69kLOC (nice) file filled with interwoven C and inline assembly. My favorite was a 51kLOC file with a 32,621 line function.

Miracle I didn’t develop alcoholism during that job.

unless they’re bacon biscuits

• Decides effectively on a whim to use a Python web framework not designed for async.
• Gets frustrated that async patterns are difficult.
• Refuses to switch to framework that’s natively async, deciding instead to rewrite entire codebase in Javascript.
• Writes smug blog post patting themselves on the back.

Definitely. I go through that same nightmare every time I have to onboard some new acquisition whose devops was the startup cfo’s nephew.

You can use the S3 API to interop with basically every major provider. For most core components there are either interop APIs or libraries that translate into provider-native APIs.

It’s 100% doable to build a provider-agnostic stack from the iac all the way up to the application itself.

This is why OpenTofu exists.

Actually there were seven kings prior to the establishment of the republic, at which point they expelled the rulers… a reg-ex if you will.

Also known as “if you ain’t storing cents, you ain’t making sense.”

VScode is certainly a heck of a lot easier to get LSPs working than e.g. vim.

If someone made it actually easy to set up neovim with lsp support that works as well as with vscode, there’d be no reason to give Microsoft any attention at all

Every front-end guide, despite modern HTML/CSS3/ES6+ being completely viable for building an entire web application without dependencies: “first, install npm and npx and npy and npppp2 and then run ‘npz create-huge-boilerplate-folder’. Now go edit arbitrarily_named_file.yaml to add requirements a, b, and banana. Now you can edit path/to/hidden/entrypoint.jsx to return ‘Hello, World!’ and then run ‘npz bloated-dev-http-server’ and navigate to http://127.0.0.1:9001/index to view it! Simple!”

I think the issue is that you need to understand who your users actually are. Documentation for a library intended to be used by a reasonably competent software engineer is going to have different requirements vs documentation for a cli utility aimed at Arch btw Linux users vs documentation for a program to help Grandma organize family photos.

If you throw a terminal command at Grandma she’s going to panic and call her grandchild. If you put instructions for extracting a tarball in your library docs the programmer is going to get bored and skip ahead.

Sad. Anyway, here’s an inbread cat.

This is fantastic.

That last one is just depraved.

No, sound-activated lamp switches in East Asia!

That’s not entirely true for a sufficiently large black hole. It’s possible to cross the event horizon before tidal forces are strong enough to cause problems. You’ll definitely be ripped apart eventually, but you’d at least be able to see the inside before you become atomic spaghet.

Well she is every woman…

//what the fuck?