The discussion starts with market proximity in a consultancy context and moves on to topics such as the developer’s role in the value chain, how to stay relevant in a fast-changing tech environment, and what is required for collaborations that actually work – not least in procurement processes.
Listen to the full episode (available wherever you get your podcasts), or read on for a few key takeaways.
The developer’s role when software is the business
A recurring theme in the conversation is how the developer role has evolved. As software increasingly defines how businesses operate, what is built in code has a direct impact on customer value, efficiency and competitiveness. This brings development closer to the core of the business.
The developer community plays a key role in this shift. Not only because of technical expertise, but also due to its ability to combine deep knowledge with creativity and business understanding. Learning and knowledge sharing are central parts of the culture – those who share experiences and solutions often gain new perspectives in return.
Staying relevant in a fast-moving tech landscape
With new concepts, frameworks and technologies constantly emerging, staying up to date becomes a key challenge. The conversation highlights that this is not about knowing everything or following every trend in detail. Rather, it is about understanding the fundamentals, filtering the noise, and distinguishing real shifts from temporary labels.
Many technological advances build on existing ideas. A solid foundational understanding therefore makes it easier to assess what truly changes the conditions – and what is simply a new variation on something familiar.
Market proximity in a distributed consultancy
In a consultancy where many employees work on client sites, market proximity becomes essential for maintaining direction and relevance. Here, market proximity is not about reporting upwards, but about continuous dialogue and presence in everyday work.
It is about creating direct touchpoints where there is time to listen, understand how work actually gets done, and capture both opportunities and challenges. An informal, low-hierarchy approach becomes important, where value and perspective matter more than titles.
Collaboration, procurement and shared responsibility
The discussion also touches on more structural issues, such as procurement processes and how collaboration between clients and suppliers can work better. A shared understanding of each other’s conditions is key, as well as creating models that allow for quality, learning and long-term value.
When dialogue and market understanding are present early in the process, the chances of building sustainable solutions increase. For consultancies, this means not only delivering according to requirements, but also contributing perspectives and experience that strengthen the client’s capabilities over time.
A picture of today’s tech reality
The Kodsnack episode offers a broad yet concrete picture of today’s tech reality. It addresses the developer’s role, learning and collaboration, structure and everyday work – and why proximity to both technology and people becomes crucial when software is business-critical.
There are no ready-made templates, but plenty of recognition and insights for anyone building, leading or commissioning software in a constantly evolving tech landscape.
