The economics of the gig economy in China mean it is not only possible but seems common to get someone to go to Starbucks and bring you your coffee in the morning.
The store is open, staff are making coffee but I’m the only customer here. Instead there are a steady stream of delivery riders turning up to collect orders.
Beijing’s air quality has been a frequent topic of conversation since I’ve been here and so I built myself a simple air quality indicator.
In building this, it surprised me was how quickly we adjust our definitions of normal. When freak events become regular occurrences they no longer stand out whatever colour we make them.
For all my work with ops, alerts and dashboards I’m not sure why this surprised me as much as it did.
Company (Google) Tried to Patent My Work After a Job Interview https://patentpandas.org/stories/company-patented-my-idea
This prompted me to loook up the origins of the phrase “Siamese twins”. Whilst I can see the connection with the picture, I had no idea that it can actually be used to refer to word pairs:
* milk and honey
* short and sweet
* fight or flight
“Before Twitter, before algorithmic timelines filtered our reality for us, before surveillance capitalism, there was RSS: Really Simple Syndication … As we move away from the centralised web to the peer web, it’s time to rediscover, re-embrace, and reclaim RSS.”
Pencilled in to give my first ever talk at a #GoLang meet-up. The theme... learning.
I'd love to hear your experiences: What helped you learn Go? What really got in the way? But above all, what projects did you invent just so that you could try things out?
I really like the sound of #SustainOSS. I don’t consider myself a project maintainer or a qualified contributor yet, but have a year to change that.
Thanks for the great write-up @firstname.lastname@example.org.
It is not often I look at a snippet of code and marvel at it's simplicity. Curiosity led me to poke at the `sync.Once` type from the #GoLang standard library. Love it!
I'm not sure why I expect complexity, magic and wizardry from the standard library. It's reassuring to learn it isn't all a dark art.
Federation Update: We have pushed most of the code, and will be making an announcement in the next few days. #pixelfed
Dynamic DNS providers seem to have fallen by the wayside recently, either shutting down completely or competing to generate the most unwanted email. So I over-engineered a solution:
- Goggle App Engine service to give me external IP
- Go client to update Route53 hosted DNS when IP changes
- Packaged in a Docker container
- Deployed on Kubernetes
- Running on a Raspberry Pi cluster
There are a few tweaks to make mostly logging/metrics, but it seems to be working well so far.
Am curious as to how others handle the issue of sensitive data leaking into logs? When I faced this, there were three strong opinions:
1. Good developers don’t leak sensitive data - improve dev
2. Ops requires everything - secure access to the logs
3. Filter before indexing - regular expressions to the rescue
I like this side-car approach, but don’t see much open discussion on mitigating sensitive data in logs. Are we pretending this is a non-issue?
The tech drove me to management, the management drove me to tech. Forever learning. Always up for a conversation.
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!