News & Insights

An Aries client recently decided to tackle BFF (Backend For Frontend) layers, how they should be implemented, and which best practices should be followed in a composable implementation. Our CTO, Tim Steele, provided an impressive workshop diving into the details, edge cases, and best practices tying it all directly to this specific project. While it’s impossible to capture the immense value this workshop provided in a blog post, I’d like to showcase some of the highlights.

If you were to plug the question, "What does QA mean?" into your favorite search tool, you would get about 7,980,000 results. However, we need to define what Q.A. is an acronym for before we can start talking about the true definition of it. I want to take a step back to reset our foundation when we talk about QA. So let’s get into it; what does QA really mean?

A strange, uneasy feeling came over me while I chatted with a project manager about an upcoming ecommerce project. As we talked about the project's goals, expectations from the team, the timeline, and the challenges the project team will face, the stranger I started to feel. Looking at the chicken scratches on my iPad, which passed as my notes, the source of the unease jumped out in three bullet points: Agile, Automation, and AI. These three elements can make or break your project.

In recent years, artificial intelligence (AI) has made its way into the developer's toolkit, promising to streamline workflows and boost productivity. In this blog post, we'll explore the impact of AI on the everyday work of frontend developers, with a focus on tools like GitHub Copilot and ChatGPT. We'll discuss their benefits and disadvantages and highlight why human developers remain irreplaceable in certain aspects of the design process.