fourspace

General Assembly (https://generalassemb.ly) | New York and REMOTE | Full Time

Looking for:

   - Front End Engineer
   - Senior Software Engineer
   - DevOps Engineer
   - Ops Engineer

Our engineering team is around 25 people that are fairly evenly split between New York and remote. We have engineers from London to SF who work asynchronously via GitHub and Slack. We place a strong focus on allowing every engineer to have a voice and an impact. We are also anti-dogmatic: use whatever code editor you like, pair-program when you like, and favor trying new things over a fear of mistakes.

We're primarily a Ruby on Rails & React shop, with some custom nginx proxies, AWS Lambda, and Go mixed in. We're looking for people that will help us shape our architecture and guide our team towards best practices. We want engineers who will not just write code but help us produce great products and experiences for our students and partners.

Learn more or apply: https://generalassemb.ly/careers

Regardless of your views on Ayn Rand, this journalist goes to a week long conference and writes about two talks? Click bait. Pass.

However, features like mobile check depositing are only available to "qualified members" (i.e. those with a military connection).

Former Google SRE here. Trust me, many of the problems we faced were solved on whiteboards, during chats at lunch, or via email. Most of issues we faced were of a class that simply isn't covered on basic sites like Stack Overflow.

The interview described is pretty much exactly as I remember them. SRE is actually quite difficult to get into, precisely because you need to have fairly deep knowledge on a wide range of topics. The "ways in which you were asked to solve problems" are actually the best way to determine if an application actually knows about what they will need to know.

An extremely common use case is to have several google accounts, typically when using various Google Apps domains.

Instead of understanding that I'm the same person with access to all of the accounts, it makes me log into each one separately. For most products you can be logged into each one simultaneously, but the first one you log into is the "default". Analytics, for example, doesn't even support multi-login, so if that "default" account is not the one you want, you have to log out of ALL of them. WAT

Congrats. The irony is that the last thing I think of when I'm using Google's long-convoluted account management system is "slick login".

For us, it just worked. I'm a one-man engineering team at a startup, so I don't have the resources to devote to running an in-house CI setup. Circle took care of it for us, and their UI and features are just perfect.

Congrats to Paul and the rest of the team! I have been recommending CircleCI to all of my dev friends ever since my first experience with it over a year ago.

We had a pretty tricky front end testing setup with our Rails app, due primarily to some bleeding edge javascript interactions that needed to be tested in a headless browser. It took ages to get right locally, so I had zero confidence that Circle would handle it. I set up our repo and promptly forgot about, as I was traveling out to SF for Startup School 2012.

While waiting in the lobby of YC for the pre-event dinner, I got an email from Circle (actually, from Paul) that our repo was ready and all tests were passing. PASSING?! Whoa. As I read it, I looked up from my phone and Paul was standing in front of me. I wanted to give him a hug, but I settled for a friendly thank you and a handshake. =)

I certainly can't get it to work. For the first problem, I tried:

  function one_bit(x) {
    return x & (x-1) == 0
  }

  Expected "}" or comment but "&" found.

Agreed 100%. I was just touching the surface, and by "shipping" I really meant inventory management, purchase orders, and everything else involved in stocking physical goods.

It's clear the POS app is a test product for them, and I'm happy to see them experiment. I just wish they'd put a little more love into the core functionality. Even for ecommerce, Shopify is lacking some really basic things:

- Editing orders (e.g. marking an item canceled)

- Editing tracking numbers (fixing typos -- not allowed today)

- Allowing coupons to offer both a discounted price and free shipping (today they're mutually exclusive)

Great news. Shopify is the one piece of ecommerce software we use that isn't completely maddening. (Having a fantastic API is a large reason why.)

I was struck by this comment, though:

   "Using Shopify and Shopify POS together reveals our true 
   ambition: To be the first company in the world that fuses  
   all the distinct parts that are needed to run a complete 
   modern commerce business - all in one amazing product."

I just switched to Time Warner Cable and they offered me basically the same plan, with 50/5 bandwidth. I forgot the price, as I don't care to pay anything extra for TV.

Any suggestions on how to actually do this?

Shopify themselves wrote an app to do this: http://www.shopify.com/blog/6668676-new-free-shopify-app-bul...

Super excited to see what these can do. Wish they were available for Pro plans as well, as I'm building similar reports for our store as we speak.

My goal wasn't to give specific advice to people in certain situations. My examples are hypothetical; maybe I didn't make that clear.

Instead, the point of the article was to motivate you to go actually make sales, create value, and build relationships. None of these things require a developer. Do I know who you should specifically call to test the market in a given context? No; that's your problem to figure out. The point is that you CAN figure it out.

As mentioned in another comment, I managed a Google SRE team that help run Borg for 5 years. I'm good friends with several of the folks who are rebuilding it using Mesos at Twitter. They are all insanely awesome people.

Let's say you have a Rails stack (app server + DB) that you want to deploy for testing in 3 different datacenters. If that works out, you then immediately need to deploy 10,000 instances each to 10 different datacenters. Oh yeah, and the storage needs to be distributed and universally available, in case any of the servers crash. Performance testing reveals that you can't have more than 10 servers per rack, otherwise you saturate the rack switch. You also need to account for power distribution redundancy, shifting traffic loads, etc.

Oh, and you want to do this with a single configuration that's manageable by a team of 3-4 people and have deployment be entirely automated and monitored.

The complexities behind this problem are simply enormous, almost too much to even comprehend. I am proud of the work we did at Google to attempt (yes, attempt) to solve this problem, and I know my friends at Twitter are doing great work as well. I'm mostly just happy that I can finally talk about it and that the badasses that do this work can get some credit.

I managed a Google SRE team that helped run Borg for 5 years, so I'm pretty familiar with this. You can certainly run multiple application servers on one machine using virtualization. What isn't easy is automating where the applications are deployed, in an elastic, constantly shifting way that deals with massive numbers of machines and constantly changing hardware.

Cheap hardware crashes. It crashes all the time. Furthermore, the application's needs themselves change all the time, depending on traffic curves and processing needs. The dynamic needs of Google's (and presumably Twitter's) completely heterogeneous application stacks don't lend themselves to simple virtualization and over-the-counter software. This is an incredibly tricky bin packing problem that was never quite solved in my 5 years at Google.

I don't know a lot about the "distributed frameworks" you mentioned, so perhaps they do this too. I kind of doubt it. If it were as easy as you think, I'm sure my friends at Twitter would be using what you mentioned.

It isn't always the software. Having open, controlled, customizable hardware can offer a huge advantage over what you're able to purchase from Cisco/Juniper/etc.

Also, a software switch allows you potentially massively scale the number of ports on a single switch.

Quick correction: only Redfin has MLS access (as they are a broker). As far as I know, Zillow and Trulia have very limited MLS access, and largely get their listings from the brokerages themselves.

We just purchased a house and Redfin by and large had the most timely and accurate data. It turns out that my experience is backed up by evidence: http://www.inman.com/news/2012/10/3/redfin-study-knocks-zill...

Congrats guys! It should be mentioned that Clustrix was part of YC's W06 batch.

Can someone provide a practical use case for prepending modules? I can't for the life of me think of one.

Hey, fellow Charlottean here! I've found a similar situation here, where my SF network still exists but isn't quite as useful as it was when I was living there.

You echoed my thoughts exactly about Noe Valley. We absolutely loved living there, but when it came time to raise a family it wasn't even an option. That's coming from a couple who both worked at Google! Obscene indeed.

I absolutely love SF, but I never felt like home there. I think what we were missing was that sense of permanence, resulting from the high cost of housing (and therefore lack of future options).

Finally! This is a fantastic Christmas present. Thanks friends at GitHub!

Clearly, Google needs to be punished for such abuses of the power, power that is granted to them by consumers voluntarily choosing to use their free product.

I can believe this in a heartbeat. I know that if Platforms and datacenter/cluster management innovation stopped, I'd see a mass exodus of my Googler friends (as well as a very noticeable change in Google's products).

I had the pleasure of helping to build and manage these facilities, both hardware and software, for 5 years. It's nice to see some of Google's real innovations reach the public eye. Some of the smartest folks I ever worked with at the company build absolutely mind blowing tech that the outside never has the opportunity to see or appreciate.

In fact, while much of the content in the article has been written about before, it's still probably 2-3 years or more behind where Google is actually at. I left in 2010 and did't read about anything I had not experienced.

I really don't think they're going after the iPhone model. I have a Nest and love it, but don't plan on upgrading each year. After all, it's the software that really matters.

Given that, this new model makes some evolutionary design improvements and finally adds support for low voltage systems. That hardware compatibility change opens up Nest to a lot more potential customers, and I think that's what they were ultimately after. If they're going to release new hardware, why not make it a little bit better?

Oh the irony of this being presented as an "interactive" infographic. Their number 1 takeaway is "Understand my users & their needs".

This information may or may not be useful, but the format prevented me from being interested in finding out. Next time just present this as a body of text and images with some nice typography.