Recent searches
Search options
Administered by:
@inthehands @nikclayton This all reminds me of one of the first actual "debugging" tools I ever used (this was before I had done enough "what-people-who-think-HTML-isn't-programming" programming to use or need a traditional debugger for it).
"Reveal Codes."
This was the magic WordPerfect command from the 80s/90s that showed you why, for example, the fricking italics weren't working or that one section on that one page was just a little bit off. "Reveal Codes" popped up a little text area (not even a window, this was DOS, after all) showing a section of your text and all the associated "codes", which were tags indicating the structure or appearance of whatever they contained.
A *lot* like HTML.
And using Reveal Codes to figure out where your document was going wrong, and why, and how to fix it, was a lot like wrangling HTML to get your web page to have the right structure and appearance...and, as noted, also like trying to figure out how to get a cranky API to get the kind of output that you need it to deliver.
@inthehands @nikclayton I'd actually go so far as to say that Reveal Codes back in the 80s made HTML almost instantly comprehensible, even with emerging complexities like (then-larval) style sheets, in the 90s. And *that* in turn made it possible for me to make the jump to web development as a career when a previous one started to head south -- more so in many ways than having a reasonably decent background in "what the annoying pedants call programming" programming as well.