Fred Lackey

Enlisted at Seventeen

Before there was any code, there was a decision made at seventeen years old. An enlistment in the United States Army — infantry — as a teenager who wasn't waiting around for the conventional path to begin.

The Army came first. The Marine Corps followed. Moving between branches is uncommon; doing it with the intensity that characterized the rest of a career that followed is not surprising in hindsight. The Marines offered something the Army hadn't: a legal specialty, an assignment to the prosecution staff of a Marine Corps Air Station, and an unexpected intersection of two disciplines that would define the next thirty years.

MCAS Cherry Point, North Carolina

Marine Corps Air Station Cherry Point is one of the largest Marine Corps air installations in the world, home to Marine aircraft groups, Fleet Readiness Centers, and a full legal apparatus for handling the range of matters that arise on a large active-duty base. It is not a quiet posting.

The assignment was to the Law Center — the prosecution staff — under the authority of a Special Assistant United States Attorney. A Law Specialist's role at a station like Cherry Point meant direct exposure to the full complexity of military justice and federal law. The Uniform Code of Military Justice does not offer simplified cases. The matters that reach the prosecution staff are the ones that matter most.

Federal Cases & Capital Matters

The prosecution work was not administrative. The cases that came through the Law Center at Cherry Point were the kind that require precise documentation, careful witness management, and a thorough understanding of both military and federal law. Some were federal felony matters. Some were capital cases. All were handled with the full formality of prosecution before military courts.

Working directly with NCIS means working on investigations that span criminal conduct at sea, criminal conduct on federal installations, and criminal conduct that implicates federal statutes. The Special Assistant U.S. Attorney's office doesn't handle parking violations. The cases include murder, crimes at sea under admiralty jurisdiction, and serious federal offenses that require the same rigor as any federal courtroom.

The experience of working in prosecution — building cases, managing documentation, understanding the structure of legal argument, learning how investigators think — turns out to be surprisingly transferable to software architecture. Both disciplines require precision, an ability to hold complex interdependencies in mind simultaneously, and a deep intolerance for ambiguity. A bug in prosecution has consequences no debugger can roll back.

The Other Half of the Job

The legal work was the assignment. The software work was what happened because the base needed it done and there was someone there who could do it.

MCAS Cherry Point in the early 1990s ran on Novell NetWare and Banyan VINES — enterprise networking platforms that required real expertise to maintain and extend. Word processing packages used by base personnel across multiple departments needed modification to accommodate operational requirements. And the Law Center's own operations needed software support that didn't exist off the shelf.

Writing in C and C++ for a military base isn't the same as writing for a startup. The users are not optional, the uptime expectations are serious, and the consequences of software failure are not an engineering postmortem — they are operational problems on an active military installation. The discipline that comes from that environment doesn't leave when the uniform does.

Two Disciplines in the Same Person

What is unusual about this period is not that it produced a capable soldier, or a capable legal professional, or a capable network administrator. What is unusual is that it produced all three simultaneously — and that the combination proved more durable than any of the parts individually.

The legal training built a kind of structured thinking that software architecture depends on: the ability to identify precisely what a system must do, what it must not do, and what happens when the rules are broken. The military environment built operational discipline — the understanding that systems exist to serve real people under real pressure, and that failure has weight.

The software instincts, meanwhile, provided something the legal work could not: the ability to automate, to systematize, to take a repetitive manual process and make it run itself. That instinct would define every subsequent engagement — not the drive to write more code, but the drive to write less of it by building the right machinery.

The Road Not Taken

After leaving the Marine Corps, the trajectory pointed toward law. A position at a prominent law firm in Orlando, Florida — working with a managing partner who sat as a U.S. Bankruptcy Court panel trustee. Corporate law, real estate, probate, complex bankruptcy. The range of exposure was deliberate. The Florida Bar exam was the next step.

The decision to pursue software over law is not a story of abandonment. The legal foundation didn't disappear — it became part of the engineering vocabulary. Precision in specification. Rigor in documentation. The instinct to ask what a system must not do as carefully as what it must. Those are not software engineering traits. They are legal reasoning traits. They happen to be indispensable in software architecture.

The legal work also demonstrated something concrete: the ability to deliver $80,000 in annual IT cost savings while operating in an environment whose primary function was legal support. That kind of dual capability — the technical instinct operating in the background of a non-technical assignment — would recur throughout a forty-year career.

1991–1994