As a frontend leader, I try to build processes so that the code is predictable and the team is on the same wavelength. One way is to fix a set of tools that solves 80% of tasks without unnecessary experimentation. Here is my current stack; it evolves, but the base remains. VS Code An editor who doesn’t distract. ESLint + Prettier are embedded in save, the terminal is nearby, Git Lens shows the history directly in the file. No “it doesn’t work for me” — settings in the repository. ...
The sprint format that actually works for frontend teams
If you’re a frontend developer, you know that feeling. The sprint is planned, the tasks are evaluated, but by the middle of the sprint everything goes awry. Suddenly, cross-browser issues surface, a “harmless” change breaks half of the components in the Storybook, and the backend API turns out to be not quite the same as described in the ticket. Classic Scrum, tailored for versatility, often does not take into account the specifics of frontend development. Endless “rallies for the sake of rallies”, strict deadlines for creative work and a constant context switch - all this kills both speed and quality. ...