Review 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).
Design needs to be able to adapt and change with the needs of the project. It can get messy and confusing, especially when you begin to introduce CSS. That is why teams have started to use design systems. They will help your team communicate and deliver a consistent design across all platforms. A design system is all the bits and pieces and components that make up your whole design. A design system is documented as a style guide. It is more important than some realize. A design system is good…
Lately, I have worked on a few projects where a single-page Angular app is contained within a site built on a server-side framework like Django. One of the challenges is to get their URLs to play nicely together. Say you have a project with an Angular 2 front end and an API back end using the Django Rest Framework. Further, imagine that your Angular 2 page is also served from within the Django app. Your URL structure might look like this:
As anyone who has read a blog post from me over the past two years knows, I am passionate about creating jobs in the software industry. Over 5 million manufactuering jobs have been lost in the United States alone since the year 2000 and no industry since has been able to keep pace with the creation of middle-income jobs needed to offset this massive loss.
The Livesaving Nature of Notes The software industry’s shift to Agile project management methodologies has many of us happily burying the waterfall project artifacts – the 13 required management plans, comprehensive work breakdown structure (with dictionary) and predefined schedule have all lost favor as useless overhead. The Agile Manifesto explicitly values working products and responding to change over comprehensive documentation and following a plan.
Uber and Darwin are getting a bad rap for killing off the taxi industry. They are innocent. As a matter of fact, Uber founders Travis Kalanick, Garrett Camp, and evolutionary theorist Charles Darwin all have a solid alibi.
Metal Toad has the distinct pleasure of working with some truly great clients representing a diverse array of industries. But for the self-professed geeks that operate in our little slice of Portland, there's something a little extra special about a client whose mission is furthering the biological sciences: namely, Schrödinger. When they came to us looking for a partner to build their brand new site, we were equal parts honored and enthusiastic.
Coming from a strict design engineering background and working in the realm of manufactured products, I have had a steep learning curve in the tech world I now find myself in. But, I have also found that there are lessons I have to share. This is my journey to find "My Thing"...
Software development in 2016 is a crazy complex process. Modern applications are increasingly distributed, regularly requiring access to an array of systems controlled by 3rd, 4th and 5th parties. So what happens when we are building the next killer-app-uber-disrupting-unicorn and the API that we NEED to access goes down? Slam our Macbooks shut, whine about up-time and go home? Consume our body weight in caffeine in preparation for the glorious return of the API? Sit quietly and wait for…
In my previous article, Angular 2: HTTP, Observables, and concurrent data loading, we investigated querying data from an API endpoint using Angular 2's Http service and the Observable pattern. In this second article, we will look at using Http to save data to our API endpoint. Consider the Angular 2 service we created in the previous article, DemoService: