javascriptBardSilo: Reducing verbosity in error handling — Day 21As Silo grows, so does the need to cut down on complexity. Javascript is very lenient compared to other languages. Can we come up with a…Jul 26Jul 26
javascriptBardSilo: Trying out the new RPC API with a silly example — Day 20In the previous article, we worked on a basic RPC API for Silo. This article is a small follow-up on that work in the sense that I wanted…Jul 25Jul 25
javascriptBardSilo: Creating an RPC API from scratch — Day 19There’s many options to connect clients and the server. I opted for a JSON-based RPC over HTTPJul 25Jul 25
javascriptBardSilo: Integrating support for layouts via JSX namespace— Day 18I’m a huge fan of code portability (to a certain degree). In an ideal world, you’d only have to write stuff once and reuse it as needed.Jul 24Jul 24
javascriptBardSilo: Integrating support for URL parameters — Day 17Silo treats the URL as the source of truth. We already had support for URL search parameters, but we needed support for URL parameters…Jul 23Jul 23
javascriptBardSilo: A basic pass on sessions with Redis — Day 16Today’s focus is going to be on getting a basic structure going for sessions in Silo. we’ll use Redis to get that to work.Jul 22Jul 22
javascriptBardSilo: Dependency injection and other module shenanigans — Day 15Silo is 100% built on es6 modules. That part is clear. It also leans very heavily on conventions. I expect files that I put in /routes to…Jul 21Jul 21
javascriptBardSilo: Let’s talk about templating and JSX — Day 14I’ve tried many different ways to present content over the years, and let me keep it short: JSX is the closest thing to an ideal solution.Jul 19Jul 19
javascriptBardSilo: Combating complexity; SQLite is enough — Day 12Picking the right tool for the right job… SQLite might just be enough for SiloJul 18Jul 18