Nowadays many web applications are Single Page Apps that connect to an API via HTTP (for example REST or GraphQL). When you develop such an application, you do not only have to run a local development server, but also an API where it connects to. The API could be running on a dev cluster, but you can also run it locally on a different port for example.
A big advantage of connecting to a real API, is that you probably create less bugs. On the other hand, it is sometimes hard to test or setup up all possible scenarios. How do you for example test, in a controlled way, that your API responds with an internal server error and how the client handles this? In this blog I explain how to do this.
It is just like in mathematics class when I had to make a proof for Thales’ theorem I wrote “Can’t you see that B has a right angle?! Q.E.D.”, but he still gave me an F grade.
For my 3D Computer Graphics course in 2010, I had to create a procedural model as an assignment. We decided to make a tree using L-systems. After a few daws of coding, the result of this assignment is a program which can draw procedural trees using OpenGL. Although OpenGL is nowadays an oldfashioned 3D drawing technique, the result looks quite pretty.