I’ll note down the key ideas of “The Design of Everyday things” as I read them. And my own views of them.
The new supersedes the old at a frenetic pace: desktop PCs rendered typewriters obsolete, BlackBerries were routed by IPhones etc.
I caught sight of a Github action which publishes and tags Ruby gems. It (hopefully) makes upgrading a little easier/more efficient. It’s one less thing maintainers need to worry about when managing a ruby gem.
We had a talent acquisition and retention problem. Here’s how we solved it:
The following is a summary of “Secrets of Consulting” by Gerald Weinberg - here is the LeanPub link or you can purchase it on Amazon, interspersed with my own thoughts and experiences. This post details the genesis of that purchase.
I had a crack at consulting yesterday. As I was randomly cruising Air Tasker - admittedly not the best place - I saw a posting I had expertise in: AWS Costing. Perhaps it would be a fun little job for me. I wouldn’t mind the occassional consulting here and there. But the problem is that you have to deal with people.
I’ve been using Elm in production for 1-2 years now. Love it. Advantages?
This is an attempt to explain AWS IAM principles. Why do we need this? I felt that the AWS Documentation was a little too complex and formal, and unhelpful to tyros who simply want to understand the basic concepts, quickly. We will start by assuming nothing, and use analogies to explain concepts. Any questions: please post a comment and I will very quickly respond with pull requests.
What is the problem?
Warning: this article uses terms of art that may not be comprehensible to the lay man - I depart from my usual policy of explaining everything simply - so I beg the reader’s patience.