For my next make vs buy decision, a simple structure risk, value, cost by Will Larson.
Super apps may enjoy a distinct advantage in markets with the following characteristics: cost-conscious consumers with low but growing purchasing power, high relative costs of internet data, relatively recent adoption of smartphones, and ‘mobile-first’ leapfrogging of the PC era.
Interesting analysis into how and why, after first appearing in Chinas and India with WeChat and Gojek, the Super App pattern - with one app as an ecosystem, instead of an ecosystem of apps like in “the West” - seems to repeat in other emerging markets across Asia and Africa.
What a gem! The reasoning and mechanics behind building an authentication system (Kerberos) in this case.
Athena: Well I’ve figured out how to secure an open network environment so that unscrupulous folks like you cannot use network services in other people’s names.
Euripides: Is that so? Have a seat.
If ever I find an excuse to dabble more in big stashes of log files: awk in 20 minutes.
What better way to learn about systems then by attempting to break (into) them?
Best quote and Twitter thread on “artificial intelligence” so far:
Our field isn’t quite “artificial intelligence” – it’s “cognitive automation”: the encoding and operationalization of human-generated abstractions / behaviors / skills. The “intelligence” label is a category error
– François Chollet / @fchollet
Amazing episode of the changelog podcast interviewing Dave Thomas and Andy Hunt about the 20th anniversary edition of The Pragmatic Programmer.
Amazing how much you can with that little code. A (simple) 3d racer in mere 2kb of code by killed by a pixel.
Great step by step guide through the basics of web auth. From this awesome mini-series about auth on the web by Andrew Best.
Fascinating write up how the Gitlab team avoided a major outage. Featuring expired certificates, high level tools falling short and some good old server admin skills. Loving the depth and detail!
Sweet walkthrough of database models and their evolution: From flat-file, hierarchical, network, relational, noSQL, document, graph, column family to time series and back to NewSQL again: Prisma.io comparing database types.
Despite connections getting faster and faster and devices getting stronger and stronger, it appears the web is becoming slower and slower. As sites, apps, media and ads (especially ads) grow ever more ambitious, ever more featureful and sluggishly optimized, browsing turns to an exercise similar to commuting in the midst of rush hour stop-and-go, with every click bringing the browser to a gruding halt. Jake Archibald found a nice angle on the irony behind this, by measuring and analyzing page speeds of Formula 1 racing teams websites.
Amazingly detailled look behind the scences of a simple web request: How the web works. Great intro for total beginners and great refresher for those in the know.
Do you need this to: a) Scale, b) deploy, c) rapidly evolve or d) fail independently? Do you need to use e) non-standard technology? Or should this serve as f) façade? Then a microservice might be tge right pattern, else, maybe a monolith would serve you better. Should that be a microservice? great checklist and insights over @ Pivotal
There is clickbait and 10-books-about-bla-you-must-read and then there is this awesome collection of cheatsheets, one-liners and tools.
Some interesting thoughts on early vs late stage projects and pre-mature optimization vs technical debt.
Great primer on microservice architecture basics by Sumit Maingi. Basic problems you’ll encounter and common solutions. Getting these right will already take you a long way.
Why some bullshit jobs are safer than others, or: Every API needs an interpreter from time to time. Click 1 for help.