Taking a picture of Helen as she is taking a picture of me @ The Hive at Kew Gardens https://www.instagram.com/p/B36125fJFtD/?igshid=bj2fmzqmsl7w
It was a long stairclimb to the top. The Pagota at Kew Gardens @ Kew Gardens https://www.instagram.com/p/B34ab5JpNyU/?igshid=1ldsxo6q8ie5t
Liberty of London @ Liberty of London https://www.instagram.com/p/B32igWvJuUQ/?igshid=pvip47ht3558
10yr ago today I tweeted <suggestion to @Amazon: You know I have a #kindle, have "send sample to kindle" and "buy on kindle now" right under the "buy it now" button>. Sometime since then, they took my advice! ;)
If it doesn't start with an API, one will never be implemented without a full rewrite.
If an API is added later, it will never be complete or correct.
If you define an API and then implement the UI/UX so that it works some other way than calling the API, then neither the UI/UX or the API will be correct or secure.
If a feature can't be defined as a set of API calls, it's not defined enough to implement well.
In honor of the morrow: https://historynewsnetwork.org/article/1493
@email@example.com @firstname.lastname@example.org @email@example.com @firstname.lastname@example.org @email@example.com @firstname.lastname@example.org I'm old enough to remember when Concur was a refreshing change from whatever godawful Oracle thing we used before that.
@email@example.com @firstname.lastname@example.org We should name this the Concur effect.
1) decision makers are not direct users
2) features are overwhelming and disjointed
3) user experience gets worse over time