Alex Banks's Blog
...On Serverless Infrastructure
In my career, I've found that there are two types of "agile" software process maps. There is Agile, with a big A, that is usually purchased from non-technical people by non-technical stakeholders. Big-A Agile is a series of meetings, metrics, and reports used to structure and monitor software teams. I've even experienced story estimates as hours, and a requirement to list "actuals" on each story to verify the estimate was correct.
In Part 2 (http://www.metaltoad.com/blog/yagni-react-architecture-part-2), we discussed configuring Director to listen for route changes and run a route handler (conveniently all Director does (and why I love Director)). In this post, we will finally do some React writing. Not a lot. But some. This series is intended to be about React architecture, not necessarily React code creation (which maybe maybe we’ll do later).
In React Architecture: Part 1 we discussed a desire to configure a working React website with as few addons as possible. The post ended with the creation of a basic Webpack config, which left us with a project structure like...
React is awesome. 11/10. In my opinion, the best UI library currently in the ecosystem. It streamlines UI componentization, reusability, UI state, and a ton of other client side headaches devs have been mitigating for years. React's greatest flaw, in my opinion, isn't even really a React flaw as much as a "new stuff hype" flaw, where the infrastructure surrounding React changes almost hourly and can be extremely difficult to keep up with. What libraries are required, which ones will make devs' lives easier, which will bring performance gains?