The short version
I did not plan a conventional career, and apparently the career did not plan one for me either.
I served in the United States Army as an infantryman, including service connected to Operation Iraqi Freedom. The military gave me a framework that has followed me into every profession since: understand the mission, identify what matters, communicate clearly, adapt quickly, and do not confuse activity with progress.
After the military, I moved heavily into technology. I worked across software, telecom, Linux infrastructure, networking, cybersecurity, web systems, databases and VoIP. I have spent years building and breaking systems, writing code, troubleshooting problems that were supposedly impossible to reproduce, and learning the ancient technical ritual of discovering that the problem was, in fact, a configuration file nobody remembered changing.
Technology and engineering
My technical work includes PHP, Python, C++, MySQL and PostgreSQL, Linux server administration, web applications, APIs, data processing, business automation, AI and LLM integrations, Asterisk, FreePBX, SIP and VoIP systems. I am particularly interested in technology that solves an operational problem rather than technology that exists because someone wanted to put the letters “AI” on a PowerPoint slide.
Cybersecurity became a natural extension of that work. If you understand how systems are built, how they communicate and how users actually behave, you quickly discover where those systems break. My focus has included infrastructure hardening, network security, VoIP security, risk analysis, vulnerability assessment, incident readiness and practical defensive design.
The legal world
My transition into the legal industry was not exactly a childhood dream. I entered personal injury practice from the technology side and eventually moved into case management, litigation support and settlement negotiations. That work required a completely different technical vocabulary but a surprisingly familiar thought process: identify the facts, understand the rules, examine the evidence, find the weak points, predict the other side’s response and make a decision under pressure.
My experience has included motor-vehicle accidents, premises cases, municipal matters, wrongful-death claims and medical malpractice matters. Settlement work requires more than asking an adjuster for “a lot of money,” although, remarkably, that strategy has been attempted by actual professionals. It requires liability analysis, damages analysis, medical-document review, policy-limit strategy, evaluation of comparative negligence, familiarity with New York practice, litigation posture, negotiation psychology, carrier behavior, client expectations and the economics of taking a case further.
Negotiation is where law, psychology and strategy become inseparable. An offer is not just a number. It reflects the carrier’s evaluation of liability, injury, credibility, venue, litigation risk, medical proof, policy exposure, prior negotiations and how convincingly each side can explain what happens next if nobody moves. Good negotiation is therefore part legal analysis, part evidence management, part communication and part knowing when to stop talking.
Writing, business and everything else
I write because there is a large gap between how professions describe themselves publicly and how they actually function on an ordinary Tuesday afternoon. My books and publications cover personal injury practice, settlement negotiations, client management, technology, cybersecurity, AI, VoIP, business operations and the occasional subject that annoyed me enough to become an article.
I am also involved in entrepreneurial projects, including Notary Ninjas, LLC and technology-focused business initiatives. My approach to business is similar to my approach to engineering and negotiations: remove unnecessary layers, make the process understandable, automate what should be automated, keep humans where judgment matters, and never create three meetings to solve something that could have been fixed in one competent email.
The operating philosophy
I value direct communication, preparation, evidence, technical competence and accountability. I do not believe every complex problem requires a complex solution. Often the hardest part is correctly defining the problem before everyone starts spending money solving the wrong one.
That is what ties the different parts of my background together. Whether I am looking at a software architecture, a compromised server, a VoIP deployment, a law-firm workflow or a settlement file, I am looking for the same things: What happened? What are the constraints? What is the risk? What does the other side know? What are we missing? And what is the shortest defensible path to the result?