1,691 karma · joined April 15, 2014
My focus so far has been making sure recommendations are good enough, but it would be nice if one could use the site on a smartphone.
There are various recommendation approaches I'd like to try. If the site had more users (beyond the ~4 friends I showed it to) I'd like to try out a collaborative filtering approach (https://en.wikipedia.org/wiki/Collaborative_filtering).
The time consuming part was manually auditing blogs for quality (and to ensure it's a personal blog, not e.g. a BBC feed). I came up with some heuristics (i.e. blogs with github.io subdomains that got upvoted were often good so I blanket approved those) to speed things along, but it did take a while.
I made blogosphere last Summer in order to improve discovery. It’s seeded with personal blogs that have at some point appeared on the HN front-page.
The intent of the site is to recommend blogs and articles to you, with the objective that it’ll get better the more you use it.
The site uses a co-occurrence matrix to recommend articles and bloggers to you based on the articles you ‘star’ and topics you follow. If you’re not logged in, the site will show you popular articles. It doesn’t track what you read, and doesn’t have google analytics. I have some ideas for improving recommendations (i.e. people like you also like.., and improving the auto tagging of articles), but I thought I’d get feedback on whether people want this first.
The site is at an MVP stage, there will be bugs and missing features, but feedback on whether this is interesting to you would be useful.
I worked on a Learning To Rank implementation a year or so ago. What struck me then (and now reading about Shopify's implementation) is that the approach is often very similar across sites, but the implementation is usually rather tailored. You see the same patterns: online/offline metrics; nDCG; click models and implicit/explicit relevance judgements; re-ranking top-k of results, and so on.
Unfortunately there doesn't seem to be a technology tying all of the components of an LtR system together. A managed service like Algolia could be an answer. I wonder if industry will eventually converge on a framework, such as an extension to Open Source Connection's Elasticsearch Learning to Rank plugin (https://diff.wikimedia.org/2017/10/17/elasticsearch-learning...).
It's a really interesting area of theory and practice - I hope Shopify write more about their implementation!
I'd also recommend reading Airbnb's really excellent paper - https://arxiv.org/pdf/1810.09591.pdf.
Rather than editors being at fault, could these indicate that Go is a bit too verbose? I wonder if generic functions will affect this. I rarely write Go, but I can imagine autocompletion macros for `err != ...` could help.
It's a fair question. Service meshes are a relatively recent development, and there aren't many papers on them, despite rapid adoption in industry (e.g. many large systems use a service mesh, and AWS App Mesh is in general release as of last year). This is a decent survey paper: https://ieeexplore.ieee.org/document/8705911.
Service meshes are intended to address some of the operational complexity of running microservices. To take Morgan's definition: "A service mesh is a dedicated infrastructure layer for handling service-to-service communication. It’s responsible for the reliable delivery of requests through the complex topology of services that comprise a modern, cloud native application."
To answer your question briefly, a service mesh is not a completely brand new thing, the pattern seems a natural improvement to having a set of SDKs (like Twitter's Finagle) and other things tying an SOA together. Consistency in an SOA is pretty valuable, and separating infrastructure logic (like retries, service discovery) from application logic is pretty nice too. Whether the improvement has been significant, I'd recommend searching for "service mesh" and you'll find some talks describing use cases.
What I have found tricky is finding critical analysis of service meshes beyond "do we need this" (i.e. what are service meshes missing, does the pattern give rise to other opportunities), but this should come as more research is done in the area.
I was a bit confused, did the tech exec just quit without notice when they learned the CEO was pregnant? How would they be able to justify that insanity to their next employer?
https://www.bilbof.com/following
It’s open source if you want to run your own: https://github.com/bilbof/feed
Improving voice assistants in particular, like with Siri, could damage Google unless they’re not careful, since these assistants go beyond search and act as an operating system, to control IOT etc.
Text search is valuable and so on, but I can imagine that voice becomes the primary mode of interacting with the world (internet, etc) in the future. In that world without screens as the gateway, where are the gateway ads?
> One Google engineer from back then says the most remarkable thing about the co-founders' code was that when it broke, users would see funny error message: "Whoa, horsey!"
You're in luck. Rails 5.2.3 was released 20 hours ago.
More seriously, I feel rails is still excellent and I'm happy to work with it every day. I'd be interested to hear more about what makes rails not modern? I find it a very productive framework.
EDIT: If you're talking about missing a JS equivalent of rails, do you know about Loopback? https://loopback.io/
I think many who posted on the Github issue will later regret the tone of their reaction. The treatment of the Docker employee was particularly nasty.
On the free plan there's a one hour cap to meetings, which is ideal as nobody wants to be in a meeting longer than an hour.
We build business intelligence software. Our main BI product solves important problems for the 1000s of orgs using it. We're an international team - ChartMogul is built by people from 13 different countries.
Engineering roles include:
- Backend
- Backend (Integrations)
- DevOps
- Frontend
- Lead (Data Processing)
- Lead (Integrations)
More info at https://jobs.chartmogul.com/Self-employment comes with personal financial risk, but the reason for their lower national insurance contributions (NIC) is to do with pensions. The UK chancellor this year:
> Historically, the differences in NICs between those in employment and the self-employed reflected differences in state pensions and contributory welfare benefits.
Self-employed people are more unlikely to have a pension, and the state pension is about £7,000 per year.
In contrast to this, people who are employed have access to a workplace pension, where an employer must contribute to the employee's pension. The average teacher will have a workplace pension of £25,000 per year.
So, the idea behind the reduced NIC for self-employed people is that they'll put the money into their savings / personal pension. If you're self-employed and adding 3% of your income into your pension each year, then the 3% savings on NIC would be the government enabling you (as your own employer) to 'match' your own annual pension contribution.
One piece of tax relief a self-employed person gets is a reduction of their socialised health care tax: National Insurance. If you're self-employed you pay this tax at 9% rather than the 12% that employed people pay.
The government that commissioned this report tried to remove this particular bit of tax relief earlier this year, but was stopped as people were really annoyed about it.
We have this thing in the UK called 'Zero Hours contracts'. For example, an Uber or Deliveroo driver is on a contract where they can work as many hours as they like. The Uber driver is self-employed, and isn't an employee, so they have to do their own taxes etc.
The government claims that A) Zero-hours contracts are being used to provide less stable contracts for the employers benefit, as a zero-hours contract can be ended without notice (this is definitely true, though I'm not sure how many self-employed people are on zero-hours contracts), and B) that self-employment is overly incentivised in the tax system.
It sounds like this report will be used to raise taxes on all self-employed people because unscrupulous employers are abusing the tax reliefs. But this will have a detrimental effect on all self-employed people (small business owners, actual freelancers, software engineer contractors).
Yet, if at least 1.4% of their 60m readers disagree with you then it can be a sustainable business.
I'm not sure I understand why you care that they have 150 employees. Both Medium and Stack Overflow think at least 150 people is needed to monetize their sites, yet you only dislike one of those businesses.
They need 1.4% of readers to subscribe
They charge 1/3 what the NYTimes does. The NYTimes company has +$1bn revenues.
They can probably get 1.4% of readers to subscribe. They could also charge subscriptions for blogger tools. They could have tiered subscriptions ($5 is the lowest guardian membership, and it looks like you get little for it). They have only just started offering subscriptions so I imagine what you get for $5 will only grow.
150 people really isn't bloat. Stack overflow has 250 employees and I bet you never paid them a penny. SO have VC funding to series D and they have fewer users and readers than Medium.
It seems that Medium has a viable business model: ads and subscriptions. Same as any other media business.