Explore >> Select a destination
|
You are here 
|
httptoolkit.com | ||
| | | | |
devopsian.net
|
|
| | | | | Discover the value of API-First design for side projects. Learn how this approach can streamline development, improve consistency, and accelerate your workflow through practical examples and code generation. | |
| | | | |
yos.io
|
|
| | | | | You're building an API. You develop a backend service with a few endpoints and deploy it to production. You publish several official language-specific API clients as well as an API documentation. The day ends on a happy note. The following day, a new feature is being added the API. You have to: Update the server implementation to support the new feature. Update all client libraries (one SDK for each supported platform and language.) Update the documentation. All the above must be consistent with each other. Also, the frontend team is blocked until your backend API is complete. You let out a heavy sigh. | |
| | | | |
jensrantil.github.io
|
|
| | | | | Many small API calls are usually better than one large one. | |
| | | | |
claritydev.net
|
|
| | | Lately, I have been asked increasingly often for some tips on how to become a self-taught developer, so I thought I'd write a post about it, reflecting on my experience and pointing out the things I'd do differently. In this article, I'll try to give general advice on how to improve for those considering or maybe already on the way to becoming self-taught software developers. It should be noted that the focus of the post is on front-end development since that's what I did; however, a majority of the advice can be applied to becoming a software engineer, irrespective of focus. | ||
