1. 2

    Company: thoughtbot

    Company site: https://thoughtbot.com

    Position(s): Lots! iOS, Android, Ruby on Rails, Elixr/Phoenix, Front-End/UX/Product Designer

    Location: Boston, Raleigh, SF, New York, Austin, London

    Description:

    We’re a consultancy making digital products. We believe there is always a better way to do our work, and we want to find it and share it with as many people as possible.

    We strive for few job titles, few departments, and few hierarchies. We prefer composition of roles necessary for projects and company objectives over inheritance of bosses and direct reports. We are at thoughtbot primarily for our design and development skill, and want to apply it, rather than creating company overhead. Check out our /purpose.

    Contact: You can DM or email me or visit thoughtbot.workable.com

    1. 3

      This blog post outlines a technique for learning new programming languages. TL;DR you build a quick tool to connect to the RhymeBrain API and return some (very bad) puns based on a keyword. It’s simple enough to fully wrap your head around but complex enough to touch many parts of any language. It’s even got implementation steps you can use as goal posts!

      1. 4

        thoughtbot is hiring. We are a software consultancy, still small in the grand scheme of things (~90 folks) with offices in Boston, New York, London, San Francisco, Austin, and Raleigh. Lots of web based projects in Rails, Elm, React, etc. You can view our jobs here or reach out to me directly: edward (a) thoughtbot.com

        1. 3

          I know that Thoughtbot is typically not open to remote workers - I live in Portland, ME, which is about 2 hours from Boston. I could come in to the office a couple of days per week if I could work remotely the remaining days. Do you know if the culture at Thoughtbot would support that sort of setup?

          I realize you probably can’t speak for the entire company. :)

          1. 2

            Hey @mosburger 🙂 I believe we’re not looking for remote workers at the moment, sorry. But if you are willing to make the commute I’d absolutely encourage you to apply. Sorry we can’t be more flexible.

            1. 2

              Greetings from the 207!

            2. 2

              I’ll vouch for Thoughtbot’s incredible friendliness. Everyone I’ve ever met from there has been a Gem.

              I used to bump into a group of them in SF at a bar nearby there office after a training and I think they always said hi. Pleasant folks and they really care about software.

            1. 4

              It’s interesting that they’re still working on CoffeeScript. The last time I used it was back in 2012 I think. I started using it while I was at ESPN and brought it over to Nickelodeon briefly before we went back to plain vanilla JS.

              With ES6, there’s not much reason to use CoffeeScript for me. I’m happy for what they ended up getting into ES6, though.

              1. 4

                That was sort of my takeaway when seeing this. Maybe I’m missing something, but why would I use CoffeeScript 2 when ES6 is becoming more and more popular? The only good reason I can think of is if I had deep reliance on CoffeeScript 1 and this fixed a bunch of issues.

                1. 1

                  Yeah, you’d have to be heavily invested in CoffeeScript to be using it at this point, IMO. If you’re starting fresh, it doesn’t really provide any advantages over ES6, especially since it compiles down to ES6 now anyway. You’re still going to be doing transpiling when necessary.

                2. 1

                  Yeah; I think it’s telling that their comparison of CoffeeScript to JS is still showing ES5. If they showed ES6, it’d be visibly less compelling than it used to be.