Apiary Releases ‘World'S First’ Automated Api Ci Testing Service - The New Stack

Industrial API Model

This reflects Tung’s model which found that in the enterprise, API maturity often begins with an individual use case for an application or workflow which leads to the creation of a specific API within that use case department. But then, over the next six months or so, other parts of the enterprise take similar approaches to pilot projects quickly leading to a chaotic catalog of APIs that have been use-case built without a long term, industrial mindset for the agency’s broader needs. Accenture’s Industrial API model suggests that after the first couple of use cases demonstrate the power and efficacy of APIs, that future design be built using internal standards so that there is common nomenclature and endpoint descriptions for APIs, and that opening data sources and functionality via API is thought of in terms of wider potential uses rather than just a single use case.

We see this time and time again with our large enterprise clients. They either have one of two things. Hundreds of smaller APIs and services, with heavy overlap of functionality. "If you need this type of data, hit endpoint X, but if you need this one other enrichment field, hit this other endpoint. But that one isn't updated as frequently, so you really need to hit both, and do a merge or something on your end". There were a number of small teams, who needed data or a process, but didn't want to get tied up in a larger department initiative, and be tied to another teams timeline. So, they built their own to very specific use cases

The other case we see a lot, is a large company trying to unify all of their APIs and data, but going about it in the wrong way. They are tying all the systems to a large initiate and building a god system. A project like this usually spans years, and by the time you get to the end of it, the earlier changes are already out of date.

Part of the work we do with clients like this is to get the teams to agree on a unified API language first, then start converting different systems one by one. As we identify overlap, we will role those systems together. That transformation or merging should be transparent to anything consuming from those systems.

We do this for a number of reasons. First and foremost is so we can get user facing changed out faster. Get the new site, or tool public so we can begin testing it against real users. Then, if we need to make UI changes, we aren't locked down to a back office system. That is all behind an API that we helped define, and can assume won't change for a while. We can iterate faster, while the back office systems continue on their slower timelines

The Drupal 8 Admin Menu Needs a Fix

I initially wanted to lead with something like “The Drupal 8 Admin Menu Sucks,” but I remember repeated corrections by one my engineering professors that things don’t suck only blow inwardly.

I pulled in the WordPress top and left admin menus to a Drupal 8 module and named it WordPress Menu.

Nice. Check it out here

How Relay Fm Proves That Podcasts Aren’T An Overnight Success

Just a year later, Relay FM features 16 different shows and delivers 1.5 million episodes every month.

A huge congrats to Myke and Stephen. I listen to a lot of the shows on Relay and couldn't be more impressed or happier with the content the network puts out

While the number of shows has tripled during Relay FM’s first year, monthly revenue has quadrupled over the same period.

Surviving Anxiety, Or, How I Re-Met Adam Culp Today | Remarks

My running is teaching me two things. One is to “push through” – to go beyond a point when I want to give up short of a goal. The other is to pay attention and take a break when I need it lest I end up hurting myself.

​One day I will write about my anxiety. But not yet

I encourage everyone to read Adam’s brief, powerful post. Even if you are not dealing with crushing anxiety, it’s certain that you know someone who is. It’s a terrible thing to experience, and it’s a wonderful thing to be past, though I’m always worried that it’s waiting for me in the wings – one never fully recovers from it, I suspect.

Cushion - From Beta To Launch - The Subdomain

When I started Cushion, I knew I wanted to keep the marketing website and the web app separate. I’ve worked on apps in the past where the marketing site is baked into the app code, so any change—even a typo—required a deploy of the entire app. This approach would make me think twice about updating the marketing site—it turned a simple task into a daunting one. Because of this experience, I deliberately separated the two, hosting the marketing site at the root domain while the app lived on a subdomain

Separation of concerns. This is a good idea. Curious about SEO implications though

Someone suggested get.cushionapp.com when I was looking for subdomain suggestions, but I dismissed it. I’m not a fan of the “get” prefix when you’ve already signed up for the app, but “get” does make sense for the sign up process, though.

At the time, I was also wrapping up the referral system for Cushion. Once I considered get.cushionapp.com, everything became crystal clear. I would use get.cushionapp.com for the sign up page, and the referral links could be get.cushionapp.com/REFERRAL_CODE. Now, the “get” prefix makes sense and reads well, too—“get cushion app”.

I couldn’t be happier with the combination of get.cushionapp.com and my.cushionapp.com. The simplicity and casual feel matches perfectly with the tone I’ve been trying to convey with Cushion. Everything seems to be falling into place, and I’m so relieved to finally be over the hurdle of this transition. Cushion has officially graduated and I’m so excited to see where it goes next.

Things I'Ve Quit Doing At My Desk

In reality, we do all sorts of things at our desks that aren’t real work (or affect our ability to produce our best work).

​We do do a lot at our desks. It's interesting though how much of "work" has spilled onto our other devices. At least during the day I'm in outlook and Omnifocus on my phone. When I have 1:1s with my directs, I bring my iPad with Omnifocus to review goals or notes I've kept track of

Thinking: Nobody does their best thinking sitting at their desk.

I do my best thinking in the shower at home. I've had sooooo many epiphanies over the years in the shower. Either brand new ideas or some problem that may have had me stumped for days.

I think it's the sensory deprivation. There's nothing to distract you, your mind is free to wander, and there is plenty of ambient noise. Sing if it helps!

This doesn't work as well for me in the shower at the gym. I'm usually rushing to let the next people in or to get to work, and the water temperature is usually lukewarm or cold to help me cool down. Anything I can help to do stop my sweating before work.


I think a standing desk hurts me on this regard. I notice that more people come up to me to chit chat than if my desk is down and I'm sitting

When Our Blog Became A Business - $2,000 From One Post

If I lacked passion or expertise I think my wife’s readers would be able to see right through it. Readers are smart; they know when you don’t care, and they know when you don’t know what you’re talking about. Don’t fake it.

​Hmm. Should I try a daddy blog? With nerdery, tech, and productivity?

It’s tough building your thing online.

Gitlab: Almost Everything We Do Will Be Open

Today we’re announcing a move from doing the majority of our development work internally, to almost exclusively working in public issue trackers on GitLab.com. This means that anyone can view and comment on all of our discussion and work. This includes bugs, new features, performance issues and everything else that relates to our products.

Awesome. We use Gitlab for our source control at work and I couldn't be happier to see this.

We were not working in the open as a true open source project should.

Open Sourcing Energy - Artsy Engineering

It’s worth mentioning that we don’t just talk externally about Open Source. Internally, the Mobile team runs talks about Open Source for the rest of the Artsy staff. As well, we discuss the tooling and business implications of having our work in public repos. Artsy strives for an open culture, in this case the development team, on the whole, is just further along in the process.

A great read about Artsy's open source culture