March 7, 2024
WHO IS THIS EPISODE FOR?
Federal CIOs, IT leaders, technology modernization teams, and government contractors interested in reducing technical debt and improving how agencies build and maintain software.
WHAT WILL YOU LEARN?
How codeless software development can reduce maintenance costs, simplify application development, address technical debt, improve cybersecurity, and help federal agencies deliver modern digital services with limited resources.
In most of my interviews, I sit down with a company and talk about innovation in solving federal technology goals. Today, a twist.
Sonny Hashmi was at the center of the battle for improving federal technology. For the past three years, he was the Commissioner of the Federal Acquisition Service at the GSA. This has given him a unique perspective on what the bottlenecks are in streamlining federal technology.
He dealt face-to-face with issues like Zero Trust, remote work, and digital innovation. After looking at a myriad of issues, he decided that the way to apply Occam’s law to federal technology was to reduce the complexity of software development.
"Because while you know, we've always known this problem exists, but the gravity of it, the velocity of it, and the impact of it's it's now unsustainable"
Sonny Hashmi, Unqork Tweet
Sonny Hashmi explains that 80% of the technology budget is spent on maintaining systems. This means continuous monitoring, patching, and applying new compliance regulations. His approach to solving the problem is to start at the beginning, software development itself.
(The founder of Unqork, Gary Hoberman, distills his codeless concepts on short, YouTube videos called “Coffee & Codeless” sample above.)
The solution is quite simple: adopt a codeless method that allows a wider range of people to work with legacy systems, rapid application, and compliance.
During the interview, Sonny Hashmi details some problems he has seen. He talks about everything from struggles with ATO to end-of-life application management.
Listen to the interview to learn how the Unqork approach can assist in many aspects of the major digital transformation the federal government is undergoing.
If you enjoyed this episode, then you may want to listen to Episode 132 Enhancing Collaboration in Federal Systems
Speaker 1 00:00
Hey, John Gilroy here. Today, we’re going to talk about motorcycles and codeless software development. Hit the music, Manny.
Speaker 2 00:11
Welcome to the Federal Tech Podcast, where industry leaders share insights on innovation with a focus on reducing cost and improving security for federal technology. If you like the Federal Tech Podcast, please support us by giving us a rating and review on Apple Podcasts.
Speaker 1 00:34
Welcome to the Federal Tech Podcast. My name is John Gilroy, and I will be your moderator. This is the podcast that connects you to federal technology leaders, and we have that right in front of us right now. Sonny Hashmi is a classical federal technology leader, inside and outside the government. We’re going to drag him into the studio today and give his insights on something called codeless software development. And he works for a company called Unqork. U N Q O R K, and you can find more information there. In fact, they have a whole page there about how they work with the federal government. And Sonny’s official title is head of global public sector from Uncork, but his unofficial title is his teenage kids don’t think he’s cool. So, what kind of title is that, Sonny?
Speaker 3 01:18
It’s so great to meet you. Good to see you, John. Thank you so much for having me on the podcast. I’m looking forward to the conversation. And listen, you know, the the funny thing is, I’m I’m very very blessed to have two boys who are who are smart and creative and passionate about their lives and they’re building their their young lives in the direction that they want. But it’s funny because I recently took them to the building when I was still working at GSA and showed them around a little bit, and they had no idea what I did. They had they were fascinated to learn about what we do, and they had no idea not only what GSA does, but what I do there. So they were pretty pretty. It was it was it was fun for for them to learn a little bit about their old dad, and yeah, I mean it’s it’s amazing how life changes, but I’m I’m just I’m just fortunate that they are good, thoughtful, kind human beings, and one day they will hopefully learn a little bit more about what I’ve done in my life.
Speaker 1 02:12
Going to an event on Friday morning at Carisoft, and I’m sure if I just grabbed random 10 people and said, “Hey, where’s Sunny work, and they all say GSA, and so you kind of that’s that’s the impression people have, and they all know you, and and kind of because you’ve been around a while. So so the question is, I think most of the people at the event would say, well, geez, why did he change, and why uncork? So that’s my question to you: Why did you switch out of GCA, and and why of all places uncork?
Speaker 3 02:36
Yeah, thank you for that question. First of all, I’ve been so blessed to have been called to serve back in the GSA under the Biden administration. We, as a team, did an incredible amount of work over the last three years at GSA, focusing on everything from recovering, helping the country recover after the pandemic, and enabling small businesses and increasing the number and dollars flowing to them, helping with supply chain risk management, really making sure that our service members have the have the tools, technology, services they need to serve the country. You know, the list goes on. But as I started thinking about one of the you know you know how we modernize the organization, and both in my previous role as a commissioner, but also my previous role as the CIO of GSA. One of the constant challenges that I faced, and and this is no news to anyone, but is the fact that about 80 to 85% of the dollars, energy, and time that organizations in the federal government spend goes towards maintaining applications, maintaining systems, and maintaining technologies without really adding more value to the taxpayers, and that leaves not only very small amount of energy and time that we can spend towards adding more value, but it’s an existential problem now because the the expectations of the citizens from their government are increasing to a level that cannot be sustained in terms of delivery. That one of the things that pandemics has shown not only that agencies can be nimble because they had to be to adopt new technologies and new methods and new processes, but it’s also set a new expectations for our citizens, our stakeholders, to deliver better and to deliver at different scale, deliver digitally, and so as those expectations, rightfully so, continue to continue to increase, agencies are now forced to make difficult choices in terms of how they meet that moment. And with 85%, 80 to 85% of your energy, your time, your money going towards maintaining technologies that were invented, you know, over the last two or three decades. In fact, at GSA and other organizations, I’ve seen some organizations maintain three to four to five generations of technology. I’ve seen organizations call people out of retirement to maintain systems that require that are vitally important for an agency’s mission. But those technologies, those paradigms, those architectures have been depreciated. For decades, and so this is a problem. This is a problem of our generation because while you know we have always known this problem exists, but the gravity of it, the velocity of it, and the impact of it is now unsustainable. So this requires us to not just invest in the next new thing, but really rethink a new way of building capabilities that set agencies up and free them up for long-term success. So, as I was thinking about that problem, I was talking to a lot of people. You know, what is that new way of building capabilities that don’t just replace one type of technical debt with another type of technical debt, but really set agencies up for for long-term success? Really free them up from technical debt. Really take you know a lot of that risk away, and certainly also find opportunities to reduce operations costs so they can reinvest that dollar towards building the next set of capabilities. And so as I started to think about that problem, had a lot of conversations. You know this uncorks kind of philosophy kept coming up, and so I had an opportunity to sit down with the CEO of the company, got to know a lot of their leadership team, and really understand how they’re approaching this problem. And I’m very, very excited that it is something that I really resonated with. And I’m excited to now be part of the company and help help help help the company bring that capability, that innovation to the federal federal market and help solve some of those, you know, confounding long-term problems for many federal agencies.
Speaker 1 06:26
I was taking notes. I wrote down 85% time on maintenance. I thought about my first car. My first car cost $300, and I got it in the summer. And I tell you, I must have spent 90% of my time maintaining it. Couldn’t get down the road without something falling off, I’d go to junkyards and come back and put in water pumps and starters and whole lot of time. And and
Speaker 3 06:47
it’s a great example too. And I sort of cut you off, but because like in all the other industries around us, take cars. You mentioned cars, right? I remember I’m a car guy. I remember working on the on my dad’s car, and something was always going wrong. Whether the carburetor needed adjustment, or the airflow needs to be replaced, or valve train has to be adjusted. But think of how far the cars have come by abstracting a lot of this technology and the complexity away. Today, you don’t even have to worry about whether the car has valves or cylinders or not, right? Like it’s basically they just run. You press a button, it turns on, and you run and like they’re far more reliable, they’re far more fuel efficient, they’re far safer. And by abstracting a lot of that technology and complexity away from the consumer, the auto industry has been able to deliver better product, more reliable product, cheaper product, more environmentally conscious product, and something that people can now rely on that they could couldn’t in the 70s or 80s, but here we are in 2024, and somehow the software enterprise software industry has not learned that lesson. That complexity has not been abstracted away. Every organization still has to deal with hiring specialized developers and DBAs and UX engineers to be able to maintain the thing that they rely on every day, and somehow that scalability that we see in automotive or medical industry or even financial services industry, where the average end user doesn’t have to care about or the customer doesn’t have to care about some of the complexity, hasn’t translated to enterprise software. And so, and by the way, this is not just a government problem. Across the board, we see the same numbers, 80 to 85 percent of the dollars, the energy, the focus goes towards maintaining risk, maintaining compliance, maintaining old software, and so that we’re trying to solve through abstraction. Similarly to how the automotive industry abstracted away a lot of the complexity to make it an easier, seamless experience for the consumer, we’re trying to abstract away the complexity of programming languages, code, database architectures, infrastructure for the benefit of organizations and enterprises.
Speaker 1 08:49
I’m just saying about your sons; they’ve never seen a carburetor, and may never see a carburetor in the future, and could care less about having a carburetor in any kind of vehicle that they have.
Speaker 3 08:57
I don’t think they’ve ever seen a ported phone before in their lives.
Speaker 1 09:00
Same thing, isn’t that something? Yeah, yeah. I’m I’m a real smart guy, and I do my research, and I use this real complicated tool called YouTube. And so I went to YouTube, and I typed in U N Q O R K. You see, I’m advanced. I stumbled on this guy named Gary, and he I don’t know if he’s guy’s a comedian. I don’t know what this guy earns a living doing. He’s got something called coffee and codeless with Gary. Maybe he stole it from Seinfeld or something, or coffee with comedians. Coffee with
Speaker 3 09:27
comedians.
Speaker 1 09:28
But I tell you what, if if you’re you know looking at Uncork and trying to figure it out, you could delve into the white papers and sit down with Sunny for five hours and go into the weeds. But hey, pop on a little video. He sits there. He talks about a new solution, and then in the middle of this, he’ll just drop in something. It’s like, yeah, when I was working with this big bank, we had this problem, and whoa, it’s it’s like you know you’re talking to your neighbor, and then you’re cutting your grass, and he goes, oh yeah, I was working on Lagrange point for the last lunar orbit, and the system orbit. What? It’s a pretty good place to go, isn’t it? This guy, who is this Gary guy?
Speaker 3 10:04
Yeah, so so Gary Hoberman is the CEO and founder of Uncork. And what’s interesting is that, and actually, you know, I do recommend if you have some time to go check out his Coffee and Coda series. One of the one of the great things about Gary is that founders for technology companies come from different backgrounds, different philosophies. But Gary comes from a background of having been a CIO for one of the largest organizations in the world. Gary was a global CIO for MetLife, which is a very, very large, complex insurance company, and managed billions and billions of dollars. Right, and as the CIO, he was facing exactly the same problems that our customers face every day. Same story: 80% of the work goes towards maintaining code. Everything is not agile. Everything is burdensome. You cannot pivot to meet new business requirements, new technology requirements, new environmental challenges because so much of your day-to-day business requires maintaining this legacy environment, and as a result, the organization is not competitive. They are high risk. They’re assuming a lot of risk. They’re spending a lot of money. And so, as he faced these challenges as a CIO, he thought, “Hey, there’s got to be a better way to kind of manage this same business process, same capability, but deliver it faster, deliver it at lower cost, and deliver it in a way that sets it up, sets us up for long term success, and so he started the company. He literally started the company to solve the problems that he was facing in that role, and so as a result, our company started solving some of the most complicated, entrenched enterprise level problems. Rather than solving for very straightforward things and going upstream with complexity, we started with some most some of the most complicated problem sets, especially in financial services, so insurance underwriting, client onboarding, know your customer, banking, wealth management, and so you know because the entire product was designed to solve for complexity in large enterprises. You know we are we are we’re we’re from the very fundamental way able to kind of do those same kind of things in other industries, including including public sector. So it’s pretty exciting for that reason. But Gary is also a huge nerd, and I think he will say that himself, and a great technologist. So if you do have some time to kind of spend learning a little bit more about his philosophy and certainly the company’s philosophy, do check them out on YouTube?
Speaker 1 12:22
I know you and Gary have been on many, many podcasts, and and believe it or not, many of my listeners are people in your position with other companies trying to learn what Uncork’s all about. And so, if you are thinking about going on a podcast, what I recommend is you go to PodScoreCard.com and take the quiz. It’s 15 questions, takes two minutes. It tells you how to leverage your next appearance on a podcast. My question for you next, Sonny, is a technical question, and I don’t want to get too serious here. But we got to get a little serious every now and then, you know. Part of the promotion for your company talks about freeing users from technical debt, and there’s some people understand technical debt backwards and forwards, and some don’t. But let me, I’ll give you my idea in audio software development. There’s different concepts and terms, and and one term is that some promise to complete tasks in the future could be listed as debt because its code is called technical debt. And however, we have someone like Gary standing up on stage and saying, “Hey, we can free you from technical debt.” Well, I’m sure there’s people listening are going to sign up for that one. So, so technical debt. You want to expand on that and how you can assist?
Speaker 3 13:27
Yeah, absolutely. So, listen. Ultimately, organizations think of a government agency. Think of an organization. They exist to carry out a mission, right? That mission is not to manage systems or technologies. The mission is to serve the public. The mission in the in the government, and I’ve spent most of my career in public service. Is every agency has a a an incredibly important mission, and ultimately they’re serving the taxpayer, serving the American people, serving the service members, serving veterans, serving small businesses. If you work your way back from that mission, right? The ideal modern way to to build the technologies to serve that mission is to you really start with user research. You understand who your end users are, and you build to solve the problems that these people use. When I was at GSA, one of the organizations that I had the privilege overseeing is the Technical Technology Transformation Service, and their entire philosophy is you know delivery is the mission because every organization, in order to meet the mission, needs to focus on delivering the capabilities that their users need, and those users could be internal users or external users. And so, you pick any example. You pick a pick USDA Farm Service. They are serving farmers and ranchers in in applying for loans, applying for crop insurance, getting assistance that they need, and making sure that that industry is supported and thriving. Those are the stakeholders. That’s the mission. Everything that we do in service of that mission, all the systems we build, all the processes we automate, all the forms that we digitize, all of the digital experience. We build are in service of that mission, and that should be the focus of the agency. How do we accelerate? How do we deliver? How do we serve? Unfortunately, what happens is that in order to do that digitization and modernization, you end up building a lot of custom technology, and those that custom technology is often built using programming languages and database schemas and middleware architectures and API specifications, all of those things come together to build some sort of an application that ultimately delivers on the mission. Well, that’s great. And over the last 15 to 20 years, the world has come a long way in modern software design, modern software platforms, modern software engineering, and languages and everything. However, the one thing that people forget is that as soon as you build that application in any modern programming language of your choice, that is technical debt. Technical debt means that that now needs to be maintained. An engineer, a developer, a UX designer, a database engineer has to understand and maintain that because the world around that changes all the time. And so, one you know, back in the 60s and 70s and 80s, people were writing these these applications in shiny languages like COBOL and Pascal and you know Fortran. And now we look back at that and laugh at that. Oh, that’s legacy. But guess what? 10 years from now, 15 years from now, your Python, your Node.js is also going to be legacy. The world is moving fast. New and new capabilities are coming in, and things that you’re building today are going to be legacy tomorrow. And so, if you look at it from a dollars and cents perspective, I’ve been at the federal government since 2006. When I started, there was a narrative around, hey, this government spends about 90 billion dollars a year in technology. 85% of it goes towards O and M, and we can’t get out of that rabbit hole. All of this work since then: cloud computing, platforms, modern agile, user-centered design. Here we are in 2024, and guess what? The federal government spends about 95 billion dollars in technology. 85% of it goes towards the O&M. Why can’t we get out of this cycle? Why is it that 80 to 85% of all of our dollars in energy always goes towards managing existing things, and that’s technical debt. Because whatever we do, whichever new paradigm we go to, whichever new technology we build, whichever new programming language we adopt, the solution, the underlying problem stays the same. Now that has to be managed. It’s been custom built.
Speaker 3 17:16
It’s been locked into a platform that is highly specialized, highly customized, and proprietary, and so now we have to hire very specialized people at very high rates to maintain the thing that we built. That’s the problem set, and that’s what we call technical debt. Our philosophy is that that is not a sustainable and long-term viable model, and we need to go to a completely different model, where not only are you able to build the application fast and quickly, and with high fidelity and high security, but then you actually have a line of sight into the total cost of ownership. What happens once you built it? How do you maintain, manage, patch, upgrade, scale, secure it? That needs to be automated. And so, entire thesis of our existence, our company, is that we abstract away all of that work that typically happens after the application goes live, and we take all of that burden away from the customer. We do that work so that the customer can continue to focus on building the next level of capability, delivering the best experience, and you know modernizing the next work workflow and business process. So, so that’s what we call abstraction, and therefore we’ve coined a name for it called codeless, because we’re getting away from writing any kind of code, and abstracting away all the complexity that’s inherent in it, and taking on that responsibility ourselves. So the customer only has to worry about what the business problem is that they need to solve, and what the user experience is that they need to create.
Speaker 1 18:40
Yeah, I think this whole concept of end of life is something that’s not ever really talked about. You know, people are so dazzled by the shiny thing in front of them they don’t realize that you know the shiny thing in front of them is going to change and and all things you know beginning, middle, and end, and has to end. And and what happens then? Okay, absolutely. I mean, if if you have a Mercedes Benz diesel and you put a water pump in it, it’s gonna it’s gonna get 200,000 miles, but it’s gonna have to be replaced. I mean, it’s end of life. It happens. I mean, I think with mechanical things makes sense, but with software, oh, Sonny, this software is not gonna wear out. It’s just software. Well, guess what? It’s gonna come the end of its life because the world
Speaker 3 19:16
around us changes all the time. Like, listen, I was in government when we found out about the Log4j issue, and now Log4j is an open source library. It’s not like a you know problem that occurred out of nowhere. But when we found out a vulnerability in Log4j that was exploitable, how do you even go across the hundreds of 1000s of applications in the federal government to update that code that relies on this one library, how many hundreds of 1000s of developers that have written this custom bespoke, you know, code that sits in networks and systems and databases and really are the backbone for how the government operates had to be touched, maintained, updated, paid for, and then what happens when the next version of logs? 4J is has another vulnerability, or next library breaks. That problem is not going away. It’s only getting more complicated. It’s only getting more complex. And at the same time, we see the government agencies’ resources are not going up. In the last three years, and working very closely with the Office of Management Budget and obviously stakeholders on the Hill, when I was part of the GSA Federal Acquisition Service, we found a significant investment of investments to modernize the government’s experience, to invest in cybersecurity, to set invest in digitization and modernization. The Technology Modernization Fund was awarded a 1.5 billion dollars that was part of that Technology Modernization Board, and we helped agencies invest those dollars for modernization. We spend a lot of money through through new programs like the ARP, new programs like the the bipartisan infrastructure law to help the government modernize states, cities, localities, and the federal government. But what happens when that money stops flowing? That code that’s been built today to modernize that process, to digitize that environment, to modernize that thing, now needs to be maintained. And so now government agencies are getting into a catch-22. We invested all these dollars to modernize our environment, to build new capabilities, to build a new system, to reduce friction, to improve user experience. But now we have to maintain all of that, and the dollars are no longer on the table. Now we have to go back to the budgets that we had prior to the to 2022-2021 timeframe. Now everybody’s getting a haircut. Now everybody’s getting a 1% reduction. And so not only do you have to pay for this new thing you built, continue to pay for it, but you have to somehow find it out of hide. And so the resource constraints are real, and we can only solve for this problem to deliver more and more capability in a in a stable, if not declining, budgetary environment through a brand new way. We have to break this cycle, and that’s where companies like ours comes in.
Speaker 1 21:55
Well, there’s not only financial constraints. There’s also I don’t want to use an indelicate word intellectual constraints too. I mean, maybe talent constraints because you know if you can simplify something, why not? And if you can adapt a codeless way to solve a problem, then you may not have to invest in talent that is as expensive as other talent. I’m dancing around this. No, no, we can’t hire people; they’re hard to find.
Speaker 3 22:23
Like there is finite talent, especially highly specialized talent, is hard to come by. It takes many years for that skill set to get to a level where you can reliably build highly complex proprietary code. And yet, there is this whole generation of smart, active, passionate, thoughtful people who are coming into the workforce that want to solve problems, and you know this traditional way of writing software becomes a barrier to entry because if you’re a passionate young you know college graduate and you have a knack for solving business problems and solving user problems, do you really want to like you know? But you can’t do that until you go through five or 10 years of experience learning a particular technology, or a coding language, or database architecture schema. Before you can do that, that is a barrier to entry. So one of the things that we’re doing at Unqork is we have something called Uncork Academy, and essentially what it is is we we we feel very deeply that we need to empower a much broader cohort of people across the country to have the skills necessary to help you know government agencies improve their operations. Right? These people not always don’t always come from computer science backgrounds. These people are not always don’t have always have deep software engineering you know expertise. They could be veterans. They could be, you know, single parents. They could be people who did career changes. They need the skills they need to be able to add value quickly in the in the organizations that they’re serving, without having to spend five or 10 years learning a technology or programming language and competing in that marketplace. So we created something called Encore Academy. There’s over 100 different courses online available, and we basically take you from the very beginning to make you an expert all the different stages, whether you’re an associate, whether you’re a professional, or an expert in how to build enterprise-grade capabilities, systems, and applications without writing any code. And it basically talks you through what data architecture looks like, what user experience looks like, how do you design for certain capabilities? How do you design for Section 508 compliance? How do you design for accessibility? All this content is available, and anybody who wants to participate, you can do it in a self-paced way at your own schedule, or you can even participate in live courses and live classes with experts. You can participate in actual live build capabilities. You can actually do practical, you know, application configuration. And so, because our goal is to empower and train hundreds of 1000s of people across the country who have now the skills to actually add value to their organizations without having. Having the luxury of a background in software engineering and a four-year college degree, etc. So, so that’s our goal, and that’s why we created. And if you’re actually curious about learning yourself, if you want to learn more, just go to uncork.com, click on Unqork Academy, and there’s a lot of information there.
Speaker 1 25:14
And I’m going to spell it again for our listeners: U N Q O R K.com. And I’ll put links in the show notes to every you know links to the videos, coffee with Gary, and links to the Uncorp Academy as well. So it’s been an interesting conversation today. You have been listening to the Federal Tech Podcast with John Gilroy. Like thank my guest Sonny Hashmi, head of global public sector at Uncor.
Speaker 2 25:38
Thanks for listening to the Federal Tech podcast. If you like the Federal Tech podcast, please support us by giving us a rating and review on Apple Podcasts.
Transcribed by https://otter.ai
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

Leave a Reply