While working on a client's app's CI pipeline, I needed to use an API key. However, it was stored as a base64 environment variable, when the tool I needed to use required it to be plaintext in a JSON file. Fun times.
I've heard quite a few times that we, as a species, are terrible, destroying the Earth, ourselves, and that we are, all in all, the worse. That's assuming a lot. First and foremost, that we are as smart and great as we think ourselves to be.
While setting up a new step for a client's CI pipeline on a macOS agent, I needed to export an API key containing line breaks to a JSON file. Meaning I had to escape line breaks, in bash, on macOS. Turns out, it's not as easy as it sounds. Who would've guessed?
We needed an OpenCV Contrib module in an iOS app, using Swift Package Manager. I thought the hardest part would be using OpenCV. How wrong I was.
With remote work on the rise, I've seen people debating the fairness of companies adjusting pay based on one's location and cost of living. As if there ever was an intrinsic justification to compensation. Spoiler: there isn't.
Once you have tasted SwiftUI, this kind of UIKit lacking makes you wish you could refactor a client's whole codebase at a snap from your fingers. At least the UI side of it. But, alas, there is no magic spell for that. Yet. What kind of lacking? UITextView doesn't have
Recently, a client told me that the code I had written to sync their systems and a new datasource blew up their AWS EC2 instances. Apparently, the synchronisation engine kept getting killed for using up too much memory. More than a few gigabytes, actually. To sync a few tens of