skysight-inc/HackerNews huggingface dataset:
Assuming that this is not a fake - who is the target audience for a such page? They are not talking about baby diapers there, but CPU architectures. I just can't imagine that someone responsible for choosing a CPU architecture will base his/her decision on a page like this. Then why it exists? To show us that ARM is afraid of RISC-V? Ok then, message received.
I'm using Pomodoro Technique to focus on urgent tasks.
I loved this language. I still have all the papers somewhere. Unfortunately, the announcement of Java killed the few remaining chances it had of outliving General Magic.
Twitter stocks are tanking today. Here is why
The simplest possible program that is not correct is no program at all, so why bother?
I've found that what keeps more programmers from simplicity is that people like things to be in order. Like their desks or their living room. I've found that seemingly messy code that are actually simple perform better than complex supposedly in-order code.
Little bit of both. But essentially the problems are getting simpler. All sorts of problems that used to occupy a lot of my time early in my career are now effectively "solved" and just need a library or SaaS to plug and play. CMS, e-comm, analytics, CRM are all pretty push-button at this point. Maybe some API calls to be made. I remember once needing 3 people spending a month trying to get SSL certs installed on a load balancer. Now it's a checkbox.
As aoeusnth1 points out, I was wrong - it is indeed looking to be much like AMD's own multicore x86-64 chips.
React Native is 0.56 now available
ARM is playing a very, very dumb game here. Do they seriously think any prospective RISC-V user has not taken this information into account? Whomever goes on to design an ASIC probably knows what they are getting into well enough.

ARM would be much wiser to embrace RISC-V early, spearheading this effort and bringing RISC-V users into their tools and ecosystem.
I want to build a small, personal photonics lab. What do I need?
> Then why it exists?

Propaganda ("FUD"). SEO.
"redefine correct" = "find a better version of the problem". Software development starts with requirements analysis.
Luckily this was also the time when people played the same games for years.

I played HL&Mods until 2004 or something. So I didn't really "need" a better GPU.
Say what?

All those legacy systems (probably) shipped with a weak IR filter, but the CCD on the the devices will more than happily react to a bright IR light.

This is even how the majority of "night" cameras operate. They ditch the IR filter, then illuminate the scene with IR.
Unlocking Intersection Types with 'var' in Java 10
The general assumption at the time when VW was put under a microscope for these issues is that everyone is cheating, VAG just got caught first.

What stinks seems to be the way the regulations are being implemented moreso than what sort of detours the manufacturers can take to avoid them.

I won't be surprised when we see more auto makers added to the list, however I wonder if anyone will criticize the regulations instead of shaming auto manufacturers.

Here's a non paywalled BBC article: https://www.bbc.com/news/business-44763905
Comment about not posting irrelevant inflammatory statements removed and turned into a submission here: https://news.ycombinator.com/item?id=17490716
Pay wall. Anyone have a link to a cached version?
Yes, correctness absolutely comes first.

One way to achieve greater simplicity is to negotiate for fewer/simpler requirements for the first revision. There's often a core set of functionality that can be implemented correctly in a simpler way, and that gets the work done. Once that's in place it's interesting to see how often people lose interest in what were "hard" requirements before. It's also common that new asks have little to no resemblance to those unimplemented features, and are instead things that they found out they needed after using the new system.
How sure are you that a given program is bug free? I feel that only very rarely would I ever assert 100%. In fact, I would generally assert with 100% confidence that there is some overlooked edge case. How many users that bug may affect... well I would generally give that a small percentage, but it still doesn't hit the boolean state of correct.

So correctness is generally never satisfied in my mind. At any given moment, the programs I am working on are in some way broken in my mind. Even if the other programmers thought that correctness was priority number 1, I will never consider the program correct. I will always suspect there is some snake in the grasses.

I suppose you could feel the same way about simplicity. I think the most charitable stance would be to give them the same level of importance. Overtly complex code cannot easily be proven to be correct amid changing business requirements. Easily testable, complex code with a full functional test suite is at less simple in one sense. Patently incorrect code is hardly valuable regardless of how easily one can understand its function.
Requiring a 10C difference to generate power isn't useful when you only have a 5C difference.
It's a clickbait headline. The story is more reasonable, about more billionaires coming from middle class or better backgrounds.

This is what you'd expect with there being more middle-class Americans than there used to be. I don't think that makes their stories boring.

I suspect availability bias. It misses billionaires not in the tech industry, like Oprah Winfrey. (Not young, but what are some others?)
It highly depends on what exactly you want to integrate on which robot. Stuff like control algorithms can be dependent on the type of robot used. Also, a lot of this stuff is already present in ROS as a downloadable package.
Parts of the some European cities (e.g. Edinburgh's New Town) have regular parallel streets - just not quite at the scale of US cities:

https://en.wikipedia.org/wiki/New_Town,_Edinburgh#/media/Fil...
I don't know if we can say Zuckberg is boring compared to Buffet - it would seem to me an intraoffice messaging system is comparable to a paper route in terms of the required skills for either profession.

In regards to the need for opportunity, I fully agree with that - I was trying to teach myself to code at an early age, but the computer I was trying to teach myself QBASIC with didn't have enough memory to load the help file, and I didn't have access to any other resources growing up in a rural community in the late 90's. Reverse engineering Gorillas and Nibbles was beyond me without outside assistance, so it was wasn't until my late twenties that I was able to rediscover the passion of my youth and turn it into a (still growing) career.
https://towardsdatascience.com/stylometric-analysis-satoshi-...
Simplicity is ALWAYS something desirable to achieve. Correctness comes first.

As code is originally written, people are (or should be) using the most "obviously" simple approach.

A Breakthrough in simplicity is often the result of additional thinking and hard work. (And cost)
The simple answer is...because they're all geeks who just got lucky.

They didn't need to work their backsides off to get to where they are. They just made a semi-decent product at the right time and money was thrown at them.

There are millions who just weren't there at the right time and probably far more flamboyant ones because the longer answer is the author is probably mixing up boring with stable.
> Dask requires users to keep in mind the computation graph and persistence

I saw this statement in the official documentation too ... in practice this isn't a big burden - if you're going to reuse something, persist it. That's about it. "Keep in mind the computation graph" doesn't mean anything - the docs and guides really gloss over why I don't have to do this. Not thinking about these is effectively a decision made one way or another.

The papers offer a bit more insight: Looks like the novelty is in the scheduler that was built for low task latencies and high throughput: wonderful for all kinds of compute-intensive workloads (they talk about Reinforcement Learning, for example) and definitely fulfills a need. They especially talk about how some tasks are dynamic in nature and spawn new tasks unpredictably and how you might not know the whole task graph in advance, or how some work can be done either locally or globally in a transparent manner, or how if you have many tiny tasks, the task overhead can kill you. But don't see what this buys for traditional table style data-heavy analytic workloads which have none of these problems.

Don't get me wrong - I'm excited about more contenders. The neat stuff about ray seems to be the scheduling model they have, the fact that they built in fault tolerance by storing all state globally in a sharded data store (redis in this case), but also they use Apache Arrow and the plasma store, which means zero-copy data transfer between workers and other data stores - awesome. Dask should probably also consider some of this. But pandas + ray just seems like an odd couple - it seems like ray's scheduler was built for the opposite use case.
Your VC needs a billion dollar exit and would like you to be that exit but does not need you to be that exit.
The AI revolution has spawned a new chips arms race
In a way, simplicity is the end result of reducing the complex and correct solution without affecting its correctness.

As in math, you come up with the "simple" solution of 0.5 only after you've realized that the "complex" solution is, for example, "sin(pi/4) * cos(pi/4)". There might be no other way to discover the simple solution.
The article says:

> shortened the silicon nanowires to 0.25nm

That's a very short wire. Isn't that about the diameter of a silicon atom? I thought the smallest wires we could make on silicon were about 20nm _wide_.
I have not used real robotic simulations, but I have used RViz and ROS for testing my own path-finding algorithms. Performance on my Late 2015 MacBook Pro was stuttery (about 15-20 fps), but still good enough to be somewhat usable.

Overall, I had more issues with finding good resources on the rospy module than anything else. It seems almost all robotics development with ROS is done using C++ instead of Python (in my little experience), so there is little I could find in terms of code samples that would allow to get past a project like this (https://github.com/gandalf15/CS3027--CS5059--Robotics-Univer...).
This is a long, meandering article with a pretty arbitrary notion of "self-made." It wants to lament both how old-school billionaires are getting rarer and decreasing class mobility. Both points are poorly made -- I read through it and it was a waste of time.
Interesting to compare the frequently used languages of those using containers to the Stackoverflow Dev survey.

- Javascript 57% use vs 71.5% I had always thought JS was high on the Stackoverflow survey because it included people using it on the frontend. Not necessarily the case.

- PHP was third at 36%

- Golang was fourth above Java
Hardship is still a story that is told in the Startup world, because how else can you get talented young people grinding 120h/week on $40k with a high risk of the company going broke in the next 1-24 months?
I'm the founder/CEO of The Lobby (YC W18). Looking for a founding team member to lead our engineering efforts in NYC. Here's a post I wrote describing it genuinely: https://medium.com/@deepakchhugani/im-looking-for-a-technica...
And on the other hand the grand canal in Venice is celebrated just to point out canals can look good https://en.wikipedia.org/wiki/Grand_Canal_(Venice)

It has a lot of decorative stuff in the form of buildings down the sides.

Maybe if you wanted to prettify the Panama you could stick something like the Marina Bay Sands by it https://www.google.co.uk/search?q=marina+bay+sands&num=30&so...
Best service for paywalled articles from my experience
https://outline.com/TF7GJv
My version of this is test cases (e.g correct), simple, fast: in that order. With test cases you can refactor your initially complex and naive solution as many times as needed until the solution is easy to understand and elegant. I've rarely made something simple the first time around. To get to simple I need to work at it. And I'd like to know I'm not breaking things when I do that work.
Show HN: Caption Cat – We post the photo, you write the caption. Every day
Software is rarely correct, because if it is not correct today it will only be correct tomorrow due to skilled interventions, and if it is correct today then it will almost certainty not he correct tomorrow without skilled intervention. The chance of skilled intervention is always low.

Simple software reduces the skill required to intervene.
>"I can win if I just work harder/emulate those more successful than I -- ultimately I'm in control and nothing else matters"

While obviously there are things outside individual's control, is this really a harmful outlook? I'd certainly rather look at my life as if I had agency vs thinking I had none, or it was incredibly limited.
In the free software world, this is not a huge problem. You can make new CPUs and recompile programs with far fewer effort. All that complexity really comes from monetization.
Radioactive materials are used in wristwatches.

https://en.wikipedia.org/wiki/Tritium_radioluminescence
You missed the point of the article if you interpreted it as correctness being intentionally sacrificed for simplicity.

Plus, a complete leap year implementation is already what I would consider simple and most standard libraries already have an implementation for it you can use directly.
PWAs: Tools to develop and debug Windows 10 specific features
If correctness is some kind of continuum rather than a binary choice, then pick whatever trade offs, cost, and other factors you want.

Plenty of times correctness is binary. In some cases it would be: passes all tests. Or: meets all requirements. Even if it could be "more" correct (or "more" simple), but those aren't part of the tests / requirements.
If it helps, I’ve used Redux in a couple production apps and loved it. Boilerplate can be a bit tedious at times, but in exchange you get a lot of sanity and clarity in your code.
Our library has a program to read 1,000 books before Kindergarten (age 5 or so), and the kids get prizes along the way.

It's easier than you might expect - the books are all short picture books at that age, so it's easy to just sit and read 5 at a time. Also if you read the same book 40 times, then it counts 40 times - so it's not 1,000 unique books (although we probably have read 1,000 unique books by now too). We also read 2 or 3 books every night before bedtime, so that adds up quickly.

Our library doesn't have any checkout limit, so we just get 30 at a time and go back once every week or two.
A Gentle Introduction to GraphQL with Elixir and Phoenix
So....young billionaires are boring because they're mostly in the tech industry and haven't seen as much hardship as past billionaires (because they have early access to a computer) seems to be the main thesis.

But...

1) even the hardships by old billionaires seems to be temporary or brief, i.e. Warren Buffet finding a way to make thousands of dollars through his paper route at the age of only 15

2) The writer provides a single instance of a 'boring' young billionaire, being Mark Zuckerberg

3) The writer provides multiple counterpoint examples to the thesis in the text with Elon Musk, Jeff Bezos, and Sergey Brin as being tech billionaires that came from nothing.

I wouldn't be too surprised if there wasn't some truth to the thesis (although 'boring' is a loaded and subjective term to begin with), but the writer does a terrible job at defending their position.

I'm seeing a lot of these poorly written articles lately. Journalists have a preconceived point they want to make, make it in the headline, and then pretend they're writing something that supports it but not really supporting their thesis at all, counting on the fact that most people are only going to skim the article and not critically evaluate it so they can put their idea into people's heads 'Hey, young billionaires are all totes boring, right?", inception style.
They had no struggles, so maybe they're missing parts of life that let you quesion the status quo?
you have to be boring to not want to just have fun past your first few millions.

elon musk is the exception, as he just made money doing fun things.
Difference Between the MacOS and Linux Kernels [Explained]
Big Clapper is a $4,500 robot that will applaud you until the day you die
How to not get screwed by your software developer
Also, I think this bug also deserves a name, but nothing comes to mind. "hddunlock" maybe?

hddbleed?
This is some really cool information! I implemented a map-parsing algorithm that used a data structure that enabled neighboring cell access in constant time. It's biggest weakness is that very high-resolution occupancy maps take quite some time to render. I'm very inexperienced when it comes to sharing my coding projects with the world, so any feedback on the readability/accessibility of my repository would be greatly appreciated! https://github.com/dwrodri/LQTLD3
it's interesting to genotype using embarkdna.com (not affiliated with them, just a customer)
DeepMind papers at ICML 2018
Make it work, make it good, make it fast.
The article and lot of comments implicitly have the assumption of you must sacrifice something to get simplicity or correctness, at least at beginning. Performance can only be picked up “later”.

The fact is retrofit performance into a sufficiently complex system is hard, more often then not the system has to be redesigned and rewritten to achieve it, as we have seen with so many OSS project.

I think with right amount of forethought, all three can be achieved. That doesn’t mean you never need to iterate on your software, because requirement always involves.
This seems to mix correctness and completeness.

A good program does only the correct thing in a particular area. It is known to be reliable in that area, sometimes even formally proved to be so.

Outside that area, an ideal program refuses to work, because it detects that it cannot obtain the correct result. This is normally called "error handling".

There's also some gray area where a program may fail to reliably detect whether it can produce the correct result, given the inputs / environment. A reasonably good program would warn the user about that, though.

A "garbage in, garbage out" program is only acceptable in very narrow set of circumstances (e.g. in cryptography).
Best advice ever.

I come from a relationship with my family like the one you described. Now my mother is dead, my father married another woman and all the advice and control they gave me is gone and they barely remember these expectations which some of them I fulfilled but actually at some point I left my home and worked in another city without having money to pay even my lunch. That made me make a lot of money, move from a third world country and meet the love of my life. I didn't have diabetes so maybe for you it might be different, but unless you take control of your life and start to have frequently moments which you are 100% responsible for, you will never truly live.

I always felt weak and had my fair amount of health imperfections, but I once thought that if I'm a bird with an undeveloped wing and I need to do my first flight, I would rather crash my face to the ground and die than to live a shitty life being abused by everybody.

Maybe you can fix your disadvantage with your brain and become a bird that makes other birds fly for yourself.

Also take out this disadvantage mindset. You should make your strong points stronger. You have gone through some crazy shit that those perfect rich white males probably never went. So at least at something you can excell.

Please also take my opinion with a grain of salt, you know your life better than me. Cheers
This story is isn't really a story. The "evidence" the author cites that older billionaires are interesting is that William Buffet great up poor and had a paper route. Extrapolating from this, apparently, the author comes to the conclusion that other billionaires must be interesting.

But think, why is it that this article only talks about billionaires everyone already knows? Why not dig into some lesser known figures on the Forbes 500 and show how interesting they are?

Probably because, as the author mentions in passing, a lot of billionaires just inherited it. Which is about as boring a story as you can get.
Do other countries also have an obsession with rags to riches stories?

Our rags to riches archetype is steeped in the depression as well as transformation from a rural to city existence and the emergence of commerce (as opposed to sheer manufacturing) as the driving force.

We’re not there any more, the economy has evolved and different things are required and opportunities now lie elsewhere. But that’s not to say rags to riches has disappeared altogether, but it’s not spearheading the economy—and that’s not the US only. Look st where new billionaires come from in other places as well. That has changed too.
Drawing and Animating Shapes with Matplotlib
It has been too long. The book described both approaches that both programmers used. I simply no longer remember those details. As I recall, the working program, when explained gave you the "Ah Ha!" experience, and thus was simple enough. The focus of the entire book was more about psychology aspects. One chapter was about how programmers come to feel "ownership" of code.

Another thing: what was an entire program back then, is sometimes a mere function, or maybe a class or code library today.
The barriers to entry of learning to code are falling dramatically though. When I was a kid having a computer that cost several thousand dollars was table stakes, and even then in practice most of the kids who got beyond basics had parents who were also engineers.

These days a good enough computer costs less than $500, and in the last five years the free resources on the web have gotten good enough that anyone can teach themselves without needing any expensive classes. At most you might need another couple hundred dollars worth of books. At this point English literacy is probably a bigger barrier to entry than the monetary cost.
Since you asked:
https://dailyflywheel.com

To be honest, I put as little effort into maintaining this blog as possible. It's a default WordPress setup I use to spew my digressions that never have the opportunity to come into conversation.

It's also to help me log the general flow of how the year went. Increasingly, as I get older, I forget things at a faster rate - not just events, but the general time frame for things. Even when I remember anecdotes, I can only remember it as happening in a general year, maybe in a specific six month period if I can recall enough clarifying detail. The blog really helped me recall specific events that occurred last year in the general time line in which they occurred. My only regret is I've stopped doing it regularly.

Edit: Recalling why I started in the first place sparked my desire to start up blogging again. Hopefully I can keep it up this go around.
Vulnerability is always a Bug.
Weakness is always a Bug.
Weakness is sometimes a Vulnerability.
Bug is sometimes a Weakness and a Vulnerability.

Vulnerability != Weakness!
Show HN: KubePub, a public Kubernetes cluster with batteries included
That's like saying, sometimes apples are so expensive you can't buy them. Perhaps surprising, if you haven't thought of it, but it is an obviously true statement about all tradeoffs. Sometimes you shouldn't make them. Still doesn't help you figure out when you should.