Posting about Work
From Alpha-Geek.com:
I was even able to find a blog of one of their workers – Paul’s Journal – though he doesn’t seem to talk about his $job too much.
It is hard to post about $job, because very little of Bloglines backend architecture is considered public information. For example, from the companies Blogging Policy Document:
“It is the Company’s policy that all employees, agents and contractors must keep confidential all information about IAC Search & Media or any IAC company’s operations, products and business activities that has not been made public …”
Which I believe pretty much includes how our custom distributed filesystem works, or how Bloglines is scaling (other than saying that memcached is awesomr, which is public), or even the details behind our new Atom Parser. It isn’t something I am too concerned about really, you don’t see anyone from Google posting the technical details behind Google Reader. It is just a standard in so many coporations to keep information close.
As Requested in the $job Blogging Policy Document: “The views expressed in this blog are my own and do no necessarily reflect the views of my employer.”
June 26th, 2006 at 12:21 am
are you sure you are allowed to mention and or quote your $job blogging policy document?
June 26th, 2006 at 1:00 am
Crap, I didn’t think of that
June 26th, 2006 at 1:12 am
Paul:
I was just happy to hear that there are engineers over at Bloglines that are passionate, working, and aware of the problems. And that those engineers are capable and are paying attention to what is being said.
It was a “sight for sore eyes” to find that there is someone out there doing this for Bloglines. Keep up the good work, Paul, it is appreciated!
June 26th, 2006 at 8:38 am
I really am appreciative of the changes made so far. As I said in the post you linked to, there is no silver bullet and getting everything perfect in one shot is not possible. Hopefully we will continue to see further improvements in the upcoming weeks and months.
July 13th, 2006 at 11:29 am
While I’m with Sam in appreciating your vast improvements to date, I wonder if it would be possible to publish the test cases that you use to test your parser. (You *do* have test cases, right?) It would go a long way towards improving interoperability. Surely we should all be competing on features instead of formats. (Parsing formats isn’t a feature as far as I’m concerned; it’s a prerequisite.)
Just a thought.
July 13th, 2006 at 11:54 am
Mark,
We have based many of our test cases on the FeedParser test cases. We have slowly been adding more ‘real world’ test cases as we find & fix problems. Our test system uses short Lua scripts to verify the expected results.
I don’t know if we can easily release these test cases, but I will bring it up.
-Paul
July 18th, 2006 at 8:47 am
First, I’m curious why the value of atom:updated keeps changing on this entry?
Second, if you have test cases not covered by the feedparser, I’d love to help get them added to the feedparser.