A few years ago, I took ownership of the middleware code-as-config service that defined our app’s API. It could only be modified inline. The first thing we did was add the ability to pull from a git repo. You could pull from any branch, except Production could only pull from a specific branch. Source control. Code review. Magical stuff. Come on AWS.

It’s 2018, and this is still how AWS thinks I should manage the source code for my lambda functions.
This makes me so mad.

2018 and this is still how AWS thinks I should manage the source code for my lambda functions.
This makes me so mad.

  • Private slack channels are better. They create a safe space and encourage open communication within the team
  • Public slack channels are better. They ensure conversation is had in the open, thereby ensuring open communication across the broader team.
    Which is it?
  • Private slack channels are better. They create a safe space and encourage open communication within the team
  • Public slack channels are better. They ensure conversation is had in the open, thereby ensuring open communication across the broader team.
    Which is it?

Outsourcing would be fine if you could ever actually outsource the delivery risk, but you never can.

https://www.smh.com.au/national/nsw/1b-compo-payment-limits-government-s-options-in-light-rail-stoush-20180412-p4z966.html

Is there a way for the iOS micro.blog app to not post square-cropped images?
/cc @manton