From the moment I started React as an Engineering student to the present day, a lot changed, especially my productivity. For the same result, my time spent on coding, delivering and fixing bugs has greatly decreased.
There is a common misconception about how much time is really spent on a task in code-related jobs. A feature is finished when it’s in production and bug-free (and often more), not when it looks finished on a developer local environment.
That’s how you can increase your productivity, of course on time spent writing code but even more by increasing the speed of deployment…
For major projects with high stakes, scalability is the Holy Grail. Rarely fully achieved, an excellent paper breaks it down into four components.
The first three are self-explaining: load scalability, performance scalability, and space scalability.
The last one can be trickier to understand and is the one discussed today: structural scalability. From the introduction of Characteristics of Scalability and Their Impact on Performance:
Structural scalability is the ability of a system to expand in a chosen dimension without major modifications to its architecture.
From computertechreviews, another definition is given:
Structural scalability is the hallmark of a system whose implementation does…
Save time and effort with React and React Native by choosing the appropriate testing tools.
You finally decided to get into testing with React — great! This will be a huge step toward writing better code.
Today, I will be talking about the different solutions with regard to testing and my experience with them. Unlike me, you’ll be able to easily choose the correct testing tool without losing out on time.
No, this article won’t be a guide on “how to write a test” but “which testing tools to chose”.
create-react-app is an amazing tool, described as the best way to start building a new single-page application in React, inside the official documentation.
By making use of react-scripts, It offers a modern build setup with no configuration.
While it may well be a fantastic tool, chances are your projects always start with a big overhead. If your first step after running CRA is to spend a day setting up default functionalities and configuration, creating your own template will definitely boost your productivity.
Using GIT the right way can resolve a lot of headaches regarding the creation and maintenance of your…
No, I won’t be talking about cutting costs on developer’s wages. On the contrary, this won’t save you any money¹.
Let’s create a scenario: you are launching a product that requires a custom web or mobile application. To avoid spending more than necessary, what should you be careful about ? From an engineer perspective.
Great application development skills are expensive. Yet, often, developers cannot focus on their job. To me, it’s wasted money. One of the reasons they cannot focus is incomplete functional analysis.
I’ve seen developers and engineers get paid to document how a system should behave instead of…
TypeScript is a wonderful tool, but what about starting new projects?
Setting up a TypeScript project with your favorite technology, tools, plugins, and configuration can be a hassle. Fortunately, this step doesn’t have to be painful.
A common practice is to use a generator, template, boilerplate, or starter project.
Dedicated developers (or official teams for some libraries and framework) often create these. Be careful when trying out a new starter project, you must ensure it meets your needs and is well-maintained.
In some cases, you might even be tempted to create your own starter project from scratch or an existing…
Although I don’t reach for React Context all the time, there are some use cases where it can be a great tool. Recently, I had to use them in a TypeScript project with Hooks, and struggled for a bit.
I’ll demonstrate how to write a React Context in a clean and straightforward way with a
Counter component. This component will work like this:
Hello, fellow front-end developer, I hope I piqued your interest. To answer my own question: “No I’m even sure that, at some point, my endpoint will answer with a format I don’t expect”.
Regardless of the technology/library/framework you are using, once you start working on a web application with a separated front and back-end, there is a risk of expecting a response whose specification changed since you wrote your request.
At some point in every project I have worked on, we had an endpoint getting an update without the front-end team being completely informed about it.
Problems that have occurred…
Mostly, statically typed languages are criticized for restricting developers. On the other hand, they’re loved for bringing early information about errors, documenting components (such as modules, methods, etc.), and now other more advanced functionalities such as auto-completion.
A preliminary study from 2009¹ on untyped languages gives us some reference on exactly those pros and cons. Today, another type of language is also widely used: dynamically typed languages.
A dynamically typed language is different from its counterpart by bringing types but at runtime. This way, you can have far more freedom than strongly typed languages while keeping their advantages.
Hi, I’m Teddy, a French React lover 🚀.
I work on :
- Custom React / React Native application development
- CI implementation / Quality process / Delivery
- Project analysis and…