182 karma · joined October 16, 2012
I agree 100% here. As a SQL veteran, it would make the transition a lot easier if you used common SQL keywords like group by, order by, limit, etc. e.g.
from employees
where country = "USA"
derive [
gross_salary: salary + payroll_tax,
gross_cost: gross_salary + benefits_cost
]
where gross_cost > 0
group by:[title, country] [
average salary,
sum salary,
average gross_salary,
sum gross_salary,
average gross_cost,
sum_gross_cost: sum gross_cost,
count,
]
order by:sum_gross_cost
where count > 200
limit 20“If you look at each one and how they’ve occurred, many have come from “dangerous areas” on the pitch. At AS Monaco over the last season, we looked at where and how goals were most often scored and key areas to shoot/cross from to apply in our game model.”
With teams applying more analytics to soccer there are more cases of high goal probability crosses and defenders’ attempts to clear these are often futile. A great example was England’s equalizer yesterday that technically was an OG but realistically the defender had no chance to clear it and Sterling was right there to tap it in.
I’ve done my share of experiments with ML/AI and where I’ve seen the most interesting value has been NLP applications (such as categorizing customer comments or assigning categories to products based in description) and finding “factors that influence behavior x” which then can be turned into either a model or a few simple rules.
I’d say go with something like Matomo (formerly Piwik) https://matomo.org. If you wanted to build your own, I’d suggest keeping it simple. Look at Matomo’s architecture and replicate https://github.com/matomo-org/matomo.
Any company who's serious about their business, eventually gets there, but still they're not 100% independent. AWS is one of the biggest platform providers out there and they don't provide an audience, they merely smooth out the "tech friction" of building a tech company. It's not a coincidence that investors always seek SAAS/PAAS companies with massive switching costs, it's in fact the biggest type of moat there is. http://news.morningstar.com/classroom2/course.asp?docId=1440...
I agree with the poster who said that the solution isn't to "host your own" but to be ready to move providers at a moment's notice, to build resilience in your tech stack as much as possible so if your provider shafts you, it's easy to ditch them. This is really hard to do for small content creators/businesses as they don't have enough resources to make it happen. This is what the article should actually cover.
I don’t know what your data looks like, whether it’s just transactional or a combination of transactional and raw server/app logs. You could ETL the raw logs into an RDBMS like Postgres but you have to worry about maintaining it though and it doesn’t sound like you have enough resources for that. To do that you need help from IT/ops to set up a replica of the live server so it can be queried without disrupting transactional operations and then write ETL code or use a service like Stitch or Panoply.
You can also use a cloud platform like Google BigQuery or AWS Redshift to dump raw data in and then create views and table extracts for all the commonly used business functions. That’s still overkill though and a simple RDBMS should suffice.
And if you want to raise awareness see this article by StichFix and the HN comments https://news.ycombinator.com/item?id=11312243
[1] https://www.nytimes.com/2013/09/15/opinion/sunday/its-not-me...