Operations | Monitoring | ITSM | DevOps | Cloud

For almost a decade, GitKraken has been building developer-first Git productivity tools and services, with one clear goal: to make devs and their teams more effective and efficient. Our journey began with desktop-centric and IDE-based tools like GitKraken Client and GitLens for VS Code, which have both become integral to the workflow for tens of millions of developers. Our tools and capabilities are robust.

A long time ago I worked on a project called Django Debug Toolbar (DJDT). It was a local development plugin that would give you a debug overlay within Django’s development environment, helping you diagnose things like the SQL queries being made, environment configuration, and what templates were rendered. In general, it made the local dev experience much better, helping you prevent or more easily fix things like N+1 queries.

As a CTO, you need to come up with new strategies and tools to ensure that your company manages the rapidly changing world of software development. Platform Engineering and Internal Developer Platforms (IDPs) have become essential elements of this journey that change how software is developed and released.

Software developers need efficient tools that facilitate collaborative development without taking you out of the zone. The CLI, or command line interface, is a developer favorite for its ease of use, quick access, and versatility. GitKraken’s CLI is specifically tailored for Git operations, enhancing the traditional command line experience with its user-friendly commands and integrations, making Git tasks simpler and more efficient.

Software development begins with code, which is then integrated, compiled, tested, and in the end distributed to users. This is often the secret sauce of innovation that organizations must protect to keep their competitive edge. With the software application development market growing at almost 30% per year and the average project taking just 4-6 months to complete – and trending downwards – the result is more software to develop and constant pressure to release it as fast as possible.

In an article titled The Worst Programmer I Know, Dan North, the creator of behavior-driven development, writes about a nearly fired developer he saved from the unemployment line. This developer consistently delivered zero story points, even though delivered story points was the primary metric for developer productivity at their (unnamed) software consultancy.