Introduction
There is inconsistency in the Redux community on how to use actions. Redux Toolkit documentation suggests the following approach:
[…] we recommend trying to treat actions more as “describing events that occurred”, rather than “setters”.
Why should we treat actions as events rather than setters? Dan Abramov, the founder of Redux, said that Redux doesn’t reinvent event sourcing. It’s up to people how to use it. It’s clear that there isn’t a well-accepted approach towards how to use actions.
Introduction
During these months at Facile.it I had to face many challenges regarding the improvement of CI/CD pipelines for the Insurance team, with a strong focus on performance and reusability. The focus on these topics is very important as it allows us to follow GitLab best practices for CI/CD such as the fail fast principle.
💬
Fail fast: On the CI side, devs committing code need to know as quickly as possible if there are issues so they can roll the code back and fix it while it’s fresh in their minds. The idea of “fail fast” helps reduce developer context switching too, which makes for happier DevOps professionals.
– How to keep up with CI/CD best practices - GitLab Blog
Today I want to talk about living documentation, having just finished the aptly-named book by Cyrille Martraire, Living Documentation: continuous knowledge sharing by design, published by Pearson.
The need for documentation
Documentation supplements the knowledge we might not have.
Lack of knowledge manifests in:
- Wasted time (finding the missing points or guessing them).
- Biased decisions due to this lack.
- Hint: when you don’t know something, you are usually not aware that you don’t know it ;)
Therefore, the time spent harvesting knowledge should be considered as helping to build the stakeholders’ application mental model. This is important because that’s the mental model that developers will use to augment the code, that product owners will use to describe the stories to implement, and that business owners will use to describe their key goals and outcomes.
Introduction
Facile.it’s Technical Writing team attended the Write the Docs Prague 2021 conference which was held from 3rd to 5th October 2021. While the conference was usually held in the capital of the Czech Republic, for the second year in a row it was held remotely due to Covid-19 restrictions.
In this article we will provide a quick overview of the event.
What is Write the Docs Prague
Write the Docs Prague is the annual European conference organized by the Write the Docs community. There are usually 3 annual conferences organized by the community: Write the Docs Portland, Prague, and Australia & India. This year due to organizational difficulties the Australia & India event was cancelled and partially incorporated into the Prague conference.
These conferences allow all people involved in documentation (of any kind and in any field, but especially in tech field) to meet, exchange ideas, and keep up to date on the latest themes. These events are attended by tech writers, developers, support specialists, UX/UI designers, and many others. Therefore, to be inclusive and for simplicity’s sake, organizers like to talk about “Documentarians”.
The technical writer, this mysterious character
Let’s face it, being a technical writer (especially in Italy) makes you feel a bit like Barney Stinson from How I Met Your Mother: no one knows what your real job is. If you’re a tech writer, we bet you have at least one relative who, at every family gathering, asks you “What do you exactly do for a living?”. In the most desperate cases, even your mom doesn’t know what your job is!
