HN user

ergest

182 karma

I'm interested in technology, decision making, strategic thinking and psychology in general.

Posts7
Comments82
View on HN

There have been other periods of massive layoffs. (I’ve personally witnessed 2001 and 2008) Weren’t workers disillusioned with full time work back then or has it become easier and more acceptable to freelance in the last decade? Was it perhaps the callousness of the layoffs that ignited these emotions?

I can't decide if it would be better or worse if it stuck more closely to SQL keywords. You use "from" and "select", but not "where", "order by", "group by". There's some danger of it being in an uncanny valley of SQLish, but I'm pretty sure I'd prefer just using those terms verbatim (including the space in "order by"... that style is less common in modern languages but it's not really that much harder to parse)

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

I agree that the 40h workweek is not technically “designed” per se but rather it’s the best confluence of factors such as keeping competition at bay, keeping society productive, making people feel useful, making life purposeful for many, etc. It’s the current local minima. If we could work 60 or 80 hours and still get the same benefits, we’d do so. However, nobody has experimented with working less while others work more because competition will eat you up.

The comment of Tyler Heaps gives a clue:

“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.

The guide is ok, but I will say that nothing works better than having a problem you’re trying to solve. The rest comes naturally. I taught myself data mining (now called machine learning or data science) in a matter of months because I was trying to build a lead scoring model.

Completely agree. Most business data is noise and most of the signals are already discovered as simple rules and heuristics. On the other hand, if you have a strong signal in your data, even a simple algorithm like linear/logistic regression will be able to help. What I’ll call “signal hunting” is probably the best use of DS resources and also the hardest thing to do.

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.

Del.icio.us 6 years ago

I second this! Algorithmic discovery tools solve for sameness whereas StumbleUpon solved for variety. It was a wonderful tool for breaking out of thought bubbles.

This is precisely the reason why I prefer playlists to anything Spotify recommends. Playlists are human curated. I kinda wish Spotify just bought Pandora and their music DNA. I really mis Pandora’s recommendations

How Epidemics End 6 years ago

Thank you, I was reading the article too trying to get the point and failing to do so.

I’ve worked with a GA implementation before which I don’t recommend if you want to own your data or if you want unsampled, detailed logs. I’ve also seen a full end to end implementation that uses server log shipping to s3, log parsing and complicated ETL processes which I also don’t recommend due to the sheer effort it would take to build.

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.

Actually I don't think that the audience is the problem, I think it's the "tech friction" Do you really want to figure out how to host your own HD videos without a video platform? How to run your own email list without an ESP? How to use SEO/SEM to attract an audience? How to host and maintain blog software? Handle your own payments?

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.

They built a pipeline that complicated for 100gb? That’s insanely over-engineered! Very typical of engineers who just want to pad their resume at the expense of unsuspecting business people. I’ve worked with single server data warehouses on SQL Server that were 10x in size and served the entire company.

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