Apache incubation cookbook, a useful blueprint for incubating projects within organisations. https://incubator.apache.org/cookbook/
Exploding Go Module version information to #prometheus: https://povilasv.me/exposing-go-modules-to-prometheus/ #link #golang
"Amazon has submitted a patent application, recently granted, outlining how the company could recommend chicken soup or cough drops to people who use its Echo device if it detects symptoms like coughing and sniffling when they speak to it, according to a report by CNET. It could even suggest a visit to the movies after discerning boredom. Other patents submitted by the company have focused on how it could suggest products to people based on keywords in their conversations."
> Feds Say Hacking DRM to Fix Your Electronics Is Legal
Twitter released a big dataset on state-run disinformation accounts from 2016: https://blog.twitter.com/official/en_us/topics/company/2018/enabling-further-research-of-information-operations-on-twitter.html
Mastodon's 2 Year Anniversary: A retrospective
a canadian apologizing too often
I apologize a lot, out of habit I think, and I've always laughed it off as "haha yeah well Canadians, you know", but it kind of bothers me that I feel compelled to say "sorry" so much. It's compulsive, nearly.
So I heard this trick, to replace apologies with thank-you's. "Sorry I broke the staging server" -> "thanks for being patient while I figure out how to deploy stuff", for example. It's really helped me with that compulsion, and makes me feel better too 🤗
After a brief hiatus I'm back!
Saw something cool in #OpenShift and I just had to sign in to share.
Docker type BuildConfigs add extra steps to your Dockerfile. They add the $OPENSHIFT_BUILD_NAME and $OPENSHIFT_BUILD_NAMESPACE env vars so you can track down the build your container image came from. They also save them as labels (io.openshift.build.name and io.openshift.build.namespace)
Another problem with #ansible is the lack of standardisation for module args/return objects. In the past I needed to constantly print returned variables to figure out how to use their data.
Luckily in the last few years a lot of modules begun documenting their return objects. Some modules even document the facts they set during execution (hurray!)
But I still need to rely heavily on those docs... A major sign of a good API is that (with experience) you can work without constantly referring to the docs.
Ugh... Doing anything non-trivial in #ansible is always a pain.
It's also really hard to pin down my particular frustrations; I have a feeling that the problem is that there's too many examples where magic is used to do practical things in the docs but the magic itself goes unexplained.
May times I've tried to modify examples to do other things and it very quickly falls apart. Then I lose loads of time frantically searching the docs.
In other news, scientist are struggling to find a violin small enough for the occasion.
Geek w/ god complex
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!