skysight-inc/HackerNews huggingface dataset:
At least COBOL in its time was a major breakthrough that resulted in immediate productivity improvements.

Crypto is more like a honeypot for the incompetent, ideologically delusional and/or pathologically greedy. (Which explains why certain FB executives are still running this doomed Libra/Diem/whatever project. They might do more harm somewhere else.)
Riyaz is an incredible engineer. I never worked with him directly in undergrad but his reputation certainly preceded him -- which is saying something, because there were a LOT of insanely talented engineers walking around Soda Hall (I, of course, was not one of them).

I got to know Riyaz more after we graduated and was impressed not just by his technical chops but also by how humble and grounded he is. I can't think of a better pick to serve as CTO, a role which requires not just technical acumen and mental agility, but also the ability to work with a wide variety of stakeholders.

I've always been bearish on crypto/blockchain but seeing Riyaz make the jump is making me think twice. A16Z made a great hire here.
That was exactly how we used to do it, from where we used to do it, haha. Are you my friend? Rodrigo? How's the weather in Miami? How 'bout those 'Canes?
take out the uniswap frontend, the volume will not be as high, without Coinbase the price of Ethereum would be significantly lower
But for the people who've already had it why bother vaccinating them against their will?

They've already run the gambit of heart problems and such, why make them run it again?
“Big companies should act more like startups!”

“Wait no, big companies should have redundant employees!”
Sadly, I was at the Bryant St. U-Haul a month ago and the lot worker was spinning around with his hands up yelling “no trucks, everyone is leaving!”

He was being facetious. The lot was completely packed. He was annoyed he had to move a panel truck so I could get a truck (always the last row) out.
Natural immunity for those who produce antibodies (I think I saw around 30% don't) probably -is- better than the vaccine, in terms of efficacy in preventing COVID again.

However, this is a false dichotomy. First, because the same studies that show this ALSO show that getting vaccinated on top of natural immunity is better still ( https://www.medrxiv.org/content/10.1101/2021.08.24.21262415v... ), second because natural immunity prior to the vaccine implies getting COVID and the extremely high risk of complications (from hospitalization, to long COVID symptoms, to death), and third, because there isn't any data around what happens if you get vaccinated first, then get COVID (i.e., is the combination of natural response + vaccine the same if the order is reversed).

There is no situation where getting vaccinated does not help reduce the likelihood of catching COVID, or suffering serious symptoms.
Walgreens closing 5 San Francisco stores due to 'organized retail crime'
Visualization of Sea Level Rise for American and Other Landmarks
Might be worth comparing to The Update Framework and Sigstore
> As any parrot owner knows, if you overheat a teflon pan, all the birds inside your house will die.

How about the newer ceramic ones? I assume nothing will happen?
This ignores the multitude of navy destroying battles Rome had in the First Punic War before gaining enough shipbuilding experience to compete, though even then their naval skills were so much worse they competed by developing a way to turn it into a land battle.

Lepanto was the opposite, the end of over a millennium of armies fighting at sea and the emergence of a new form of naval supremacy.
sounds like a locality thing. I owned a personal car at 16, like many other mid-west US people.
Everything in your second paragraph points to companies that either through hiring, firing, or attrition have successfully excised all real systems expertise from the entire company. This isn't the fault of any ops methodology, so let's maybe call it "shrug-ops."

>few people notice or care about the difference between a well-built corporate citizen that runs well & is monitored & operated according to whatever the in-power SRE cabal wants

QED
What about non-competes where the employer actually does pays-up to the former employer to prevent key people joining the competition, aka “gardening leave”? Common in fin, I hear - Normal severance in the US is a bit of a joke…
If I broke into your home tonight to play a prank on you and then handed you a white paper about how to better secure it, how would you feel?
prophylaxis isn't all its cut out to be. that said, an amazing number of people 50+ are carrying health burdens, and probably would qualify for asprin/statins, if their doctor checked them over. So.. don't self-medicate without talking to your GP might be the shorthand, for all things.
It's not hacking if you have ssh access. I missed the part that explained how they got that.
It’s called “spaced armor” and there’s a whole wikipedia article detailing its use in the last century of tank design.

Army wants to save weight too btw, they do fly these things in after all.

https://en.m.wikipedia.org/wiki/Spaced_armour
You laugh, but Active Directory supports SMTP as one of its transport options, because it allows occasionally-connected sites to participate in replication.
It seems like the crux of this article is “ten percent of the population is richer than the other 90%.”
Unlocking a phone is a pain* (at least in the US), so I recommend buying one that is already unlocked. For example, a listing that says both "T-Mobile" and "unlocked" is for a phone that was originally locked by T-Mobile when it was sold as a new phone, but was then unlocked by T-Mobile before it was listed for sale as a used phone. For this type of phone (carrier unlocked), you'll just need to request a bootloader unlock code from OnePlus, which takes a week.

(Not all manufacturers require a bootloader unlock code, but having this option is still better than not being able to unlock the bootloader at all.)

And yes, the OnePlus 8 is faster than any Pixel phone released so far. It's only a year old after all.

* https://www.digitaltrends.com/mobile/how-to-unlock-a-phone-o...
It would be wrong to characterize this as a miracle cure, especially given the significant time and effort required to get any effect. It also makes a lot of sense that dementia would end up being like cancer and heart disease in terms of being complex, systemic, and fundamentally related to metabolic activity.
You're in LA County, so you should be aware of https://myvaccinerecord.cdph.ca.gov/

That's just as trustworthy. Probably more since what it asserts is less variable than how long you maintain antibodies.
You probably would have liked the IBM System/38 - AS/400 - System i - IBM i (whatever it's called now) command line.

It had a defined standard vocabulary and a system for defining commands.

Built-in command names were constructed out of a few verbs, a few adjectives and a few nouns. To compile a Cobol program, the command was CRTCBLPGM - create cobol program. So, verbs were CRT, CHG (change), DLT, DSP (display), and a few special cases. Likewise there were limited lists of objects (PGM, here) and adjectives (CBL).

There was also direct help for commands.

You typed in CRTCBLPGM and pressed F4. You got a TUI, with labeled fill-in-the-blank fields for all the arguments, with mandatory arguments indicated as such, default values displayed for optional ones, selection for those that have a fixed list of allowed values (e.g. YES, NO), and with help text available for each parameter, each parameter value for enumerated values, and for the command as a whole. So the command is its own man page, pretty much.

If you didn't know the name of the command you wanted, there was a topic-organized menu system, think GNU `info(1)', also available from the command line.

Having gone through the menus and found the command you wanted, you could start the fill-in-the-blank execution of it right from the menu.

After filling in the arguments but before pressing Enter, you could press a function key (F12?) to see the command as it would have been typed out directly on the command line, for future reference or for pasting into a script.
Is there any actual precedent for the scheme they present here (basically preventively give these antibodies to people who can’t mount their own response every 6 months)? Do we already do this with other diseases?
Deployments:
GitHub ci + docker stack + docker swarm + docker machine + docker-flow-proxy + docker registry

There are a few rough edges you face once and then forget about but minimal resource impact and it was fairly simple.
I have another project that is using hacky scripts and it's a pain when something is off or I need to run something else on top of the machine.

Some stuff is not terribly maintained but everything works.

If you're small, it's definitely not a full time job.
I didn't pick k8s because I initially deployed on a single machine and didn't want overhead. Things kept working afterward and I'm reconsidering whether I need k8s at all.

Rollbacks are just deploying an old version + optional down migrations if needed. I try to minimise them and fix the code and redeploy anyway.

For migrations, I guess it's very application specific, but most tools in most languages are fine these days.
I use typeorm, a node.js library.

There are some practices you can follow that you probably heard working in some normal company.
Eg. I don't break the db structure immediately, I deprecate columns and then delete them after a while.
Can you expand/replace some of the numerous acronyms/initialisms in here? Like "CHO", just write "carbohydrates". This list could be helpful but it's written too opaquely to be easily digestible by someone who isn't already well-versed in health/diet terminology.
Isn't that KVM? Why don't they say they use KVM if it's the case?
>not sure why this was downvoted

Perhaps because spreading the agenda-oriented opinion about fusion of someone who knows exactly as much about fusion as a high-schooler maybe isn't the best?

https://news.ycombinator.com/item?id=28781178
I think this is an article about writing tests. Some code the author depended on changed the behavior of their app, while they were focused on releasing a critical fix. They deployed the critical fix and noticed the change way too late in the process, thus wasting an entire workday getting it fixed. Well, that's what tests are for -- so that when some person you don't know edits a dependency, they get a message "you can't check this in until you debug this code you are affecting". Maybe you don't need that for your one-person weekend project, but at a company with tens of thousands of developers working in the same repository, it can sure prevent a lot of problems.
It actually sounds more like what I'd expect: microservices don't scale.

I've never been a fan of microservices for this simple reason: every boundary, every interface, every connection is friction and a potential source of bugs, performance issues and problems.

It's now been several years since I worked at Google so I can't speak to the current state of things but when I was there, monoliths ruled the roost.

It seems possible there was some experimentation with microservices given the rise of Docker and Kubernetes in the last few years. I'd be surprised if this made serious inroads into high-traffic core services.

It's also worth mentioning that generally Google has (had?) SRE teams rather than SREs embedded on SWE teams. You'd never have one SRE supporting a service as there'd have to be enough to maintain a healthy oncall rotation (typically 8-12).

I can't help but feel like the author is projecting his own experiences onto what Google has said here.
Oh yeah the early 2000s, not a great day to be a hacker (by hacker I mean actual hacker: http://catb.org/~esr/faqs/hacker-howto.html).

I remember getting yelled at for changing the display resolution and typing a few commands in DOS to change file names quickly.

Computers were never up to date of course, we had cathodic displays up to 2010.
Let's spouse I have two properties, one big and one small, and I sell you the small one for $X. But I miskick and send you the big one. If you don't want to return it to me, can I go to a judge?

What about kidnaping? If someone kidnaps me and use a wrench to send my property, can it be returned?
I think "baseball cards" is a limited view of the NFT model, which is what's being argued in this article; it's essentially a programmable, global database.

Just like how we trust certain government records to be accurate & representative of ownership, each chain, if secure, can achieve the same functionality in a more open and decentralized way (also its inherently global, which can have huge implications wrt globalization)
My understanding is that the blockchain records ownership of just a token. If OpenSea or Nifty (or whatever NFT marketplace) shuts down, who then associates the artifact to the token on the blockchain? Would the token you own on the blockchain go worthless?
It's okay but this real-time map of the weather anywhere in the world is more useful I think, with a nicer interface too:
https://www.ventusky.com/
Edit: I removed my comments due to obvious reasons.
This is spot on. I Used to work as a sysadmin for a large private school and always enjoyed the red/blue dynamic of tech team vs the smarter students trying to poke through the restrictions of their laptops and network.

It was always disappointing when they took it too far and were directly caught by teachers or administration before I could tell them they were being a bit too blatantly malicious.
Yeah I agree, these settings should be disabled by default and require explicit opt-in. That said, I am impressed by how privacy/security-conscious the OS seems to be otherwise!
I consider it a matter of mutual respect. Early humans and dogs are both pack hunters and likely stalked the same prey.

I figure dogs were pretty impressed with our take-downs and were glad to share the spoils, and vice versa. Throw in a warm fire and you got yourself a friend.
Mellified Man
This is probably sarcastic, but it has long been said that if exercise could be made into a pill it would be one of the best medicines ever and it is true that exercise is known to help with a majority of these issues though not necessarily all. So take an exercise and wash it down with some water and you may get some of these positive effects.
> During this time to help combat this issue, we increased our investments in security measures in stores across the city to 46 times our chain average in an effort to provide a safe environment.”

I wonder how they arrived at this number of 46x.

46x the chain average of single minutes spent reviewing security staff resumes?

46x the chain average of security camera photos sent to LEOs?

46x the average number of bic lighters placed further back? No, up more? No, up and back higher, like where you can't reach? No, they can really jump that high, so up higher?
Productized class methods.
How to find your zone of genius
Yeah, the JWT is huge, and contains a bunch of unnecessary data, even ignoring the huge signature (132 bytes, I think?). It even uses error correction M, down from NSW’s H or the article’s Q. It looks like they still end up as version 18 despite that.

That said, it seems like there’s two versions of the Victorian codes. I can find others online that have a base64 snippet containing:

{
"t":1,
"lid":"<base64'd 64-byte ID>",
"ln":"<name here>

(Yes, seemingly without the trailing "}, as a microoptimisation?)

This uses error correction M, and ends up as a version 12 code.

I don't know for sure which codes are 'current' but I suspect the JWT ones are the older ones, based on https://www.theage.com.au/national/victoria/victoria-s-qr-co...
People usually aren't very contagious past the initial stage of the disease.

And yes, there are virologists who are studying the mutation-space of the virus and are planning a vaccine regimen which targets all possible mutations of SARS-CoV-2. Check out this absolutely terrific lecture by Paul Bieniasz about his work on exploring the mutation space of SARS-CoV-2: https://www.youtube.com/watch?v=LIcaSqQFrX0
Mathilde Collin with practical tips on energy management, structuring your days to maximize the areas you enjoy (high energy) and excellent at (provide high impact and value few can do): "There’s a very practical exercise you can do to figure out what activities fall within your zone of genius: the Energy Audit. You can do it on your own, but it’s best to have someone to hold you accountable."
> If the only way you can rebut an argument is by silencing it, then you lose the debate.

This cannot be underscored enough. If you censor criticism of a viewpoint, people won't decide it's right. They will decide it's definitely wrong.
> That database is heavily guarded by layers of human administration. I can't sell you my land without involving a bunch of humans who interpret contracts and push buttons. In a world where land ownership were recognized by tokens on a distributed ledger, buying and selling land no longer requires the overhead of all that administration.

Those layers of human administration are called a "state". Without that, the concept of property is pretty much meaningless to begin with. I can claim to own any piece of land I want. The state pays people to show up with weapons if I'm using land that they've decided "belongs" to somebody else. It gets to set the terms of land ownership and to insert itself into every transaction because of the ability to use force, not because it has the most efficient record-keeping system.

What that means is that the fundamental premise of blockchain technology, that there's no need for an external authority, is completely at odds with the reality of how property works. If there's a smart contract that says I own parcel X, but the people with guns say I don't own it, who wins that argument? That means the state needs a way to insert itself into and modify the blockchain, but that kind of obviates the whole point of the blockchain. If the state can't alter it, it's not a meaningful source of truth.

That of course leaves the benefit of automation. But all of that automation could be done with a SQL database and a PHP web app. The reasons it isn't done that way are policy ones, not technical ones.
Because they use QEMU, which in turn uses KVM where appropriate, or some Microsoft thing on Windows, or an Intel equivalent on Intel-Macs. EDIT: and since this app is for now only for Mac and Windows if I read the page right, it's probably not using KVM obviously.
Author here; I agree, and this is something I've been wrestling for years. The lack of centralization means it's impossible to reverse hacks or scenarios you mentioned--I personally think _some_ centralization is crucial, but not sure to what extend (and if that basically just means we should just have private companies like we do today).
One temporary solution would be for businesses to distribute / sell rolls of their no longer needed toilet paper to employees. Employees might not have a compatible dispenser at home, but in a shortage they could put it on a flat surface and peel off as needed. Lack of out of the box thinking...
Yeah that is sad. Software engineering for the most part has become "standardized" and it is unfortunate this individual either missed the boat on the upskilling or just ran out of steam/luck from what may have been (possibly successful) cowboy coding days!
That's been called "creeping featuritis" for about 25 years now. :)
What about the very unlikely event that someone loses access to their private key or gets hacked? Does that mean their house now belongs to someone else? I suppose this speeds up the ability to lose one's home through cryptocurrency scams.
JSC limits recompilation only in the sense that we have exponential back off on each jettison. But that means that a sufficiently hot function will keep getting recompiled forever even if speculation is permabroken in that function.

Other than that JSC has only very weak heuristics for aging out code. And on sufficiently empowered devices our JIT pool is hundreds of megs.

So, we will happily compile your whole program with the jit if your whole program is warm and runs long enough.
> I think "baseball cards" is a limited view of the NFT model, which is what's being argued in this article; it's essentially a programmable, global database.

NFTs are built on a preexisting global programmable database, but are specifically a use of that database to create digital baseball cards.
And if a second government sprung up with more support, the old one would be out of luck, too.

I don't think we can simply discount the power these developers wield. They have a lot of explicit and implicit (as in "just install the latest version") trust. Sure, they could loose it, but they can do a lot of damage before doing so.
jsonb has become the crutch on which I build everything. And I'm not going back.
You'd also need the actual patch to survive future commits, especially without introducing any merge conflicts
Private Devices No Longer Private [PDF]
It seems like a pretty excellent way to refer to the 1980s.
Crime follows homelessness and unemployment around. If you fix homelessness, and give people meaningful work, or the best substitute, and invest in them as people, they stop doing as much crazy shit.

It takes time. Once you have a street culture which includes public defecation and leaving drug detruitus around, it takes time to fix. Sure, you can Bloomberg "tough on crime" it away, I suspect some of that isn't viable now for a number of reasons. Not the least because some of the public health and mental health interventions, and the universal income stuff strongly suggest that kindness works better.

I'm not pretending the problem isn't there. I just think that the root cause isn't the needle per-se: its why people are reduced to needles on the streets in the first place. Blaming this on lax social policy around arrests misses the point I think.

(Where I live in Brisbane has pretty high rough-sleeping, and street drug use. Intervention programs to help people seem to work better here, moving them on, or beating them up, or locking them up doesn't seem to work that well overall)
Huh, good point; I wonder if my mind mixed up the org chem with the numbers (likely) or if that's some kind of unique Belgian affectation.
The “experts” don’t say “4%” but they also don’t even bother to give an actual IFR. Why haven’t they? We’ve known it for quite some time.
"why make them run it again" - the vaccine doesn't have nearly the likelihood nor the severity of complications that COVID has. And it still reduces their likelihood of catching COVID again, and the likelihood of serious symptoms even if they did. And the protections last longer and more predictably than natural immunity does.