UserIsUnused

I see thanks

Abandon is different from deleting everything.

Ofc, git is distributed, so someone should have a copy of the repo, even if it's not updated.

Edit: disregard post, apparently it's just moved to the personal account.

But you see, it's because of the environment that that it's not as economical viable.

Green sources are becoming more and more cost effective because of lots of tax money went into them because people care about the environment.

Eventually there shall be plenty of more green alternatives that are more economically interesting than coal, but they only reached that place in refinement because environmental focused measures took place.

problem is color.

An e-ink is enough to program on emacs all day, but color highlights is a missing feature.

Maybe when patents expire, the tech will improve faster allowing for acessible color ones.

>increases your odds of success,

Exactly. Odds.

Both Fortune and misfortune can happen in the middle. This doesn't mean to stop practicing/learning/improving, it's just life. Be aware of these things, and look for opportunities. Also, remenber that because of this, some very skillful person might be underperforming just because of a bad day, be nice to them.

Thanks!

Is there a non-paywalled version of [1] ?

Ofc CEO sending messages at bad hours to workers and denying vacation times is nothing.

What a work culture.

you should always do regular checkups. New years is a good reminder that you haven't got your check-up this year.

Things like pipeline definitions and helm charts are generators.

but swarm mode is now part of "regular docker"

There are declarative general purpose programing languages.

That data you are talking about does need to be debugged, like Helm charts and pipeline definitions. Sure data is better, but config is code, not data.

Tooling. Data transformation. Libraries.

Emacs is configured using Lisp. Because of that it is amazingly configurable. XMonad uses Haskell, which gives types to avoid lots of error cases.

The thing is providing an actually programming language doesn't remove anything specially if the same config can be written as cleanly.

And you would avoid "YAML templates for creating YAML", when you actually need to process some data (even if it's just for pre/suffix creation in names). Secrets retrieval is another thing that you also need to do and template.

Also, YAML is a terrible to parse language, with can give out weird error cases. Other languages compilers/interpreters are more mature.

And ofc, if you provide SDKs for your IaC tool, you should be able to use the language that your developers are more familiar with. Taking advantage of the good practices their are used to. Don't limit with "declarative languages". Use a programing language that make more sense, and leave data languages for data.

There are plenty of declarative programming language families. Lisps, MLs, SQLs. Configuration is code. Use a programming language.

Thank god trends like Pulumi and the new AWS sdk is emerging.

General purpose programing languages are getting more expressive by the day, why do we use data serialization languages instead for configs? it doesn't make any sense.

Configuration is code not data.