I've eaten the same breakfast, and the same Sweetgreen salad for lunch (in 6-12 months streaks) for the past 5 years. The reason it works so well for me is the reduction in needing to make decisions every day, and feeling bad about having made the wrong choices.
I like this because this is in a part of my day where I need to focus on work, and being productive, and don't need to be distracted by food decisions.
I also LOVE food - so dinner, and weekends, are times where I actually love making decisions about where to eat, what to eat.
As somebody that has started learning AI/ML and was looking at the exact question here three months ago - I found the Andrew Ng deeplearning.ai Coursera course an amazing starting point.
It was high level enough, and got me to understand enough, to get me to a point where I could start trying to build a side-project, without exposing me to the deeper math behind Neural Nets.
It was a great starting point without being overwhelming. Now I feel that I have the option to either go deeper if I need to, or go wider.
I find Andrew Ng to be an amazing teacher - explains things simply, clearly, and in a way that I find super easy to understand.
I don't know enough about HighCharts. Funny to see that they also copied / were inspired by the Google Finance Charts sparkbar (that's what we called the thing that shows you the summary at the bottom with the handles that you can drag).
I'd imagine is a combination of "not built here", pride (google engineers always feel that they can build everything better than the outside world), and performance (Google was investing, and I imagine continues to invest, vast amounts of engineering in speed).
Despite being a little bit more complex than I think it needed to be (I was a junior engineer after all, and this was my first project at my first job) I still think there's more complexity than meets the eye. Like anything that looks simple, there's tons of work behind it.
I built those charts on Google Finance. At the time (10 years ago) there was no better alternative for building interactive charting in browsers.
After I left Google Finance I feel that the team has attempted a few times to remove Flash, but I don't know why they didn't succeed.
Others on this thread are probably right - finance is not enough of a focus for Google, only so many engineering hours, better spent on other parts of Google Finance (more, better and cleaner data) than on replacing something that works well enough.
Spring is one of the Best Apps Of 2015 according to Apple. Buying things directly from brands on mobile sucks - people don't use the individual brand apps or eCommerce sites for shopping - so we've built Spring to solve this problem at scale.
Our team is small but we’ve hired the best from companies like Google, Foursquare, Bitly, and Chartbeat, and we’re looking to add other software engineers to the team. http://jellolabs.com/team/
Our current stack is Go (all our backends are in Go), PostgreSQL, AngularJS and ObjectiveC and we picked them thoughtfully because they are the right tools that will help us move fast and build high quality products.
We're looking for an iOS developer with a great sense of UX, that can both build the best iOS app out there and also help give valuable feedback on building some industry-leading world class UX.
We're a pre-launch, funded startup, about a year old. We already have an amazing team with engineers from Google, Foursquare, Ebay, Chartbeat, Medium etc.- http://jellolabs.com/team
We're moving and growing quickly and are looking to add smart, experienced engineers interested in e-commerce to our core team. We love GoLang, AngularJS, and ObjectiveC. We do code reviews and care deeply about moving fast while maintaing reliable systems. We use Asana, Hipchat, Google Apps and Trello. Every dev gets a Mac Book Pro, large monitors and Aeron chairs.
Our office is a hybrid of engineers and our brand team, which is made up of some of the best people in fashion and e-commerce. We're a tight knit bunch, just moved into an awesome office in SoHo.
We take our work and our culture seriously. Our goal is to create a happy, productive workplace! We keep a stocked fridge, bring in breakfast 3 times a week, lunch on Tuesdays and Thursdays. We play boardgames, have a kickball team, enjoy a good karaoke outing from time to time. Our two puppies, Fred & Gizmo, keep us on our toes.
We offer full benefits, unlimited vacation time and a competitive salary. Plus our team is the best in New York!
We are on a mission to create the world’s best mobile shopping experience.
We are well funded and we have an amazing team with engineers from Google, Foursquare, Ebay, Chartbeat and Medium - http://jellolabs.com/team
We love GoLang, AngularJS, and ObjectiveC. We do code reviews and care deeply about moving fast while maintaining reliable systems. We drink lots of tea and play lots of board games. Every now and then, we ride bikes.
We're looking for an iOS developer who cares about building awesome experiences. Contact us if you enjoy making fast and responsive UIs, even under the slowest network conditions.
We are well funded and we have an amazing team with engineers from Google, Foursquare, Ebay, Chartbeat and Medium - http://jellolabs.com/team
We love GoLang, AngularJS, and ObjectiveC, if you want to write Go as a full-time job you should come join us! We do code reviews and care deeply about moving fast while maintaing reliable systems. On Wednesday nights, we play board games.
We are changing the way mobile eCommerce works. We are well funded, have an amazing team and we're growing quickly.
We have a high quality team with engineers from Google, Foursquare, Ebay, Chartbeat and Medium - among others - check out http://jellolabs.com/team
We love writing GoLang, PostgreSQL, AngularJS and ObjectiveC - if you want to write Go as a full-time job you should come join us. We play board games on Wednesdays, do code reviews and care deeply about moving fast while having reliable systems.
We're looking for an iOS developer with a great sense of UX, that can both build the best iOS app out there and also help give valuable feedback on building some industry-leading world class UX.
I understand what you are saying, and indeed I am trying to be diplomatic.
Picking on Rails/Node was not my goal and I feared that a stronger comparison between these choices would have been seen as such by the current startup community.
At the end of the day most of these choices are tools and I truly believe that while they have their trade-offs, they are all good from one point or another. The point I was trying to make is that Go is a tool worth looking into as an alternative to Rails/Node for early stage.
Unless you build the exact same product in Rails/Node/Go it's hard to make meaningful broad comparisons - and you end up comparing lab experiments around speed in specific toy examples, or end up comparing only certain isolated parts of the toolset.
We are planning on writing more blog posts about our experience using it, more into performance internals and how it all plays out - but I do feel that we'll stay away from comparisons.
What we are discovering is that actually it doesn't sacrifice as much as you'd think - and I think that's the point we are trying to make with our article.
You get both the performance, and you get a very lightweight language - I'd say almost as easy to write as Ruby or Python - with great open source support and growing and with a great community around it.
We haven't really ruled out any of the common stack tech choices. They are all good in their own ways, and have their own tradeoffs - and the intention here was not to spark wars about which tool is the best.
I think the choice was much more of a proactive choice - we liked Go, we like the way it fitted us - good for fast iterative development upfront, good for the long term, fun to write code in and with a lot of advantages that come with the fact that it's a language designed today - with a lot of lessons learned from the past.
We are building something awesome around mobile commerce, trying to connect the people who make products directly with the consumers who love them.
Our current stack is Go (all our backends are in Go), PostgreSQL, AngularJS and ObjectiveC and we picked them thoughtfully because they are the right tools that will help us move fast and build high quality products.
I was at Google for 5 years building the google finance charts, gmail's multiple inboxes, some maps infrastructure, and the like. My co-founder was at Fab for a little under a year.
We're looking for an iOS developer with a great sense of UX, that can both build the best iOS app out there and also help give valuable feedback on building some industry-leading world class UX.
I couldn't agree more. What I feel a lot of people are missing here is that Marissa's making Yahoo a place where good engineers want to work: where empowered smart people can make a difference in a scrappy way.
We are building something awesome around mobile commerce, trying to connect the people who make products directly with the consumers who love them.
Our current stack is Go (all our backends are in Go), PostgreSQL, AngularJS and ObjectiveC and we picked them thoughtfully because they are the right tools that will help us move fast and build high quality products.
I was at Google for 5 years building the google finance charts, gmail's multiple inboxes, some maps infrastructure, and the like. My co-founder was at Fab for a little under a year. We have a fantastic team - http://jellolabs.com/team - are seed funded, and growing quickly.
We're looking for an iOS developer with a great sense of UX, that can both build the best iOS app out there and also help give valuable feedback on building some industry-leading world class UX.
I also disagree with the "wear a suit" idea. After about a hundred interviews at Google, I've seen a pretty good inverse correlation between how dressed-to-impress a candidate is and their real performance in the interview.
The best engineers rarely give a shit about how they show up at an interview, and I don't really care if they wear a tie or a tshirt, as long as they are comfortable.
Maybe a good rule for presenters would be to imagine what happens if they replace the photo of girls in bikinis with a photo of guys in bikinis. If that makes the presentation awkward, then bikinis are not the answer.
I like this because this is in a part of my day where I need to focus on work, and being productive, and don't need to be distracted by food decisions.
I also LOVE food - so dinner, and weekends, are times where I actually love making decisions about where to eat, what to eat.