1–5 of 5 posts
Here are some questions that may set a guideline for the discussion: - What are your methods of writing and testing certain APIs or algorithms (e.g. rate limiters)? - How do you benchmark/stress-test your code? - Resources on how you can improve your back-end development skills?
Feel free to ignore the questions and answer in your own way.
2. Make an ugly frontend, just for demo purposes
3. Write tests to call your APIs
Not everything necessarily needs a frontend. Imagine you're creating a SaaS API, there usually aren't Frontends except for maybe an API testing tool
1. Use tools like curl/postman/etc to query your APIs 2. Make an ugly frontend, just for demo purposes 3. Write tests to call your APIs Not everything necessarily needs a frontend. Imagine you're creating a SaaS API, there usually aren't Frontends except for maybe an API testing tool
This is almost trivial if your chosen language has capabilities built-in, as in `python -mSimpleHTTPServer`. Add endpoints to return in plain text or maybe json. One thing I often do is log to an in-memory array of strings, then add an endpoint `/log` that returns the contents of the array. I usually go a bit farther and use a circular buffer, so the in-memory log doesn't grow too big.
Postman is a good tool also, though the learning curve can be a bit steep.