Automatically generate R package skeletons from application programming interfaces (APIs) that follow the OpenAPI Specification (OAS). The skeletons implement best practices to streamline package development.
The Web API Checklist -- 43 Things To Think About When Designing, Testing, and Releasing your API
When you’re designing, testing, or releasing a new Web API, you’re building a new system on top of an existing complex and sophisticated system. At a minimum, you’re building upon HTTP, which is built upon TCP/IP, which is built upon a series of tubes. You’re also building upon a web...
Learn how to design REST APIs to be easy to understand for anyone, future-proof, secure, and fast since they serve data to clients that may be confidential.
How do you use API specifications and standards, such as OpenAPI and JSON Schema?
Learn how to use OpenAPI and JSON Schema, two popular standards for describing and validating RESTful APIs and JSON data, in this article for back-end web developers.
Parkinson's law: why you waste time and how to avoid it
Have you ever heard of the word spuddle? It’s the verb from the 17th century that means to work ineffectively, to be extremely busy whilst achieving absolutely nothing.
If you’ve been spuddling these days, you may be a victim of Parkinson’s law. Don’t worry if that’s the case, we have a solution
This page shows how to configure liveness, readiness and startup probes for containers. The kubelet uses liveness probes to know when to restart a container. For example, liveness probes could catch a deadlock, where an application is running, but unable to make progress. Restarting a container in such a state can help to make the application more available despite bugs. A common pattern for liveness probes is to use the same low-cost HTTP endpoint as for readiness probes, but with a higher failureThreshold.
A book about engineering shiny application that will later be sent to production. This book cover project management, structuring your project, building a solid testing suite, and optimizing your codebase. We describe in this book a specific workflow: design, prototype, build, strengthen and deploy.
Efficient R Programming is about increasing the amount of work you can do with R in a given amount of time. It’s about both computational and programmer efficiency.
rOpenSci Packages: Development, Maintenance, and Peer Review
Extended version of the rOpenSci packaging guide. This book is a guide for authors, maintainers, reviewers and editors of rOpenSci. The first section of the book contains our guidelines for creating and testing R packages. The second section is dedicated to rOpenSci’s software peer review process: what it is, our policies, and specific guides for authors, editors and reviewers throughout the process. The third and last section features our best practice for nurturing your package once it has been onboarded: how to collaborate with other developers, how to document releases, how to promote your package and how to leverage GitHub as a development platform. The third section also features a chapter for anyone wishing to start contributing to rOpenSci packages.