skysight-inc/HackerNews huggingface dataset:
> the solution for which is to use icu

We ran headfirst into this issue at my company and we've actually been recommending the opposite (use the "C" locale on the database, treat collation as a render level concern).

I have a whole write up explaining the technical motivations behind that recommendation: https://gist.github.com/rraval/ef4e4bdc63e68fe3e83c9f98f56af...
Ask HN: What technical skills will the starts ups of the 2020s be found upon?
What if the construction cost of the fusion plant is so high that the electricity price is not competitive? That's already a concern with recent fission reactor projects, where the investors demand price guarantees from the public.
Quinoa is also an excellent source for a full amino acid complex. It has substantially higher Lysine content then that found in other grains.

[1] https://www.ncbi.nlm.nih.gov/pubmed/1546052
Fargate definitely takes some time to figure out. It took a while for us to realize that we needed to bump up our instance sizes because the default instance was a t2.micro.

However, now that we got it configured properly (took about 6 hours over the span of 3 days to catch the issues), we flawlessly serve 11M API requests/day without a problem. We were running these on DO boxes, moved it over to elastic beanstalk which caused more problems than it was worth, and finally landed on Fargate.

Tried EKS, but it was a bit more cumbersome than we would have liked for a K8s service. (We run another product of similar scale on K8s via GKE).

If you're looking for something closer to Heroku than K8s, then Fargate is decent option.
Agreed. Would like to see an article on tooling, to address common pain points. This article simply says "try a monorepo", and when you hit problems, figure them out. It mentions that Twitter had issues, but no specifics.
In the days before mobile devices and pervasive internet, retreats could have a productive use. Get people out of the office, clear their heads, get them focused on whatever task you think is necessary to perform away from work (brainstorming, team building, etc).

Now that's all changed. The last couple of retreats I've been on, people are on their phones handling emergencies all day long and then quickly pull back to their hotel rooms after hours to catch up on work that needed attention while they were gone.

And I've never heard of a company that pays for space away from the office for one to work. That seems like a stretch to ask for.
Chromium on Fedora gets VAAPI support
TL;DR
Block-chain: Solving imaginary problems that nobody has -- and doing a terrible job at it

Yet another example of solutions trying to seek a problem
Calculating shortest paths with neural networks
It's not a matter of memorization, at least for me, it is exposure. You can understand the underlying rules without enough exposure to the subjects of those rules.

I suck at memorizing and dont use it as a study technique, but when picking up a new skill I cant say "what are the underlying principles?" because I lack the context.

(Well I can say that, and then I'll get frustrated when no one can express them for me, and the ones that try dont make sense)
I don't agree with the "rubbish part".

WeWork single handedly changed the way we work. It is way easier to build a tech startup with the help of a co-working space company than before.

I suspect that WeWork's business model ain't the problem but it's competitors, for example in London, UK. Competition drives prices for new real estate, crashed margins.
Ballmer had some bad ideas, but he wanted Microsoft to succeed. He didn't see the attrition as a problem.

The Sears folks are pirates, they don't give a shit about Sears and just want to extract as much money as they can.

Big difference.
All the other languages OP mentioned make a good deal of use of prefix notations.

f(x,y) is a prefix notation and so are command languages: "command arg ...". Statements like "while (x) { y }" or "return z" are also a prefix notation, as well as declarations like "struct foo" or "int x, y".
Why? The {} doesn't prevent glob expansion or field separation.
This is very sad indeed, because Qbs was both well architected and well executed. Very fast and the only build system where I never had to clean the build because the build system broke itself due to bad design/assumptions (e.g. mtime checking).
Brand new ‘Captain Marvel’ trailer may reveal the origin story of the Avengers
That sounds cool. Could you elaborate on this "Our use of Bazel quickly gets us around git scale issues by enabling external dependencies that can be loaded into the workspace without fully vendoring everything."?
I tend to agree that Uber and Lyft are qualitatively different from traditional cab companies although, as many others have said, I'm not sure they have much of a moat or economies of scale. For the overwhelming majority of Uber users, it's irrelevant that they're in 72 countries or even multiple countries. In fact, I'm sure many users would switch to a better service that just operated in their own city.
Blockstack engineer here. Your points are well-taken, and are straightforward to address.

Blockstack uses a storage system called Gaia, which in a nutshell acts as an overlay on top of existing commodity storage systems (including cloud storage, your personal server, decentralized storage systems, etc.). Blockstack apps like Graphite Publishing interact with the user's data via the user's preferred Gaia hub. The Gaia hub holds the user's storage credentials (if applicable) and uses a storage driver to store data to the underlying storage system, so applications don't have to care about interfacing with a specific storage implementation (Gaia and Blockstack implement their own authentication mechanism for applications). In the default on-boarding flow, you get signed up to use a Gaia hub that uses Azure blob storage to host and serve data.

That said, if the operator of your Gaia hub's underlying storage system can determine that content you store is objectionable, then it would be obliged to take it down. However, to prevent such power from being abused, the user has the ability to switch Gaia hubs and migrate their data between Gaia hubs. If you notice someone storing objectionable material in Blockstack, you should notify the user's Gaia hub's storage provider so they can take the appropriate action.
That's not true in the slightest.

Medicare - gets an automatic discount equal to the average discount that commercial customers pay

Medicaid - gets another 23.1% discount on top of what Medicare gets

VA - lowest price of all customers, get at least a 24% discounts on top of what Medicare gets
True! There is a lot missing. Is this just a side-project, never more than a few hundred bucks a month or is the plan that you want/expect it to take off and then you can hir emore people?

YCombinator will not take on companies with one founder because the non-direct workload is significant in most cases and few people would have the energy to keep going through all the set backs. Even if you can, you are unlikely to go fast enough to make the most of your product before the competition starts taking your customers.

Of course there are exceptions and small projects that just work but unfortunately, you have to take some serious risks to give your company the best chance of success so trying to hold on to a "day job", for example is a distraction from your new company.

Best advice is probably to find some local entrepreneurs and get their advice. Paul Graham writes about stuff but although he has a lot of experience, it doesn't necessarily mean his advice is 100% reliable or accurate - which also doesn't mean that you should ignore it!
What if you take a barista, buy a percentage of his or her income for two years, and use that to make the barista an engineer?
It's really nice to see a good-looking computer. Not that the Z's aren't cool, but they are, essentially, large black bricks.
Hmm, perhaps we’re talking about different things but I don’t mind memorizing the alphabet of a language or (partly) its vocabulary but the pronunciation is best learned in terms of its fundamental components and to an extent, so is the vocabulary.

Fortunately, most things in modern life require no active memorization. You use and you remember.

But if I were to learn Hindi, I would memorize the basic glyphs of Devanagari. It’s the highest ROI operation for the task.
You are reasoning backwards. Had the cause been something besides a bone spur, such as a tumor or vascular problem, the X-ray might have missed it. Some things like soft tissue calcification don't show up as well on MRI as on a plain X-ray film which is a really low radiation dose these days anyways. Go read up on the terms sensitivity and specificity.
I'd be really excited and willing to pay much more than the normal mobile app price to have this for my podcasts.

Nothing pisses me off quite like the time waste that is podcast advertising. I skip them, but I was dreaming of a system like this...
How to stay motivated when you come back to work after a holiday
For me, web development quickly led to full stack development. Once you can comfortably write the full stack, you’re pretty much guaranteed to find a job doing that somewhere.

I recommend looking at job posts for the jobs you want and teaching yourself the technologies they require. Consider looking for paid internships, especially if you’re in college (even if you’re just taking some community college courses).
I've had the same thing. It was impossible for me to remember complex mathematical equations in school until I figured out how to derive them myself. That didn't help me with integration, sadly.

Same with history: years are meaningless. What's interesting is how historical events follow from earlier events and lead to later events.
Community Podcast – Nutanix Files: File Storage for the Cloud Era
Longer Equity Vesting for Founders
Detecting speech and music is particularly intriguing for different variable playback speed for speech bits and 1x for music bits.
Hyundai shows off 'walking car'
WeWork is exactly the same everywhere, just as you described in the US. It is far too noisy to get any meaningful work done.
Even if they only increase your speed by 50%, it seems like a worthwhile gain. Anything to get to that escape velocity.
> WeWork single handedly changed the way we work.

Why? Coworking is not a new concept. There are plenty of local coworking spaces in every city that has WeWork. How are they better than their local competitors?
>It has as much bioavailable iron and protein as the same size serving of ground beef

Which ofc it's nothing but marketing nonsense considering that the most bioavailable form of iron Heme-iron is found only in meats.
> Does the practice of keeping all code together in one place lead to better code sharing? In my experience that's clearly the case.

This is where abstraction comes in. When done correctly abstractions are necessary so that you can separate your work from things you don't want to work on. In my application I want to be able to access and modify files on the local filesystem. I don't care about the differences between opening files in Windows versus Linux or the intricacies of how filesystems work at the bit level. My application evaluates some code and writes some output to a file. I use Node.js to solve for a universal file management API. This is an example of a good abstraction because the separation is clear and explicit.

The simple rule for abstractions is if you can do the very same job in a lower level you don't need the higher level code. In the Node.js example you cannot access the filesystem in a lower level, because no such standard library exists to JavaScript.

Bad abstractions don't provide separation. Many times developers want to use an abstraction to solve for complexity, but inadvertently do the very same things the abstraction is supposedly solving for just in a different style or syntax. Many JavaScript developers use abstractions to access the DOM or XHR. XHR is simple: assign a handler to the onreadystatechange property, open the connection, and then send the request. You lose huge amounts of performance by abstracting these and dramatically increase your code base and the separation between the API, the framework performing the abstraction, and the code you are writing are all superficial and self-imposed.

By using and enforcing good abstractions while avoiding bad abstractions you keep your application far more lean and restrict the focus of your development team to the goals of the project. Without that your code isn't a monorepo, its a dependent library of another repo.
About 20 years ago, I implemented a hash table that used binary trees for buckets. It was supposed to support Unicode strings as keys, and I used the Windows comparison functions to figure out how to compare the keys, in order to handle case insensitive lookup IIRC.

I tested the table with randomly generated strings, and was puzzled to discover expected lookups would fail with some table constructions. I narrowed it down to inconsistencies in collation.

It turns out that the collation order implemented by Windows was not transitive. You could have three code points, a, b and c, where a > b and b > c and c > a. Sort order is well defined within blocks, but there isn't necessarily a meaningful sort order across blocks; how should your Cyrillic letter compare with your Greek letter vs your Armenian letter?
Star ratings are for Medicare plans only, not commercial. They are related to the quality of the insurers for the customers, not prices.
What does Postgres Aurora use?
I can’t provide a good answer to your question, but as a failed solo founder my talk on my experience may interest you: https://youtu.be/huOzokY_fME

In particular in the Q&A I talk about some things I would have done differently. But one of those things was that I would not be a solo founder again - I just don’t have all the skills necessary to both do the product and the business side.
Lot to take away from pricing design[0] section.

https://www.landingfolio.com/category/pricing/
I'd like to see a model where Patreon expands into making their apps more optimized for audio/video playback.

People could produce ad-free versions of their podcast for Patrons.

Apple or other podcast vendors would also be in a good position to provide an open standard for subscription podcasts without ads.
Cofounders are indeed critical to success. Don't feel tempted to compromise just because you are in a hurry (same as marriage!).

Also, you should plan for bad outcomes like a founder who doesn't fit in, can't fit in, etc. and ensure you haven't signed away a load of equity, which will make you want to keep them on board! Take legal advice on a good balance between attracting good talent and not risking the company equity in the process.
How would you go about finding a salesperson?
Curious where you get "Hadoop is gone" by two companies (who employ hundreds of open source contributors and committers) merging. I think it's in fact the complete opposite. I get the whole buy-in into the FUD that Cloudera ships proprietary software so they're evil, but the fact of the matter is their core system (CDH) is 100% open source. Impala, open source. Kudu, open source. Anything that is in CDH that isn't in Apache Hadoop is in a pull request. You can literally download every last source file that you trust your data with.
It is very hard to honestly evaluate your own idea, because it's, well, your idea.
You get to tell about it to someone. And when you tell and ask for feedback and help - voila, you are not a pure solo founder anymore.
Location: Pakistan, Karachi (GMT + 5)

Remote: Preferred

Willing to Relocate: Yes

Technologies: Python(Django), JavaScript - Angular, Docker, Kubernates, Jenkins

Resume: https://drive.google.com/file/d/1r_OcRqiyuWSPAeIOfrOlbPbt8iw...

Email: adilmalik393@gmail.com

Linkedin: https://www.linkedin.com/in/adilmalik393/
I've already seen some magic tricks similar to this with some small HD cameras.
I disagree, you should know enough about what field in your in so that you have some credibility.
For me, the big advantage of Electron is that the entire app, all of its dependencies, and its browser are packaged together into a single installable. This frees the developer from worrying about which browser or version the user might have. I'm not sure that it's true anymore that "native apps are always light years better." Spotify is probably the most famous Electron app. Would it be better if it were native?
That too. So how is all computer science not 'web dev' and not a viable career choice? Assuming we are talking about the "right" kind of web dev, I guess.
You get into some fundamental signal-processing type issues in terms of how quickly you respond to increases in a given value (incoming requests in this case, but it's a general issue) vs. (in this case) spinning up too many things and overcharging the customer. There's a limit to how reactive Amazon can be here, even in theory. You may have to do some pre-sizing if your needs are that great, and choose to take a possible over-provisioning hit vs. a possible underprovisioning hit. I think it's pretty obvious why Amazon would choose to bias in the underprovisioning direction in this case.

(There's some really good stuff in the signal processing field for anyone responsible for high-scale systems. An underrated branch of math for computer programmers. Believe it or not, the "fundamental limits" I'm referring to are the same ones involved in the Heisenburg Uncertainty Principle, when you get down into it.)
I remember Olivier Giroud breaking his foot by blocking a powerful kick from very close range.

So I think the answer is, there is a certain healthy respect for a ball kicked at close range by another professional soccer player.

EDIT: Also, looking at it again, looked like the player was trying to get in front of it, and just couldn't make it in time.
[video] Wobble chess set
I have always wondered what the value of common shares really is in a founder controlled voting corporation. For example, SNAP, which is fairly pure, what does that share of common SNAP give me? It seems very much a baseball card. It gives me something that while other people see it as valuable it holds value and it also coincidentally refers to something popular in real life.

In the end though, if the founders of SNAP wanted to sell SNAP, they'd sell their voting shares. If they wanted to pay dividends, they'd pay dividends to only the voting class. Why would they ever need to bother with including common, what could the common shareholder do, ask a question at the shareholder's meeting?

Q: "In the buyout offer from Facebook, Facebook is buying the Preferred Series of shares only, leaving SNAP as a subsidiary of Facebook. Facebook is planning on a tight integration, one that will essentially turn the SNAP app to a rebranded Instagram. What does the common share holder get out of this deal?"

A: "Well, the SNAP common shares still exist, they remain non-voting, non-dividend shares in the subsidiary. Next question."

Q: "So, the founders get paid, but common doesn't get anything? As a common shareholder, I object and I don't agree to this buyout"

A: "To answer your question, if you look at your shareholder agreement, as an owner of SNAP common, you get the right to ask a question. You will still retain that right to ask questions. As for your second statement, please ensure your spoken comments take the form of questions please."

I think this goes for all founder controlled companies, but even more so when the class structure is used to move voting rights to just the founding shareholders.
Fast Typechecked Markdown Documentation with Clear Error Messages
I am quite decent at vanilla javascript, but building a website in vanilla javascript is like building a REST API in vanilla C. It's possible but will take a long time.
Good to know! I work just a block or two down from the Unilever Canada offices in Toronto. Hopefully they'll decide to bring it in.
It's essentially the build a little/sell/build a lot cycle you mentioned, but you want to minimize the first step as much as possible. As tech folks, it's easy for us to overestimate the importance of technology to our end customers. They're not buying code, they're buying a solution that will make their life easier/better.

"Sales" is a long term process, but the first meeting usually starts with understanding the customer's problem. If you build something before that (and demo it at the beginning of the meeting), you can bias the process with your assumptions. Instead, if you try to get inside the mind of your customer, you can get closer to the correct solution.

For a lot of those first sales meetings, you don't necessarily need technology to demo. Instead of showing/telling your customer, you're starting by listening. Then, you can build a small demo of something interesting before the next meeting (often, this is more to keep the conversation going and explore new ideas than to immediately solve the customer's entire problem).

I agree with the other comments mentioning an initial (days/weeks long) MVP build cycle. However, over the past few years, I've found it helpful to adopt this mindset: "my idea for the best possible product is at least slightly wrong, and the more code I write the harder it is to fix". There's a psychological concept of functional fixedness, where you view an object only as its traditional use. I think a similar concept exists in technology. Particularly as a founders-only company, the technology you build has some inertia, and impacts your mental models of the problem you are trying to solve. The more code you write, the higher the "cost" of changing (both in your mental models, and the technology itself).

All this really means is you're right about the build a little/sell/build more cycle - but what you build is less important than what the customer says. The first build is often just a means to start an interesting conversation about the customer's true problem, and you might need less technology for that than you initially assume.
A Reliable Video CMS Is More Than Just Video Sharing
There's no doubt that it's great for you as a consumer of VC-subsidized services but given that their largest investors are basically echoing what the OP wrote, I would have to agree with "rubbish" differentiation.
My mother has an interesting story related to this: she is/was a child prodigy. She graduated high school (Texas, early 50's) at age 13, earned an accounting undergrad at 16, and then University of Chicago law school. During law school, she worked as a CPA, and although she knew her job, all the tasks, roles, and strategic aspects of her position, it was not until she worked as a CPA for a few years when one day "it just clicked" and she realized what she was doing. She says it was a shock to her system, simply realizing. It ruined her productivity for the day, but she laughs now, telling about the strange questions she asked people that day.
Good advice. I met a guy who was selling screenshots of a product to ensure it did what people expected. He then got a team and built it and recently sold his company for some good dollars so this isn't as weird advice as it sounds!

Also be careful about using a single customer to "co-design" your product since it can affect appeal to other customers.
While I don't necessarily disagree with you on that, and I do think a lot of the hype comes from speculation, its worth noting that many ubiquitous technologies we take for granted started as a narrow niche.
2018 Microservices Trends Reflection
It's an open source company you can find all their releases on GitHub and try it yourself if your model is supported https://github.com/commaai/openpilot/blob/devel/README.md#ha...
For a tiny subset of "we." And, in any case, there are lots of local alternatives.
As the quote goes... Money can't buy happiness. It can, however, buy many things that can make you happy.
second kinesis.
after getting one for work, the wrists are not hurting anymore!
also, now I touchtype on other keyboards as well, which I could not do before.