skysight-inc/HackerNews huggingface dataset:
It seems to me you are really interested in an answer, so maybe you want to workout an answer yourself:

* When did vaccination start for the group 10-59 in the UK?

* How does the makeup of the group "unvaccinated" change over time?

* What is the average distance between the two lines, are there any trends?

Let me know if you have any questions.
By using this in an Arduino program, you can use the little reset button on the board as a button for user input.

Whenever the button is pressed, the CPU resets, but doesn't erase RAM, so if you write the code with that in mind, you've just saved yourself hooking up a button to the board.

There is also a special register that can be used to know if the CPU was reset or if power was pulled.
This will be controversial, but: I think the EU should set a deadline for IPv6 adoption to ISPs and impose fines afterwards. They seem to be legislating all kinds of crazy things (like type C connectors), so it's quite within the realm of possibility, and unlike some other things, there really isn't a way they can screw this up.

Rationale: It's in the custoners' best interest to have unique publically routable addresses and without IPv6 we'll be stuck with CGNAT. The providers don't care, because rollout is expensive. So, for the good of the customer, legislation with fines is needed to better align the financial incentives.
'Sounds Shady': Elon Musk Spars with Binance CEO over Dogecoin Glitch
The person writing the doc seems to go out of their way to use let everywhere instead of const when appropriate. Where I work there is also a guy like that, curious is this some new "rethinking" trending opinion or what?
You don't really need an aircraft motor to have a dangerously fast car: "The Tatra 87 was praised by German officers in World War II for the superior speed and handling it offered for use on the Autobahn. The Nazi armaments and munitions minister Fritz Todt declared: "This 87 is the Autobahn car ..." It was known, however, as the 'Czech secret weapon' because it killed so many Nazi officers during World War II that the German Army eventually forbade its officers from driving the Tatra." <https://en.wikipedia.org/wiki/Tatra_87>
If I find myself running a set of commands in parallel, I'd keep a cheap Makefile around: individual commands I want to run in parallel will be written as phony targets:

all: cmd1 cmd2

cmd1:
sleep 5

cmd2:
sleep 10

And then

make -j[n]
100% agree. Frameworks are an incredible starting place and allow everyone to get a head start. But there's still a big gap between what a framework will cover versus what a SaaS app needs.

Also boilerplates occupy a very important world between no-code and code-everything-yourself. In a no-code world you're fully at the mercy of whatever options someone has provided you with. But starting from a boilerplate allows you to dive in and completely customize things how you need to, without having to worry about the provided abstractions. As a developer the interface I want to use is code, but few products provide that.
Are they selling the same goods as walmart/target etc. or have their own branded goods?
I just get annoyed at the address bar not showing the full address. Thankfully some Chromium derivatives have a toggle to get the full url to show, but only on desktop.
I'm not familiar with state of the art for language servers but here's common IntelliJ refactors I use across Go and TypeScript (and Java a while ago):

- Add a parameter to a method signature and fill it in with a default value.

- Reorder method parameters.

- Extract a block of code to a method that infers the correct input and output types.

The most advanced refactoring I've done with IntelliJ is structural replace for Java which can do something like: for every private method matching the name "*DoThing" defined on a class that extends Foo, insert a log line at the beginning of the method: https://www.jetbrains.com/help/idea/structural-search-and-re...

I make heavy use of the "integrated" aspect of IntelliJ. One of the nicer benefits is that SQL strings are type-checked against a database schema.
To me it feels like the entire thing was engineered with only IPv4 in mind from day one, and a decade into it some customer demanded IPv6 support. So of course, some middle-manager at Microsoft gets assigned the "task" of enabling IPv6, and he dutifully went over to the engineers and asked them to turn it on. Horrified, they tried to explain that it's a ground up re-engineering of their entire network stack, at which point I don't need to have been in the room to play out the conversation that unfolded in that meeting room line by line:

"Just tell me what the minimum set of tasks is to enable IPv6!"

"You don't understand, it's not like turning on a tap! We have to redo all of the infrastructure around networking!"

"Do we need all that? Just tunnel the packets or something!"

"That's not the same thing, that's only supporting IPv6 in a technical sense, it doesn't really mean the same thing as doing it properly, and it won't work long term. It'll have to be ripped out and replaced, but while maintaining backwards compatibility with a jury-rigged IPv6 implementation. It'll be a nightmare!"

"Don't worry about that now, I just need to say that we've enabled IPv6 so I can satisfy this requirement."

"It'll just tick the check box! Nobody will be able to actually use it! Our customers will be confused and support will have to deal with the fallout!"

"Let me deal with that."

Etc, etc...

Translation: I just want my KPIs so that I can get my bonus. I'm quitting before the fallout hits.
Not only in rural areas. I was commuting for 3 years and i had to deal with the German network coverage every day. Every single time i though "great, i can start reading", the page went blank, because it couldn't load "click_my_fancy_newsletterbox.js" in time. That's why i try to make sure, that my crappy hobby project is also able to load without fancy js.
For people looking for a bit of a "hefty" thing about generative art with Processing, "Generative Design" is a great little book that describes intuitions for making cool art, along with lots of inspiring examples and schematics describing it. It helps to fill in the missing gap for people who might know how to computer but just don't have much imagination.

Book is very costly, though.
It's kind of hilarious that programmers, who learn again and again the value of decoupling and cohesion, fell so hard for the idea of an Integrated Development Environment. There's nothing about syntactic/semantic code analysis, to pick one example, that requires it to be packaged along with a particular text editor in a single big blob.

Ironically, the most successful IDEs today, the Jetbrains ones, are demonstrations of this. They are built out of reusable components that are combined to produce a wide range of IDEs for different languages.

LSP and DAP aren't perfect, but they're a huge step in the right direction. There's no reason people shouldn't be able to use the editor of their choice along with common tooling for different languages. The fact that IDEs had (for a while) better autocomplete, for example, than emacs wasn't because of some inherent advantage an IDE has over an editor. It's because the people that wrote the language analysis tools behind that autocomplete facility deliberately chose to package them in such a way that they could only be used with one blessed editor. It's great to see the fight back against that, and especially so to see Microsoft (of all people) embracing it with LSP, Roslyn, etc.
So that we are only spied on by bigger agents (e.g., China), and Apple can continue to lie to the roof about how its anti-user, anti-competitive behaviors are for our own good, and are not mere security theater designed first and foremost to enforce Apple’s rent-seeking.
What worries me (I write Django, Rails, Phoenix web apps - different customers at the same time) is that I'll have to learn yet another three different ways to do the same thing. What I'm doing now is either creating HTML pages (the 3 ways are pretty much the same, Django a little bit more set apart) or a JSON backend (basically the same everywhere.)

But to be fair it's fear of the unknown: I read about all of these approaches but the only new project started with a SPA and the other ones will never move from backend generated HTML.
When is open-core more useful than open-source and vice versa
I want to customize every last element of my editor, have native VI bindings for everything, and run in a terminal. What IDE does that?
Adding my $0.02.

I've had a non-trivial # of bank accounts in numerous countries, and generally speaking, DBS is good. I think people constantly complaining about DBS have no clue how awful retail banking usually is (especially internet-banking), and that most definitely includes other Singapore banks. Apps are generally modern, usable and responsive, and I find their fees and transparency reasonable. But what sets the bank apart is their customer service, the people on the other side of the phone (or counter, those few times) are incredibly friendly and helpful (again, compared to, say HSBC).

(I didn't need to interact with any other bank during COVID, so I can't compare, but I was particularly pleased with how well DBS let me do even complex banking remotely, and I hope they adopt it as a permanent option).

Things do seem to be getting _slightly_ worse though. One issue I have with the bank is that they use push notifications to advertise products and also use push notifications for security purposes. It makes me wish apple/google would require push notifications to be categorized. Also, over the last year, push notification spam seems to be linked directly to my purchases, e.g. "Got a new gadget, consider DBS payment plans..." shortly after buying new phones. It's like they've confused digitization with social network.
Their customer service UX is also hilariously bad. You can send a message to the bank from the app, which still makes sense, but to read the response, you:

- need to wait 3-5 business days

- eventually get an email notifying you that there is a response and directing you to the chat to read it (!?)

- to access chat, you need to complete a separate authentication process that requires SMS (can't use the digital token used everywhere else)

- and then you finally get a chat bubble containing the precious response.

- The kicker? If you want to respond, you need to do all of this again and get routed to another random agent with no access to your previous messages, since there is no concept of threading at all!
Putting monetisation before use case, rather than the traditional use case before monetisation, leads to several perversions:

- It turns practitioners into "relentless door-to-door salesmen" as you put it, fanatical commission-based salesmen, which makes any kind of rational discussion about pros and cons etc. impossible.

- It allows you to monetise without having anything to monetise, which has drawn in the scammers and fraudsters on an unprecedented scale.

- It offers no incentive to working solutions. All the ICOs failed because they got the money up front with no obligation to deliver anything, so even the small number that weren't out and out scams ended up effectively becoming scams. Spend any time in the space, and you'll realise the gap between what is promised and what is possible is often insurmountable, but the gap isn't important, because you just need to convince enough people that what you are trying to do is possible for long enough to get rich quickly.

- It offers no incentive to more efficient solutions. Why use existing fast, free and low energy money transfers, for example, when you can make slow, expensive money transfers that use up 5% of the world's electricity but make a handful of people rich in the process? There are very few cryptocurrencies which have genuine legitimate use cases, and the small number that arguably do are always worse in every way than what they replace, but they are still attractive and gain traction because they can get a small number of people rich quickly.

- It doesn't look like it'll go away. While putting use case before monetisation means something without a use case will wither away, with monetisation before use case it could go on burning up trillions more programming hours and countless other resources indefinitely without ever finding a genuine legitimate use case.
This is a good list, but I'm trying to understand the following in better detail:

> [12] Be conservative on APIs and liberal with implementations.

> [18] Maintain multiple implementations in test for APIs; compare results between them. The cost is worth it (it will help with correctness, and also prevent leakage of implementation detail).

The word implementation is thrown out a lot. What does implementation mean in these quotes? The databases used (ie. dependency injection), the endpoints (ie. /user, /user/123), or something else?

I'm trying to visualize this in my head and am having trouble.
China will not, if possible, willingly put itself in a position which admits any likelihood of losing face. If they couldn't rule out the possibility themselves and/or cover up completely that it was in fact a leak, they won't let anyone in - not because it happened, but because it might have.
Is bitcoin mining really that energy hungry that it overshadows security apparatus needed to enforce fiat?

I thought that would be impossible.
In the same way standard oil was just another oil company. Execution and business strategy set Microsoft apart, not unique software.
It seems literally impossible for an entire market to be paying under market. This market equilibrium is definitely rising over time, but it’s still a market.
One thing that is missing from Flash in there is the whole "you edit this thing visually, click on it and can attach a script onto it".

Of course big "serious" flash projects would be more organized in how stuff happened but I think that Flash's success was from being this animation/drawing/moving making tool where you could add scripts, instead of this dynamic programming environment.

"Make this movie interactive" has always been a bit easier than "make these words turn into drawings".
If I didn't have a ton of debt, I'd probably need a particularly intense desire for material wealth or financial independence in order to drive me into business. I don't currently have a ton of debt, just a bit, and I'd like to get rid of it, but beyond that I'm not terribly interested in the bullshit products and crap most people spend all their money on. Therefore, money itself isn't motivating enough to sacrifice so much for it. Likewise, arguments about changing the world are hollow at best most of the time, and overall those claims by previous companies have arguably worsened the world more than helped it.
I would also expect traffic patterns and frequencies were a bit different in 2002 as compared to 2019. It is likely that with China having had a rise in general wealth, more travelling was done, which made containing the virus harder.
The 12dicts Word Lists
Unlocking _your_ device willingly and unlocking someone else's device against their will are two completely different things.
No, those two are not the same thing. Redirector can redirect anything based on regex, privacy redirect is for fixed services at the moment.
China trying to export its Great Firewall and governance model
JavaScript: Best Practices for Functions
I'm not super motivated to read a long pile of text starting with "If you had unlimited free energy".

My answer is: You don't.
>Speed isn't the problem... uneducated drivers, poor vehicle maintenance, poor road quality, etc are the problem.

Speed isn't the problem, neither are any of the others you mentioned. They all add to the problem of traffic fatalities though.

They did a study in Germany and were able to halve traffic fatalities by adding a speed limit of 130kph on one Autobahn section, measured over 3 years.[1]

Sure you can improve road conditions and driver education, but a multi-pronged approach including speed limits is sensible.

[1] https://www.spiegel.de/auto/aktuell/tempolimit-mit-130-km-h-...
A similar argument has been used in the more-or-less famous proof of how to assemble a lamp with Tetris-shaped components into a rectangle:

https://jackmorris.xyz/2015/the-simple-proof-of-the-tetris-l...
I’m not super familiar with the full content of their regulations but in my experience working with banks that maintain a presence there, Singapore control requirements tend to be fairly specific, opinionated and far reaching. For example, in developing OS security standards, I found myself having to actually incorporate requirements specifically for the Monetary Authority of Singapore that bled into operations in North America.

These requirements extend into resiliency as well. I’m curious how well DBS has been fairing in audits.
USDC is upfront about being centralized.
Another reason would be language and legal requirements.

I work for the software division of an international wholesale chain, based in Europe.
For the checkout process, not only we have to translate everything in tens of languages, but we have to implement many legal requirements in price calculations, taxes, discounts, money laundry, invoicing and so on.

Even a single country like India is a headache because they have different legal requirements in each Indian state.

When you add countries from Europe which aren't in EU, countries from Europe which are in EU but have different legal requirements, countries from Asia, it can become really complex.

And we are just a handful of people and not payed a lot.
Virtual Webinar on 'Reliability Reimagined: How SREs Spearhead Competitive CX'
Topic - "Reliability Reimagined: How SREs spearhead competitive CX"
Date: 9th Dec, Thursday
Time: 10:00 AM PST
Hosted by: DNX Ventures in collaboration with Squadcast.

Keynote speaker and industry expert - Salim Virj, Sr. SRE at Google along with Biju Chacko, VP of Engineering at Squadcast will be sharing their thoughts on how practising Site Reliability Engineering can effectively improve Customer Experience.

The second half of the session will be a thought leadership panel with speakers and Eva Nahari, Principal at DNX Ventures, discussing methods and practices on how organizations can achieve competitive CX by leveraging SRE.

Register here: https://us06web.zoom.us/webinar/register/4816346604076/WN_AV...

Organizations both, big and small have started to realize just how crucial system and application reliability is to their business. The role of the Site Reliability Engineer presents a unique opportunity within an organization, and can spearhead vital customer experiences through application of reliability principles. SREs understand a product from its user experience through the infrastructure systems it relies on. From data governance to client experience, building reliability into the entire product forms a key part of the SRE role. They’ve also learned just how difficult it is to maintain reliability while iterating at the speed demanded by the marketplace.

Site Reliability Engineering (SRE) is a proven approach to this challenge.
If they put themselves in the same league as LinkedIn, that explains a lot.

Shittiest website I ever need to use from a technical point of view, never mind “content” and dodgy hard-sell techniques.
Indeed - it's a known anti-pattern[0].

[0] https://en.wikipedia.org/wiki/Cat_(Unix)#Useless_use_of_cat
The genie is out of that bottle - the research has been done, and can be replicated by less honest actors. Under these circumstances, continuing this kind of research to understand how to combat viruses created by rouge actors might be the right thing to do.
People often react with incredulity about FAANG comp, while forgetting that the company makes several times as much per employee as mean comp package (2/3rds of which isn't even cash). All of that value is generated by employees. Is this a fair split? I suppose we'll find out soon. Someone has to blink, and then everyone will blink. Google did blink circa 2011, and raised its (until then) fairly modest comp something like 30%.

I think a cool and "googly" thing for Google to try would be to do what one of the companies in the article did: reduce the work week to 4 days while keeping the same pay. All tech companies should do that. Working the same hours as factory workers did 100 years ago is absurd given the productivity improvements in the interim.
Original headline says, "Singapore bank DBS says services disrupted for second day", so I'm not sure where the "with no meaningful update from DBD" in the HN headline came from, nor am I sure of the meaning of DBD.
If it is good for a customer then the provider will care. The customer will switch ISPs to those that support IPv6. Then the IPv4-only providers will get less money.
Do they? Really?? I know some people who don't even go the the store for apps and do everything through the Google app that includes app results as well, but the other way around?

I just searched for "buy coffee" in G Play and not a single one of the top 15-ish results let me buy coffee apart from one coffee shop in New York, which is off by roughly one half globe circumference. If anyone ever did that, they'd quickly realise there's nothing there and go back to a search engine.
I can't say I agree with either of you 100%. For example, your statement that VCs expect each and every one of their investments to turn into rocket ships? Nah. If they don't know that a % of their portfolio will fail, then they're idiots. Also, FOMO. Any time there's a new hot technology, VCs soil themselves trying to get a piece of the action (AI, I'm looking at you). So they end up investing in start-ups that probably won't succeed (BUT IF THEY DO, RIGHT???)

I definitely agree that it's all about appetite for risk. I'm not sure you disagree with each other fundamentally, you're just watching from different sides and wording it accordingly. Some people buy stocks for long term investment, some people short sell, and some bet their house on a hand of poker. I'm sure they would have a bar fight if you got them talking about risk appetite.
I've heard that some bitcoin miners get started when there is an oversupply of energy to burn the excess power. I think this is the direction bitcoin mining could take.
But it sure seems like you were talking _about_ them, seeing as they are the grand-OP. What the fuck did you expect?

Full disclosure: I'm not responding to you. I'm responding near you.