The comments table has been repopulated! I’m currently working on restoring their hierarchy. For ease, I’m working backwards, from the newest to the oldest posts. Please bear with any site instability/sluggishness you might encounter. Cheers! ☺


“If you read someone else’s diary, you get what you deserve.” —David Sedaris

This all started off in written form back when I was a kid. As an introverted only child with both parents at work most of the time, I had a lot of time to myself. So when I learned to write and that writing down my thoughts for posterity was a thing people did, I went at it myself.

I still have some of those papers which are basically just short recollections of the current day at kindergarten or elementary. Sometimes funny, oftentimes doodles of robots, I don’t think they’re particularly publishable to the internet at large, much less have an appreciative audience.

The bulk of these entries start off from high school and were largely typed on a then-modern 80386SX in plain text files (anyone remember Wordstar?) saved on 3½″ floppies. They were eventually transferred to Microsoft Word (receiving italics, boldface, tables, and proper typography in the process) and then to XHTML 1.1. They currently exist as XML-typed records in a MySQL database served through a custom PHP-based CMS. How far the times have come!

You’re welcome to comment and message me on these. However, please remember the historical context in which some posts were written. While some posts are mundane (I’ve always been my worst critic), if you read enough, you’ll notice the change in the topics, entry length, grammar and vocabulary, and tone of my writing.

If you see any typos or lapses in grammar, no need to call me out on them. I’ve probably seen them already as I was digitizing the physical copies of these entries and during their conversion from plain text to Word to XML. I’m keeping these as close as possible to their original form.

P.S. Some entries require further explanation or clarification and any editorial additions will be indicated in a box that looks like this.
P.P.S. It’s not readily apparent but there are a number of unpublished entries to this blog and large gaps of time between entries. Let me explain this briefly.

For the unpublished posts, those cover my life as a teenager full of angst and hormonal confusion from 1995 to 2000. While I initially balked at adding these, the thought of losing them won out. For purposes of posterity, these entries have been included in the database. After careful review, however, I’ve considered some of these entries to be too private for general public consumption. Maybe someday I’ll decide to eventually make them public.

As for the long hiatus between entries, I have only life to blame. While life certainly went on during the intervening periods, I just either didn’t see fit to make those entries public (for my own, as well as others’ privacy), events weren’t that important to write about, or I was just too busy at the time to write anything.

If you’re terribly curious about the more private entries, drop me a line and I’ll consider giving you access.

Initial Thoughts on Google AMP Project

Written by Raymond Santos Estrella on Thursday, 04 February 2016. Posted in 2016

Initial Thoughts on Google AMP Project

I’ve been tinkering with Google’s Accelerated Mobile Pages Project (hereinafter AMP) to see if I could utilize it on other projects either wholesale or as part of the current main spec. For a brief introduction, Google is pushing AMP as a way of serving a lighter, faster loading content page to users (ideally) coming from its search engine results. By enforcing a stricter set of rules for building an HTML page (asynchronous Javascript, statically-sized resources, inline CSS at < 50Kb in length, CDN-served cached pages, etc.), we’re talking about a significant reduction in page downloading time and faster browser rendering. How the “standard” achieves the speedup is discussed further at their project page with source code hosted at Github.

On Making Document Interconnection Possible, part 1

Written by Raymond Santos Estrella on Tuesday, 26 January 2016. Posted in 2016

I’ve been making some more headway into designing the site’s interconnection framework between documents. They’re still mostly just a combination of sketches and musings with no particular direction. While I still don’t know how to fully implement this feature, I’m beginning to gain some insight into the fundamentals of this problem and how I might be able to solve it. I know that I’ll have to make sure that the framework for mapping out what documents are related to each other, add semantic meaning to that connection, and figure out a ranking algorithm to show the most relevant documents first is as robust as possible.


Written by Raymond Santos Estrella on Thursday, 07 January 2016. Posted in 2016

Where I'm so burned out I just wrote and made a list of things to do

Alright, just about done with the next batch of updates for Republic Acts. I know that this batch really took quite a while to complete. I tried to complete it all before the new year but I just needed more time. What can I say except that the holidays got in the way and I was feeling a bit burned out on working on the site relaunch and all the editorial work so I took a day off here and there.

Detailed Consequences of the Corpus Juris Relaunch

Written by Raymond Santos Estrella on Friday, 18 December 2015. Posted in 2015

Some More Lessons to Learn From My Fail

Ever since I was working on the Corpus Juris redesign, I had been both anticipating and dreading the moment when I would flip the switch from the old site to the new one. Anticipating because, of course, it’s exciting to launch a site! Dreading because I was afraid of the inevitable dip in Google rankings for my pages. All the old URLs would no longer work with the new site. 301 redirects would help alleviate some of the pain but it wouldn’t be a perfect solution. It’s well known in the SEO world that 301s don’t exactly capture the whole value of a link in one’s favor.

Post-Launch Lessons Learned

Written by Raymond Santos Estrella on Wednesday, 16 December 2015. Posted in 2015

Learn From My Fail

Spent the day cleaning up my buggy metadata implementation. I realized late last night that the method I used was only partially correct. I followed the examples from which, by the way, isn’t exactly the most well-documented site. In any case, when I used Google’s Structured Data Testing Tool, I came up with a partially validating schema for Articles. However, a more encompassing schema existed which I wasn’t ready for. Furthermore, the method I used to validate for the Article schema wasn’t the best way to go about things since it also broke HTML5 validation.