Recently, Jason, one of Sema's founders, posted a thought-provoking article on technical debt. As he points out, technical debt is analogous to financial debt and software accrues technical debt when teams decide to defer all those “little” non-functional things.
The Sema team has spent the last year interviewing software development leaders in organizations of all types: Fortune 500 companies with decades of legacy code; start-ups who accrued tech debt as they moved quickly to grow their business; private equity-owned companies that acquire multiple new tech properties a year; and outsourced development shops who track every line of code written.
I used to have a trick when I was job hunting. The interviewers would drill me on all the hot problems in coding, and clever new techniques in data science and machine learning. Then when my turn came, I’d ask targeted questions about how they’re employing these a specific system. As soon as I saw smirks, sidewise glances, and the word “well…” forming on someone’s lips, I knew I was in. It was my specialty: bug squashing, refactoring, modernizing, and just wiping out tech debt with feel-good newness.
Tech debt was shrouding their dreams.
Sema is delighted to share the news that one of our partners, Govtech Fund, today announced the launch of its second fund, a $25M early stage venture fund focused on modernizing the internal operations of government. More details here.
Earlier this year, the Defense Innovation Board- a national group of leading technologists including Eric Schmidt and California Institute of Technology professor Richard Murray - put out a list of recommendations to improve how the Department of Defense creates software.
Sema is delighted to welcome Brendan Cody-Kenny as a founding member of our scientific team, and leader of our Ireland initiative. We asked Brendan to share a little bit more about himself and why he's so excited about Sema's mission.
Topics: Sema Team
Imagine a world in which your software development teams could double the time and energy they spend on creating new code. Double.
Think about how rapidly technology has advanced in the past few decades. And then consider—developers spend an average of 55% of their time on legacy software maintenance instead of creating new code. What could technologists accomplish if they could apply more of their brainpower to innovating and solving new problems instead?
Topics: Sema Team
I still remember my first assignment on my first job. It was a four-month project to improve the performance of an application critical to providing workforce services to the state of North Dakota. The year was 1987 and the application was written in COBOL. Our team worked for four months on tens of thousands of lines of code and improved performance to more than the target. An achievement to be proud of, but all we did for four months was refactor code. We developed no new functionality.