skysight-inc/HackerNews huggingface dataset:
interesting, I'm very curious which tools she's using for all this :)
My approach to negotiations is described in the book "Never Split the Difference" by Chris Voss.
Writing "correct" software is possible IMO, but is it worth it?

For most applications, is it worth spending several times more time and resources in order to make it "correct"? I don't think so.
I came to write something simular.. Just because you havent come accross it, doesn't mean its beyond our capabilities, infact, by definition its within our means.
It should be fair to start with the premise that this behavior creates a noise pollution problem. Otherwise the authorities would not be working to curb it.

Everyone has an excuse, but two wrongs don't make a right. Drivers are not justified to create noise pollution because pedestrians or other drivers are indulging in inconsiderate behavior.

I've lived on both sides of the world and frankly, it all comes down to how the individual regards himself and his social obligations. S. Asia is notorious for it's poor regard of public spaces. These are foundational cultural concepts that I don't see changing any time soon.

Without a sense of personal responsibility the individual is powerless to act. The excuses you provide make the problem perpetually someone else's fault. The comment above spoke to the "entitlement of drivers" and this is the key to the whole issue.

In the west, I've seen known gangsters stop their limo to personally remove a single piece of litter from the street. These are people who explicitly live outside of the bounds of the law. This person could have made his chauffeur or assistant retrieve the trash, yet he took such pride in his neighborhood that he had to do it personally. The contrast is obvious.

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3968587/
https://en.wikipedia.org/wiki/Health_effects_from_noise
Yeah, I think the author is being a little pessimistic here, but for the benefit of the doubt it may be interesting to understand what correct means in that sentence.

I mean, if correct = 100% uptime, 100% effectiveness, etc., then it's not so much of a software problem, but a hardware one.
No One Can Predict Future Climate, So Stop the Scaremongering
+1. In fact even the JavaScript heap isn't limited to 4gb, just the space that pointers can point to. For example, we allocate large typed arrays outside of the V8 heap.
So don't build ghettos. A modest proposal: make every builder donate a proportion of the flats/houses they build to local government, but decide which ones are to be donated by random lot after building work is complete.
To be honest, as a group, I find C and C++ programmers (even the ones with decades of experience) to be below average in knowledge and skill.
Honestly, the whole thing is a total disaster. Yet another game driven by bottom line profit and trying to save costs on virtually everything related to development.

Hopefully users' actions - boycotts, refunds and review-bombs - will prove useful in improving the situation, though I do not believe any game company will learn anything from the incident.
This article highlights some security errors that are not really related to React Native:

1. Firebase permissions

That is a problem of a badly configured server, in firebase you need to write some rules that are less permissive as possible, making possible only to read what the user really needs (for example it's own data and the data that is truly public), same for writing.

2. Debug files in the APK

The map file should not be in the APK (unless it's an internal-only debuggable APK), webpack/gulp can be configured to not produce that file when the target is production.

If you use tools that collect errors like Sentry, you can upload the map file to their servers and avoid releasing it.

It will not stop the attacker from obtaining your API_KEY but it will make it harder (security through obscurity).

Both problems are not exclusive to React Native but are shared to any app/web-app that uses firebase.
It's very amusing looking at the replies in this thread with widespread horn use because in the UK using the horn is very rare indeed. It is sometimes used to encourage someone to go at lights that have changed because the other driver is obviously not paying attention to driving a 1+ tonne vehicle, and used in anger when someone does a "dangerous" maneouvre eg. pulling out on someone at a roundabout, but I always think "if you have enough time to sound your horn, you have enough time to react (and therefore not honk)".

Having said this, there are an awful lot of very angry, selfish people on the roads as indicated by the "dash cam" videos on YouTube (where mostly it seems that the driver has submitted a video of a "appalling driving" but actually demonstrates their own inability to control their hot-headed exceedingly short temper in any rational sane manner, thereby indicting themselves rather than the "appalling" other driver).
"Turn display_errors off" is a good answer for a production website. You will get problems with headers and cookies, if notices are printed before headers are sent. You might also divulge information about your stack to users.

For a development and staging website you do want notices and warnings displayed. For a production website possibly only when testing something.
Dashlane brought back Deadspin for Super Bowl weekend under a new name
Making automatic yet informed decisions when upgrading dependencies
Yes, but look what happened when we tried to digitise and preserve a 1000 year old book.

https://en.wikipedia.org/wiki/BBC_Domesday_Project#Preservat...
Most cities will enforce fines/issue warnings if you don't mow your lawn and the wild grass on it gets taller than a couple inches.

I don't know if this is done to curb the spreading of ticks (and Lyme disease) in urban areas or to avoid "lowering your neighbour's properties value", but it's terrible for bio-diversity... Insects have it already pretty hard in cities and on top of that they've got nothing to eat in the tiny patch of grasses people call "gardens."
> If you get a theory, develop a test which the theory is vulnerable to [...] Some people seem unable, or unwilling, to think like that.

Because developing that test is often even harder than developing theory itself and developing nontrivial theory requires ALL of your mental effort.
It's kind of curious coming out of university where I learned about doing requirements properly and up front (which I suspect kind of tends towards a waterfall approach) then comparing that approach to my work now.

Project managers constantly change their mind about requirements and then wonder why we're shipping late, although I suspect some of this is not considering failure/bugs when planning. Even when it comes to breaking down and estimating work, if the estimates software engineers produce don't align with the high level schedule they're automatically wrong or people start asking about what we can trim down (which somehow is always testing).

Perhaps it's idealism vs reality, but I find it a bit bizarre.
That's extremely easy to explain. They are expensive and therefore nobody wants to be the scapegoat that is responsible for hundreds of billions of lost tax dollars unless a convenient event like Fukushima offers an excuse.
It is said that the Apollo 11 lunar lander computer rebooted twice during the final approach. We could probably not say it was correct, but still it was robust. "for any meaningful definition of correct" sounds a bit to strong as an hypothesis. Maybe we could rephrase: for all piece of software S, there exist a definition of correctness for which S is incorrect. Timings in particular are very difficult to ensure.
Boost Your Productivity by Using the Terminal (iTerm and ZSH)
are you the same guy on r/sysadmin?

Try use MPLS. It's expensive but the latency and bandwidth is guaranteed.
Well, that's one job that's tough to do remote, isn't it?
Writing non-trivial, correct software while not blowing the budget is beyond the capabilities of the human species.
I’ve used WSGR countless times at startups and while they are great to deal with the fees are very cost prohibitive for a bootstrapped company. I think in the case of UpCounsel there’s significant pushback against this business model from big law firms as well as competition. They lost a lawsuit with another somewhat competing company called LegalForce I wonder if that influenced them shutting down.
I'm guessing this is an average rather than absolute amount every day, and I also don't quite think it's possible to 'force' yourself to be more productive, as being productive is both about how fast you think, how fast you type and how fast you come up with solutions to a problem.

No matter how much you force yourself you can't just force yourself not to feel exhausted/restless/depressed or whatever else is effecting your productivity, you sure can alleviate these symptoms, but that's improving your well-being generally rather than forcing yourself to be productive.

So it sort of depends what you mean by force, I'm guessing it would just cause you more stress and make you eventually burn out because you're not in reality becoming more productive by focusing more, you're only stressing yourself out further.
Or until they just slow it down a little... nobody needs a major OS release with 20 shiny new features every year. We need quality and stability.
As a die hard Quakeworld fan, the relatively boring movement physics of CS was one of the things that put me off.

I'm not mentioning this to be a jerk, just that I totally understand how the movement can make someone addicted to a game.

Side note, when id software handed off maintenance of Quake 2 to Threewave, Zoid added full air control ala QW to Q2. Suddenly I loved the game. Alas, Q2ers almost rioted and it was changed back.
1) Main strategy to avoid this is to just coat pipelines with plastic or make them out of plastic. Not all metals are equally susceptible to this process, and newer alloys are being developed that can strongly resist this phenomenon. While it is a problem, it is a solvable problem.

2) What I’ve read is that they’ll build hydrogen sensors and alarms for this.

3) This is hugely overstated for two reasons. One, just because an process contains inefficiencies, doesn’t mean the entire process is invalid. After all, gasoline powered cars throw away more than 80% of the original energy found in crude oil as waste heat. Fuel cell cars may waste more energy than battery cars, but it is less than ICEVs. Also, you do want to have excess heat sometimes.

Second, most of the sources of inefficient are solvable and/or were wildly exaggerated to begin will. Many arguments against hydrogen seem to cite some 20-30 year old source, and had some extremely pessimistic projections like hydrogen tanks leaking 20% or more of their fuel. Most of these projections haven’t been borne out.

4) Why do electrolysis plants need to run at 100% utilization rates? In a renewable world, almost nothing will have 100% utilization. This is not really a big deal since electrolyzers can be turned on and off quickly.

5) That’s true of any subsidy. One of the biggest complaints of the subsidy regime is how wasteful it is, and how poorly optimized it is for reducing GHG emissions. It will be almost a relief if hydrogen gets of those subsidies, since right now it is an important necessary technology that’s getting close to zero subsidies.

6) We don’t really need two overlapping infrastructures. Limit each infrastructure to where it is most effectively used.
Owning isn't free either. Instead of paying your landlord rent, you pay rent to the city (property taxes), the bank (mortgage), repairmen, and to opportunity cost (these x00,000$ would yield interest/dividends if invested and not tied up in your house)

In some places, it's also much cheaper to rent that own after factoring all this in.
We have lost huge proportions of ancient writings because of the amount of resources making and maintaining enough copies took, and the resulting physical destruction.

A lot of works that we know had a big impact on culture, for example, are only known through us through quoted fragments in the works of others. Heraclitus "On Nature" (though even the title is not certain) is one example - a work significant enough that over a hundred fragments were preserved through quotations in the work of others significant enough for their works to have survived, but still the fragments makes up only a tiny portion of his work.

And for every significant work we have fragments of, or know of, there are bound to be huge numbers of works we don't know of because they were only ever mentioned in other works we have lost.

We may have become better at protecting paper copies, but they still require someone to carefully maintain the archives and ensure new copies are made once, inevitably, the number of copies of the works will dwindle with damage.

Having it on paper does not remove the need of an archivist; and the sheer volume required for paper copies means that even with a tiny number of locations suffering environmental damage every year, over time the number of copies will dwindle and new copies will need to be made.

This is true of digital copies as well, but the ease of making them and the density makes it increasingly possible to store larger number of copies, and re-copy them regularly. The biggest hindrance today, I think, is curating the increased volume of material published only, more than the challenge of ensuring there are enough copies.

> So if you have an archive on 5 1/4 inch floppies from, say, thirty years ago and a printed copy I think that the printed copy is likely to be the only one that is now readable.

The amount of archived productions of material for home computers from further back than that suggests that while if there is only a single archive extant, chances are you might be right, it doesn't take many copies before the odds of successful complete retrieval are quite good.

Sure, there is a risk there will be a gap in which we lose material that was only published on more perishable material, but that would by no means be the first time that has happened either - what survives to date is largely the subset that was important enough to be made available in the most durable means and then copied and re-copied because people at the time found them important; not by any means everything.
Be careful with that though as it will only work once and you might not last long there after that.

While the company might give you what you ask for this one time, they will feel blackmalied and will see you as a flight risk, ready to leave for greener pastures at any moment anyway, so they'll prepare themselves by restricting your access to promotions, trainings and critical work so you don't pull that stunt again and slowly reduce its dependency on you and you could soon find yourself training your future replacements. It's all 101 in the HR handbook.

Try it, but only as long as you always have an exit planned.
This is such a non-argument. They could've easily just started with text-diffs, then photo diffs. And later do doc diffs. Perhaps with some disclaimers. Heck, they don't do that for their main product, so why would they even do that for such a product. It's probably in the terms somewhere.

The reason they're not doing it is because they want a piece of the productivity pie.

They're not getting it from me. Ever.
For me, I think I can achieve 8 hours if:

- I'm working on something I'm interested in

- I feel like there's upside for me if the project succeeds

- I can work in different places throughout the day, like my desk, my sofa, in another room, etc. Not really possible in an office

- It's a quiet area where I won't have people interrupting my flow state

- I'm not blocked on things I need to know

- I'm working on something that's been de-risked. I know what I need to do and I know how to do it
The special tumbler is an annual holiday offer that bundles free coffee/tea for the entire month of January for $40.

Starbucks accounts (free registration) get free refills.

Own-cup gets a $.10 discount.
Nonsense. See video linked in https://news.ycombinator.com/item?id=8819614 starting at minute 3.
> Nicely looking idea. Not sure about the benefit though.

The ExpressCard slot on my x230 is completely unused ever since. But storage... Oh boy, I always need more storage.
Thanks, but I wanted to understand what the actual problems of Time Machine are, especially with Catalina, and - most importantly - which are the symptoms I should be wary of.
Running NixOS on a Consumer NAS
This is really interesting, and I think 32-bit pointers make sense for a significant class of problems. At the very least, having the option could be useful. But...

One time in node, building a react-native project, the build failed with
`FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory`. (see issue here: https://github.com/expo/expo-cli/issues/94)
I ended up fixing it with
`export NODE_OPTIONS=--max_old_space_size=8000`
But it took a while to find that. In an era where developer experience is king, maybe the default should be 64-bit pointers with an option for 32-bit.

Also if a 32-bit pointer type option existed in say C, I worry that programmers would abuse it, chasing performance at the expense of bugs.
> there was plenty of wrong with php. Messy Api, terrible default, wonky typing, no namespace, etc.

"Messy Api" is discussed above ("it came down to people complaining about some function names / param orders as if it were the end of the world") so I won't comment.

"terrible default": would be interested in specifics here

"wonky typing": every scripting language had wonky typing 15 years ago, and many of them still do today. This has never been a valid criticism of PHP when comparing to it's primary competitors.

"no namespace": THIS is a very valid criticism. PHP really wasn't a sane language before they added namespaces. But... they added namespaces 11 years ago.
Peer-to-peer has its advantages, but it's no panacea.

After all, practically everyone is behind NAT these days, and it's so rare for an application to ask you to open a port in your firewall, most users probably don't know how to do it.

And early videoconferencing was famous for its unreliability - even simple things like people being able to join calls. Particularly as users might be behind restrictive firewalls on corporate networks or cell phone connections. Video calling that only works 95% of the time isn't good enough for things like job interviews :)

And users don't only expect one-to-one calls - everyone offers multi-party calls. If eight people want to watch Bob while he's talking, you've got to find eight videos' worth of upload bandwidth from somewhere.

And there are far more people trying to video call from battery-powered devices and metered connections than there were 15 years ago. If your competitors' apps uploads one video stream and yours uploads eight at once, users are going to notice the battery and data consumption.

And if you only have to test compatibility between your server and every version of your software, that's a much simpler task than testing compatibility of every possible n-way call between different versions of your software. Especially as you'll have to support Windows, OS X, Android and iPhone at the very least.
Nobody cares whether you used Declarative or Imperative Programming
So what would you say is an appropriate end goal to max out productivity, collaboration and reusability of/on code?
Team building, wining and dining are resource intensive activities as it is, and we would do well to adopt WFH more to save the environment too. Replace Coronavirus threat with the threat of environmental destruction and you get similar solutions.
Open source it (if that's possible), let's figure out if there is community who would see value in it!
Right now, the UK is getting 7% of its electricity from burning biomass, primarily woodchips. CO2 capture there seems eminently doable, as a source for methanization of hydrogen.

It seems unlikely that hydrogen will be a viable fuel for commercial aircraft, given the difficulties of keeping hydrogen liquid or storing it compressed without excessive mass. Liquified natural gas (primarily methane) is however a viable fuel: https://www.wired.com/2012/03/boeing-freezes-design-with-liq...

If we can generate hydrogen from wind and capture CO2 from biomass, and use them to generate methane, this seems a viable way to power aviation going forwards. For most other things, batteries or direct hydrogen use seem viable, but aviation is hard.
Allocating the correct budget to write non-trivial, correct sooftware is beyond the capabilities of idiot managers.
This sounds like a process issue to me. If you document what was discussed as it happens ("Just to confirm, you're happy with X?) and have a record of that (actually recording a conversation, with everyone's approval of course) is a good way to keep everyone honest.

That's not to say you can't have a dishonest counterpart - they certainly do happen. But in my experience when there's an issue like you described above there is fault to be found on both sides of the table. Leaving your notes visible in some form during a chat is another way to solve this. By having it written and in plain view it suddenly becomes much harder for the other party to come back later and say 'well I didn't actually agree to...'
Thanks a lot for your contribution. You write:

"The only visible symptom is that a few minutes after each backup starts, it ends without copying all that it promised at the start of the process."

So you mean it ends "too quickly"?
How can you tell if it missed some files?
Hah! Excellent point.
The object heap can be up to 4 GB. The contents of ArrayBuffers and the like could live in a separate, much larger, space. I don't know if V8 is doing this, though.
I'm not sure you know how money worked in communist countries.

The character wasn't the same, because money was not enough to buy you things. You needed special coupons to buy things, and coupons were distributed by the government using various systems.

So you could have enough savings to buy a new car/fuel/washing mashine or even meat, but unless you had a coupon the money gave you nothing.

For that reason for example used cars were sold for above their original price. You could buy a car for an amount, drive it for a few years, and sell it for a higher price than originally - but you wouldn't be able to buy a new one unless you had a coupon for a new one.

The same with fuel or meat. You could have a ton of savings, but unless you have a coupon, you wouldn't be able to buy meat or fuel to that car.

The coupons were distributed by the government through government companies.
I did something similar just yesterday.

The original 2001 edition of Fantastic Beasts and where to find them (JK Rowling) was presented as a copy of the book that Harry borrowed from the Hogwarts Library. As such, it had notes and scribbles (and a hangman game) from the trio.

The publisher made a lot of changes with the 2017 re-release, mainly new illustrations, and content changes to get it in line with the new canon of the movies. A few original (but really terribly) illustrations from Rowling were dropped or made better.

The scribbles and comments were left out as well. So I decided to scribble in those myself. Was quite fun to scribble on the contents page of the book and write "==chudley cannons==".

The wiki has a list of comments: https://harrypotter.fandom.com/wiki/Fantastic_Beasts_and_Whe... if you'd like a chuckle.
The effort needed to create a "hello, world" program is not trivial. ie, creation of the tool chain (compiler, linker), the OS which to run the "hello, world executable", the text editor to write the code, the code that is in your keyboard, and the list goes on. All software.

No software is trivial if the author wants to broaden his argument to the human species.