Digital Ladybug Labs

yahoo:

image

I’m delighted to announce that we’ve reached an agreement to acquire Tumblr!

We promise not to screw it up. Tumblr is incredibly special and has a great thing going. We will operate Tumblr independently. David Karp will remain CEO. The product roadmap, their team, their wit and…

(via xkcd: Real Programmers)
Getting rid of old code

devopsreactions:

image

Submitted by Stephen

nycgov:

imageToday, Mayor Bloomberg announced the selection of Micro Office Solutions to develop, launch and operate the Harlem Venture Space, a new business incubator to be located on 118th Street in Harlem. The incubator will be part of the City’s network of co-working spaces to support entrepreneurship…

snipeyhead:

@dbareactions:

When they try to take away my domain admin permissions

snipeyhead:

@dbareactions:

When they try to take away my domain admin permissions

jstn:

alwaysintransit:

Fuck this bullshit.

My sentiments exactly. Google Reader does two things that are going to be very hard to duplicate: 1) parsing of broken feeds, and 2) historical archiving. The parsing piece is especially important, RSS (as a format) is a huge mess and Google has spent a long time normalizing and fine-tuning the ingestion of all the poorly implemented feeds across the internet. Since so many were made by hand, especially in the old days, parsing RSS is a bit like parsing HTML (i.e., you have to assume it’s going to be broken most the time). Code that deals with flawed code written by humans is among the hardest to write.
I wonder if they’ll continue to ingest RSS feeds, if only to collect the data? If so, I hope they’ll consider making it available as an API (the “current” Google Reader API was never official). If not, I hope they open source their parsing code so the work isn’t lost. It’s the kind of thing Google was uniquely positioned to do, vast resources and nearly infinite sample data to analyze.

jstn:

alwaysintransit:

Fuck this bullshit.

My sentiments exactly. Google Reader does two things that are going to be very hard to duplicate: 1) parsing of broken feeds, and 2) historical archiving. The parsing piece is especially important, RSS (as a format) is a huge mess and Google has spent a long time normalizing and fine-tuning the ingestion of all the poorly implemented feeds across the internet. Since so many were made by hand, especially in the old days, parsing RSS is a bit like parsing HTML (i.e., you have to assume it’s going to be broken most the time). Code that deals with flawed code written by humans is among the hardest to write.

I wonder if they’ll continue to ingest RSS feeds, if only to collect the data? If so, I hope they’ll consider making it available as an API (the “current” Google Reader API was never official). If not, I hope they open source their parsing code so the work isn’t lost. It’s the kind of thing Google was uniquely positioned to do, vast resources and nearly infinite sample data to analyze.

lickypickystickyme:

evangotlib:

Go home Google.  You are drunk.

very fucking drunk.

nycgov:

image

Twenty middle and high schools have been selected for the new Software Engineering Pilot program to begin at the start of the next school year. The schools will receive comprehensive computer science and software engineering curriculum for the 1,000 students expected to participate this fall…

NYC Tech Companies Tell their Stories

nycgov:

With the launch of the “We Are Made In NY” initiative, some New York City companies have shared their stories at www.wearemadeinny.com/video.

To get involved, submit a video following these guidelines to introduce your Made In NY company to New York CIty. We may feature your video on the Made in NY Tumblr.

heygeeksugar:

Sweetest picture on the Internet today.
10 Things You Didn’t Know About Bill Gates

heygeeksugar:

Sweetest picture on the Internet today.