Person
1 episodes · 17 quoted claims
Kris Tokarzewski says Vitality holds about 12% of the UK market and competes with institutions that are centuries old.
“We've got about 12% market share and we compete against large institutions that have been in business for, like, hundreds of years.”
Vitality is building event-driven architecture to support its product requirements.
“we are building event-driven architecture that supports our product requirements.”
Vitality is building microservices that are event-driven services.
“we're building microservices, which are actually event-driven services, and that's quite important.”
Over the previous couple of years, Vitality modernized a chunk of a legacy system each time it built a new product.
“Every time we would build new product, we would then take a chunk of a heritage system and we would modernize it.”
Vitality began its work with Blitzy by using it to reverse-engineer legacy code.
“We started with Blitzy on reverse engineering of legacy code”
Vitality's context engineering ingests its code base of millions of lines plus engineering and development standards into the AI's context.
“the context engineering is effectively ingestion of code base, millions of lines of code of, uh, uh, of our systems, our engineering standards, our development standards”
Vitality has adopted test-driven development, defining test cases before code is written.
“We've gone to what we call a test-driven development, and what it means is they that you define test cases before you actually write the code”
Tokarzewski says AI lets Vitality reverse-engineer legacy code about five times faster than manual work.
“We are able to reverse engineer our code probably five times faster than we were able to do it manually, uh, by people.”
Vitality has not fully quantified end-to-end gains and currently sees pockets of efficiency.
“We haven't fully quantified end-to-end the entire cycle, but we've got pockets of efficiency at this point in time”
Vitality calls its approach an AI-native software development life cycle, with autonomous development as only one part.
“we call it A I native software development life cycle, and then autonomous development is just part of it”
Tokarzewski says code generated at scale, such as 100,000 lines, is too much for humans to review alone, so another AI would review it first.
“So if we generated, let's say, 100,000 lines of code, who is gonna review 100,000 lines of code?”
Tokarzewski says Vitality can generate requirements and code rapidly but cannot review the code fast enough, making code review the next limiting factor.
“we can generate requirements rapidly, we can generate code rapidly, but we cannot consume that code fast enough.”
Vitality operates a matrix organization where R&D, product and engineering work as one blended team.
“At Vitality, we operate in matrix organization and R and D product and technology or engineering are actually one team.”
Tokarzewski says some Vitality requirements engineers are now reading code with AI's help.
“we've got examples where requirements engineers dive into actually code and actually they want to have a look at what the code looks like.”
Tokarzewski says Vitality wants evidence of the value gained from the AI tokens it consumes.
“we are consuming tokens, so the question is, what do we get for those tokens, right?”
Tokarzewski says the AI effort has support from Vitality's board, executive committee and management.
“we've got a a full sponsorship and full support at all level of all the way from the board, through executive committee, through management”
Tokarzewski says Vitality believes AI is as important as the internet.
“We believe that A I is as important as the internet.”