Olap

Pandas. Python's only killer library imo

Kings decide to come out of hiding, and come out at the same time holding hands and rainbow flags

https://github.com/bash-lsp/bash-language-server

• pretty much all editors support LSP these days

Yes, Tories are the baddies

WhoBird

AntennaPod for podcast travels

The question is: how high have you doubled already? Bet we smash it!

Almost like relying on wireless connections is a recipe for disaster for longevity of any tech. We can't build anything any more to last more than a decade

The jack connector has a really long history, back to the telegraph. The simplicity, the dependability, the interoperability, the lack of it falling out, or needing magnets, or who knows means it will be very tough to replace. And it has evolved too, it used to be a ball end, they have switched sizes, added channels

https://en.m.wikipedia.org/wiki/Phone_connector_(audio)

When does systemd stop? Linux without it is increasingly looking unlikely in the future. Are we not worried about it being a single point of failure and attack vector?

This isn't a moan about the unix philosophy btw, but a genuine curiosity about how we split responsibilities in todays linux environment.

why do you recommend other tools over things which are tested and will last way longer than whatever the current fad is? The best part of Jenkins is it's ubiquitousness - writing code that will run forever is not to be sniffed at

You know what's a hard pill to swallow for Jenkins haters? It's likely older than your career, and is going to outlive you too. Like bash, and C, and gnu-utils.

Want to appear godlike in any org? Learn a tiny amount of groovy and read the pipelines pages - https://www.jenkins.io/doc/book/pipeline/

Jenkins is battle tested, Jenkins is likely already in your org, and replacing it for anything else is almost not worth the time from a strategic perspective. But it isn't perfect, testing it in particular - a pain in the ass

So here's the best tip: skinny Jenkinsfiles. When you use a sh: have it run a Makefile command, or your build tool command. Keep them short single line things. Don't rely on massive ENVs. Dockerfiles for most stuff. Dynamic container agents in the cloud are actually good. Learn to use archiveArtifact, integrate with test report plugins. Learn about parallel pipelines.

Archer returns!