CircleCI

FEBRUARY 28, 2022

There are two primary sources of technical debt: Business requirements including time pressure and changing conditions. Technical leadership problems can include poor technological design or flawed review processes, tools, documentation, and test suites. It is not always necessary to repay technical debt right away.

Technical Review 96

Technical Review DevOps Weak Development Team Software Review 96

Marv's Smart Future

MAY 21, 2018

can no longer remain ahead while fielding and sustaining 3, 4, or even 5 generation old information technology. By taking advantage of publishable program status, program decision briefings and most of the acquisition documentation could be replaced with “Passive Oversight” of program planning and tracking information.

Technical Review 49

Technical Review Systems Review Technical Leadership Programming 49

Marv's Smart Future

MARCH 7, 2019

The result of these law changes has been the breakup of the Under Secretary of Defense for Acquisition, Technology & Logistics, into two Acquisition Under Secretaries, one for Research and Engineering, and the second for Acquisition and Sustainment.

Budget 45

Budget Programming Policies Program Management 45

Greg Brockman

JANUARY 9, 2017

It’s been two years since I wrote #define CTO , in which I documented my quest for a role where I could have scalable impact by writing code. Technical leadership should call the shots while still doing hands-on technical work. This struck me as the right way to run a project to build AI.

Technical Review 52

Technical Review Software Review Machine Learning Artificial Inteligence 52