Full Width 
Shortcuts 
Sign Up 
Log In 
Articles 
Reading List More from Joel Gascoigne
By now we have a fairly long history of doing retreats at Buffer. We’re now a 75 person team [https://buffer.com/about], and we just wrapped up our 8th company retreat in Madrid, Spain. Here’s a quick history of retreat locations, timeline and size over time: 1.
> Note: this was originally posted on the Buffer blog [https://open.buffer.com/change-at-buffer/]. We’ve always done things differently at Buffer. For me, this has always come from a natural desire to question things. Why base your company and team in a single location? Why is it customary to
> Note: this was originally posted on the Buffer blog [https://open.buffer.com/from-startup-to-scaleup-what-were-changing-as-we-make-the-transition/] . In the past couple of months, I’ve had a number of thoughts around the growth Buffer has experienced in the last year and some interesting challenges and paradoxes that seems to be bringing us. I’
In December, my friend and co-worker Brian [https://twitter.com/brian_lovin] casually mentioned to me that he would love to go traveling and explore Asia. I love Asia. I lived in Japan as a kid for 3.5 years, and I lived in Hong Kong for 6 months in
We’ve been lucky at Buffer [http://bufferapp.com] to receive a number of acquisition offers along our journey so far. When I mention this to people, a key question that often comes up is “how did you decide not to sell?”. The earliest offer we had for Buffer was
More in programming
In this video, we look at why fork() needs copy-on-write, how it works inside the kernel, and a memory usage problem that Instagram encountered with Python.
Comments require commitment, but they’re worth it.
In his Rails World keynote, David Heinemeier Hansson (DHH) declared the end for writing code by hand for professional work – at 37signals at least. Is this change now unstoppable?
My last official contribution to GitHub was something I’ve wanted for a long time: Writing the code to display an ACCESSIBILITY.md file’s contents on the repository landing page. This content lives in the same tab component that the README, License, Code of Conduct, Security, and important information is surfaced. For example, I’m using an ACESSIBILITY.md file located in ./github to communicate my accessibility statement on my a11y-webring.club repository. Here’s an image of it in action: The file only appears if it is supplied, so it is not a required part of creating or maintaining a repository. However, it is my hope that the act of providing one becomes more commonplace the same way providing those other special kinds of files are. Another broader hope I have is that this promotion of content helps to normalize accessibility as a consideration and practice in some small way—something that helps to send a signal of a mature software project. I’m excited to see how people use this new addition to the platform. I would also like to extend a huge thank you to Jan Maarten and Maria Lamardo for their help getting this effort across the finish line.
