How we rewrote our tech stack in under a day
Last week, we deleted 16,000 lines of code, rewrote 11,500, migrated frameworks, ripped out React, and swapped our entire CSS setup with AI. It took less than 6 hours.
17 posts
Ignoring revisions when using git blame
Tired of git blame pointing to useless formatting commits? Learn how to ignore revisions with --ignore-rev or .git-blame-ignore-revs to keep Git history accurate and helpful.
Taming a Python: don't let the snake bite
Adapting to a new tech stack is all about mindset. Switching from PHP to Python was an eye-opener. Package management confusion, unexpected paradigms, and a lack of encapsulation made for an interesting challenge. Embracing constraints is the secret to growth.
How to manage technical debt as part of your agile process
How to manage technical debt effectively to keep startups agile with strategies for documenting and prioritising technical debt, integrating it into your roadmap, and creating a culture of continuous improvement. Keep your codebase healthy and your team productive with these actionable tips.
Why code quality matters
In today's digital landscape, software development is a crucial aspect of most businesses. However, many organizations overlook the importance of code quality. Ensuring code quality is critical for various reasons, from financial stability to customer satisfaction.
Why you should invest in consolidating your documentation
Where is your documentation kept? Is it one tool that everyone has access to? Here's why you should consolidate your documentation.
Why a microservice-based architecture isn't a holy grail
Microservices are a very popular architectural approach — maybe too popular! Here's why it might not be ideal for your organization.
Why is it good to deploy frequently
Do you deploy every day? Your team probably should. Here's why.
You are not Spotify: how efficient teams are born
We see teams blindly following Scrum, Kanban, or the Spotify model and introducing roles into teams (such as a Site Reliability Engineer) because other companies blogged about it. These models and roles are created because of specific struggles these companies faced. While all these processes thus contain valid solutions to...