Suggestions
Lorna Mitchell
Software leader, developer communications expert, open source maintainer, API/OpenAPI specialist, OpenUK board member
Lorna Mitchell is a prominent figure in the tech community, currently serving as a Technical Steering Committee Member at the OpenAPI Initiative. She has extensive experience in the field of APIs, having worked as an API Evangelist since 2010, where she focuses on the intersection of technology, business, and policy related to APIs. Lorna is known for her ability to provide governance and clear guidance in API development and implementation.12
In addition to her role at the OpenAPI Initiative, Lorna is also recognized for her contributions as a software developer, technical writer, and community manager. She emphasizes building user-friendly experiences through effective communication and has authored various resources that include code samples and real-world examples aimed at helping others navigate API technologies.123
Lorna is active in the tech community, frequently participating in events such as APIDays and FOSDEM, where she shares insights on OpenAPI and engages with other professionals in the field.45
Highlights
We don't talk enough about boring technology. Well-known, established technology that maybe won't make your teams excited but that already has a strong ecosystem, established practices and lots of humans who know it well. What's your favourite under-evangelised "boring technology"?
I'll start: APIs.
Working on OpenAPI Specification itself, I find myself representing in general terms the overall picture of the use cases that I see at work and more widely across the industry. After a few weeks of handwaving and saying "pipelines" a lot, I wrote up a blog post to try to capture the (many, optional) steps I see in a general API description pipeline:
- collect all the ingredients: written, generated or microservices - and combine them into one API description
- sort out the major howlers/gaps
- lint, format, etc
- (breathe)
- filter to a smaller set of endpoints (possibly a few sets)
- add destination-specific metadata for your API gateway, SDK code generator, documentation tool or [insert thing I didn't think of yet]
- bundle the API definitions, and dereference if the tools don't handle $refs well
Read the full post, then tell me what I missed?
