362 karma · joined June 27, 2012
Staff Software Engineer at Merit
Previously - * Software Engineer at Synapse Technology Corporation working on deploying AI for threat detection (acquired by Palantir) * Software Engineer at VIAAS working on IP security cameras (acquired)
Our 30-day plan is $20/month msrp whereas Nest is $30/month. (Your Nest pricing is not current - you're probably grandfathered on that rate)
Our main market is businesses with multiple locations who need role-based access and/or LDAP integration for cameras with cloud storage.
Most home users aren't going to pay full retail for cameras, hire a professional installer to put 1-4 cameras outside, then pay for cloud storage... or at least not without a huge amount of Support effort. Given their feature list, they aren't going to be able to compete with the business/enterprise market due to both having worse features AND being more expensive.
(shameless plug: I work for a company making enterprise IP cameras, and both our cloud storage AND cameras are cheaper, while having way more features)
Anyone who uses MacOS (ie. can afford a MacBook Pro) to work on has to have enough money to buy one despite being in a job interview.
Most people who use vim and emacs are going to be older, more experienced engineers, and as such, have the resources the acquire the tools they need to succeed (time to learn, books, computer, paid IDE).
I see statistics like this and just think about all of the kids who didn't get a free ride through college and a MacBook given to them who aren't succeeding.
It doesn't matter what dataset you are using to base it off of, if you think that the average person pays $1,263 per year in total healthcare costs you're crazy. I'm paying something like 3 times that as a very healthy 20-something.
The author comes off as deeply uninformed about how legal proceedings in the U.S. work, for example talking about how he had to refute arguments in court and such, which is just not how things work at all at that level. Some basic Googleing would have taught him all he needed to know about defending himself in small claims court without stress.
While I would normally be fast to offer advice to the author on how to improve the tone and resonate with the reader more, in this case, this article is not something which needs to be written in an engaging, interesting way - it is just a collection of data, presented in an accessible manner. It encourages the reader to change their opinion in a Bayesian manner and use the sources, not just blindly follow the author.
I also really dislike the fact that the language used would be very hard to a non-native English speaker, which makes me question how useful it is at solving the problems it is obviously addressing (cultural differences, social norms, etc.).
I also have a lot of first-hand experience with this since I taught paid lessons in CS 1.6 way back in the day. Generally the market for lessons is full of mid-tier players who are very dedicated, but don't have the support necessary to improve (ie. a team of players as good as them or a proper coaching system). These players are almost all looking to go pro some day, and want to be able to break through to that level. Since the difference in skill between a Top 1% player and a Pro in CS:GO is so massive, any random competitive player won't be able to give good advice since they are at the same place as the client, and can't understand WHY things are done the way they are among the Pros.
It's worth noting that the Orbit Female CS:GO team isn't even all among the top 1% of players - they went 10-6 in ESEA-Open last season, which is the lowest level of competition which is even sanctioned. Any team that is dedicated and practices, even if they aren't good, will make it through Open at X-4 without much difficulty (I've coached a few teams through this).
I also find it kind of amusing that you're advertising esports advice from a woman who plays on a CS:GO team which can't even compete with a mediocre ESEA-IM team... she might be an absolutely amazing teacher and amazing person to work with, but she isn't good at the game, which really undermines your marketing strategy.
Caffeine.
This is a serious problem. Research suggests that one of the main causes of obesity in children is lack of ability to identify portion sizes or understand how much to eat.
Obviously there is a market of people who understand this well and want to track what they eat, but you are very likely going to be misleading a very significant amount of your userbase into making worse decisions for themselves.
Cleaning:
Open Refine seems to be the best product in this category. I haven't used anything but my own tools to do this before, so I can't really offer any advice.
Warehousing:
My understanding is that this is just a fancy way to talk about a database with a schema designed for analytics. There are many open source databases which do this very well, the one I use being Cassandra (and/or KairosDB), though it is also likely the one that is hardest to use. For a beginner, you might want to refer to this SO answer: http://stackoverflow.com/questions/8816429/is-there-a-powerf...
Data processing/collection:
This is something that is incredibly dependent on the data sources, so I likely can't tell you anything that will help. Most of my data sources I've worked with have been internally sourced log files, messages from ZMQ, or CSV data - you might be working with something far different though, since there are lots of public data sets and such which are common. Ideally, this would be integrated into the tools that you are using to clean the data, but I don't know if that exists.
Handling input from many different sources at different rates is not a very hard problem to solve if your system is build correctly - you could for example run a daemon for each data source which will populate the database when there is new data available, then send a message off to the processing engine, which will integrate the data into whatever reports you are running.
Specifically for a use case of a hedge fund, the reports could be triggered by a message which is sent when the new data is available, and processing could be done in parallel in Lambda or similar dependent on need to get a nearly instant return, enabling nearly real-time reporting.