At Sauce we are always looking to stay on top when it comes to using the latest and coolest new frameworks and services. It was with that in mind that myself, and two of my fellow Sauce developers James and Xing took the trip down to London to take part in the ServerlessDays 2019 conference.
The Sauce Developer Blog
It’s never too early or too late to learn the concepts behind development. It demonstrates logical thinking and problem solving which are skills any person would benefit from improving.
Since some of our projects are written in React Native, when the React 2019 conference was announced in Amsterdam, it was a no brainer that Sauce should get on that ticket.
An app we’ve been building recently for Moodbeam required working with some fairly complex SVG files for visualising charts and graphs, so I did some investigating into general SVG optimisation and graphic visualisations.
We recently discovered that the AWS IoT Device SDK does not support React Native. One often mentioned solution was to use rn-nodeify, but we are using Yarn Workspaces to share dependencies between React and React Native apps and this would have really compromised that, so we went looking for something that would work for us.
I wanted to make note of a handful of APIs that are likely to be useful when building applications with React Native. If you’ve been wondering how to save and load data, check if a device is online or offline, know if your app is in the background or active for performance reasons, using geolocation capabilities, vibrations, animations and a few more, then keep reading.
Some thoughts on working at Sauce from our intern Rebecca, who joined us on a Summer placement in 2018.
We’ve been investigating AWS IoT as a platform for our upcoming IoT projects. Here’s how we worked our way to a solution using Cognito User Pools.
When I first joined Sauce, I wasn’t looking forward to leaving student life. But Sauce has proven that my preconceptions did not apply to them, exceeding my expectations every step of the way.
We've been working with WebSockets for a while now and we've found the Phoenix Channel implementation to be really effective.
One thing we haven't seen discussed on a huge level is security.
I remember when I first came across lazy loading, I thought it was great, but it's so easy to end up with N+1 issues etc that it was refreshing when I realised Ecto didn't support it.
We've been introducing a few developers to Elixir recently, who haven't seen the pipeline operator before. We figured it might be useful to point them to a blog post.
If you've not seen it before take a read.