| — | Flavor Flav |
After all the talk of VCs vs. Founders.
This.
This is the kind of relationship we’re all hoping to build with the founders we back.
Congratulations to all involved.
via bijan
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 irreverence will all remain the same as will their mission to empower creators to make their best work and get it in front of the audience they deserve. Yahoo! will help Tumblr get even better, faster.
Tumblr has built an amazing place to follow the world’s creators. From art to architecture, fashion to food, Tumblr hosts 105 million different blogs. With more than 300 million monthly unique visitors and 120,000 signups every day, Tumblr is one of thefastest-growing media networks in the world. Tumblr sees 900 posts per second (!) and 24 billion minutes spent onsite each month. On mobile, more than half of Tumblr’s users are using the mobile app, and those users do an average of 7 sessions per day. Tumblr’s tremendous popularity and engagement among creators, curators and audiences of all ages brings a significant new community of users to the Yahoo! network. The combination of Tumblr+Yahoo! could grow Yahoo!’s audience by 50% to more than a billion monthly visitors, and could grow traffic by approximately 20%.
In terms of working together, Tumblr can deploy Yahoo!’s personalization technology and search infrastructure to help its users discover creators, bloggers, and content they’ll love. In turn, Tumblr brings 50 billion blog posts (and 75 million more arriving each day) to Yahoo!’s media network and search experiences. The two companies will also work together to create advertising opportunities that are seamless and enhance user experience.
As I’ve said before, companies are all about people. Getting to know the Tumblr team has been really amazing. I’ve long held the view that in all things art and design, you can feel the spirit and demeanor of those who create them. That’s why it was no surprise to me that David Karp is one of the nicest, most empathetic people I’ve ever met. He’s also one of the most perceptive, capable entrepreneurs I’ve worked with. His respect for Tumblr’s community of creators is awesome, and I’m absolutely delighted to have him and his entire team join Yahoo!.
Both Tumblr and Yahoo! share a vision to make the Internet the ultimate creative canvas by focusing on users, design — and building experiences that delight and inspire the world every day.
could this be more perfect? I am not sure
Daniel Johnston - True Love Will Find You in the End
19 feet away from history.
This is the office where I worked in 2007. That’s me on the bottom left corner, hard at work making the Meth Minute 39 series for Frederator Studios ( who were at the time developing a little show you may have heard of called “Adventure Time”).
See that long-haired guy all the way on the right side? That’s David Karp in the preliminary stages of inventing Tumblr. At this point, the only people who had heard of Tumblr are in the room. A lot can happen in 6 years! But don’t worry, everyone… he knows why we all love Tumblr and he’s not going to let it get ruined! I got a feeling.Awesome.
This was the year I joined Tumblr. Living way up in Seattle, I felt like I’d stumbled onto a well-kept secret because there weren’t that many people here then, and those of us who were here were all following each other, for the most part. It felt like a small town.
It’s been a blast watching it grow. Change is good, embrace it always.
Leadership is often defined as having the ability to make others want to do what it is that you would like them to do. You want people to want to use your software, and often their first introduction will be through the README in the source code or on the project’s GitHub page.
The BasicsThere are of course components to a technical document that make it more effective. Describe what it is that your project makes easier. Provide code examples detailing how the use of the library. Document the installation process. These are the basic elements which define a README.
Creating a great face for your project, however, requires still more.
Don’t get lazy just because this is for developersTechnical writing is still writing, and need not be dry and boring. Just as if you were writing an essay or blog post, you should strive to grab the attention of your reader early. This can be easily accomplished with a well-written introductory paragraph. Use strong or emphasised text to give a short description of what the software does, such as “Receive emails in your Rails app”. You can also use an image which relates to the functionality of your library or alludes to some pun in the name.
Your readers will most likey view your README in a browser. Please keep that in mind when formatting its content. Put the name of the library in an <h1> at the beginning of the file. Categorize content using two or three levels of header beneath. Make use of emphasis to call out important words. Link to project pages for related libraries you mention. Link to Wikipedia, Wiktionary, even Urban Dictionary definitions for words of which a reader may not be familiar. Make amusing cultural references. Add links to related projects or services.
Besides speaking English, your readers also understand code. Developers love to see code samples, and a few lines of syntax highlighted source are worth a thousand words. plataformatec/simple_form does an excellent job of providing code examples as well as explanations for nearly every setting and interface call. Besides being extremely greppable, simple_form’s README is the top Google hit for nearly all simple_form searches.
Be aware that sometimes the reason someone is visiting your project’s page is that they have a problem. If you know about persistent issues, such as resolving a functional dependency, call that out in a section of its own and provide a solution or workaround. Right in the README. Yeah. A great example of one such issue is thoughtbot/capybara-webkit’s dependency upon Qt. Because a gem cannot satisfy this dependency, we added a notice about installation issues to the README.
You are also encouraged to add “badges,” such as Travis CI’s
Written by Caleb Thompson.
