skysight-inc/HackerNews huggingface dataset:
I agree regarding the offline ability, though literally all the things I'm using 2FA for are online, as they are about logging-in to services.

As for the 2nd point - I definitely don't think it has to be a separate app for each service. Why would it? Imagine an app that holds a private key, the website showing a QR code, you scan it with the app, the app sends the public key to the service using a URL provided in the QR code, and the service stores your public key. From now on, every time you want to login you're asked to scan a QR code, which makes the app send a signed request to the a URL encoded in it. The service gets the request and proceeds with the login. One app, all services.
Bullshit about the devil to blame for Haiti's problems and not the French who abused them and forced them to pay billions for their freedom. France needs to repay them with interest.
https://play.google.com/store/apps/details/Apple_TV?id=com.a...
> dynamic pages on the SQLite website typically do about 200 SQL statements each.

[0]: https://www.sqlite.org/np1queryprob.html
Why use k8s over just a docker container?
I dislike explaining string compares to monolingual English speakers who are programmers. Similar to this phenomenon of Й/И is people who think ñ and n should compare equally, or ç and c, or that the lowercase of I is always i (or that case conversion is locale-independent).

In something like a code review, people will think you're insane for pointing out that this type of assumption might not hold. Actually, come to think of it, explaining localization bugs at all is a tough task in general.
IANAL but many sites that sell illegal drugs can get you in serious trouble. And I'm pretty sure the same goes for terrorism related searches and even searching for illegal downloads.
I'm partial to forecasting volatility via GARCH models as well!
How did I publish a paper in ACMKDD as an undergraduate? (2022)
I wonder if there's a way to document such replaceability failures as an erratum to the original manuscript. I feel like this would help in at least two major ways:

1) It provides a reproducibility filter. If a method isn't shown to be reproducible, publically documenting that adds to the body of knowledge, and this would help drive an incentive towards reproducing work rather than just searching for novelty. It would document work that would otherwise be lost because there's no incentive to showcase it. When the lack of reproducible results isn't public, it's now more likely that others may waste considerable effort in the same vein.

3) It may enlist the original authors to help understand why the work didn't reproduce well. Maybe the secondary effort lacked some crucial step or understanding. The people best positioned to remedy this are the original authors, and this secondary publication incentivizes them to dialogue with those who couldn't reproduce the outcome. It doesn't mean they have to engage, but it at least gives them some reason to involve themselves in the process.
Yes you took the bait!

> This was at a 100+ developers organisation.

IMO the vast majority of software development happens in much smaller organisations than that. Dev Ops still matters there, and the requirements are different.

I am working in an organisation with one and a half developers. I am lobbying that the third of fourth developer concentrates on Dev Ops here.

It is very important. Look at the back up/recovery procedures at your organisation. Has there ever been a fire drill? Are you sure the back ups are sound? Can you recover? What if data corruption occurred a week/month ago. Have you a back up of the uncorrupted data?

That is a very unsexy aspect of Dev Ops, and without somebody dedicated to the job, your backups will not be any of those things.

Bitter. Experience.
Switching the primary energy source from solar or wind to nuclear wouldn't do anything about the need to de-energize certain branch circuits during high wind events. It's worth discussing, but it doesn't make sense as an antisolar talking point.
At least with an aircraft carrier you can make your money back by holding a small country for ransom, har har.
> and if you have good form, warm up, and only add 5-10lbs per workout

Most beginners I’ve seen do not take the 5min it takes to learn proper form. And even if they do, they lack the proprioception to know when they’re doing it right.

You really need a mirror or someone to keep you honest, preferably both, for the first few sessions. Someone needs to tell you what correct looks like on your body. It’s very hard to get right on your own if you don’t have a history of working with a coach who developed your proprioception.

I’m what you would call a grinding amateur. After 10+ years of daily workouts it takes me only a few hundred tries to do what a coach tells me. My sister has been a competitive athlete since 4 years old. It takes her 2or3 reps to perform exactly the movement a coach gives her (even in a new sport). Just because her body control is so much more developed than mine.
Yeah, I'm an independent, selling these solutions. My minimum stack costs about $500/mo in AWS costs- and you could save 90% of that. But then you'd be paying me $20k more to set it up again when you expand to another dev team, while this way I can add your second dev team for $10k and practically zero additional AWS cost.

Going straight to overkill is good business sense for any company that's going to make it to a medium-sized business, and it's not going to be the differentiating factor for a company that burns out.
Our environments are entirely automated on AWS. It takes about 10 minutes to get an ALB and a mysql instance just on the AWS side. We've configured ECS to have the quickest health checks we can manage, and it still takes 3 minutes from the initial call before everything is happy.

Our environments are easily repeatable, they're very maintainable, but they're not quick to start up
It's not a replacement for passwords, just an obfuscation in terms of what sites are on a server... you don't know what host names point to a given IP only knowing the IP... you'd need to have a man in tne middle.
All the Endangered Languages, by Country
According to Chatbot Arena where people vote on responses blindly and an ELO rating is determined for each LLM, gpt4 is on top slightly ahead of Claude 3 Opus

https://huggingface.co/spaces/lmsys/chatbot-arena-leaderboar...
> I've never come across a devops person who'd say "Hey, that sofware is too simple to prematurely scale for sudden spikes of irrational amounts of traffic, so why not just deploy it on a cheap vps?"

I’ve lost startup jobs for basically this. As in “let’s focus on our mvp instead of adopting k8s and discussing “the definition of done” for literally six hours a week”. That one ran out of money and folded, sadly. They had tons of potential and a few bad hires.

But also on the other side, my time is expensive, engineering time is expensive, downtime is catastrophic for a new business. Some people want to spend 4 5 or 6 figures to save twenty dollars a month. Imagine my time is worth $500 an hour, if the effort to make something cheaper doesn’t pay for itself in a year then it’s probably a waste of resources.
The best metal umlauts are placed on a consonant (e.g., Spın̈al Tap). This makes it completely clear when it's there for aesthetics and not pronunciation.
It is going to sound a little weird, but some people have trouble understanding complexities of ethnicity, country of origin, its intersection with local history, religion and so on ( my wife struggled hard with this ). Some people see Huang as Chinese, the same way they may see me as European. It might be technically true ( and it does betray some perspective a person may have on the subject ), but it happens to ignore some reality on the subject ( as in, how does Huang see himself ). I guess what I am saying is that it is an easy ( if a little lazy ) way to label people.
> Developers write apps, engineers write software.

That is a classic distinction without a difference!

Engineers have been to engineering school. If you have not been to engineering school, you are not an engineer!
Your conclusion is correct, but most of these shutoffs don't affect anybody. The utility has to announce them but usually they don't cut anybody off. There was only one event in 2023 during which SCE de-energized more than single digits of customers.
Well you can always drill holes in the platter, or hit them with a strong magnet, or just separate them and toss them in the trash. Unless you're fighting the NSA, you can probably get away with enough physical destruction to make recovery challenging.
yup, especially if they are not including the standard: "Disclosure: I have positions in this security."

This could be interpreted as (and/or variously written to indicate) "this person is just talking up his/her book" or "they like it so much they have skin in the game".

Plus the factor of how much noise there is to any signal in the social media & message boards, how much attention can one reliably actually get for your shilling?

Wrong vs provably wrong are often different
Yeah my search engine, back when it was hosted on a PC in my living room off domestic broadband would shrug off HN[1][2] without the fans even spinning faster than usual.

And like, internet search should be more resource heavy than the sort of websites that regularly do keel over to HN. Every query is like up to 50 MB in disk reads.

[1] https://news.ycombinator.com/item?id=28550764
[2] https://news.ycombinator.com/item?id=35611923
You believe incorrectly. Not even Canonical XML requires normalization: https://www.w3.org/TR/xml-c14n/#NoCharModelNorm
You are aware bloomberg presents at CNCF?
My impression is that your standard wordpress + Apache + mod_php + mysql on same server install cannot, without plugins that improve wordpress' caching behaviour, and that's a large portion of the sites that do fall over.
I agree w/ the sentiment, but the author doesn't seem to understand why people tend to like touching the customer at the edge. Since everyone is doing TLS these days, you have to do a TCP connect round-trip and a TLS round-trip before you can start yammering over a connection securely. So that's at least three round-trips. If you're one-way latency is 200ms, that's about a second of delay before things start happening. The benefit of the edge is you can establish a connection with an endpoint that's "nearby" with less latency for the TCP & TLS round-trips and then use a previously established connection (that does not require you to do the TCP & TLS roundtrips.)

There's still latency, but the impact of the round-trips at connection time is reduced.

Also, web-apps use horizontal scaling largely to reduce the impact of head of line blocking (where requests are queued up at the client waiting for the current request to complete.) Browsers will sometimes (often?) open multiple connections to the same endpoint to reduce HoL blocking impact. But, sometimes apps are inherently serial (you don't know what the next request is until you get the response back from the current request) so YMMV. Also... HTTP/2 and QUIC are cool, and I think most major browsers support either or both.

Amazon is also sort of (in)famous for triple-redundancy. Their apps run in at least three different availability zones (think different data centers) to avoid the impact of one data-center going down. Sure, it doesn't happen very often, but Amazon REALLY doesn't want their site to be down at all.

So sure... you COULD run the overwhelming majority of web apps on a single container in a small VM on a single machine somewhere, but it's more than just resource utilization. It's also responsiveness and resistance to single data-center failures.

But don't confuse my comments with a callous disregard for the OP's concerns. Dude has a point. I think anyone who tries to deploy a web app to AWS (or Azure or GCP or ...) is barraged with messages about how you have to deploy things in multiple data-centers and you're not a REAL developer until you've crafted your own customized templating engine for spitting out TerraForm or CloudFormation scripts that automagically deploy to N+1 unique datacenters.

There's probably a market out there for a simplified system that's "here's a simple {Node|Python|Ruby} app. Automagically distribute the backend to N different data-centers, maybe only one is up at a given time and the other N-1 are hot spares. And make the persistence tier indistinguishable from a local DB like Mongo or PostgreSQL (or some weird Prevayler-like thing.) Don't make me craft custom TF or CF to manage redundancy.)"

Please note. I'm not talking about using SAM.

To recap... I think the OP has a very valid point, but may not be familiar with all the current triple-redundancy dogma.
I'd argue for a third category where the new thing addresses a problem that the company themselves is making more problematic (e.g. TurboTax) or where "more efficiently" involves cases where costs to the company are exchanged for costs to society (e.g. petroleum companies, cambridge analytica).

I think this category represents the majority of economic activity today, which is why I'm skeptical of markets being zero sum.

The result is the same though: find was to get more of (1) and less of (2) and (3).
It's not that much of an exaggeration. Tenochtitlan--the capital of the Aztec Empire--is estimated to have been about 120-150k people at the time of contact, which is larger than any city in the Spanish Empire at the time. Even the Spaniards themselves, as they recorded in their journals, were astonished at the scale of Tenochtitlan.
It seems to me that it is important to communicate that you can injure yourself easily if you do deadlifts wrong. With any weightlifting exercise it is important to start with an easy weight and make sure that you are confident that you have good form before adding weight.

Deadlifting can be done safely which is evinced by the many people who have done it without injuring themselves. I feel for you that you got bad advice. I do agree however that with good form, it should be difficult to injure yourself seriously deadlifting. The rub is that not everyone has the ability to self-assess and some coaches are also bad. If you are not very confident you will not hurt yourself, you absolutely should not deadlift heavy weights.
> Try register on Twitter. They'll let you register but then randomly suspend your account for alleged ToS violations (even if the account was outright inactive) but will give you the option of instantly unbanning yourself following phone number verification. Microsoft will randomly lock out MS accounts without a phone number attached and will require a phone number for "security" upon the next login (the security angle being very dubious considering they don't have a number on file to compare to, so even an attacker can pass this challenge just fine). Etc.

I have accounts with both of these orgs, not equipped with 2FA and none of what you describe has ever occurred.
> The problem with devops replacing the old title “sysadmin”....

That is a very good observation.

I think that now I am going to stop using the term Dev Ops and start using System Administration.

Wise words, thank you
I imagine a huge leap in a single individual like this millions of years got us from primitive pointing to something like language.
Yeah, plan on hitting the road and more or less following the path if the forecast doesn't look good where I am.

In general it looks like the closer you go to Mexico, the better your odds — historically.
It depends. I've had close to 100% uptime with my single server, whereas one of my customers who has hundreds of AWS servers has had some pretty severe downtime (hours at a time) due to some screw-up on their end. Complexity creates its own risk.
Scale Was All We Needed, at First
https://web.archive.org/web/20240324201541/https://www.techn...
I know what you are talking about, unfortunately it's way worse than that.

The same guy that runs the k8s is the guy that "reviews" my PRs. It's also the same guy that can't get eslint into our PR process, and the same guy that merges code from other people that just out right brick the server because it had some bad syntax.

I _wish_ my problems were caused from too strict standards and procedures. But really is just a lack of understanding and cooperation.
The issues tend to be around bandwidth and power delivery.

The caldigit thunderbolt 4 dock has 5 usb-c output ports, 2 are thunderbolt 4 and 3 are 3.2. Only the host t4 port is 98w, the rest are 20w, 15, or 7.5.

It does however only support one display.

If I needed 4 displays I would probably put this between my host and the four display device posted on here.

I would however prefer to see a single dock that can both accommodate a modern port set and multiple monitors.

https://www.caldigit.com/thunderbolt-station-4/
The Lone Volcano in California's Central Valley
Somehow hearing of getting free hosting from Oracle makes me think of the advice to not stick your "thing" in crazy. It's probably fine, but I'd not touch it if it can be avoided, especially if I can just pay a small and fair fee at another provider (or, in my case, self host it)
That paper says you need to control "0.1% of the training data size" for a 40% chance for one single injected prompt to fire. So that's millions of images or billions of text tokens for real-world models.
Gold nanoclusters offer sustainable solution for wastewater polluted by dyes
But you’ve got 100 developers. That’s not “most web apps”, that’s firmly in the set of companies that need standardisation and potential scale, where the devops team makes the life of many devs far better. When it’s just a few devs and cash is limited, the business doesn’t need the complexity. It’s mostly for ego and branding.
Majority of tech companies could run on just a handful of nerds. But VC comes in, pretty soon you've got a bunch of lawyers telling you you need HR people, more lawyers, people to run ERGs. Soon you've got server farms all over the world to handle a couple dozen simultaneous users, thousands of employees, and you've made it!

Then the board fires you.
And you would prefer the English flag then - not the flag of the UK?
Of course. The entire point is that so much of that is just unnecessary for 90% of web projects. Most projects that are basically a front-end website backed by a local DB can get by on a 2GB VPS if they embrace classic web tech and don't get sucked in to whatever framework/cloud service/container craziness is hot this week. Once they start hitting millions of page views a month, we can talk about upgrading to 4GB :)
The question is whether you need active-active or if failover will be enough.
You can be silly and original. Being another team of young engineers that really love coffee and call themselves code artisans is anything but original.

It's like the widespread humanistic art style that 99% companies have adopted in the 2010s to show they are not another faceless corporation, but instead are a friendly business where you matter.
> unnecessarily complicated with k8s

Kubernetes is/was a way to fight off walled gardens from cloud providers. The other path would have been to learn the bespoke implementation of each cloud provider depending on what that employer ended up using.

Kubernetes was at the right place, at the right time just as AWS was trying to force feed people their own proprietary solution, as Azure was trying to wall off people into their own walled garden, as GCP was being Google just not giving a damn about any other usecase than what works great at a massive search company.

With Kubernetes, developers can learn one API to deploy their applications and hopefully it works on AWS, Azure, GCP, DO, OVH or a laptop at home.

So that way, developers can learn one thing and transfer their knowledge at an employer that hosts on AWS, and then another that hosts on Azure and so on.

This is in contrast to the experience of a Python developer who's mastered FastAPI/Flask/SQLAlchemy and feels absolutely lost in a Django project or an Angular developer who stares a Next.js project wondering what the heck is happening and how it all works. Neither a Next.js or an Angular developer would start off with an AWS Amplify solution if they could help it.
If those are the metrics we should be using the Indian flag.
But that's like saying "you can play Russian roulette safely if you do it properly". Sometimes you get injured no matter how good your form is, and sometimes you get lucky and are fine even if your form is poor.
The irony of reading this article on pc gamer and getting a pop up for them sending me notifications in my browser was priceless.
HTML does not require NFC (or any other specific normalization form):

https://www.w3.org/International/questions/qa-html-css-norma...

Neither does XML (though it XML 1.0 recommends that element names SHOULD be in NFC and XML 1.1 recommends that documents SHOULD be fully normalized):

https://www.w3.org/TR/2008/REC-xml-20081126/#sec-suggested-n...

https://www.w3.org/TR/xml11/#sec-normalization-checking
https://otherweb.com/
That's really the kicker for me.

When the company is set up well on k8s, then choose k8s. If the company is set up well on VPS, then choose VPS.

If it got neither, I'm unsure what's the better way to go on a greenfield.
k8s has nice tooling, but part of that is required because it is massively complex.

But with managed k8s providers (e.g. GKE with autopilot) you can just put in proper CPU and memory limits and essentially get yourself a VPS provisioned without having to worry about anything by k8s measures.

If you have different pricing or location constraints, then it might be better to go with different models and some custom orchestration.
I guess Microsoft realised that most users would install "third-party" adware anyway, and decided to get in on the action.

Fortunately these days computers have gotten to the point where you can run an old OS from them, like 98/2K in the browser[1][2], or make a little VM and install it, so you can remind yourself that MS wasn't always like that.

IMHO the messages coming with updates started becoming intensely creepy around Windows 10, the first time the unskippable "all your files are exactly where you left them" ominous ransomware-like screen appeared:

https://www.reddit.com/r/windows/comments/3x88yj/all_your_fi...

[1] https://news.ycombinator.com/item?id=15763418

[2] https://news.ycombinator.com/item?id=38376731
Maybe that still counts as an unpopular opinion in the large, but I’ve never seen it be an unpopular opinion by the standards of really effective teams or really productive hackers I had the privilege to be around at times, and it seems to me that your good idea is coming back in a big way recently.

When I worked on teams that denominated egress in terrabits/s, TPS in millions or higher (sometime much higher), and daily warehouse ingest in petabytes it was just the default thing to spin up an instance and a hot standby (sometimes per region or something) if that’s all that was required, and containers and whatnot were used only in the context of bare-metal: you do usually want one level of indirection so containers are really useful if you’re racking metal from a small menu of SKUs.

But as for why it ever became conventional wisdom to wrap a venv inside a container on a hypervisor, often with multiple images composed on a dizzying array of low-friction SKUs?

I never got it and still don’t.