Category: Engineering

In today’s fast-paced work environment, it’s easy to get caught up in processes and frameworks, losing sight of what truly matters: creating value. The key isn’t in perfecting every process but in understanding why we’re doing what we do. By focusing on purpose and aligning every decision with delivering real impact, we ensure our work drives meaningful results. Whether it’s measuring return on investment (ROI) beyond revenue or adapting frameworks to serve the bigger picture, value should always be the North Star guiding our efforts.

Read more ›

Unlock the potential of AI in software development: streamline workflows, automate tasks, and boost productivity. Embrace the future of coding, where human ingenuity collaborates with intelligent systems to create remarkable technologies.

Read more ›

Your technical debt is product debt and product debt is business debt! Start giving your technical debt the attention it deserves or it will punish you later. Technical debt is business debt, the funds are just not borrowed from a bank but taken from engineers. This sounds provokative? Read further because tech debt is business debt! What is technical debt? The term was coined by Ward Cunningham, who said “If we failed to make our program align with what we then understood to be the proper way to think about our financial objects, then we were going to continue to stumble on that disagreement which is like paying interest on a loan.”. Further he added “Shipping first-time code is like …

Pay back time… tech debt is business debt! Read more »

Write a test that covers a use case or some functionality, then let the test run and fail. Once this is accomplished write as little code as possible so that the test passes. After the test passes turn the code into clean code; meaning refactor, simplify, adhere to convetions, etc. Done? …repeat that cycle. That approach is called Test Driven Development (TDD) according to Kent Beck. But why are we doing that?