I love grammars. It’s like an API or a data schema, but for a language. This would be very cool and I would love to see it!

Devops is a meaningful term

You’re out here solving impossible problems. You’re “The Fixer” from Pulp Fiction. Fools look at story points. Pros see an unsolvable story that languished for years until you came along and defeated it. A single point for you is an entire epic to other teams.

Everything is a differentiator that can be spun to your advantage. The points aren’t accurate, and you’re the only one with enough guts to step up to the plate and finally work these neglected tickets; even if it won’t “look good” on some “dashboard” - that’s not what’s important; you’re here to help the organization succeed.

If the system doesn’t make you look good, you have to make yourself look good. If you weren’t putting in the effort, it would be hard - but as you say, everyone who takes a deeper look clearly sees the odds stacked against you, and how hard you’re working / the progress you’re making; despite those odds.

Don’t let some metrics dashboard decide your worth, king!

I’m very flaky here, as rust is the big one, but I think zig and/or nim might be

Vscode already supports linting yaml against a schema file. Once you start configuring your code with configuration-as-code, you’re just writing more code.

If I need to “generate” some insane config with miles of boilerplate, I would use js to build my json, which can be ported to just about anything. This would replace js in that process.

I’m not sold on the need for this.

Even with something like k8s, I’d reach for pulumi before I put another layer on top of yaml.

JavaScript / TypeScript are famously free-form, but a number of styles (and style-enforcing tools) have emerged.

“Prettier” is the most recent. It actually parses your code into an AST and then re-prints it according to its style.

“ESLint” is the most widespread; it is more of a framework into which rules can be plugged.

I use “XO”, which is essentially a custom eslint ruleset with a few other nice things tacked on.

The best part of eslint/xo is the “—fix” command, which can auto-fix most mistakes.

This is pretty huge. Rust support is one of Pulumi’s most requested features. Hopefully azure follows suit.

I’m here to throw Inconsolata into the mix, though I use Fira more frequently now from a compatibility perspective.

Of course!

In other words though, for those just starting their monad journey:

An endofunctor is a box. If you have a box of soup, and a function to turn soup into nuts, you can probably turn the box of soup into a box of nuts. You don’t have to write a new function for this, if the box can take your existing function and “apply” it to its contents.

Arrays are endofunctors, because they hold things, and you can use Array.map to turn an array of X into an array of Y.

Monoids are things you can add together. Integer plus integer equals integer, so ints are monoids. String plus string (concatenation) equals a longer string, so strings are monoids. Grocery lists are monoids.

Arrays are monoids!

Arrays are both endofunctors and monoids, so for everyone except category theory purists, they are monads.

Javascript promises hold things, and you can transform their contents with .then - so they are endofunctors. You can “add them together” with Promise.all (returning a new promise), so they are monoids. They are both monoids and endofunctors, so they are monads.

I’ve just upset all the category theorists, but in the context of programming, that’s all it is. It’s surprisingly simple once you get it, it’s just complicated names for simple features.