Welcome to the latest edition of #FlutterFunFriday. This is the another instalment in a new series of posts where we’ll be spending some time to have a bit of fun with Flutter on a Friday. So grab a beverage of your choice, fire up your favourite IDE and lets have some fun!
Get up and running with automated testing and deployment of your Flask app using GitHub Actions and Heroku.
Welcome to the first edition of #FlutterFunFriday! In this instalment we’ll be learning how to use the new support Flutter has for custom shaders. So grab a beverage of your choice, fire up your favourite IDE and lets have some fun!
In this blog post, we will explore the process of building a back end using only Dart. With the numerous options available for achieving this, it’s normal to feel overwhelmed or unsure of where to begin. Thus, this post is primarily directed at Flutter developers who are considering Dart for their back end for its various benefits, which we will discuss later on.
It’s your first day at an exciting company, and everything’s going great. It’s time to familiarize yourself with the codebase. So you fork it from GitHub, and lo and behold, your warm smile is replaced with utter confusion. The codebase is filled with spaghetti code. Simply, it’s chaotic. We developers are often faced with scenarios like this.
Choosing a solution to create or improve your CI/CD pipeline may seem like a daunting task. Read on to learn more about the benefits and limitations of choosing CircleCI, Github Actions, and GitLab.
