TekMetrics (Brainbench) | Transcript ID 91390 | Web Programmer

On September 5, 1999, I earned my TekMetrics Web Programmer certification. This was not just another badge. It marked a point in time when the web was still young, unpredictable, and full of possibilities, and when being a web programmer meant something very different from what it does today. After the name change, I received a rebranded certificate for Brainbench.

This was before Web 2.0. Before social media shaped online identity. Before modern frameworks, build pipelines, dev consoles, and giant JavaScript ecosystems existed. The web in 1999 was hand-built, fragile, experimental, and constantly evolving. You needed to know what was happening behind the curtain, not just how something looked.

Most websites were still static. Server round-trips handled most logic. JavaScript, while available, was not yet fully trusted. CSS was still developing. DHTML felt experimental. Table layouts ruled everything. Netscape Navigator and Internet Explorer were in open warfare, and each one treated code like a suggestion rather than a standard.

And all of this had to work under one massive, defining constraint:

Page weight mattered

Back then, most people were still on dial-up internet. If you were lucky, you had a 56k modem. If not, you were probably stuck at 28.8. Cable internet was only beginning to show up in certain areas, and DSL was just starting to gain popularity. Even so, the experience was slow, noisy, and fragile. Connecting to the internet literally sounded like machinery struggling to wake up.

And in that environment, performance mattered in a way modern developers rarely experience.

The ideal target for a home page back then was about 64 KB total. Not per asset. Not per script. The entire page: HTML, images, stylesheets, and JavaScript combined. And that size goal was tied to what user-experience research considered acceptable: roughly a 2-second load time before people lost patience.

Not per image.
Not per script.
The whole experience.

If you built something bloated, users did not see a sluggish animation.
They saw a blank loading screen.
They heard modem tones.
They waited.
Or they gave up.

JavaScript was not trusted yet. Browsers often had it disabled. DHTML was experimental. CSS was still evolving. Internet Explorer and Netscape Navigator treated standards like suggestions. Most of the logic still ran on the server. Pages blinked between requests instead of dynamically updating.

And even beyond technology, trust in the internet itself was still shaky.

I worked places where developers did not even have internet access because management did not trust employees to use it responsibly. Some saw the internet as a liability, something too risky to allow in the workplace at all. Imagine being a web programmer without access to the web. That was a real situation.

So when TekMetrics created its Web Programmer certification, it meant something. Their exams did not test trends or buzzwords. They tested whether you understood the web, how it worked, where it failed, and how to build something reliable in a constantly shifting technological landscape.

For someone like me, who was self-taught through curiosity, experimentation, and persistence, this certification provided something powerful: validation. It proved that my understanding was real, measurable, and respected.

It was not a degree.

But it was an achievement in a time when the internet was still finding itself, and so was I.

And I am still proud of it.