When faced with a challenge of implementing breadcrumbs for a business critical application recently I went down a rabbit hole of trying to understand the semantics of react-router and finding a good way of building a dynamic breadcrumb component that didn’t break every time a route was added or changed. Let alone need to implement a custom route for every new page. In this post I go into what I ended up with as a routing model that supports dynamic breadcrumbs
Notes on the talk on Building Resilient Frontend Architecture by Monica Lent.
In this wonderful talk, Monica cuts to the heart of core aspects of rewriting code and presents 3 strategies to increase the resiliency of frontend architecture.
Why do we usually rewrite code? Inexperience, it’s fun, better solution available and (the big one 🥁) Technical debt 🎉.
Monica’s definition of Technical debt:
Code that negatively and repeatedly affects the speed or quality of delivery.
There was a recent blog post with the status of Aurelia vNext. For those of you that don’t know, Aurelia is a front-end framework with a focus on standards, extensibility, ease of use and performance. It’s been a while since a new major release, so vNext is a pretty big deal.
There was recently a post on the Aurelia Discourse that caught my attention asking how react-like hooks would work when using Aureliajs. The response from Aurelia’s creator underlined some of the reasons why I trust Aurelia to build JavaScript applications with Aurelia.
