Skip to content

Instantly share code, notes, and snippets.


Ronan Flynn-Curran flynnduism

View GitHub Profile
flynnduism / aws-two-app-fo-life.json
Last active Aug 29, 2015
Multi App Instructions
View aws-two-app-fo-life.json
"id": "two-app-fo-life",
"name": "TWO APPS FO LIFE",
"information": "When one is just not enough!",
"tags": ["aws"],
"configuration": {
"accounts": [
"providers": [
flynnduism / gist:0aaad22001893ea47acf
Last active Aug 29, 2015
Notes on maintenance mode
View gist:0aaad22001893ea47acf

The messaging here is pretty wordy - it would be great if we could include a little bit more info here (with examples) to give a heads up of what this does - showing rather than telling,with some little inline example:



Mainteance mode will direct traffic to your application's maintenance page (at public/maintenance.html), or fallback to use our system default (preview^) if none exists.

flynnduism / gist:2ceeee3a5be59b2f215e
Last active Aug 29, 2015
Johnny Cash - Local Development errors
View gist:2ceeee3a5be59b2f215e
I, [2014-07-17T16:05:15.676107 #76042] INFO -- : Refreshing Gem list
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.0
DEPRECATION WARNING: The Active Record auto explain feature has been removed.
To disable this message remove the `active_record.auto_explain_threshold_in_seconds`
option from the `config/environments/*.rb` config file.
See for more information.
flynnduism /
Last active Aug 29, 2015
Platform updates: naming convention

Part of this YouTrack ticket on UX issues with the current platform updates / platform changelogs:

Release vs Update vs Version

I think it makes sense to talk about new versions of the platform purely as releases (or patch releases) and avoid using the word 'updates' to describe the releases, instead keeping that word to describe the action a user takes to get the releases. An update should be reserved for what you do to a cluster to apply the Engine Yard platform releases.


I think the current copy we have is a bit too indirect / wishy-washy! Ideally these sorts of important instuctional messgaes should be more assertive, but not too formal.


Current instructions:

Unless your git repo is public, you must copy this ssh key to your repo settings, otherwise we won't be able to access the repo to deploy. Managing Deploy Keys on GitHub explains how to do it, just skip Step 1 and use this key:

Rewording proposal:


At the age of 20, I was in my second year of my BSc in Multimedia at DCU in Dublin, Ireland. We were given an assignment in one of our Media Culture classes to invent a meme. I took this very seriously, and made a controversial website depicting one of Ireland's most beloved TV stars (a puppet by the name of Bosco) as a sort of arch-villain.

The site earned me a spot in a national tabloid newspaper, a lot of confused emails from the public and top marks in my class!


commit 368d8f5e40a4ffc47c1333560995833f0845732b

Author flynnduism Date: Mon Oct 20 12:10:43 2014 -0700

Add power off icon, small screen tweaks



Hey Eben, dumping my thoughts on inline snapshot info here.

Server Status

I think if we’re going to show live info on in-progress snapshots, then it should follow the activity state indicator we use for other event types...

flynnduism /
Last active Aug 29, 2015
Product Feedback Form UX

RDS Only Feedback?

The User Story and screenshots are specific to gathering RDS feedback, using a UI based on AWS’s feedback tool. Their tool is consistent across all of AWS’s services, you can launch a feedback window for any part of their product ecosystem.

Implementation Effort

I believe the effort required to implement this feedback form in our product will be increased by requiring it to be limited to only appear in specific views. The UI templates are shared globally across all views, so conditional logic would be required to show and hide the form across different areas of the product.