I am grateful that VS code is free and if they want to monetize this by having some kind of paid upsell to another product, then all power to them.
They made a good product and if this is a way to fund improvements, I say it's a good thing.
293 karma · joined September 17, 2012
They made a good product and if this is a way to fund improvements, I say it's a good thing.
The product was so good that people noticed. They were able to take this and leverage this into being search for a really large property, like
Back in the 90s there were lots of search engines. People didn't pick Google because it was hard to switch, they converged on Google because the product was that good - there was Infoseek, HotBot, AskJeeves, Alta Vista, Lycos, Yahoo, Excite ... the list goes on.
It's a theoretical problem to have a significantly better search engine and not find users for it.
Also, it's a flawed abstraction to view large companies as a monolith: the investing arms are usually very separated from product teams.
TLDR: If a large company wants to enter a space, that's their choice. Accept this as a fact of life if you want to go work on a startup.
This looks like a distressed fire sale rather than a good exit, considering the product failed.
- Realize you are signing up to be part of a bigger machine, and there are things you will have less control over. This is both limiting and empowering.
- Both people in small and large companies can be smart, but they are typically a different flavor of smart. Learn from them accordingly.
- You should plan to have a much longer lead in terms of getting things done if it requires a dependency on a team you don't work with frequently.
- The team you work on is far more important than the company you work for.
- Be active rather than passive about finding opportunities and projects to work on. You can easily get stuck working in a role you might not be a fit for or a manager you don't click with.
There are so many nice software touches on them that you just have to experience to appreciate.
And in particular, try to build things that force you do things from first principles vs. using a library.
And really with video conferencing product, I don't get the whole trope of "but they might discontinue it." - the utility is immediate in terms of the calls that you make with it, and time boxed till by when a call ends.
For example the code search, testing, code review tools are amazing and better than any commercial equivalent.
Other tools like the bug database are on par with the industry.
Others like the food, directory and interviewing tools are still pretty damn good and even if they are lacking some polish, are often far more functional than the average commercial equivalent.
And of course they are hit and miss - because there are so many of them. The ones that are commonly used are well funded and have lots of people working on them.
I no longer work at Google but still consider it a role model for how companies should take tooling seriously.
https://cloud.google.com/maps-platform/terms
(a) No Scraping. Customer will not export, extract, or otherwise scrape Google Maps Content for use outside the Services. For example, Customer will not: (i) pre-fetch, index, store, reshare, or rehost Google Maps Content outside the services; (ii) bulk download Google Maps tiles, Street View images, geocodes, directions, distance matrix results, roads information, places information, elevation values, and time zone details; (iii) copy and save business names, addresses, or user reviews; or (iv) use Google Maps Content with text-to-speech services.
(b) No Caching. Customer will not cache Google Maps Content except as expressly permitted under the Maps Service Specific Terms.
I don't think this article has good reporting, because it suggests that the company has some hidden agenda, when really all it's doing is complying with local laws.
This is a very cheap price.
Sheets -> Great collaborative experience for simple to moderate complexity use cases.
Excel -> The heavy artillery.
I think conceptually this is a better test, more so than say if you have access to a raw pointer - because more important parts of how to handle core issues like scheduling, storage management, concurrency, parallelism and distributed computation manifest themselves in many forms.
I started my career doing C programming in a OS / kernel environment. In retrospect a lot of pieces of applications I've worked on are what I think of as systems, and many parts of kernels are more applications than systems.
Were I working there, this would have made sense to me.
I didn't work there to be an activist. I worked there to go work on products.
I don't get other comments that say "courted activists". The recruiting pitch is about impact, a good work environment, compensation and interesting products.
You don't need a giant codebase to start benefitting from it. Even if you have a smaller codebase, and properly use bazel to setup tests, you only test what needs testing, and that makes a huge difference in productivity.
We are a couple of Xooglers who worked in Google Research now working on making a better multi city travel planner / travel search engine called Preso Trip.
Live site: https://www.prestotrip.com/?source=hn
The blog post describes the details of what motivated us to work on this problem and the approach we are taking to find great prices for multi city deals.
Video demo: https://youtu.be/9ggFSjKAMIA
Product Hunt entry: https://www.producthunt.com/posts/presto-trip
Why did you reshare it ?
The cost for the shots was ~200$, and ~300$ for consultation, which was a PA giving me printouts about information of what diseases are found in which countries.
What a scam.
All 3 variants listed are fabulously unhealthy coming in at 500 calories per serving.
If you want to pitch this as a tastier product and pursue that angle, that's one story but pitching this as "healthy" is quite flawed.
This is the kind of thing that you go over laborious detail in over privacy design docs at Google to make sure you have it covered.
Source: I'm a Xoogler.
Amazing tool. Great integration with version control, code search, continuous integration.