Projects + Thoughts + Experiments
This is Part 2 of a series of posts about refactoring Nitrolinks out of Pondo. Last time we’ve successfully moved Nitrolinks out of Pondo but we left most of the Nitrolinks-specific tests on the Pondo source code itself. This time we’ll move the tests to Nitrolinks so we can narrow Pondo’s test concerns.
I am building Pondo as an experiment on how to build a functional, modern web application without necessarily using a large front-end framework (e.g. Angular, Ember, React). The idea is to mostly develop applications as one would within the usual semantics of the normal Request-Response cycle. If you’ve used Pjax, or Turbolinks then you’re familiar with this.
Ideas are cheap. That’s great. Expend just a few calories and after a while, we have a lot of them. Executing on them is harder.