RTK Query is the latest addition to the Redux family and brings a much needed data fetching solution for apps using Redux to manage client side state.
At the time of writing the library is in alpha so expect there to be changes.
In my experience, working on large projects and reading online discussions from developers using Redux day-to-day the biggest issue is the massive flexibility and granular control you have with Redux (sounds like…
We’ve got the Freshers fair tomorrow so no partying for us today. Besides, Monday is Tank night and I’m not sure how easy it would be to talk to people while raving.
The goal tomorrow is to build brand awareness and drive app downloads which from going to these fairs in the past means giving away free shit.
Let’s go with the classic goody bag: a flier, a couple of Attracted stickers, and some sweets… simple! We can ask people to download the app to get one.
I tried to keep the fliers clean and generic allowing us to pivot…
If you want to read the series from the beginning go to Day 2
After getting some real-world feedback from drunk users last night I got straight into improving the app.
The biggest issue we saw was that the user would sign up and enter their details which would authenticate them and leave them on the discovery screen. Unfortunately, I had decided to hide users that don’t have a profile photo. Meaning the user had to go to the profile screen to add a photo for others to see them. Easy fix… let’s add a second prompt screen!
Intro: I regularly write journals to review the day and highlight the things I could have improved on and also what I’m proud of; which made me think that it would be cool to share something like that for the week I launch Attracted (https://attracted.app).
I felt rather confident going into the day, very relieved to have finally got the approved status from the Apple review team. (My pessimistic side definitely thought I was going to have to promote the beta test flight release.) The T-shirts arrived just on time as did the fliers; they came out pretty nicely.
As a developer you’ve probably seen or heard the famous quote;
It serves as good advice to help you avoid overengineering and reduce time to getting user feedback. But, like most rules there’s subtalties to when it should be applied.
Let’s imagine… you create a component for a page your team is working on to display a small list of users.
As per the requirements, it takes a small list of users and sorts them by name in alphabetical order. …
The modern version of the classic science fiction book 1984. People sat on their phones scrolling through their friends photos on Instagram. As they scroll, their camera watches their face as each post comes into view. Noting which ones encite a reaction, both positive or negative, which helps improve the algorithm that is becoming ever more personalised to them. The algorithm that ensures people are seeing the content that releases the most dopamine and in turn keeps them on the app longer…but maybe this isn’t just science fiction.
I see so many articles debating whether companies like Facebook are watching…
Test Driven Development (TDD) is a widely used term in the developer community, but until you really understand why it’s useful, it can be hard to see the benefit. Simply put, TDD is writing tests to define how your code should work, then writing code to make those tests pass.
This article will go through the basic way to develop using the TDD process by writing a simple function that adds two numbers together.
Note: This article expects you have a basic understanding of Jest.
We’ll set up a super simple project to get up and running, we won’t do…
Writing quality code is an art, an art that requires periods of patience and focus. When working on complex code, a developer has to keep many things in their head, from requirements to low level state, and to get to that productive state it takes time.
Unfortunately for most, losing that focus doesn’t take much. Having to answer a quick Slack message, although it may take only a few seconds, can be enough of a context switch to impact efficiency.
Communication is vital between everyone in a team, but the way most organisations handle it does not work well for…
As developers, we tend to be very optimistic and we often give lower estimates than we should. Even when working on a project with little amounts of pressure, we usually underestimate the time or complexity of a task.
There are many reasons that cause us to underestimate, and most come down to the old saying:
You don’t know what you don’t know.
No-one can always anticipate every issue that might arise, and there will always be times when even the biggest overestimate will be wrong, but making sure to keep that simple quote in mind will help you make better…
There’s a lot of guides on the best practices for code reviews but in practice it’s very hard to stick to those ideals. In the real world, teams are under pressure to deliver which leads to a decline in quality without solid processes in place.
In this post, I will try to set out a simple guide on how to implement beneficial but practical code reviews into your team’s development process.