<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://ebastien.name/</id><title>Emmanuel Bastien</title><subtitle>The personal blog of Emmanuel Bastien, writing about software engineering, architecture and API design.</subtitle> <updated>2023-11-22T14:17:21+01:00</updated> <author> <name>Emmanuel Bastien</name> <uri>https://ebastien.name/</uri> </author><link rel="self" type="application/atom+xml" href="https://ebastien.name/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://ebastien.name/"/> <generator uri="https://jekyllrb.com/" version="4.3.2">Jekyll</generator> <rights> © 2023 Emmanuel Bastien </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Enterprise integration and the API-first cargo cult</title><link href="https://ebastien.name/posts/enterprise-integration/" rel="alternate" type="text/html" title="Enterprise integration and the API-first cargo cult" /><published>2023-11-22T00:00:00+01:00</published> <updated>2023-11-22T00:00:00+01:00</updated> <id>https://ebastien.name/posts/enterprise-integration/</id> <content src="https://ebastien.name/posts/enterprise-integration/" /> <author> <name>Emmanuel Bastien</name> </author> <category term="api" /> <summary> A lot has been written on the potential of a sound API strategy in the enterprise. APIs are everywhere, and even in the enterprise, the so-called API-first approach is getting traction. IT departments are waving the benefits of reuse and investing in enterprise architectures to support API cataloging, gateways and release management. Many companies are doing the right things, but we also see s... </summary> </entry> <entry><title>Parsing a programming language in Rust</title><link href="https://ebastien.name/posts/parsing-in-rust/" rel="alternate" type="text/html" title="Parsing a programming language in Rust" /><published>2023-10-12T00:00:00+02:00</published> <updated>2023-10-12T16:53:51+02:00</updated> <id>https://ebastien.name/posts/parsing-in-rust/</id> <content src="https://ebastien.name/posts/parsing-in-rust/" /> <author> <name>Emmanuel Bastien</name> </author> <category term="programming" /> <summary> I recently rewrote the parsing stage of Oxlip. As a matter of fact, it is the third significant refactoring of the parser. I must admit it took me quite some time to land on a solution I feel comfortable with. Even if all the libraries I am discussing here are viable options for parsing programming languages, each one of them had limitations that were not obvious to me at the beginning. My ambi... </summary> </entry> <entry><title>API design first: a case for a better language</title><link href="https://ebastien.name/posts/api-design-language/" rel="alternate" type="text/html" title="API design first: a case for a better language" /><published>2023-09-20T00:00:00+02:00</published> <updated>2023-10-26T13:30:06+02:00</updated> <id>https://ebastien.name/posts/api-design-language/</id> <content src="https://ebastien.name/posts/api-design-language/" /> <author> <name>Emmanuel Bastien</name> </author> <category term="api" /> <summary> Building web APIs as products and thinking of digital products as APIs first is a well established practice. API-first makes digital products more versatile by giving control to the end-user. Instead of a rigid graphical user interface, a business offers a programmable interface over its domain. Adopting a product mindset means caring for the goal, journey and experience of the user of the API,... </summary> </entry> </feed>
