skysight-inc/HackerNews huggingface dataset:
I have built a lot of stuff on kubernetes. Outside of certain edge cases I've had to use almost none of the actual system administration knowledge I have. The vast majority of things are relatively simple, or can be handled via a nice UI provided by <cloud_provider_here>.

In fact, I'd argue that kubernetes was really made to remove sysadmin from being needed. For large kubes obviously some skill is needed but in the average case a developer can do 99.9% of all the work needed. It was a huge boon for businesses that would otherwise have to pay both developers and sysadmins. Now they can pay one of them half the value!

The majority of other sysadmin tasks have been offloaded to cloud providers. For example, AWS makes setting up a network topology/compute/etc very easy. Sometimes these tasks are handled by SRE, a lot of times they are handled again by developers. Terraform really brought everything together in an absolutely brainless mechanism to get things started (with the subsequent pitfalls).
> Like me, the majority of the campus was not here at the beginning of this matter in 2016.

This is a dynamic not enough people appreciate: universities are not generally permanent communities.

This fact is lost again and again in public debate.

For example, there’s debate about how allegations of rape should be handled by a university.

However the university handles possible rapes, they have to take into account the fact that everyone involved: victim, accuser, and witnesses, might drop out or graduate a week into the investigation.
"Here's the first 20 inches of the screwdriver isle."

"Can I keep going?"

"No. You need to be more specific, no browsing more than a few dozen models at a time."
Honestly the biggest hurdles are the mythical free time and being comfortable enough with my understanding of the material to allocate said free time. I love the Khan Academy-style super casual, not overly produced, just "here's me writing out the concept and providing a worked example". Take a look at the link in my profile, you'll see its mostly that and talking head over code/slides recorded on OBS. I like that style because it requires minimal overhead work on my behalf.

Students' attention is low (not an insult, just what my analytics show). They are mostly searching for a fix to their immediate problem when coding. So my videos are split into 3-10 minute chunks covering that single thing. Recordings for a single concept take roughly 1ish hour, mostly a combination of setup, being human and flubbing words, and something in my examples going awry and taking too much time on it rather than demonstrating the example. I mostly record on Sundays (again, free day) or at night if I know I'm going to be away. As faculty, you're not paid extra to do this, so its very much intrinsic altruistic volunteering your time to do it.

And like I said, the second part is being comfortable enough with the material to record it. I'm teaching Intro to AI for the 3rd time this semester and while I'm confident in my ability to teach it, I still have some kinks in my examples. Typos, what gets covered when, etc. type things. I feel ready to record it during my next iteration, but then we fall back to making time to do it.
I know a graduate of Oberlin who is a wonderful person. Bright, publicly dedicated, wonderful.
I can feel uncalled hostility in your attitude, dictated by your conjecture which isn't the right indicator to make judgement about this specific incident. Ad hominem is irrelevant here since it's not about me but service operations.

Anyway, I'll still respond.

>Idk why you think you should be able to login to a cloud SaaS product while its down

The application works without internet access.

> Not all forms of Auth can be done locally, for example most 2fa requires server access.

TOTP validation can be done at the offline level. And the hardest proof of it is that the tokens themselves are generated offline. All that is required at the server side is shared secret and a Unix time syscall. This gets done at the browser extension level[0], no network required.

[0] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
My limited knowledge comes from a former life where I was trained diesel mechanic for heavy machinery, and this was a specific part of our education. Cold weather was never a concern related to nitrogen.

The scenario everyone worried about, and was beaten into our heads, was a bit of oil or grease leaking into the tires, which is pretty normal on heavy equipment. Under typical conditions, this is harmless. However, under high compression that oil can start to vaporize, which basically turns it into highly flammable fuel. Under the right conditions this fuel when mixed with the pressurized air can and will spontaneously combust. Failures can be pretty spectacular, and they had video to prove it. The nitrogen removes the oxygen from the equation so that the combustion can never occur.

Apparently it happened often enough historically that it is mandatory practice in many domains. For me, this was received wisdom because I've never seen this kind of explosive failure in real life, which is a great thing. But if I put my chemical engineer hat on it also is eminently plausible, so I put it in the category of "lessons they learned the hard way".
I really doubt the staff are making much money.
Even if you sell, you are still reducing the carbon footprint by 50% though.
This sounds like something out of the Middle Ages.
I think you're failing to respond to the strongest version of what someone is saying...

Home depot has roughly 36000 items stocked in a store. Try using that number for _jal's argument.
It died because it's stupid and useless.
He's got some kind of autoblocking going on. Apparently I'm blocked even though I didn't even know who he was until a week ago, and I barely use Twitter (110 followers). I do follow some people involved in SF housing reform.
Big question. Some glittering generalities:

1. These languages, having been used many times over to write compilers, have been battle-tested.

2. These languages do a good job of making immutable data structures easy to reach for and use, with escape hatches for more performant, mutable structures if need be; it's easier to reason about correctness when things are immutable by default. Correctness matters a lot for compilers.

3. Compilers are, in some sense, a bag of functions that iterate or map over trees. Pattern-matching is a way to reify trees: the branches of the trees become branches of your match expression. These languages support pattern-matching in a pervasive, first-class sort of way, as they prefer recursion and pattern matching over other kinds of control flow.

4. ML-likes have an advanced type system, while still being relatively ergonomic to write code in, as the type system admits some form of Hindley-Milner type inference. Good for correctness; but not strictly necessary for a compiler, maybe.

5. Lisp-likes don't generally have a type system (although some do!). But Lisps have extreme dynamism in the form of macros. Being able to tersely write code that expands out to exactly what you need can carry the day too. Whereas imperative languages sort of strike a compromise: their type systems are neither all that great (although C++, C#, and Java have all improved on type inferencing in the last decade) nor do they have anything as powerful as Lisp macros.

6. People and culture. Compiler people are generally made forged in academia, where it's generally taught in some Lisp or ML derivative. Type theory papers are usually written in some Haskell-like. Implementing a GHC extension is a path to a degree for grad student.
Most of the time, I believe resource orientation works extremely well.
Are you comparing the impact mass farming cattle to that of free-ranging large herbivores?

Because if you are doing it in good faith, I am sad to inform you the difference in number of individuals is an order of magnitude.
Flights that go to certain countries or that members of certain countries fly through tend to be exceptionally dirty. You know who you are, fam. I’ve been on emirates flights that look like a trash tornado hit them after a 15 hour flight. Be neat!
Using unsafe blocks would fall into the category of "sidestepping the borrow checker". Again, it's possible to do it, but if you're going to do everything in unsafe rust why not just use an unsafe language in the first place?

And how does rust allow you to "maximize multi-threading" over what's possible in other languages? Anything you can express in rust can be expressed in C or Zig as well. The only difference is the implementation you reach will come with static guarantees about memory ownership (so long as you don't use unsafe). So the set of all rust programs is a essentially a subset of all C/Zig programs.
You misunderstand. It's a database built purposely for ensuring transactions happen in an ordered manner an as correct of a way as possible. The constraints and basic rules of accounting are generally pretty slowly changing so it makes sense in a domain that has:

* Very slowly changing validity requirements. Things like (optionally) preventing overspending are things that are pretty intrinsic requirements of the domain (depending on the context, obviously many banks allow overdrafts so they can charge you a fee for spotting you the difference). The validation space is relatively small such that you'll want to allow most transactions that aren't blatantly wrong

* Emphasizes correctness and ordering over everything else

* The transaction rate is relatively inelastic, that is there aren't huge swings on how many transactions are requests per second such that dynamic scaling is not a desirable property to have if it means being less reliable/correct. Conversely, it's a known slow operation that most people are fine with not being instant. Ex. I'd much prefer my rent payment take 10s to process and be more or less guaranteed to be correct than it take 1s and not.

That's why it's domain-specific. You can optimize for the things you care about in your domain most while reducing operational complexity to the minimum viable to meet those demands.

It's amazingly well-focused and solves what I assume are hard, limiting problems that the existing financial infrastructure is not equipped to support.
I'm a happy user of Obsidian, but always considered the graph visualization gimmicky. Still I make heavy use of note linking, so in that sense I'm using a knowledge graph to sort notes.
I think JS had a perfectly reasonable and workable OOP implementation, actually pretty elegant, but so different from the C++/Java class paradigm that almost nobody used it the way it was supposed to be. Instead, JS Objects were treated like broken Java classes, which led to all sorts of problems.
I disagree that the logistical costs have anything to do with why libraries would not remove a book simply because the author didn't like it or want people to read it anymore. If the work is still relevant/important/frequently accessed enough to warrant space on the shelves, then it is a thing of value and the library would have no reason to throw it away just because someone else asked. Moreover, libraries generally see themselves as having a historical and preservation mission that would not support retracting books.

Likewise in the case of Wikipedia, if your contribution meet the standards to be included in the first place and has not yet been replaced by other edits, then presumably the article is better with it than without. Why would they agree to go back to a worse version of the article?

Although digital, I believe a repository of academic publications is far more similar to a physical library than it is to a social networking site.

Social networking sites simply need people to look at their ads to make money. Whether or not people can delete tweets is not that big of a deal one way or the other to their business purpose. The purpose of arxiv is to permanently archive open-access versions of academic papers for academic study as well as preserving the history of the field/academic progress, even if the papers themselves are no longer current or accurate.

In any case, the site is clear that contributing a work to their library involves the grant of a perpetual, non-exclusive license to publish and redistribute it.
I have bad news for you. Cofounders are like any other employee. You don't automatically get a say in every decision just because you were one of the company founders. Often, the CEO has the power to simply fire you. The CEO certainly has the power to demote you to a non-decisionmaking role. The CEO does not have to listen to you about every little decision like having a company retreat.

First, you should have gone to the company retreat. As a manager it's your responsibility to support team-building things like this, even if you don't agree with the CEO's decisions.

Second, your communication style is hurting you. Don't just reject the CEO's initiative. Don't complain about your boss on HN in a way that, honestly, will be completely obvious to your CEO if they read this thread. Politely bring up your objections, and if the CEO overrules you, accept it and move on. It's a company retreat, you must have more important problems.
I'm constantly chuckling at the underestimation of Apple's influence in the US and worldwide. Do you really think all of the cellular providers and resellers are not at this moment reviewing their business model and giving strong consideration to supporting eSIM activation?

The folio of "stupid" ideas that people claim Apple adopted which are now readily adopted by many Android phone purveyors is substantial.

No one spends more money on all consumer products domestically and internationally than Apple users especially folks with a new phone.

We shall see how many "cheap" SIM purveyors suddenly figure out a way to go eSIM. In the meantime I'll take the increased security (now my SMS 2FA is a lot more secure than before) and one less opening for dust and moisture to get inside.

I can't wait to send my first Satellite message...
Maybe they were skunkworks programs so secret the rest of the military was in the dark - hence classifying them as UFOs.
I should have said more - by making a very tall, thin cylinder world you have to fight your way past some civilizations before you get to those furthest from you, and they'll have developed quite a bit before you conront them, or even find out much about them. So there's a lot more suspense. The drawback to CIV back then seemed to me that often you could tell far too early that you were going to win (or lose) for sure; not much suspense. The early game of quick primitive development yielded to a middle game; but often the game was obviously over, for all practical purposes. Not so with a tall thin world. Lots of good wars at the end with modern armies and units. Great fun.
Right, I should said more, so now I have, as a reply to my comment. Thanks.
I think the crux of the problem is not expenses themselves but that you learnt it from slack. It doesn't matter if the CEO is wasteful or miser, it looks like his decision making is one sided. I don't see much future in things frankly.
I see a lot of concern here and elsewhere about getting local pre-paid SIMs when traveling. Wouldn't widespread eSIM support be a boon for those carriers? As I understand it all they need is a thin app and a sign-up process. It's not a high barrier to entry and most pre-paid markets are very competitive, so I think there soon will be many choices. (The iPhone won't be the last to drop the physical SIM port.) The real losers will be the corner stores.
I'm pretty sure that setting up entanglement involves information transfer.
Wow! - A 4x increase in minimum memory over just 5 years. And it appears that they are desperately fighting memory leaks.

Maybe the Android Team should consider a "Rewrite to Rust" project, introduce a better designed API for native apps and market an "Android Yoga".
The fact that linux systems need adminstration is one of the reasons why they suck.

Imagine after buying a macbook that you also need to hire a sysadmin to keep it running smoothly? The idea is laughable.

> Learning how to effectively use the command line. Unix philosophy. Pipes, scripting, and tooling. So much of programming is stitching things together.

This is really bad. Much of the complexity in contemporary software architecture arises from this mentality.

"Do things by stitching programs together" only works for relatively simple tasks. For everything else you need to program the thing properly.

One of the worst ways this manifests is in how websites are built: use a combination of a scripting language, a database server, an http server, a memory cache server, etc.

I'm really grateful we have things like Go and SQLite that make it possible to create fully functional websites as self-contained programs instead of the hot mess that everything else uses.
They did that, and I'm not sure they could have gone much further in the way of restricting OEMs, considering they were told to knock that shit off by the EU [0]. Few people that I recall so much as batted an eye - even XDA in the earlier days was stuffed full of people wondering how long until Google came down harder on OEMs for better update support, and many people were in favour of Google using Google Play Services as a stick.

[0] https://www.cnbc.com/2018/10/16/google-will-stop-bundling-it...
Oh no they want phones made in 2022 to have a whole 2GB of RAM! So that consumers can expect a certain baseline level of responsiveness and performance on any Android phone unlike the fragmented mess now. so evil omg fuck google!!111 i hate technology take me back to Nokia 3300!!!!! I used to be young and free and hot :( :( :(
Not the device vendors. Some device vendors did that. Some other device vendors would have preferred to use the Android branding and comply with Google's restrictions than to alienate the existing userbase. Can you really imagine Samsung selling SamsungOS phones? Once Android was established it was well within Google's possibilities to impose restrictions, but they instead chose to let the manufacturers do whatever they pleased.
https://nandgame.com/ will guide you through using NAND gates to create one computer. (There's lots more to learn about how to create other kinds of computers, and other ways of designing them, but walking through that one example should at least dispel the illusion of magic.)

The last time I did it, it took me two hours, but I think that if you are coming at it without any previous knowledge of digital logic it should be tractable within about 40 hours.

Then the only remaining things to understand are:

① how can you create NAND gates with transistors?

② why are transistors better for this than, for example, relays, pneumatic valves, or neon tubes, all of which would also clearly work?

The answer to ① is actually pretty simple; the best explanation I've found is in The Art of Electronics, though Ken Shirriff's blog has a lot of great stuff on it too. And Falstad's circuit.js has some good simulations, like https://tinyurl.com/2eegeyxj and https://tinyurl.com/ybpo5ls2, which I think are nicely complementary to the theory.

I've never seen a good explanation of ②, but I think the main answer is that electrons are about ten thousand times lighter than atoms, so with the same energy, they move about 100 times as fast. The result of that is that switches that work by moving around electrons can switch a great deal faster than switches that work by moving around atoms. Neon tubes also work by moving around electrons, but they're slower than transistors for a different reason: it takes the gas a long time to thoroughly deionize.
Yea. It's really put a dent in Apple's sales. Why do you think you are Apple's primary customer type? They want a solid phone with secure OS and App Store, no wires and they already have a dozen USB charging bricks.

BTW The iPhone 14 Pro is actually thicker than the 13 - you know because they needed to put in a better camera and larger battery. And your snide comment is somehow implying that Android is more useful and intuitive? Hahah.
A kazillion images are used to create/optimize a neural network (basically). What you're working with is the result of that training. These are the "weights"
If someone has a giant tumor taking over their heart, one "obvious" answer is to cut their heart out. Problem solved.

I mean, patient killed, but ...details.

I don't know the answer. I do know that some of the tax incentives related to real property in California are seriously problematic. How to fix them? I don't know. Tax law is not one of my areas of expertise.
I don't think they were racist and I am flad for their victory but for the convicts... yeah this is America we're talking about their confession means something only if there was no plea-bargain and I highly doubt 3 young people will in unison confess to a crime without being under duress (plea-bargain). However, the fact that oberlin couldn't prove their racist history in court is all I need to know about the baker's innocence.

Plea-bargains are a mockery of justice as is cops being allowed to lie to get confessions.
Eh, just call it out, it's India and its subcontinental neighbours. And the reason is less culture and more there being a lot of first-time passengers going to menial jobs in the Gulf, who have been recruited from deep in the countryside and are entirely unfamiliar with things like non-squat toilets and how garbage collection works on planes.

I once flew DEL-AUH next to a gentleman who was clearly very puzzled with nearly every component of his in-flight meal. Not sharing any languages, I helped him out best I could with sign language, but I still remember his expression of surprised delight when he poured one packet's contents straight into his mouth, expecting gutka (powdered smokeless tobacco) but getting powdered coffee creamer instead.
I feel like there is only one aspect mentioned that is actually a domain specific thing (the double entry bit)... everything else is just a list of features that all sorts of general purpose databases have... am I missing something?
Eliminating computer usage isn't a valid solution. Computers are too useful to simply stop using them. Maybe computers were a mistake that will eventually destroy society but for now they're here to stay especially mobile computers with built in archaic telephony.

So the question is how to improve privacy and control while using computers.
You're putting a lot of words in their mouth that they didn't say. Their original statement was perfectly valid; the business probably has losses they can use to offset the tax liability. That's all they said. They didn't make any further judgements about whether that was overall better or worse.