tedepstein

CEO of @RepreZen_API. Seeking and occasionally finding profound insights into API design & Microservices @ Like2Code, but Live2Model.

[tedepstein @tedepstein]

@CillizzaCNN Cilia

[tedepstein @tedepstein]

@WindyRoadTech @samnewman Once a term gets appropriated by vendors, overloaded, overhyped, over-promised, under-fulfilled, and exploited as a meaningless marketecture buzzword, it takes on such negative connotations that nobody wants to be associated with it anymore.

[tedepstein @tedepstein]

@DeniseA42265011 @walterdellinger @matthewamiller It only matters if you take the position that Trump should have gotten away with his crimes, that American voters & congress didn't deserve to know, and the truth of this whole scheme could've been kept secret if it weren't for this one person. Really???

[tedepstein @tedepstein]

@JohnKingCNN What's the point? You want to scrutinize the whistleblower's motives? Background? The process of filing the complaint? Those things have zero legitimate bearing on the trial, but they have enormous potential for distraction, deflection, scapegoating, and worse.

[tedepstein @tedepstein]

@JohnKingCNN The whistleblower is NOT the initial source of this scandal, Donald Trump is. You don't blame the camel's broken back on the last straw. And there's nothing particularly interesting about the raindrop that started the avalanche.

[tedepstein @tedepstein]

A big step forward for @OpenAPISpec and @JSONSchema!

[Phil Sturgeon @philsturgeon]

WE DID IT!!! @OpenApiSpec v3.1's Schema Object will now be proper JSON Schema. Amazing work everyone. This took about a year(!!), and there was much whooping on the call. Thanks to @darrel_miller @webron @tedepstein Henry Andrews and many others. https://t.co/cX2GOnPbMj

[tedepstein @tedepstein]

@philsturgeon @darrel_miller @PermittedSoc @OpenApiSpec For anyone who had questions about #nullable, or anyone worried about what the change means to your @OpenAPISpec tool implementation, here's the full background. We think this clarification is helpful and non-breaking. Any concerns, please comment! https://t.co/FlO0B1gz5f

[tedepstein @tedepstein]

Still working on the plan to fully integrate #JSONSchema into @OpenAPISpec, but we have cleared some of major hurdles. Great work, everyone! https://t.co/MydRp90VKu

[Phil Sturgeon @philsturgeon]

I would like to thank @darrel_miller, @PermittedSoc, @tedepstein, Henry Andrews and everyone else at @OpenApiSpec for the hundreds of man hours that went into getting this tweak made in OAS3. https://t.co/3MKNnEigJx

Clears the way for JSON Schema! 😍 https://t.co/cX2GOo6MDR

[tedepstein @tedepstein]

‘Nothing Sexier Than An #API’ by fuzzleonard on #SoundCloud. #np https://t.co/R15ghKmqJl

[James Higginbotham @launchany]

My #gluecon slides for "Beyond REST - Moving to Event-Based APIs and Streaming" are now available: https://t.co/iWVWQp1RTx

[tedepstein @tedepstein]

@inadarei I'm duty-bound to point out that OpenAPI, as a matter of policy, doesn't create or endorse "reference implementations." OK, not duty-bound, I just wanted to say that.

[tedepstein @tedepstein]

The seven make-or-break API challenges CIOs need to address - @McKinsey on metrics, team organization, & other key success factors for #enterprise #API programs. https://t.co/i8L2wK3RUE

[API Handyman @apihandyman]

Reading a post which basically says "... we were struggling to build consistent REST APIs across our organisation so we switched to gRPC ...". Sorry but no, changing technology will not solve such governance problems.

[OpenAPI Generator @oas_generator]

Happy New Year! #OpenAPI #Generator 4.0.0-beta is the last release in 2018: https://t.co/VZkjCQ9dA7. Look forward to more generators, more contributions from the awesome #developer community in 2019 🎊🎉🎊🎉

[tedepstein @tedepstein]

@PermittedSoc @whitlockjc @lindybrandon @darrel_miller @earth2marsh @usarid @matthewtrask @emckean @taylor_atx @developerjack @RomanHotsiy @webron Chapter 8: Stupid Schema Tricks. Subtitle: Ron & Ted’s Bogus Journey

[tedepstein @tedepstein]

@PermittedSoc @whitlockjc @webron @darrel_miller @lindybrandon @earth2marsh @usarid @matthewtrask @emckean @taylor_atx @developerjack @RomanHotsiy I volunteer to make everything complicated.

[OpenAPI Specification @OpenApiSpec]

Thank you to the @OpenApiSpec community and our fantastic roster of supporting members for 3 years in #opensource! https://t.co/ElqEXL5U7C …. Share your favorite #OASv3 implementation in the comments!

[API Handyman @apihandyman]

Panel discussion on the future of the @OpenApiSpec with (from right to left) @isamauny , @tedepstein , @webron and @manp #apistrat

[tedepstein @tedepstein]

@hibaymj @apihandyman I'm assuming that these commits happen before deployment, so review can catch accidental or detrimental API changes. Is this about 2 truths, or is it about the 1 truth being prone to change without immediate visibility, therefore hard to ascertain at development time?