thoughtbot New Bamboo is now part of thoughtbot

Read the announcement

The Bamboo Blog

Our thoughts on agile development and web technology

  1. Damien Tanner

    New Bamboo joins thoughtbot


    Max and I started New Bamboo over 9 years ago. Max had just finished a degree and I hadn’t yet stepped foot in a university. We soon grew into a team of incredible people, all endlessly passionate about the web.

    Early on we made a decision to focus exclusively on building with the brand new Ruby on Rails framework.

    As a team, we made a commitment to being curious, transparent and effective.

    Our curiosity drove us down a path of continuously learning, which in turn lead to our many contributions to the Open Source community. Our transparency earned us a name for being direct and honest with our clients, even when it wasn’t always want they wanted to hear. Our effectiveness was shown in our refusal to produce poor quality “quick fixes”. Together, all these traits earned us a solid reputation in the industry.

    At the time we didn’t think much of it, but in hindsight these things made New Bamboo the company it is today. A team of exceptional developers who are always pushing each other to improve.

    Several months ago we met Chad Pytel, CEO of thoughtbot, and learned about their incredible success growing the company and what the future looks like to them. Both companies share many similarities, but also bring their own unique approach to many things. For us it became clear that thoughtbot was a natural fit, and being part of the thoughtbot journey was an opportunity not to be missed.

    I’m therefore delighted to announce that New Bamboo is joining thoughtbot to found the London office and help grow thoughtbot in Europe. We’re extremely excited to join the thoughtbot family and start this new chapter.

    Visit thoughtbot

    Continue reading

  2. Pablo Brasero

    Don't Inline-Rescue in Ruby


    Do not use the inline version of rescue in Ruby, unless you REALLY know what you are doing

    We are currently hiring at New Bamboo. As part of the process, we send candidates a code test to complete at their own leisure. I won’t reveal any details here, but it’s nothing special.

    Nevertheless, I have personally reviewed a bunch of these code tests, and there’s something that has caught my attention. A number of applicants misunderstand the usage of the “inline rescue” construct in Ruby. Not a whole lot of them, but enough that I felt compelled to write this piece in order to help other people out there.

    Continue reading

  3. Laurie Young

    We're Hiring


    Over the past few years we’ve slowly been growing our team, and its time to take on a few more people. So we’re on the lookout for one or two new developers to join our team.

    Continue reading

  4. Claudio Ortolina

    The Problem of State


    When we build client-side applications, most of the problems we face are related to state management: what elements on screen need to be in sync with each other, how do we track changes locally and from the server, how do we effectively handle computed properties (like a user’s complete address when it’s composed by separate pieces of data).

    What can we do to tame this complexity? In this post we’ll explore some ideas and lay out the basis for a unified strategy.

    Continue reading

  5. Laurie Young

    Our March 2015 Hackday


    Our latest hack day gave the team a chance to wrestle with new technologies, refine some older code, and improve our life in the office. We gained an insight into finance, a virtual train set, a translator, an altar, and much more: not least, a deeper understanding of some great technologies.

    Continue reading

  6. Claudio Ortolina

    Prototyping an Analytics Service With PostgreSQL and Clojure


    During our last hack day I decided to work on a proof of concept for an analytics service, with the goal of being able to instrument any of our running applications (both server side and client side) and expose the data with a restful api and a web sockets interface (for eventual dashboards, etc.).

    Continue reading

  7. Laurie Young

    How Many Teams Does It Take to Change a Lightbulb


    You’ve probably heard the joke about how many software developers it takes to change a lightbulb (none, it’s a hardware problem). But if it were a software problem, there’s a philosophical puzzler when you ask yourself how many teams it would take to change it.

    Let’s say the light bulb is a software feature that needs updating. The update will require the input of designers, back-end coders, and front-end coders. There will be business people who decide whether or not the customer will ultimately like (and pay for) the “light bulb”. And there will be people who are responsible for some other applications that this new feature needs to integrate with. Crucially, the people who have these skills are employed by two or three different companies. How many teams does that make?

    Continue reading

  8. Murtaza Gulamali

    Building secure web applications with Ruby on Rails


    The advantage of using a mature framework like Ruby on Rails to build your web applications is that it is reasonably secure by default. Current versions (4.0 and above) have several built-in mechanisms to stop opportunist hackers; the Rails community actively works to identify and patch new vulnerabilities as they come along; and, the framework is well documented both officially and unofficially. However, if some of the security features are disabled, your code doesn’t conform to best practises, or you don’t appreciate web security in general, your Rails apps can be left open to attack.

    Continue reading

  9. Laurie Young

    How Some Lost Keys Lead to our New Chill out Zone


    One of the joys of working in a company where everyone feels empowered is the way that something unexpected can trigger a change that makes everyone happier, and that it can happen spontaneously without the need for approval.

    Take for example the story of the lost keys. It started with an email sent round on our internal mailing list earlier today (we use Slack, but email still gets better reach). “Help” it said, “I’ve lost my keys!”

    Continue reading