skysight-inc/HackerNews huggingface dataset:
You wouldn't write the code in the kernel because writing safe code is almost impossible for humans without a lot of tooling help, and that tooling looks a lot like a sandbox.

I think you're fundamentally not understanding why we have virtual machines in language implementations, or process boundaries in operating systems, and why these things are good and useful. Because if you did, you'd see that a sandbox in the kernel is a hybrid of the two ideas.
That's a big list of those who missed the mobile boat:

Microsoft, Intel, RIM, Nokia, HP, MIPS, Sony, HTC

And this are just the few of the big players.

And even if Microsoft lost with Windows on phones, they still try to make apps. I am currently using Edge on Android because its built in ad block is quite good.
I disagree.

I think books on software management and process are mostly lost on someone who hasn't been involved in the process. (Hell many of those books are lost on project managers)

I think the most important subjects to teach students are javascript, css, & sql (or mongo). Before you teach a beginner wood worker the "Zen of wood" you teach them how to cut a piece of wood without sawing off a finger.

The rest will come later.
I like AWS Lambda with RDS and Cloudfront or whatever. It can be a pain setting up the VPC and security stuff, but it seems worth it because as far as I can tell it is extremely reliable and there is no server to maintain or secure.
Something similar happened to me. Utility company called me with important news about my account. I called them back later and the other department had no record of this call even though it was correct information. So weird.
I can second the experience that learning things in order to solve a problem works great. I struggle when I just have to sit down and lear something from scratch, without any direct application to the knowledge. But as soon I can project concepts and theories onto a problem I want to solve, I have no issue learning new things.

Currently I learn a lot about relational algebra and algebraic semirings, because they are part of the theory behind constraint programming, which I use in a current project.
House passes Covid-19 relief package to replenish PPP loan funding
For people that can't afford a new phone every year with a contract. You can buy cheap button-phones and get a phone card that cost you money every time you call but is free while you don't call.
Not only on goods, they even charge commission on shipping costs. With eroding seller protection and stupid changes to the UI, I guess one of the only reasons they still have vendors is their monopoly.
He says that this is a fallacy:

> It reinforces the idea that any one person or piece of code can be blamed for a given failure.

Why is that a fallacy?
Would you be ok with your dentist being OK with her slip-ups?

“I really should have checked the x-ray better before I extracted your front tooth. But you know, I’m not sorry. It was an external constraint — there was a queue of patients waiting”.

I can’t believe how low we let this profession sink. I hope in 15 years we will look at thies era like we look at the Wild West today. Exciting from a distance but nobody would really like to live like that.
So 2 days ago, we received the news that the first human trials on a vaccines by a biotech firm from Mainz have gotten approval by the Paul Ehrlich Institute [1] as well in Germany. Good news, let's all work together to kick this things ass!

Source [German News]: https://www.sueddeutsche.de/gesundheit/coronavirus-impfstoff...

Main source [PEI, English]: https://www.pei.de/EN/newsroom/press-releases/year/2020/08-f...

[1] a federal institute for vaccines
An WHOs advice is exactly what? Take some untested meds, because why not?

Don't act in time, and if you must act, act in the most destructive way possible. Don't close borders before your country has infected. Close the whole bloody country down after the fact!

Im sick and tired of every tech company and goverment using this as an excuse to limit rights and censor left and right. I'd rather have to filter out a few videos about bleach curing SARS than living in this censorship nightmare.
I think it scratches an itch similar to Harvest Moon and, to a degree, Stardew Valley.

The crucial difference for me between AC and SV is that the former all but forces you to take a relaxed approach. SV felt more like a typical game where I tried to do everything the 'best' way, and optimize and 'level up' things. Which is a ton of fun, but also a bit stressful.

In AC, on the other hand, everything is real-time. Lots of activities can only be done once a day, if you build something it will take at least until the next day for it to show up. The shop refreshes items once a day. 'Collectibles' either randomly show up, at particular times of day, in particular months, or during particular events (easter, etc.).

Furthermore, this 'do nothing and relax' philosophy extends to pretty much everything, so for example buying stuff forces you to go through dialogs every time, and both buying and crafting can't be done in bulk (for the most part). Quite frustrating at times, but I do think it helps me at least not find clever ways to stress myself out and 'optimize' again. I have other games for that :).
I'm sure we can all agree that trials with the potential to require medical intervention shouldn't take place in areas with overloaded hospitals. But most areas of most countries don't have overloaded hospitals right now.
Reading this book AND trying to follow its key lessons makes a huge difference in productivity, which I can testify from my own experience. This book is often compared to the bible of software engineering, suggesting that everyone knows about the book (ex: 'no silver bullet'), some people read it, but only few people abide by it. So, its key lessons are hard to follow in the real world, but for a good reason.

We started a project 5 years ago, after a few months of failed attempts. From the very onset of the project, we tried to adhere to the key lessons of the book. Examples are: recognizing the importance of minimizing communication overhead (the most important assets are not people but time), following the surgical model (key decisions should be made by a single individual), practicing effect-free programming whenever possible, allocating enough time for testing, and so on. I would definitely attribute the success of our project to the teachings of the MMM.

Like many books on software engineering (and self-help books in general), just reading a book and learning its contents may not make any difference in practice. Only when you seriously make conscious efforts to practice its teachings do you realize what the book is really about. This is also the reason why many university courses on software engineering are boring.
Agreed. Pure waterfall has become a strawman for the Agile zealots. Realistically, Waterfall is used as one component of the overall design and implementation process.
I think people with computers more than five years old already know that their computer is slow.

Why exactly do you think seven-years-old is too-old, but five-years-old isn't?
IIRC D templates are more powerful than C++ templates, and certainly turning complete. CTFE is also turning complete.
The whole concept of having to 'order' and wait for something digital online seems to be missing the point...

Imagine if Google decided that to do a search I first had to add it to my basket, check out, and then wait for my search to be 'delivered' via a link in my email...
I recently tried reinstalling Lubuntu on a netbook with a very small EMMC (4GB if I’m not mistaken) and couldn’t find a way to slim down the install to the bare essentials.

(It was running 14.04, and that, I think, had a CLI installer with package selection)

Anyone know if 20.04 lets you install without LibreOffice and the like or have some tips on how to get to the old installer?
Show HN: New PHP router wich is faster then Klein
How to create AI song lyrics
Good. The fuckwits have had a platform to spread their uncontested fuckwittery long enough.
Another term for this is the Hegelian dialectic [0]. Very similar to your term playful association but it describes that the "first" old idea, the thesis, allows there to be a counter idea, the antithesis. These two counter ideas morph into one idea, the synthesis. A consequence of this term over playful association is that these New Ideas are more tangible and have less sense of randomness.

An example of this playing out - First came Disco, the thesis. People who didn't like Disco came up with Rock, the antithesis. The combining of those two became Pop, the synthesis. And the music timeline continues (don't overthink the music choices I'm completely guessing)

[0]: https://en.wikipedia.org/wiki/Dialectic#Hegelian_dialectic
We should back up Wikipedia in stone tablets and bury them in various places on earth and on the dark side of the moon, just in case our Library of Alexandria gets burned by an EMP during a nuclear war.
I too have a very good experience with them. Very, very simple and no hassle to set up.

In particular, all the web hosting side of things is preconfigured.
This comparison is like comparing apples to oranges.

I believe we need to get the "context" before judging any situation.
I largely disagree with YouTube's stance here, it's stupid. They kinda forced themselves into a corner with this one, I don't realistically think they can enforce this. Yet this is just another step in them screwing over creators. I'm especially worried about retroactive enforcement. As they often do. For example: which WHO advice do you need to contradict? Would they take down a video from January that says there's no need to worry because there is no human to human contact - as the WHO said in January? YouTube generally speaking has done shady stuff like this and it never ended well. There has to be a better way to handle this but I generally think that Susan has been busy waging a PR battle with people who don't even matter for the future of her platform.
Breakthrough: How to Make Cheap Rifled Barrels at Home
Any comments people?
Can You Get Siri on Android Smartphones?
Will multicloud and Kubernetes finally drive the prices of cloud providers down?
That they do this shows that they have been getting bad publicity by calling the wrong number and give private information to the wrong person. Now and then you see articles about this or that hospital sending faxes with patient data to some company fax by mistake. I'm sure this also happens with phone calls so they are just trying to cover their back, has nothing to do with your security. They get annoyed when it means more work for them.
It would make more sense if the grocery buyers were instead bidding on a delivery service by an instacart shopper. This is really what is happening with tipped groceries delivery.
(I don't speak Russian, yet)

Given how politicized this has gotten, in general for treatment of this virus, I'm not optimistic that we'll be sharing information. Praying I'm wrong.
I've been looking into streams in detail recently because I'm preparing for the OpenJSF exam... maybe this is relevant to you too: https://nodejs.org/es/docs/guides/backpressuring-in-streams/
http://scaleway.com it costs 3$/month for a vps
Probably because there is always a bigger picture: culture, process (e.g. testing, code review, time pressure, feature centric performance metrics).

Surely, the person making the mistake is the proximal cause for a given bug, and surely all other things being equal personal attitude matters (i.e. a more careless person is going to make more mistakes), but if you zoom out to the big picture you see other responsibilities and more importantly you see opportunities for improvement that vastly exceed the playoffs of "just putting more care" into each commit.
It's going to harm the integrity of the scientific community a lot more once the world starts counting up the lives human challenge trials could have saved.
This sentiment reminds me of Gerald Weinberg's observation of four plus decades ago - "If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." I was trained as a computer engineer, and the difference between those who were taught to approach software development as a craft and those who think bugs are ok and it's really about feeling good about myself at the end of the day is clear and obvious in most organizations and in the product that comes out of them.
No, I'm not going to stop taking responsibility for my actions.
Conceptually, there's supposed to be a process that reduces errors, rather than relying on each individual to be infallible.
There's absolutely no reason it _has_ to be one-way: It's not like the CPU intrinsically speaks x86_64 or is directly attached to memory anyway. When inventing a new ISA we can do anything.

And if we're talking about memcpy over (small) ranges that are likely still in L1 you're definitely not going to notice the difference.
I created a little chat app with GUN (a decentralized database) and Svelte
If you want to discuss that with the GGP, and think you can do so fairly, in good faith, go right ahead. I'm just tired of the absolute degradation of quality dialogue on this site, which has accelerated during this period of mass unemployment and sheltering in place. Extreme misrepresentations have become the norm. It's tiresome and is no way to attempt dialectic.
Well there are multiple kinds of bugs.

You did not test it? Apologize.

You were sloppy? Apologize.

In most other cases I can agree with the author.

All I can add is that, as a freelancer, I always explain (like they are 5) what went wrong. My customers don't care about the details but they like it when they know I made an effort of creating good software (bugs included).
"I'd like to welcome you to this course on Computer Science. Actually thats a terrible way to start. Computer science is a terrible name for this business. First of all, its not a science. It might be engineering or it might be art. Well actually see that computer so-called science actually has a lot in common with magic. We will see that in this course. So its not a science. Its also not really very much about computers. And its not about computers in the same sense that physics is not really about particle accelerators. And biology is not really about microscopes and petri dishes. And its not about computers in the same sense that geometry is not really about using a surveying instruments."
Yeah, I’m aware of that, thank you. I was wondering if there was a way with a faster feedback loop and allowed for bug fixes without creating a new migration.
Basically on 11 of April they started a trial. Up to today WHO approved for trial 9 potential vaccines made in Russia.
Online grocery shopping takes me twice as long, and I lose out on the discoverability of a physical store.
A password manager makes this attack vector useless. The sound of my typing my password on any site is the keyboard shortcut to activate it, my finger silently passing Touch ID, and the "enter" key.
Bluetooth microphone enabled face masks
There are often more costs in sticking with the same tech for forty years...I would still be coding for DOS...I hope with new generations of devs will come better tools...as well as a greater willingness to move on...
Three minute secret trick to bring money, happiness, and success to your life
Show HN: We mapped Epidemiology Twitter to combat Covid-19 misinformation
try https://uberspace.de - name your own price (1-15€), HTTPS, python, sqlite, shell access, databases and much more included. Docs: https://manual.uberspace.de/ https://lab.uberspace.de/guide_django.html

disclaimer: I work for them, but used to be a customer long before I started.
I'm going to assume you are not arguing ad absurdum. Maximizing for X doesn't meant that factors Y, Z, etc. can be completely ignored. Nothing can be optimized "to the last 0.1%" given that other factors become important at that point.

(Eg, it might be possible to make to make space access more robust by spending the next 100 years of the world's combined effort to build a space elevator. But that's not going to happen because there's no perceived need to have that extra robustness given how much human focus is required.)

Forward error correction systems are designed to improve signal robustness in the face of noise - based on a given noise model. It can be made more robust by assuming a much higher noise than what actually exists.

This would probably require more transmission time. But the robustness level, by any usual quality measure, would increase.

"The whole toilet paper fiasco is a good example" ... for my clarified version, yes. That system was was optimized for profit extraction, probably also with the expectation that the government would throw money at them if things went really bad. ("Socialized risk.")

It was not at all optimized for an efficient transition to a widespread shelter-at-home world.

It could have been at least somewhat optimized for that, which is why I think your original statement was too broad. But it wasn't, because it was maximizing for profit, not social stability or happiness or other more nebulous criteria.
I think it's worth acknowledging over your customers that the bug has caused them lost time or other kinds of issues. Whether you do that with an apology, it doesn't really matter, but I know I'd personally feel better when a vendor emphasizes with me.

Something you definitely don't want is to sound like it's an inconvenience for you that they're reporting bugs. Bug reports are extremely helpful and you should be grateful that they're taking the time to report them to you.
The game "Cities: Skylines" is also Turing-complete: https://medium.com/@balidani/cities-skylines-is-turing-compl...
If cable gets cut somewhere, how they find out where it happened?
I think you missed my point.

"EVERYONE IS GONNA DIE AHHHHHHHH!!!!!" is not a good basis on which to be making planetary policy.
Bugs categories are also important. My project and my leadership was destroyed when a non-technical wanna-be "operation" manager without experience in software development, started to see only bugs and reduce all development to bug fixing. Some "bugs" are in reality wrong or misunderstood requirements. Some are missing features. Sometimes the joke "it's not a bug it's a feature" is real. Sometimes "bugs" are edge case we didn't want to solve immediately, until the edge case it's not edge anymore.
I think what is dangerous it's seeing ONLY bugs, focus dev ONLY on bugs. Shift a little the point of view from bug fixing to software evolution.
I would argue if your frontend is just a js client with no server component you are already doing it wrong.

Of course, that then becomes a much bigger discussion about websites vs apps and the current state of the web which we have on here quite regularly.
Why do software engineers constantly try to project that they are a special snowflake of a profession?

Would you accept such nonsense from your plumber, or your dentist, or your electrician?

Software engineering is one of the most fundamental building blocks of modern civilization, and yet it continues to be so fragile because of this kind of cavalier attitude.

Also, apologizing doesn't mean you have a moral failing. It means accepting at least partial responsibility, and being humble about it. Any good org knows that you don't just design your system with the hope that people won't screw up, you need to design it to work despite some amount of screwing up. But in either case, it is still both an individual and collective responsibility.
But they can infect others
Yes it follows Harvard architecture, still you can produce exploits by corrupting memory, no need to rewrite code, it just becomes harder to achieve them.

Basically by corrupting memory, you can achieve that the executing path changes and what was false is now true, thus influencing the outcome of what gets called and their parameters, without having to change any byte of the code.
We used to do it but we stopped because they don’t know how to pick fruits and vegetables, and they never know what a turnip is.
I earn a living from my SaaS. I am a solo founder, responsible for everything. I wrote all the code. My customers pay subscription fees because the software makes their work easier (it's a B2B SaaS, https://partsbox.com/).

Bugs are solely my responsibility: there is no one else to blame. And bugs mean that my customers paid money for a product which did not work as intended (certainly not as I intended it to work). I feel it is definitely right to apologize for bugs!

I disagree with the author: if I worked at a workshop and dropped a hammer onto my customer's foot, I should apologize. No matter what the reason: I could be clumsy, or you could say that no one could be expected to never drop a tool — still, an apology is in order, because I did drop that hammer, and it made my customer's day worse.

Therefore, I always apologize for bugs.

What I did, however, learn to do, and it is quite important, is not to apologize when you are not sorry. An example is when a customer is unhappy with the pricing, or complains about a missing feature. Many people will begin a reply with "I'm sorry, but…", and it's the wrong thing to do. I only say I'm sorry when I really am.
How the Spartans would fight Covid-19
I literally made the same comment a few days ago but here goes: every thread about a study such as this one is has criticisms concerning the scientific accuracy even though all these studies point to the same conclusion and not one of them provide evidence to the contrary.

This isn't exact science, we're in the middle of a pandemic. But all these antibody studies are pointing towards the same conclusion.
"In NY, the issue was not about wanting to be tested, it was about "are you there when they're picking people to test""

It's the same critique. If you pick the people anywhere other than from their home, the argument is that they're not at home, therefore they're more likely to have it.

OK, so how do you get them in their homes? If you solicit them on the internet, then there's sample bias because you're telling them they'll be tested. If you knocking door-to-door, it's the same thing: you have to tell them what you're going to do, so you're "selecting for people who want to be tested". You can't win.

"Or at least pick people truly at random,"

You can't force people to take blood tests against their will. You have to tell them what you're doing, and why you're doing it, and they must consent to participate. The same objection always applies to any "random" selection of humans: it's biased towards the people in the place at the time of selection, who agreed to be selected.

"you can at least try to account for the ways in which your sample is likely to be different from a truly random sample."

Right, as all legitimate researchers in this area do.

As I said before: this is all just a highbrow way of rejecting studies for lowbrow reasons. You will never find a survey without some form of sample bias. You control for it and move on.

We are now seeing multiple independent serological surveys with different methods pointing in the same direction. It isn't a methodological error.
On this day in sport: Niners take Smith as Rodgers slides, Long and Gayle set
"You are under no obligation to remain the same person you were a year ago, a month ago, or even a day ago. You are here to create yourself, continuously" --Feynman
Out of curiosity, how would you say that relational algebra and algebraic semirings help you with constraint programming? While that can indeed be useful in some cases when doing research in constraint programming, I am curious how it helps you?

Background: I'm a researcher in constraint programming and sometimes user of it in work-related projects.
What were the nice parts? Curious on Xubuntu 20.04 now but to be honest I dont think I notice anything different than 18.04 or earlier
https://www.youtube.com/watch?v=NmRlvX3VrAQ