skysight-inc/HackerNews huggingface dataset:
Clicking on the title of the kbin post takes you here where there are more comments: https://mstdn.games/@chris/110553477682106144

This seems like such an unwise thing for them to do that I feel like there must be another explanation.
The Seattle Visionary No One Talks About
Without wanting to be too techo-utopian, it would seem like some kind of automated system, that actively pulled in cooler outside air when available would outperform the manual intervention described in the article.

But generally, reversible air-con, in houses designed to be heated and cooled via heat pumps is a fine solution. Applying aftermarket air-con as a band aid is probably counterproductive, but that's not the only way to use air con.
From what I've seen recently is the inverse of that.
There are scores of developers who have little understanding of OS scaffolding or networking, but are good at writing merge sorts in Python.
Most Devops people I know are not the ones pushing "vanguard of a new paradigm" BS, they are just ops who can code and understand performance tradeoffs, networking, subsystems, etc.
I guess we can blame Devops for one thing, the paradigm has encouraged the behavior of "real devs" (TM) not understanding anything about the underlying platforms they are writing code for. That was the point, but it's not all gravy.
The 2 month version experiences scaling issues at a 20% rollout, or takes 20s for a database query before returning a page.

In 6 months you need a better scaling version while the current version is creating cascading database failures; it's got terabytes of denormalized data that is out of sync and a 2nd team can't migrate the data in 12 months.

In 12 months, you find 5 other teams copied the 2 month solution.

In 2 years, you have 0 devs left that can solve the problem and a 1000% grown dev team that is great at the 2 month solution.

You ask the teams why they don't use the scalable solution and they say, "do we have any examples of that, the unscalable way is our convention"
Extinction is normal, but we probably don’t want to go extinct either.
Why Kubernetes wasn't a good fit for us
Some people don’t care, others think with their dick and ignore it, when they urgently want to access something - which is the reason MANY people pay for porn with credit cards.

But I would think, the majority of reddit users would not.

In theory you could offer anonymous payment, paysafe and co. but more and more governments implement age restriction for porn anyway. No one cares for small sites (yet), but reddit could be pressured to not accept anonymous payments as the are big.
Requiring a Computer Science/Software Engineering degree for a non programming job is a little weird.

The point is coding skills are not required to do the job. Sure it would be nice but if somebody ticks all the other boxes then being good at programming isn't important.
Cloudflare’s core business is being the front end of your web presence. They provide DNS and CDN services, so bring a registrar is a natural fit because it provides the last thing you need to keep your web site online and secure. There’d be demand for a registrar just because that’s what prevents domain takeover attacks on the first part of that security chain.
Hahah. We did, but we were a few years too early for many parts of it. The Global Learning XPRIZE was a $15M challenge to build basically this: tablet software that could let kids without access to schools or teachers teach themselves.

We (Learn Leap Fly) were a semi-finalist in that competition. We bet heavily on AI, but again, were a few years early (Note the constraints of the problem said that the devices were NOT connected to the internet, which makes things still challenging today)

We were also a semi finalist (round 3) in the AI XPRIZE (with the same tech).

We’ve thought about whether to resurrect the core ideas and give it another go. For that we need partners. Education isn’t the most lucrative of fields, it turns out.

That said, anyone who wants to go down this path, send me a note. I’m happy to talk nerdity on this topic all day, be it AI, literacy education, pedagogy or grand challenges!
Discourse, open source, is probably the most mature platform for tight communities. One issue with Discord
is that it can't be search indexed, but Discourse is more similar to a forum and can be indexed (if public).
https://www.discourse.org/
>This is a false choice - there's no reason the iPhone can't be both a walled garden-type device and support alternative OSes/software, just like a computer.

There are a few reasons.

E.g. allowing sideloading amounts to basically allowing any third party with clout whose apps users want to use (Microsoft, Facebook, Google, etc) to mandate the use of their own apps bypassing all related protections and integrations.

It also enables smaller malicious third parties to demand the same (but at least there the user has to be duped into installing them. Whereas with big-name apps, even users who know what they're doing could have a legitimate need to run those apps).

So, what about supporting alternative OSes/software? So basically, Apple not to sell a phone (with OS and everything), but a generic target phone hardware, that comes with their iOS preinstalled? Isn't that a quite different demand?

>The future on a long timescale may not be so nice.

On a long timescale you can change devices. It's not like something you buy now you'll have to run in 10 years.
Fraction of that if we just run old.reddit.com instead, you know the good version of the site that actually loads and works.
Looks interesting!

Almost feels like reinvented Perl, which can be a great or terrible thing depending on how often you invoke perl from the shell or scripts.
If Reddit's goal is " is a 2-5bn market cap business with solid 0.5bn revenue", then do they need an order of magnitude more staff than say, 5 years ago? My understanding is their, rather dramatic, scale up was to chase Twitter/Instagram/TikTok. If they're going to drown in expenses before achieving it, then it seems pursuing that was a poor business decision driven by investor expectations of hyper scale (never mind its effects on the product for users).
This is one of those rare articles about DevOps that isn't bullshit. The irony...!

This part, while true, bothers me:

"Simple, just hire some more frontend and backend engineers to develop a great internal PaaS with all the golden paths your operations team is architecting while you are trying to build your actual product that runs on top of it."

I've been on that team, multiple times. It doesn't really work, because it's yet another silo, and it takes years to bear fruit. We shouldn't be developing platforms, we should be buying them.

It's like building and running a factory so you can have an assembly line to make widgets. Most people who want to make widgets today actually contract that out to a company in China who already runs a factory where they adjust their tooling to make your widgets. That's what economies of scale and specialization do: you pay somebody else to do the hard, expensive thing that isn't a core part of your business. You get to market faster, you waste less money, and carry less risk.

We're doing business wrong. You should not be building factories, you should be hiring a factory.

Do I mean "hire consultants?" No. What we need doesn't seem to exist. We need companies who do white glove integration of a software product with a bespoke PaaS. Like Heroku, but with more attention to architecture, monitoring, alerting, security, ci/cd, etc. Someone who will give you the tools, train your people, do integration alongside them, and provide support. And they could do this on a cloud account that the customer owns, with IAM guardrails to prevent them fucking up the platform.

There is no value added to your product by building a factory. You might reduce cost, eventually, if your business is huge enough. But there's a small number of such businesses out there, and yours likely isn't one of them. So let's start some platform companies and make those the default choice.
Doesn’t Google just ignore paid users too?
When I use Reddit without logging in, the homepage for my country shows some really detestable subreddits promoting outright, peak election-season Facebook-tier propaganda and hateful content.
Building a new database management system in academia (2017)
In faanng componies I know, they r usually the infra engineer/reliability engineer/production engineer, etc. They are treated the same as typical software engineers just that their focus is not on the product.
Can't say too much about it. Didn't really follow the whole Covid discussion and just continued my lifestyle. Eating healthy (fresh self-made food), doing sports and looking after a good mental state. Family and my circle did the same. Friends who have been vaccinated got Covid several times. But are also good now... My grandmom (89 years), also unvaccinated, didn't get Covid. Her sister got it (vaccinated). Both healthy now... Just let everybody do their own thing... The whole hate in the communities was unnecessary.
> ...there was another high profile malware incident (SpinOk)...

Based on what I'm reading, this "high profile malware":

* Requests permissions to access a ton of information on your phone

* Uses those permissions to read and transmit the ton of information that you granted it permission to access

"This software did what I permitted it to do, but I'm not happy about what it did." is a complaint that's pretty solidly platform-independent.
The old code that reddit published says you have to put a copyright on any service that runs the software, so /r/foo would be fine, and the bottom of each page would say something like “Portions of server software copyright reddit 2017”.

I am not a lawyer, but that’s my reading of the license on that repo.
Eh. It might be fine until it isn't. One build system breakage and you are looking at an afternoon of fiddling if you are like me. (not much experience in C++ and it's tooling)
This is indeed the case. Have run into a few surprising things like this when implementing posthog experiments recently
How about not calling something a crisis if it isn't? A crisis is usually short-lived, not a permanent state.
What happened in Alberta was just a couple weeks of warm weather after a fairly cold winter. The timing was right when new growth hadn't had a chance to take hold so all the dry grass and tinder was perfect fuel.

The rap attack helicopter crews were dismantled in both BC and Alberta to save a few millions at best. Easily doubled the size of the burn area not having this capability.

This is normal but not new. Alberta has had larger amounts burned and the trend is down. The 1920's to 1940's were the worst in recorded history. Accurate measuring of what was burned has improved each decade too. Earlier in the record much was not included.
>I'm just saying, the Apple II shipped with AppleSoft Basic. The Mac had no such language or built in compiler.

So? Apple II shipped in a date when you did a lot of stuff on your own. All home computers had some BASIC or similar built in.

In any case, OS X shipped with C/C++/XCode IDE and several scripting languages and shells, more powerful than Apple's II BASIC.

And XCode and all kinds of computers is an officially supported install away now too.
While I support the efforts to prevent and reverse the environmental damage we're causing, personally I don't believe they'll really succeed. It seems that human society is fundamentally incapable of acting in a coordinated way against a global, long term threat. So at a certain point convincing people to take the bus instead of a car, specifically because that will save the planet, starts to seem like a lie. It's not unreasonable to start thinking in terms of preparedness, rather than just prevention.
> and that the person responsible for work prioritization gets every single page in order that they feel the pain of that.

This sounds like an incredibly toxic work environment
Running the experiment until you have a specific pre-determined number of observations is okay.

However, the deceptively similar scheme of running it until the results are statistical significant is not okay!
The other part is that management/PMs usually care about deadlines, not work effort (duration in man-hours, story points, or whatever).

Allow me to indulge in a fictional narrative:

You are handed "high level" (a.k.a rooted in the fuzzy non-technical alternate reality that is product management) requirements resulting in known unknowns and unknown unknowns. You're junior and naive and you put real tech-borne effort numbers in front of each task; or you're experienced and you put O(t) numbers on the first ones and random but high numbers on the second ones.

Anyway, the estimates end up landing past the desired deadline, management mutters TLAs such as "OKR" and whatnot, you'll have to justify why it doesn't fit, so you communicate work effort.

You are summoned into a retroplanning meeting to cull out stuff based on work effort so that it fits management's expected deadline, and try to pretend you're doing agile when it's all waterfall Gantt in disguise.

Project starts. Implicitly man-hours become wall-clock-hours, irrespective of other tasks such as CI/tooling/dependency breakage, code hygiene, or customer support escalations; your effort estimates became t{project start}+effort == deadline. You are now held accountable for the latter based on you communicating the former.

Time is now the scarcest of resources, you do your best, conjure magic, work extra hours, take shortcuts, and make it to the deadline, sacrificing body and soul. In a cloudy spreadsheet checkboxes have been checked, management is happy. Deployment is smooth but soon corner case bugs and escalations start trickling in. Management is either oblivious or not so happy after all.

Time for a new quarter to start. You know issues borne out of past quarter will rear their ugly head, and there's much tech debt to repay before interests quickly accrue towards tech bankruptcy. You're junior and swear to yourself to not make the same mistake, and you start inflating numbers; you're experienced and you realise the whole number dance is a sham as they don't matter anyway, but you still are required to do the dance because that's how the game is played, so you turn Scotty and just throw outrageously big numbers up in the air and just make sure the deadline is not too ludicrous, still hanging to the hope hoping that someone, somewhere, has seen the light of reason and built a company around it, and maybe you could go to these greener pastures; you're very experienced and you realise the only winning move is not to play, so you quit (not the job, the _industry_) and move to a remote plot of land with literal green pastures and a small cabin mountainside to raise sheep, or cut wood, or whatever, where the smallest time unit is the measurement error of eyeballing the zenith-relative angular position of a giant fireball 8.3 light-minutes away.
Yes! Possibly relevant article on your point: https://medium.com/swlh/yes-devops-is-a-role-you-just-do-it-...
> ~60 applications, ~15 interviews, ~8 technical coding style interviews

Some people can go as high as several 1000's applications and several 100's of interviews and still no offers. So do not despair, it's number game even if you knew your craft really well.

2 pieces of advice:

-Do not overly target your application to the job posting, as long as you have a 50% match, go ahead and apply.

-Opt initially for non-remote jobs, if there are more non-remote options, and then either lookout for remote jobs, or stop showing up at the workplace and work remotely saying you have obligations. It may go against your personal ethics to do so but for most part the corporate world is sufficiently twisted that one has to (seemingly) break one's personal moral code of conduct.
Yes. Their Indian branch was called लाल टोपी

https://translate.google.com/?sl=hi&tl=en&text=%E0%A4%B2%E0%...
> Tracking hours is a pain in the ass and we do it mostly in Jira tied to tasks but the data we get is invaluable.

The important point here is to actually feed that information back to the people that originally did the estimates and also to the people that are (to them) "pointlessly" clicking on the "start work", "stop work" buttons on their JIRA tickets.

Most of the time, this sort of timesheet stuff is fed to an accountant somewhere that turns it into magical "earned value" based on inaccurate project schedules that are always 99% complete but with a vertical S curve.
Thinking about it more, one cool thing about level scaling is I can play with my friends at whatever level they are. It doesn't really matter for the endgame at all, but when you're leveling up early on it is pretty nice.
As an Italian I've studied Latin at school and was quite good at it. Some 45 years later I still can read and translate on the fly very simple texts, but the two languages are two planets apart; different structure aside, they share some common terms but Italian adopted others from foreign languages, to the point that some Latin terms are still present in English but were eliminated from Italian. A couple examples: the Italian for "paper", "carta", in latin was a quite similar "papirus", while "charta" was used only for government documents and the like. Also, the Italian for "cheese", "formaggio", is more similar to the french "fromage" than the also Latin but rarely used "formaticum", while the most used term in Latin was "caseum".
I suppose I'm the guy you're talking about - I'm the lone ops guy on the one dev team for a small SaaS business. I try to write as little code as possible actually; which isn't to say I try to spend little time writing code, it's more that I try to rely on community maintained frameworks because I fear creating some complex duct-tape and zip-tie web of homebrew automation that becomes increasingly hard for myself (or god forbid another person) to maintain.

I like the term platform engineer or maybe just infrastructure engineer, but I don't think they really add much specificity. For instance, we don't use any of the big three cloud providers, which I suspect would be an expectation for most of these titles. I think the possible diversity of modern tech stacks is just too much to pin these titles down, and mostly I just tell people I'm an "IT guy" ; it's only when you talk to someone in the industry that titles like Devops or Platform Engineer have any meaning, and as this thread shows, there's not even that much consensus within.
This is crazy! I like the following comment on kbin:

> I said it before and I say it again: if you have the patience to do so then make sure you overwrite your content with chatgpt generated content, as the future AI that will feed on your post HATE feeding on already AI generated stuff. It makes the AI diverge.

People should not be deleting their posts but actually just replacing them with random AI generated content. This will make Reddit a mess.
I take a different view in the sense that reddit has benefitted from the unpaid work of mods for 15+ years.

Mods have generally been either neutral or positive towards reddit as an entity in the past, now... I suspect a lot are asking themselves if continuing to be a mod is worth the effort, at least on reddit itself, I can imagine a lot of them are looking for alternatives or just thinking about giving up altogether.
> they should have bought Imgur instead

In that case, wouldn't they still be paying for the hosting?
> may be due to the vaccination

Emphasis on may, or might. Your experience is certainly valid, and I'm sorry you have to go through this, but it's still a sample of one with no theory of causation. If a certain percentage of people are vaccinated, and a certain percentage of people develop heart problems regardless of vaccination, a few of those people will develop those problems immediately after vaccination. Such things can be just statistical accidents. If I developed heart problems at 58, after years of poor diet and other bad habits, I don't think I'd ascribe it to one discrete recent event unless I was predisposed to believe that the two were related. Therefore, I think it's worth asking: did (or do) you have any such predisposition?
Back when I hunted willy mammoths, "DevOps" meant that there was no "dev" and "ops"; developers did ops, to avoid the friction of throwing code over the wall. Essentially it meant more "vertical" "full stack" teams, instead of horizontal layers. You knew how to write and run your system, and probably has a narrower scope of product than someone who was dev for more features or who was ops for more apps.
Does this comply with GDPR?
Wait you guys get reply notifications?
Actually, it was a role before it was a culture.
See: "COO", "SalesOps", "PeopleOps", etc.
Well they just had to build out this completely ridiculous chat room feature and the sorta nice looking but slow redesign.
Maybe some database restoring gone wrong?
Where does the idea come from that not allowing users to delete content is against the law/GPDR?

You have the right to ask for deletion of personal information they store, and even that has certain limits. You don't have the right to force the company to delete content unless they granted you that right via the licence somehow.

Whether this is a good or bad idea for a company to do is a different question. But I don't see a legal issue here like the linked post claims.
There has been a constant stream of negative top HN posts about Reddit for a few weeks now, even if they often get manually pushed down from the front page. Was there ever a comparable shitstorm on HN against a big corp? Will this go down as the fastest suicide of a social media company?
Of course not!
The problem is that the card reader will be by far the most expensive part of the charger, plus the service fees for using the payment network.

I agree that having 5 apps and needing a phone is bad, but the cost of the card reader will be passed onto you and less chargers will be available.

An NFC-based solution which worked with a single card or a phone would have been better.
No it isn't, obviously.
…to automate everything. I wrote it out fully the first time, and didn’t think I’d have to write it out the second, but hey, there’s always one person. If you don’t think devops is about automation… honestly I actually don’t care have a great day.
Naomi Klein: AI machines aren’t ‘hallucinating’. But their makers are
I haven't had need to use it, but an improvement on the "I have an index to an object which has been replaced" has been to add a generation to the collection & index, a la the generational_arena crate. If the generation attached to your index doesn't match the generation in the collection at that index, your index is stale.
GPT-4 Beats Humans in Pitch Effectiveness
This is definitely unwise.

I run forums and have done for +20y.

Reddit may have a user agreement that allows them to use the data forever, but historical versions that were not visible (effectively soft-deleted on edit) puts this into a risk area as it removes the ability for someone to control the data thus transferring ownership far more explicitly to Reddit.

Reddit should be very cautious here... you only get a lot of protections (EU eCommerce Act, etc) but being mere conduit. Arguably volunteer moderators took on a lot of the liability by their act of moderating, and Reddit were able to distance themselves from a lot of the content on the platform.

But once Reddit go intervening in the content, choosing to make some old revisions public, they're now taking editorial decisions that strip them of a lot of the things that protect them.

This is an incredibly naive move in the big picture.
If you voluntarily give money to a buisness, and this should be the buisness modell, wouldn't that buisness be better a non profit in the first place?
Has anyone tried using the reddit data dump to just stand up a copy of an old subreddit?

Apparently the whole site is 2TB, so you can probably fit all your subreddits on a tiny cloud instance somewhere.