Evolving Distributed Systems
A discussion on the architectural and communication challenges in distributed systems and microservices, focusing on contracts, APIs, and team dynamics.
A discussion on the architectural and communication challenges in distributed systems and microservices, focusing on contracts, APIs, and team dynamics.
Explores how hypermedia APIs reduce coupling in distributed systems by minimizing client assumptions, using RESTBucks as an example.
Explains how to customize ASP.NET Core's model-binding conventions for API commands, moving beyond default query string binding.
Explains callbacks in Swift 3.0 for iOS development, covering definition, async programming, and API design with practical examples.
Explains Swift callbacks, their purpose, and usage in iOS development with a practical API design example.
A critique of pragmatic Java 8 Optional usage, advocating for a stricter approach than the common library design recommendations.
Explores the design decision behind Java's Optional class not implementing the Serializable interface and the reasoning of its creators.
Explores Java's Optional type as a tool for writing intention-revealing code and avoiding null references, part of a detailed series.
Explores the critical importance of URLs for collaboration, institutional knowledge, and transparency, especially in tech and government contexts.
A follow-up discussion on Swift type inference, emphasizing clear naming and predictable return types for code clarity.
Expanded thoughts on Swift's type inference for clean coding, emphasizing making return types unambiguous.
A guide to implementing a custom Observable property wrapper in Swift, covering API design, type conversion, and current language limitations.
A developer lists the 7 most common code quality issues found during code reviews, focusing on maintainability and best practices.
Explores a Go design pattern using self-referential functions to create a clean, extensible API for setting and managing options on a type.
Analyzes why government open data initiatives fail due to poor API design and documentation that ignores developer needs.
A guide to designing clean, well-structured RESTful APIs, covering naming conventions, HTTP methods, versioning, and best practices.
Discusses the internet's pragmatic ethos and why using GitHub for large datasets requires rethinking desktop paradigms for web-native, granular data delivery.
A guide on using assertions in code for debugging, API contracts, and server integration, with strategies for handling release builds.
An open letter advising government CIOs to adopt lean, iterative, decentralized, and open development practices for better tech outcomes.
A summary of the OpenStack Havana Design Summit, focusing on the Ceilometer project's discussions, new features, and roadmap.