For almost four years I have been sending out a weekly newsletter with things I learnt and read during the week. Some of those trivia are not trivial at all, so I decided to share the condensed crème de la crème of the Internet in this New Year special edition.
For almost two years I have been sending out a weekly newsletter with things I learnt and read during the week. Some of those trivia are not trivial at all, so I decided to share the condensed crème de la crème of the Internet in this New Year special edition.
For the past six months I have been sending out a weekly newsletter with things I learnt and read during the week. Some of those trivia are not trivial at all, so I decided to share the condensed crème de la crème of the Internet in this New Year special edition.
By the end of this post we will build a Github Actions workflow to detect broken localisation keys in iOS projects; however this can be easily adapted to other cloud platforms (Travis, CircleCI, etc) and projects (Android, React, etc). Bonus: I will show how to quikly test that localisation files themselves are properly formatted or exist.
This year I sent out quite a few proposals to the majority of mobile conferences in Europe. Some ignored me, the others replied with automated rejections. However, some accepted and it was fun. Here is what I've learned on the way.
Apple recently started to enforce 2FA for account holders and preventing uploading builds without 2FA. However, managing SMS codes is pretty hard when it comes to CI pipelines, so I've decided to share a few approaches I tried to overcome this inconvenience.
Since I moved my Wordpress- and Medium-based blogs to this standalone platform, compiled by Eleventy and deployed by Netlify, I was wondering whether there is a way to persist original Markdown formatting even if someone copies the prerendered text from the browser. Initially I was considering two approaches...