Denis Knjazihhin

Denis Knjazihhin

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Posts by Denis Knjazihhin

The DTwo Blog

The DTwo Blog

Hello, I'm Denis Knjazihhin, founder of DTwo. For this very first post, I want to clearly outline the blog's purpose: why we are launching it and what we aim to achieve.### [#product](/categories/product) This blog will, of course, be centered on the DTwo platform. We are building a product that allows organizations to securely connect AI workflows to their internal data and systems.You can expect regular updates as we move through beta and general availability releases, continually adding new features and capabilities. This space will be your primary source for all new releases and product announcements.### [#culture](/categories/culture) Every start-up develops a unique culture. It’s a dynamic blend created by the people who work here, their shared experiences, and how they choose to collaborate.Throughout my start-up career, I've actively fostered a certain style and culture. While I hope DTwo inherits many of those elements, I recognize that it may well evolve into its own distinct identity. Regardless of how our culture develops, I believe it's important to acknowledge it and it's fun to share the journey of building our culture with the rest of the world.### [#journey](/categories/journey) My personal start-up immersion began in 2007 with BladeLogic. Since then, my path has included Aveksa, building an internal start-up ("Alpha Project") for Cisco, co-founding Genie Life Sciences, and now launching DTwo.Each of these ventures has been a unique adventure, filled with its share of triumphs and inevitable hurdles. I've been through this cycle many times, and I frequently chat about my experiences with friends, many of whom worked with me at those same companies. We often analyze what strategies paid off and where we stumbled. However, none of us ever took the time to write about our journeys while they were fresh in our minds, capturing the moment before hindsight colored our perspective.This time, as we build DTwo from the ground up, I’m excited to blog about the process in real-time. I sincerely hope other members of the DTwo team will contribute their voices and unique perspectives as well.### [#tech](/categories/technology) At our core, we are a team of passionate technologists dedicated to innovative solution building. Every time we embark on this "zero-to-one" journey of creating something new, the landscape has shifted. There are always new tools, frameworks, and approaches that promise to make product development faster, better, and stronger.As we architect our new technology stack, we will try to share our decision-making process, technical experiences, and the lessons we learn along the way.--- We look forward to revisiting this post in the future and evaluating whether the DTwo blog fulfilled its original vision or evolved into something entirely new.Stay tuned for our next update!

Read More
Viking Culture

Viking Culture

### The "Viking" vs. "Village" Approach to Startup Culture At DTwo, we are intentionally building a culture defined by collective momentum and shared responsibility — a concept my longtime friend Didi Dotan and I refer to as the Viking Culture.### The Core Analogy: The Viking Ship To understand this mindset, imagine a Viking ship. Every person on board is rowing, and everyone is rowing in the exact same direction. * No one is too special to row. You want to do something special like be a navigator? Row, then navigate. * The alternative is having a Village, where everyone has a static, specialized role (the blacksmith, the merchant, the noble). In engineering, this often leads to a "Village Culture" — a slow, bureaucratic environment where ownership is unclear and debates last for months while progress stalls.### Breaking Down Silos In a Viking Culture, we eliminate the rigid boundaries that often plague tech teams. We don't have "pure" architects, designers, or testers who refuse to step outside their job descriptions.* Business-Driven Agility: If the company’s most urgent need is a UI overhaul, the whole team focuses on UI. If we are facing a quality crisis, everyone tests and fixes bugs. * End-to-End Accountability: There is no "throwing code over the wall". If your work causes a production issue, you are the one responsible for fixing it, regardless of what part of the tech stack you typically work on.### Expertise Without Ego This doesn't mean we don't value specialization. We recognize that everyone has one or more areas of expertise — whether it’s front-end development or back-end development or cloud infrastructure.* Leadership through Expertise: Specialists lead the charge when the team is working in their domain and provide oversight for others. * Priority on Delivery: The ultimate value is placed on getting things done.### Why It Matters For a "zero-to-one" startup, this culture is vital. It attracts people who are passionate about hard work and want to be surrounded by like-minded peers. More importantly, it ensures the team’s output is dictated by actual business needs rather than simply trying to find work for people based on their specific job titles.

Read More