Okay, let's see if I can set this one up properly...
In my professional capacity, I work with computers. Specifically, I'm a programmer - I deal with a wide range of software development tasks, such as designing web-based systems. One of the webpages I've been working on recently was a pretty dry pipeline page - lots of rows of information, lots of words, not a lot of pictures. It needed a bit of tweaking, so I was industriously working away on a local copy of it. This means I had my computer (named Honeydew) running a Spyce server, which means it can serve Python-based webpages. (I'm sure I've lost 95% of my audience by this point.)
To sum up that last paragraph in more understandable terms, I was working on a webpage, which was being served by my computer, Honeydew.
This means that the address to the local copy of the webpage I was working on was something like http://Honeydew:8000/blah/blah/blah. This was fine for my machine, because I had set up my browser to not look externally for a server named Honeydew.
But I forgot this fact when I finished my work, and sent an email along these lines to my co-workers:
"Hey guys, I was doing a bit of work on the pipeline page, I think I managed to make such-and-such page look a little better, take a look and let me know what you think. Here's the link: http://Honeydew:8000/blah/blah/blah."
So when I click that link on my machine, I get the dry pipeline page I expect, because I have that browser option set. When my co-workers clicked the link, because their computers weren't set up this way, their browsers translated Honeydew:8000 into some kind of automatic Google search for "Honeydew", and they ended up with this page. Everyone agreed that it did look much better.
1 comment:
I showed this post to Claude and he agrees - he quite likes the page as it appears now! :-)
Congrats on your new little girl! How are mum and baby doing?
Post a Comment