For those who prefer the default Reddit UI:
https://www.reddit.com/r/kindle/comments/1hrwytr/all_kindles...
739 karma · joined September 11, 2012
- <80 person team (total); ~60% engineers
- 0 product managers: design and engineering are equally empowered to make the site nice within general business/product definitions defined by GM who would constantly get excited about the work you showed her, making you feel good about yourself and your work
- 0 project managers: business understands that there is no magic formula for delivering products that haven't been built yet and so long as we try our best to hit dates and cut scope as needed, it's on us to track our progress and determine priorities
- gm, cto, and head of hr all supportive of growing team and individual members in a non-political way
- politically-driven employees (typically a head of sales or marketing) shut down and churn out quickly
- engineers talk directly with customer service
- engineers perform rounds helping out in support forums
- domain specialists, but no fences. i might be a web engineer, but if there's a sql query i feel compelled to optimize, nobody is going to stop me.
- company regularly interacts with, and hosts local events for, an engaged user base. engineers actually end up having in person conversations with our users, gathering honest feedback for improvements while simultaneously being told how great the product they contribute to is overall
- relaxed hours ("you're an adult; we trust you to get your work done")
- when dining out or getting drinks, even paying by cash a large group is able to come up with the right amount of money, with no one person needing to chip in more than necessary
- anyone in the company can deploy the site with a single chat room command
I don’t miss it and am quite happy that I got around to it and that a one-time cost of 45 minutes of my time has likely paid itself back twice over by now.
“If I don’t get it in the first crack, I get it in the second. And if I don’t get it in the second I almost never get it.”
"I’ve never been a refiner"
This is not identity design—this is ego.
A.) I want to live in Berlin B.) I do not want to live in Dubai
What will it take to dispel the myth that JS rendering isn’t SEO friendly? There seems so much confusion on this point but the fact is that as long as your UI is rendered synchronously (i.e., any data needed for the UI doesn’t have to get fetched from a server), the page will be crawlable by Google.
Further, the goal of isomorphic rendering/rendering static sites in general is not to serve individuals who have JS disabled (that’s a bonus, sure), but rather to remove JS loading and execution from the equation with the end goal of faster paint times for your application.
To be clear, this is a really cool project but I fear that many of us throw out keyword spam like SEO and UX to make something more digestible, when the reality is that the performance gain is the real hero!