software_
Stuff we learned
along the way
2024
Code for humans (Part II)
Opinionated practices and advice on what human readable code usually looks like.
Peter Cs.2024
Code for humans
Why it is important to write code in a way that other humans understand.
Peter Cs.2024
Bringing an outsourced development in-house
While rebuilding their platform from the ground up, our partner needed us to ensure their in-house team could maintain the new version independently. These were the key actions we took to comply with this request.
Adam T.methodology
The hidden costs of feature parity
Adam T.Our partner almost fell for the feature parity trap. Here are the top lessons we learned on how to avoid it in the future.
architecture
Reducing costs with a unified Web API
Adam T.An outdated legacy system caused a lot of headaches and unnecessary expenses for our partner. We joined forces to clean up their architecture in a renewed REST API.
frontend
Working with reactive arbitrary values in TailwindCSS
Adam T.Tailwind's arbitrary values are a great way to use custom values in your design that are unavailable through the included utility classes. Still, they get tricky when using values based on user input or any other variable comming from your JavaScript code. In this guide, we will explore the optimal way of using dynamic arbitrary values in any Tailwind project.
Need a software team
that can deliver?
Schedule a meeting with no commitment and let
us see if we can help you realise your vision.