skysight-inc/HackerNews huggingface dataset:
It's not bullshit but a lot of companies are definitely overthinking, over engineering, and overspending here. I've seen the transition from before the .com bubble to where we are now. Things changed and improved quite a lot. But the ambition level also went up. Puppet, ansible, teraform, cloudformation, ansible, salt, packer, etc. you name it and I've been there and done that at some point. But without ever having taken devops on as a full time responsibility. I'm a developer that can do ops when I need to.

If you know what you are doing you can actually minimize your cost and complexity a lot and get away with not having to actually do a lot. I am a startup CTO these days. That means I'm not bored. Devops is not a person, it's me in what little time I can budget for this among many other more interesting, lucrative or tedious things that I also need to take care off. I need my servers to run and not die on me. I need decent uptime and build automation. I need backups, alerts, and all the rest. I've seen it done well and I've seen it done poorly. I don't like it when it's done poorly and I know what that looks like.

If I had the budget, I'd probably get a person to delegate to and invest more in this. But I don't. So, I go for minimalism and reduced complexity.

So, good bullshit free devops is what I do. No mico-services in my company. We have a monolith. That's not likely to change any time soon. We can't afford the operational complexity and I frankly don't see the added value of having to have that complexity. I don't use kubernetes for the same reason. Using kubernetes to run 1 docker container is nonsense. We run nice simple docker containers. Most common cloud providers have easy ways to scale and run those. I used google cloud run for a while (cheap and easy), but our use of websockets and threads made using traditional vms and a loadbalancer a bit more flexible. That's what we've had for the last two years.

I don't need a teraform script to create that for me and I just clicked that together in a few minutes. My infrastructure is fine. I do use build automation. We have a few lines of gcloud commands in there that tells the instance group to apply a new template with our latest docker container. It runs when we merge to our production branch. We use Github actions for this. Our master branch goes to a similar staging environment on every pull request merge. That's simple devops.

We also have a few managed services, alerts, monitoring, logging (via elastic cloud), and few other bits and bobs. I'm not a caveman. But you get the idea, this is not something that we need to spend a lot of time on. Set it up right and you can do more fun things. Our uptime is fine. I can scale this endlessly.

I can also setup a new environment without too much hassle. If that actually becomes a regular thing, I'll automate it further. But that just isn't a thing right now and not worth a minute of anyone's attention in this company. Automating things you only do once every few years is a waste of resources.
As someone who transitioned from a DevOps role to a Security Engineer role, the thought of going back gives me anxiety. Having my "log light" turn red at 2am? No thanks. It's not like it woke me up or anything, I'm always awake at 2am, I just don't want to deal with servers at 2am. I'd rather get a good night of sleep and go in the next day and destroy all of the hard work that the DevOps team spent so much time working on. That's a much better fit for me. I wouldn't take a DevOps job even if it paid $50k more than what I'm making now. I just wouldn't enjoy the work. That isn't to say that I'm unwilling to help the DevOps team (I help them all the time by hacking their shit), but I wouldn't actually want to be them again.
It seems to be a state that can send stale data to loads, but will get invalidated if the CPU performs a barrier.

It doesn't work of course, obviously because there is no forward progress. CPU1 can order all previous stores, then later store some flag or lock variable, and that will never propagate to CPU2 spinning on that waiting for the value.

But also because CPU2 and CPU3 can see different values depending on the state of their caches. If one had no such line and the other had a valid-stale line, then they will end up seeing different values. And the writeback out of CPU1's cache needs to write back and invalidate all possible older such written-to lines. By the time you make it work, it's not a cache it's a store queue but worse because it has to do all these coherency operations and barriers have to walk it and flash or flush it, etc.
"DevOps" was never originally a team or job role, it was just a workplace culture philosophy that dev and ops should work closely together rather than in isolated, and often mutually hostile silos as was common in the 90s.

It just became a buzzword that everyone had to have, then C-level leadership needed "invest in DevOps", "grow the DevOps team" (because buying is easier than fixing the culture) until we lost sight of the original point and DevOps just became... ops.
Sounds like a good problem to have?
I've read several comments here on HN from so called "insiders" over the last few months that old.reddit.com is going to go away this year. They already shutdown i.reddit.com for mobile users so I tend to believe that old.reddit is next.
because it’s incredibly difficult to build, not to speak of maintaining it. I have seen things close to this, but can’t quite get to the finish line. I’m sure some people are doing it, I guess, but I have yet to see it. a lot of times a team will architect a good, automated solution that works for 3 years untouched and then fails catastrophically because it wasn’t maintained or assumptions start to fail.

this dream of self service devs is becoming a myth. devs do so much incredibly thoughtless stuff to infrastructure all the time. you need an infrastructure person in the process to make it resilient and allow them flexibility to do the stupid shit they want to do - with guardrails.
I agree. Judging from r/all, they seem to be chasing tictok. It's an almost entirely auto-play short videos, mostly reposts from tictok.
Wait, isn't one of the benefits of such federation that (the equivalent of) subreddits _don't_ live on one specific instance? So if an instance goes down for whatever reason, that subreddit still maintains its existence since it's shared across other instances.
Webmaster: 1997
> So even in factories, either you listen to the lowest level employees

If you listen to programmers, the app has technical debt, and needs to be rewritten on [next tech stack needed on the developer’s resume]. I’ve hear that on a 6-month-old app written in SpringBoot/React in 2020.

Leader-blaming is a nice sport, but actually working together with full responsibility on both sides is a much rarer skill. Including being fired with damages if you summon KubernPyKafka in Scala and your team doesn’t produce features during 6 months.
> You're lucky if you can use Terraform, but that's not the default.

Oh god I thought that was unlucky. I have huge respect for Terraform for popularising what they call “infra as code” (we used to just do this with the actual AWS API) but now there’s multiple modern IaCs that use actual code with real tooling.
Someone pointed out that 90% of that 2000 is probably ad sales teams. Their actual software and UI people are likely appropriately sized.
I surely could have done that. The reason I didn't is that I live in a place where some people leave old cars out in their yards for years, and so I had no assurances that whoever picked the generator up would do something reasonable with it.
Isn't Gauntlet considered an ARPG?

https://en.wikipedia.org/wiki/Gauntlet_(1985_video_game)

I always chose the sexy role, myself ..
I'm pretty sure just giving app developers more time to prepare for price increases would've been enough. If they'd given Apollo and RIF 6 months notice of the new pricing instead of 30 days, the devs would probably have adapted to a paid model and moved on. There would still have been plenty of grumbling, but not nearly as much outrage.
> shadowbans are sneaky and malicious, in my opinion, and there is no scenario where they are not; if you have a problem with someone, you say it to their face. If you kick someone out, you call the bouncer or you do it yourself, you don't send a robot to waste potentially years of their mental energy. That's being a shit human.

Yeah, shadowbans suck.

On the other hand, some people will just keep creating new accounts over and over every time they are told that their account has been banned.

It’s a difficult situation.
With random bucketing happening at the global level for any test, the proper thing to do is to take any segments that show interesting (and hopefully statistically significant) results that differ from the global results and test those segments individually so the random bucketing happens at that segment level.

There are two issues at play here -- one is that the sample sizes for the segments may not be high enough, the other is that the more segments you look at , the greater the probability for finding a false positive.
No my assumption isn’t that consultants make good estimates. It is that nobody in our entire industry knows how to accurately estimate how long a software project will take, so I would be a highly sought-after rare commodity in our industry.
I'm not sure, but I haven't seen places where devops team hire people without exp. I myself tried to get some interviews (I do have some dev exp, albeit data engineering ones, not backend) to no avail. To this point I believe most companies don't hire green for the devops team.
My point was simply that at some point the buck stops and someone has to write the code to mutate a memory cell.

Regarding your point, shared xor mutable is nice, but databases are an example of a shared mutable (and even concurrent!) yet safe resource, so other models are possible.
> The problem is that many people have come to think of reddit as a public utility

That's a good summary of the problem, and I would extend that to say that public utilities should be in control of the public, which means federated services.

My hope at this point is that Reddit massively doubles down (and that Twitter goes back to trying to eat itself) so the migration to Lemmy and Mastodon continues. Neither has quite crossed the chasm out of the early adopter/tech sector users. It looked like Mastodon got close at one point and then Twitter ran out of completely idiotic ideas.
> Google Domains might have been a shortlist for tech-savvy people

In the 2000s, yes, but Google has worked hard to shed that reputation - starting with Reader and especially after mismanaging Google Apps for Domains. Even the total Android fanboys I know tend to recommend not using Google services, which is impressive for how much goodwill they torched.

I think a large part of it is that even their fans never thought they were ever good for support. As you mentioned, a really nice reason to let Squarespace et al. is that you have one place responsible for everything without finger-pointing.
Payroll taxes are dedicated to pay for Medicare and Social Security programs. The amount you get in old age is directly proportional to how much you paid in (with a formula that favors lower earners via “bend points”), so its disingenuous to just lump it all in with regular federal income taxes.
> Normally this forum has a lot of nuanced thought but on this one I'm seeing a lot of VC groupthink happening.

This usually translates into: "I thought HN was great as long as I agreed with the general sentiment, but now that we disagree the VC groupthink is too much for me".

If you thought HN normally does a lot of nuanced thought then maybe that's still the case today and it's you that lost the nuance.
>>How do you reckon time vs money vs knowledge?

Don't forget the value of the satisfaction from having fixed something yourself and how good fixing stuff helps with recovering after spending hours in front of a computer
> what could you have done with your time instead?

Improve my HN karma.

;-)
Well spotted. This comment should be upvoted - the article needs to be read through this lens.
Presumably having to carry two phones?
It's called a 'thought terminating cliche'.

The most far-reaching and complex of human problems are compressed into brief, highly reductive, definitive-sounding phrases, easily memorized, and easily expressed. They become the start and finish of any ideological analysis.

* https://en.wikipedia.org/wiki/Thought-terminating_clich%C3%A...
My mom can use an iphone easily, mac not so much but that's because of her history with windows. I think her mac almost certainly has malware. it's an older one and it probably doesn't support the latest OS anyway sadly.
Intel's biggest processor rebranding in 15 years ahead of Meteor Lake launch
I never really saw the "factory" analogy of software development: it just makes no sense, unless you look at your CD pipeline and think that's your whole process and where most of the work happens.

The very definition of a factory is that it manufactures the same thing, or a limited range, of items over and over and over again.

That's not software development: you're either doing something new, or working on an existing codebase but, of course, because each part of that codebase is quite different to the others, there's no real uniformity to what you're building. Sure, there are processes that are similar (writing tests, debugging), etc., but it's much more like the design and testing phase of engineering a product rather than the manufacturing phase.

Overall, "factory" is an incredibly vapid analogy that simply needs to die in our industry.
Business rules written into the ICANN contracts. And said rules are enforced in "technological" code as well.
Deep-Stack Engineers?

(Full Stack, a misnomer, is already taken)
For most things, me too. I have no qualms about running a keygen for example. It doesn't get updated, doesn't reach out to the internet, and has a tiny set of functionality.

But a browser is none of these. If one of the devs gets their machine hacked, a trojanized build can reach you in mere seconds if you are unlucky enough to start your browser shortly after the build pipeline gets infected.
From the document:

> The world of Diablo will have a dark, evil tone. Initial levels will be set in an abandoned Gothic church. A marble mausoleum and progressively darker, dingier crypts and catacombs follow.

As someone who has been down in the crypt of an abandoned Victorian Gothic church, I can confirm that they definitely do not look like the level in Diablo does!
Considering how easily you can run Windows games on Linux, it makes the platform even more open.
I’m not sure that’s disagreement: people expect support for this so Google knows that they either have to staff up or get out of the business, and they picked that option.
> If you click on the username you will see that this person tried the same post 7 month ago

I bang this particular drum quite loudly, for sure. However if you'd indulge me as to _why_ I hope I'd be able to change your mind.

To start with, I'd like to state that while I'm not a fan of useless things, I can definitely make peace with non-perfect terms, systems and things that serve no purpose.

However, when it comes to things that actually cause harm: I can't abide that.

Why would "DevOps" as a term cause harm?; you might ask.

It's harmful because it is:

A) Rewriting history

B) Has no universally agreed upon definition

C) Is a term that's proginator can't even define in his own terms

D) Has no chance of ever having a universally agreed upon definition.

The deal is thus: if you have a devops team, some people will say you have failed devops.

If you have a devops engineer; some people will say you failed devops.

If you "practice devops" and you have no people focused on operations: I would say you've failed devops.

So what do we call the people who actually ensure operational excellence and best practice? Aha. DevOps.

I'm not trying to sell you anything, I just think this treadmill needs to stop.

I know it's unfashionable but hiring sysadmins into your project team and having them tied to your Agile methodologies is fine, sysadmins need to code though, as they always did. Heck, even Pat Dubois (originator of the term DevOps) originally envisioned the role as "Agile Systems Administrator".

You might think me pedantic or that I'm being needlessly overwrought on this topic; but precision in language is a very real engineering problem.

We must be precise with our terms, and if we can't even get our methodologies or job titles to align as an industry, can we really be trusted to get any other terminology right.

If you think I'm kidding about precision in language being an engineering problem I invite you to read: https://fileadmin.cs.lth.se/cs/Education/ETS170/IREB_CPRE_Gl...
My favourite phrase for a “new normal” moment is the borrowed Simpsons joke:

A: “This is the hottest summer ever!”

B: “This is the coldest summer of the rest of your life!”
But if you don't have a dedicated ops team, some people get pigeon-holed for the role in the team. Not necessarily the best thing for them, because now they face pressures from both sides.

I'd recommend the lead takes the role.
This happened because people accepted the linguistic uncertainty, pushed by vendors who wanted to sell stuff.

The well may be poisoned, but the original meaning is still perfectly well alive.
This is part of futile attempt by management of creating spherical worker in a vacuum so there is as little specialisation as possible.
The big reason why parallel memory buses aren’t wider is pin count. If you have all the memory interfaces over the substrate, the bus can be as wide as the substrate can accommodate.

BTW, what is the usual width of memory buses in discrete GPUs?
Supposedly Spez was made a mod of that subreddit by a troll who exploited a bug/feature that allowed you to make anyone a mod of your subreddit. However reddit did host that community for years (Spez claimed the creep mods were helpful in flagging cp throughout the site), and it's ironic you mention "problematic" communities migrating to 4chan in the same context, since 4chan takes a much harsher stance on the sexualization of minors than reddit. KiwiFarms even more so.

> You really don't want reddit users here

No one wants reddit users.
When you run out of ideas in your B2C business the answer is always pigeonhole some B2B model on top of it whether it fits or not.

Reddit is an ad business. Increasingly a mobile ad business. 3rd party apps do not fit that business model and never has. Everyone is blowing it out of proportion because Spez didn't want to be honest about it.

AI/LLM is just a sweetner on top but probably not a billion dollar API business.

What Reddit should be doing is making a better mobile app (and web app at that). Design and software dev in general has not their strong suit and hasn't been for the last decade.
No, that's a question for a dev.

If the CEO can tell you about how engineering changed the product, but the dev can't, then your experience is going to match the dev's. And the part of "engineering" that changed the product was almost certainly not a dev.

Besides, it is common for CEOs to think that they are more responsive than they really are. And they are generally better at marketing than truth. So for both reasons, I would not trust their answer unless it is backed up by the rank and file.
I would say that this is an extremely narrow view of "memory safety", and totally ignores the broader concept of "lifetime safety". Yes, if the thing you want to prevent is crashes due to segfaults, indexes in Rust prevent that. But I would argue there's no practical difference between "crash due to segfault" and "panic due to index overflow" (which is definitely possible with the Rust model): both are just different ways of looking at "you dereferenced an invalid pointer". It does prevent the pointer writing into different data structures though, which is definitely an advantage of Rust (which comes with the runtime cost of bounds-checking, but that is probably worth it).

But more generally: imagine you're making a game where you shoot a bunch of dudes, so you have a `std::Vec<Dude>` to store them, and elsewhere in the code, you reference this vec using indexes. When you shoot a dude, you want to remove it from this array, but being a programmer concerned about performance, you don't want to literally delete the entry, as that is an O(n) operation. Instead, you mark the dude as "despawned" or whatever, and then when you want to spawn a new dude, you keep a list of despawned dudes and just recreate the new dude in the same place in the array. If other places in the code are holding on to indexes to this array, the index is now invalid, but it will not be detectable: it'll just point to the wrong data, which can wreak all sorts of havoc.

This is almost exactly equivalent to "use-after-free" issues in C. In most cases, `free()` will not literally free the memory, it will mark the memory as unused and stored in a free-list, to be available for the next `malloc()` call. If you're holding on to a pointer that has been free()d, it's not that the program will segfault, it's much more insidious than that: it will point to memory that is apparently valid, but actually garbage.

This is precisely the kind of lifetime issue the Rust borrow checker was designed to solve, but by using indexes like this, you've basically just turned the borrow checker off without realizing it. If the borrow checker is intrusive enough that this becomes a very common pattern in Rust, I personally think it does serve as a pretty good counter-argument to a lot of things people say about Rust. Rust people are very quick to sing the borrow checker's praises and say that "as long as you learn to work with it, it stops becoming a problem!". If it stops becoming a problem only because you sneakily turn it off using tricks like this, maybe it's a bigger problem than people are willing to admit.
I agree with all that.

DevOps is similar to agile. Originally they both described a set of principles, an ethos, not a specific role. DevOps was your development team work closely with ops as one team, using software engineering practices, config as code etc etc.

Then, it just came another name for sysadmin and later platform teams and back to where it all started, passing things over the wall from engineering to platforms.
I've been using Lemmy, and while there are a couple of places to improve (around how interacting with communities on other instances works, and how you end up looking at your own instance's view so you can interact) my only issue is the critical mass. There are some decent communities on gaming for instance, but I can't do the thing I can on Reddit where I know there's going to be a good community on every hobby I have an every game I play and I can just join if I want.
> The solution is to use an A/B test running time calculator to determine if you have the required statistical power to run your experiment and for how long you should run your experiment.

Wouldn't it be better to have an A/B testing system that just counts how many users have been in each assignment group and end when you have the required statistical power?

Time just seems like a stand in for "that should be enough", when in reality you might have a change in how many users get exposed that differs from your expectations.
Goodbye, clean code (2020)
Cloud Domains is being killed along with Google Domains, TLDs are OK for now.
> A decade later someone announces the concept of DevOps, which is an infrastructure engineer that knows how to code.

… except that’s not what the concept was.