Thursday, April 23, 2026

From Zilch to Debt Blaster: The 40-Year Journey Behind a Debt Payoff Program That Refused to Die

Debt Blaster for Mac. Same mission. A clearer name and a modern experience.


A Kitchen Table in 1986

In the summer of 1986, I was not trying to build a brand, start a company, or create an industry. I was a Marine with a computer, a friend with too many bills, and a problem that took more than five hours to solve at a kitchen table. 

At the time, I had no way of knowing that night would set something in motion that would still be alive forty years later, eventually re-emerging under a new name with the same mission it had from the start: help people get out of debt faster.

The whole thing began when a fellow sergeant showed me a magazine article written by a military chaplain about how to quickly pay off debt. The idea in the article was simple, practical, and powerful. Instead of trying to attack everything at once, you focused on one debt, paid the minimum on the others, and kept rolling the freed-up payments forward as each balance disappeared. Years later, people would come to know this as the Debt Snowball. Back then, it was simply a good idea passed from one struggling person to another. My friend asked if I would help him turn that article into a real payoff plan, so we sat down and spread his debts out across the table. Twenty-one of them. We worked through balances, interest rates, payment amounts, order, tradeoffs, and timing. One page led to another, one calculation led to the next, and before long we had spent more than five hours figuring it all out by hand.

By the time we finished, two thoughts had settled in hard. First, this is a really good idea. Second, nobody is going to want to spend five hours doing this.

The First Attempt (And the Drawer)

That was the moment the light came on for me. I had a Tandy 1000 SX, and over the next three months I built a crude little program that duplicated the same payoff process. It was not pretty. It had no polish, no marketing plan, no slick presentation, and no grand vision attached to it. But it worked. It took a mountain of debt and turned it into an ordered plan. At that point, I did not even have a real name for it. I just called it the "payoff program."

Thinking I might be onto something, I showed it to a few fellow Marines. They were not impressed. Maybe the program was too rough. Maybe I was too rough. Maybe I simply did not yet know how to present something useful in a way that made people see its value. Looking back, I had what you might call all steak, no sizzle. I knew how to build something practical. I did not yet know how to make people lean in and pay attention. So I copied the program onto a floppy disk, tossed it in a drawer, and let it sit there.

The original “Payoff Program” sat in a drawer for three years.

That disk stayed in the drawer for about three years, but not because the idea had died. It stayed there because I had not yet become the person who could carry it forward.

The Wall

During that stretch, I decided I ought to take a more respectable route. I started taking night classes, working toward a business degree. That seemed like the practical move. Maybe I needed more education. Maybe I needed more credibility. Maybe the road ahead was going to come through a classroom instead of a keyboard. For a while, I thought that was where things were headed. Then I hit a wall.

I was told I had to take English 101 before I could take any of the other classes I wanted. That was frustrating enough, but the real sting came from what I already knew: a year earlier I had taken the English 101 with Composition CLEP test and missed passing by one stinking point. One point. Not ten. Not twenty. One. And now, before I could even take English 101, I had to take an English placement test. The results came back saying, in effect, that I could read but struggled with writing, so before I could take the course I actually needed, I first had to take a remedial grammar and writing class.

I asked how long the class was.

Eight weeks.

I asked how many credits it gave.

Zero.

That was the turning point.

There was no way I was going to spend two months of my nights off from Marine Corps work taking a zero-credit class just to earn the right to take the class I actually wanted. I quit college on the spot. I went home, turned on my computer, and said to myself, "I guess I need to make this thing work."

The Real Beginning

That sentence mattered more than I knew at the time, because it was the moment I stopped waiting for another path to open up and decided to build one myself. I fooled around with a few small programs, but my mind kept drifting back to that earlier idea, the one that had started at a kitchen table and been shoved into a drawer after nobody seemed to care. Finally, I reached into the drawer, pulled out the floppy disk labeled "Payoff Program," and got back to work.

Looking back, that was the real beginning. Not the first crude version I built in 1986. Not even the day I tossed it in the drawer. The real beginning was the day I decided that if nobody was going to hand me a path forward, I would build one myself.

This time I was serious. I spent the next year of evenings and weekends turning that rough idea into a real product. I rebuilt it, sharpened it, and prepared it for the shareware world. What I lacked in polish, I tried to make up for with persistence. I did not have investors. I did not have a team. I did not have a roadmap pinned to a conference-room wall. What I had was a problem worth solving, a stubborn streak, and a very small amount of startup capital.

$93.95 and a Shot

My initial investment was $69 for Borland's Turbo Pascal 3.0 compiler and $24.95 for Jeff Duntemann's book, Complete Turbo Pascal Third Edition

My original classroom: a $24.95 book that taught me how to build something real.

That was it. No giant stack of venture money. No fancy hardware. No incubator. Just a compiler, a book, a computer, and the refusal to let a useful idea die. I do not have the original Turbo Pascal diskettes anymore, but I still have Duntemann's book. It sits on my bookshelf to this day, its binder cracked and held together with tape. I have kept it not because it is rare, but because it reminds me what this whole thing really started with: a modest bet, a lot of effort, and the willingness to learn by doing.

Naming It Zilch

By December of 1990, I was ready to begin distributing the program. That is when I ran into a problem I had not expected to matter so much: I needed a name.

Back then, shareware authors like me distributed software through bulletin board systems, or BBSs. Those boards often displayed files in one long, continuous alphabetical list. The list would scroll and scroll, and only the savviest users knew how to pause the screen at just the right moment. Naturally, when the list stopped, anything closer to the end of the alphabet tended to remain visible longer. I may have been naive as hell when it came to marketing, but I was not blind. I understood enough to know that visibility mattered, and I needed a product name that started with the letter Z.

So I thought about it for a few days. Then one day it hit me.

Zilch.

Zilch your debts. Make your debts zilch.

That was the name. It was short, memorable, and started with Z, which in those days actually mattered. More than that, it captured the goal of the program in a single word: take debt down to zero. At the time, I had no idea that the name would still be hanging around decades later. I was not thinking about a forty-year journey. I was not thinking about rebrands, websites, Mac versions, iPad versions, or cross-platform development. I was just a young Marine with a useful idea, a computer, and enough stubbornness to keep going.

The First Proof It Worked

Other shareware authors told me not to expect any sales for at least six months to a year. Two months later, I received my first order from Gifford Wherry of Kennewick, Washington. I have not looked back since.

What Quiet Success Looks Like

What happened next was never flashy, but it was real. 

This is what people actually used. No polish. No fluff. Just a plan to get out of debt.

Zilch kept helping people. One household at a time. One payoff plan at a time. One debt at a time. Over the years, the software evolved because the world around it evolved. The original DOS version eventually gave way to newer versions, then Delphi, then a long-running Windows desktop application. Operating systems changed. Development tools changed. User expectations changed. But the mission never changed. The mission was always to take something overwhelming and make it clear, to take chaos and turn it into order, to take a pile of bills and show someone a finish line they could actually believe in.

And quietly, steadily, year after year, people used it. More than 16,000 people. More than $114 million in debt eliminated. 

In 1994, Zilch was featured in Military Lifestyle as a real-world solution helping people get out of debt.



Along the way, it was featured on Good Morning America, profiled in Military Lifestyle magazine, and used by people from all walks of life who were simply looking for a fair shot at financial freedom. Those numbers matter, but not because they make for a nice headline. They matter because each one of those plans belonged to a real person or family who needed clarity, relief, and hope.

Why This Was Never About Software

That is why, to me, this story has never really been about software. It has always been about what software can do for a person when life feels stuck. Debt is not just math. Debt gets into your chest. It gets into your sleep, your marriage, your confidence, and the way you walk through a room. It can make people feel trapped, ashamed, and tired. What I learned all those years ago at that kitchen table was that people do not just need information. They need clarity. They need a plan they can trust. They need to see that freedom is possible. That was the whole reason for the software in the first place, and it still is.

Which brings me to this next chapter.

Why Zilch Had to Change

After all these years, the name Zilch has finally run its course. That does not mean it was a bad name. It was the right name for the shareware era. It was clever. It had personality. It worked in a world where bulletin board visibility mattered and a name that began with Z could literally stay on the screen longer than one that began with A. But times change. And as much as I still appreciate the history behind that name, it no longer says clearly what the product does. Back in 1990, I needed a name that would stay visible on a BBS screen. Today, I need a name that tells people, plainly and immediately, why they should care.

Debt Blaster does that.

Debt Blaster says exactly what it does. Get out of debt faster with Debt Blaster.


That line may sound simple, but simple is hard-won. It took years to get here. It took years to move from a clever name that fit the mechanics of the shareware era to a direct name that fits the clarity people want now. And there is another detail that makes this feel less like a sudden rename and more like the next step that has been waiting for its turn: I have owned the domain for more than ten years. In a strange way, this chapter has been sitting there patiently in the wings, just like that old floppy disk once did.

So no, I do not see this as abandoning Zilch. I see it as honoring Zilch. Zilch got me here. Zilch survived floppy disks, DOS, shareware catalogs, bulletin board systems, Windows versions, and decades of technological change. Zilch proved that a simple idea, if it solves a real problem, can outlast almost everything around it. But Debt Blaster is the right name for what comes next.

And what comes next is bigger than a new name.

The Three-for-One Breakthrough

When I decided to rebuild the software in Delphi FMX, I did it for a practical reason: I wanted both a Windows and Mac desktop version of the software. I also made another deliberate decision while building it. I crafted the default screen size around a 16:9 layout because I wanted any future tutorials or product videos to fit naturally on YouTube. That seemed like a straightforward design choice at the time. It turned out to be a blessing in disguise.

Because the same 16:9 layout that works beautifully for video also fits the iPad extremely well.

So what I thought was a two-for-one decision turned into a three-for-one: Windows, Mac, and a future iPad version as well. The Mac version is close to being ready. The iPad version is already in the planning stage and should not be far behind. That means Debt Blaster is not just getting a new face. It is opening a new front door for Apple users. What started as a rough proof of concept on a Tandy 1000 SX became a shareware product, then a long-running Windows application, and now the next chapter is taking shape for the Mac, with iPad waiting in the wings. Delphi FMX did not just help me modernize an old product. It gave that product a wider future.

The Long View

When I step back and look at the whole journey, it still surprises me. A friend. A forgotten chaplain's article. Twenty-one debts on a kitchen table. A crude program nobody respected. A floppy disk in a drawer. A one-point miss on a test. An eight-week zero-credit class. A hard stop. A decision. A compiler. A book with a taped-up binder. A bulletin board system. A name starting with Z. A first sale. Thousands of families helped. Millions of dollars eliminated. And now, after all these years, not just a new name, but a broader future.

That is the story behind Debt Blaster.

Where This Leaves Us

It did not begin in a boardroom. It did not begin with venture capital, branding consultants, or a polished startup pitch deck. It began with a real problem, a useful idea, and a stubborn refusal to let the idea die. I could not see all of that in 1986. I could not see it when I threw that disk in a drawer. I certainly could not see it standing in front of a college wall that felt like it had just shut me out. But here we are.

Forty years after the first spark, the mission is still the same: help people get out of debt faster, give them clarity, give them hope, and show them a finish line.

Only now, it has a new name.

Debt Blaster.

One More Thing

And before I close, let me say one more thing to any software developers reading this. If you have an old idea, an old codebase, an old project you once believed in, or a product that still solves a real problem, do not be too quick to bury it just because it is not flashy or because the first version did not impress people. Sometimes useful things need time. Sometimes they need better timing. Sometimes they need a better wrapper, a better name, or a better platform. And sometimes they just need the right person to refuse to quit.

If I can do this, so can you.

Stay Connected

Debt Blaster for Mac is coming soon. The iPad version is not far behind.

If you are an Apple user, visit:

👉 https://debtblaster.com

…and sign up to be notified when it is ready.


Enjoy!
Semper Fi
Gunny Mike
https://zilchworks.com



Saturday, April 4, 2026

Everyone Needs a Miyagi: What I Understand Now About Mentorship

I have loved The Karate Kid for years, which is why I use the word "Miyagi." To me, a Miyagi is more than a teacher. He is the kind of man who shapes you by example, raises your standards, and leaves something in you that stays long after the lesson is over. Looking back now at age 67, I realize I was blessed to have that kind of influence in my own life - not once, but twice.

Pictured left to right:  Bill Wallace, me, and Reggie Wournos

The Reunion

In 2008, a bunch of us from GSE got together in Memphis for a weekend.

Most of us had not seen each other in more than 25 years. Time had done what time does. Hair was grayer. Waists were thicker. Rank was no longer something we were chasing. It was something we had already carried and put down.

But the minute we got in the same room, a lot of that disappeared.

For one weekend, we were not old men, retirees, grandfathers, or civilians. We were those same young Marines again, laughing too hard, telling old stories, and picking up right where we left off.

At some point during the weekend, I made a toast to Reggie Wournos.

I thanked him for what he had meant to me back in the early days and told him, in front of everybody, that he had been my Miyagi.

Everybody knew exactly what I meant.

If you ever served around Reggie, you knew. He was one of those Marines. Squared away. Steady. Sharp without needing to show off. The kind of man who could teach you something without making a speech about it.

My First Miyagi

When I was a young Marine on my first four-year enlistment at MCAS Tustin, Staff Sergeant Reggie Wournos was one of the men who helped shape me. He taught me the Marine Corps version of "wax on, wax off."

Not karate. Standards.

Do it again.
Do it right.
Pay attention.
Carry yourself like you belong here.
Take pride in the little things because the little things are never little for long.

He did not just bark orders and move on. He took several of us young Marines under his wing and worked on us. He expected something from us. More important, he made us expect something from ourselves.

And I was not the only one.

If you asked the enlisted Marines from Headquarters and Maintenance Squadron 16, GSE, back in those days, I think you would hear the same thing from a lot of them. Reggie had a way of leaving a mark on people.

Now, if the story ended there, it would already be a good one.

But it does not end there.

My Second Miyagi

A few years later, military life did what military life always does. People moved. Units changed. One chapter ended and another one began.

By then I was at MCAS Cherry Point, North Carolina. I had picked up a couple of promotions and was now a sergeant. I had a new boss: Gunnery Sergeant Bill Wallace.

And just like that, I had Miyagi number two.

Wallace taught me a different set of lessons.

Reggie had helped teach me how to be a young Marine. Wallace helped teach me how to carry responsibility.

He had a reputation, both inside and outside our organization, as the guy who had his stuff together. When people talked about Wallace, they did not talk about flash. They talked about confidence, competence, and trust. He was the kind of man people counted on.

And if you worked for him, you learned why.

So yes, I was lucky. Luckier than I knew at the time.

I had one Miyagi early, and then another one later.

The Realization

Back in Memphis that night, after the toast and after the laughter had died down a little, I found myself in a private conversation with Reggie.

By then, we were both retired, me as a Gunnery Sergeant and Reggie as a Chief Warrant Officer 4.

I thanked him again for being my Miyagi.

Like a humble man usually does, he tried to wave it off.

But I meant it, so I pressed the point.

Then I asked him a question I had never asked before.

"Who was your Miyagi?"

He looked at me and said, "Bill Wallace."

That stopped me cold.

In one sentence, two separate chapters of my life snapped together.

The only way I can describe it is this: it was like having a light bulb go on inside another light bulb.

First I realized Reggie had a Miyagi too.
Then I realized it was Bill Wallace, my Miyagi number two.

Out of all the people Reggie could have named, he named the one man who had later shaped me too.

That hit me hard.

Because all those years, I had thought of these as two separate blessings in my life. Two separate men. Two separate chapters.

But they were not separate.

They were connected.

What Wallace built in Reggie, Reggie helped build in others.
What one man took seriously enough to pass on, another man was humble enough to receive.
And somewhere along the line, some of it made its way into me.

What Good Mentors Do

That is what good mentors do.

They do not just help you in the moment.
They put something in you that keeps working long after they are gone.
They steady your hands.
They raise your standards.
They change the way you carry yourself.
And if you are paying attention, they become part of what you pass on to somebody else.

Everybody needs a Miyagi.

I was blessed enough to have two.
And in the end, they turned out to be part of the same light.

- Michael Riley

Friday, January 23, 2026

Low Carb Breakfast #01 - 3.2 Net Carbs

Low Carb Breakfast #01 - 3.2 Net Carbs

Yes! That's Real Buttered Toast!

You are probably thinking, "How can you have two slices of buttered toast and keep that breakfast to 3.2 net carbs?" 

The secret is Sola Low Carb bread. Before when I was doing low carb I tried a different bread (Hero). Hero bread was hard to find in local stores. When I did find a local store that carried it, it was either out of stock, or too close to the "eat by" date.

So, I stared at the bread shelf for a long time. And... I saw a huge 1G Net Carbs on a wrapper. It was a brand of bread I had not heard about - Sola

I bought a loaf.
Brought it home.
And...

I've been hooked ever since. And the best part... it's always in stock and has an extend shelf life.

1G Net Carbs Sola - Always in Stock

Sola Seeded - 1G Net Carbs

Here is the breakdown of my breakfast:

Qty Item Net Carbs
2 Hard Boiled Eggs 1.2
2 Bacon Strips 0.0
2 Slices Buttered Toast (Sola Seeded) 2.0
Total Net Carbs 3.2

My wife made hard boiled eggs yesterday, and the bacon was cooked a few days ago. I reheated the eggs and bacon in the microwave for 45 seconds on 50% power (twice). Came out perfect.

I can't express how grateful, and pleased I am to have discovered Sola bread. It really is delicious just like it says on the wrapper.



Enjoy!
Semper Fi
Gunny Mike
https://zilchworks.com



Tuesday, December 2, 2025

Delphi Tip of the Day: Editor Font > Line Height

Delphi 13 Options: Editor > Display > Font > Line Height

I recently installed Delphi 13 on my new development machine. And ever since I watch Alister Christie's Code Font video, I've been hooked on using Consolas. I like how it distinguishes between zero and capital "O".

When I brought up the options to change the editor font to Consolas I noticed a new Line Height feature. I played around with some different line heights and for me personally, I settled on 1.2 which fits my eye nicely.

Line Height of 1.2 fits my eye nicely


I don't remember seeing Line Height in Delphi 11. And a quick confirmation of the Delphi 11 IDE options proves it's not there. I installed Delphi 12 but never really used it. I did a quick check and lo and behold the Line Height feature is available in Delphi 12. I must have missed it because I totally skipped using 12 all together.

I also decided to check out if there were any other fonts I might like. Here is the list of  alternatives to Consolas that ChatGPT gave me. I tried the ones that were available in Delphi and decided to stick with Consolas.

Font What makes it good
Fira Code A modern monospaced font with programming ligatures (so =>, !=, ->, etc. can render as single, clean glyphs). Improves readability of symbol-heavy code.
JetBrains Mono Designed specifically for developers: clean shapes, tall lowercase letters (makes code easier on the eyes), and good clarity even at smaller sizes.
Hack A clean, well spaced monospaced font — good if you like clear distinction between similar characters (0 vs O, l vs 1). Good for plain-text editing or coding without fuss.
Cascadia Code Created by Microsoft for terminals/editors. Has optional ligatures and good support for modern coding environments. Works nicely for both GUI IDEs and terminals.
Source Code Pro A straightforward, clean monospaced font with consistent spacing and good legibility — useful if you prefer simplicity over styling.
Iosevka A very flexible monospaced font (lots of glyph/width/variant options), popular among people who want tight control over how their code appears.
DejaVu Sans Mono A classic, reliable open-source monospace font with wide character coverage and solid legibility — good fallback or default choice on many platforms.


Here is Alister Christie's video on code fonts I watched many years ago. Wow, this video was released in 2013.



Enjoy!
Semper Fi
Gunny Mike
https://zilchworks.com



Saturday, November 29, 2025

How Ray Konopka Improved My Delphi Code Overnight

Every now and then, you get a piece of advice that stays with you. Not because it was dramatic or complicated, but because it quietly made everything better.

Two years ago, I sent a simple question to Ray Konopka — the Ray Konopka — about his coding style. I had noticed that his Delphi method declarations didn’t look like the IDE defaults. He added spaces inside parentheses and brackets, and his code just… breathed better. It had clarity.

I finally went back and reread that email thread, and I realized something.

The guidance Ray gave me that day permanently changed how I write Delphi code.

This blog post is long overdue.

How It Started

Here is the short version of what I asked Ray. I wanted to know why his method declarations looked like this:
procedure FormCreate( Sender: TObject );

Instead of the standard IDE formatting:

procedure FormCreate(Sender: TObject);

My question was simple:
Is there a setting that does this automatically? And why do you prefer this style?

Ray’s reply was thoughtful, detailed, and generous. And it opened my eyes to something subtle but powerful.

Why Ray Adds Spaces Inside Parentheses

Ray explained that adding a space after the opening parenthesis and before the closing parenthesis helps your eyes distinguish the method name from the parameter list. It creates a visual delimiter that makes code easier to scan.

He illustrated this beautifully by showing side-by-side method declarations from the TString class. With spacing added, the entire block becomes more readable and less cramped.

When you look at example after example, the difference becomes obvious — almost impossible to ignore.

Smart Tab: The Secret Weapon

The second thing Ray emphasized was the use of Smart Tab.

With Smart Tab enabled, wrapping long parameter lists becomes far easier and dramatically cleaner. Ray demonstrated it with a real method declaration on multiple lines, perfectly aligned with a single press of the Tab key.

After seeing that, I turned Smart Tab on — and I’ve never turned it off again.

Delphi 13 Options - Smart Tab

https://docwiki.embarcadero.com/RADStudio/Florence/e/index.php/Source_Options#Options_tab

The Three Rules That Changed My Coding Style

After just three days of practicing what Ray shared, I wrote him back with a summary of what made the biggest impact on my coding clarity. Here were the top three:

1. Smart Tab On

It makes aligning wrapped parameters effortless. This one toggle improves readability more than people realize.

2. Spaces after ( , [ and before ] , )

This small visual pause gives every method declaration and parameter list more clarity. It is now second nature for me.

3. Two blank lines between method implementations

This simple spacing rule makes code blocks easier to navigate, search through, and mentally organize. It is one of the fastest ways to reduce visual clutter.

These three rules alone made my Delphi source code noticeably cleaner.

Not fancy. Not complicated. Just better.


Ray’s Full Coding Style Guide

At the end of our email exchange, Ray did something incredibly generous. He made the full Raize Delphi Coding Style Guide available as a free PDF download.

If you want the complete reference, you can access it here:
https://raize.com/wp-content/uploads/RaizeDelphiCodingStyleGuide.pdf

This is required reading for any Delphi developer who cares about clean, consistent, readable code.

Two Years Later

I’ve been following Ray’s guidance ever since that email exchange. You’ve even seen it in the code I’ve generated or shared online — it became the standard I hold myself to.

What surprised me most is how such small adjustments created such a big improvement. Enough improvement that I felt compelled to finally write this post, two years delayed but not forgotten.

Ray — thank you for the clarity, the generosity, and the craftsmanship you bring to the Delphi community.


Enjoy!
Semper Fi
Gunny Mike
https://zilchworks.com

P.S.
Over the past two years, every time I asked ChatGPT to help me generate Delphi source code, I asked it to follow the Konopka Style Guide. It became my north star for clean, readable formatting — and even AI had to get on board.


Wednesday, November 26, 2025

Delphi Tip of the Day: Restore Tools > Manage Features... After an ISO Install

 



I recently installed Delphi 13. I went back today to install the Help and Samples and could not.

Tools > Manage Features,,, gave me the following error:



WTF! 

I remember this happening to me about 3 years ago. I was as lost today as I was back then. 

How do you recover from this?
It's 2025, how can Embarcadero still let this crap happen?


A simple dialog that says "Would you like to switch to online mode instead?" which then gracefully handles the fact that the temporary ISO directory used during the initial install is no longer available.

Aren't we paying enough money for Embarcadero to put this type of fix in place?

Anyway, I dug up the old instructions Glenn Dufke posted three years ago when this happened. And his instructions worked today, just like they did back then.


If this happens to you, here is the fix:

  1. Open an elevated Command Prompt
    Right-click Command Prompt ? Run as Administrator

  2. Navigate to your RAD Studio 13 bin folder
    cd "C:\Program Files (x86)\Embarcadero\Studio\37.0\bin"

  3. Run the command Dufke mentioned
    getitcmd.exe -c=useoffline typo
    getitcmd.exe -c=useonline


Semper Fi
Gunny Mike
https://zilchworks.com

Monday, August 18, 2025

Zilch and Delphi: Standing Strong Since 1991

 


Zilch and Delphi: Standing Strong Since 1991

I’ve heard it said that if you don’t tell your story, you may not like the story that’s been told. For more than three decades, the story of Zilch debt reduction software — built on Turbo Pascal and powered by Delphi — hasn’t really been told. Yet both Zilch and Delphi share a remarkable trait: they’ve quietly endured while so many giants of the software world have faded away.

Turbo Pascal first appeared in 1983, giving programmers an accessible, structured language at a fraction of the cost of its competitors. Three years later, in 1986, I saw Pascal for the first time when my college professor put C and Pascal source code side by side on the blackboard. The C code looked cryptic. The Pascal code? Clear as day. That choice — Pascal — shaped my entire path as a programmer.

Five years after that moment, in 1991, Zilch was born. And from the very beginning, it carried Pascal in its DNA. As Delphi evolved, Zilch evolved with it. The same clarity and stability that drew me to Pascal has allowed Zilch to keep going strong for decades.

And here’s the part I think the Delphi community will appreciate most: just as Turbo Pascal and Delphi have stood the test of time, so has Zilch. While giants like Lotus 1-2-3, Netscape Navigator, and MSN Messenger have all faded into history, Pascal/Delphi continues to endure — and so does Zilch.

👉 I just published the full story, including a list of 25+ once-dominant apps that disappeared while Zilch endured. You can read it here:
Zilch: Standing Strong Since 1991

If you’re part of the Delphi community, it would mean the world if you visited, left a comment, and helped boost the presence of this new blog. Your voice will help shine a light on one of Delphi’s quiet success stories — and on the remarkable longevity of Zilch and Delphi, standing strong together since 1991.

Semper Fi,
Gunny Mike
https://zilchworks.com