skysight-inc/HackerNews huggingface dataset:
entirely depends on what those 4-5 oncalls are per week.

4-5 Pagerduty Pages is either 1) bad software or 2) mistuned alerts.

4-5 Cross team requests + customer service escalations, <= 1 Page per week is not that bad, and likely can be handled by 1 week rotations with cooperative team to cover 3-4 2hr "breaks" where the person can (workout, be with their kids/spouse, Forest Bathe) would be a decent target.

For me the best experience across >15 yrs experience was at a company that did 2 week sprints. For 1 week you'd be primary, 1 week you'd be secondary, and then for 4 weeks you'd be off rotation. The primary spent 100% of their time being the interrupt handler fixing bugs, cross team requests, customer escalations, and pages, if they ran out of work they focused on tuning alerts or improving stability even further. So you lose 1 member of your team permanently to KTLO. IMO you gain more than you lose by letting the other 5-7ish engineers be fully focused on feature work.

> Often, the on-call engineers are pulled into working on production features or long-term fixes from previous issues, leaving little bandwidth for proactive system improvements.

Have a backbone, tell someone above you "no".
Well, tbf, he’s one of the only ones left. There’s so much ethical/political/cultural attrition at these companies that even the company founded by attrition (Anthropic) looks like Theseus’ ghost ship these days. And Altman is, somehow, seen as an indispensable mascot for the general public and/or politicians worldwide.

After all, what are the engineers gonna do? Quit? They’d be replaced in a month, I’m sure every open position OAI posts gets thousands of qualified applicants from people dreaming of FIRE and/or terrified of automation. And obviously they’re way too proud to consider unionization.
> on the day or day after the murder.

They found this a 8-10 months later, not the next day. So much misinformation, I believe on purpose. And her GF snitched before, not to mention she wanted the reward.
The problem with remote work is lack of accountability. Every worker bee buzzes that "just let me finish my work and be on my way", but that's just not how business works. Employers require either bossware to watch employees at home or they will watch them physically in the workplace. Take your pick.
To paraphrase a notable example: We will have full self driving capability next year..
I don’t have a printer either, but 80% of the time if I need something printed it’s a form containing sensitive info like SSNs. I mostly rely on a trusted friend. I occasionally will use a business like Staples. I would not trust a random stranger.
this provocative parent-post may or may not be accurate, but what is missing IMHO is any characterization of the question asked or other context of use.. lacking that basic part to the inquiry, this statement alone is clearly amateurish, zealous and as said, provocative. Fighting in words is too easy! like falling off a log, as they say.. in politics it is almost unavoidable. Please, not start fires.

All that said yes, there are legitimate questions and there is social context. This forum is worth better questions.
Ah, Republicans are the responsible party here. Right to life my ass.
Valve's Mike Blumenkrantz Hoping to Accelerate Wayland Protocol Development
That sounds like what `git add -p` is for, stage part of the current changes.
“The” prosecutor was not pushing against the execution. “A” prosecutor was, who did not have significantly greater relationship to the case than thousands of other prosecutors in this country. I don’t see how this guy’s opinion is more relevant that anyone else’s.
Can't you just do it on the phone? I don't actually know I am asking it's not a leading question. I would assume that there is a legacy export of some sort.
My understanding is that the opposite is closer to the truth: most cases are made on circumstantial evidence. Jury instructions apparently tell jurors not to weight it any differently than direct evidence.
I mostly agree with you but take the opposite position: attacking memory safety bugs has been so successful that we should use the same pattern on other large classes of bugs.

It's absolutely possible to write a reasonably usable language that makes injection/escaping/pollution/datatype confusion errors nearly impossible, but it would involve language support and rewriting most libraries--just like memory safety did. Unfortunately we are moving in the opposite direction (I'm still angry about javascript backticks, a feature seemingly designed solely to allow the porting of php-style sql injection errors)
there are community center pools deeper than that, so no.
Enigmatic mummy from western China was swathed in cheese
I still have no idea what the "open" in OpenAI stands for, but at least we now know that it rhymes with the "non" in "nonprofit".
Alert fatigue. Alert fatigue. Alert fatigue. It's the single biggest quality of life thing that you can do to help with the annoyance that is on call. If you know you're in store for the same alert again and again, or perhaps even know that you know you're going to get paged, it's hard to think about anything else. It becomes then a game of normalizing deviance and burnout: "oh, we just ignored that one last time". Ok, why are they alerts then if they can be ignored? It's just going to murder people's spirit after a while.

Someone gets called in the middle of the night? Let them take the morning to recover, no questions asked, better yet, the entire day if it was a particularly hairy issue. This is the time where your mettle as a manager is really tested against your higher-ups. If your people are putting in unscheduled time, you better be ready to cough up something in return.

Figure out what's commonly coming up and root cause those issues so they can finally be put to bed (and your on-call can go back to bed, hah).

Everyone that touches a system gets put on call for that same system. That creates an incentive to make it resilient so they don't have to be roused and so there's less us-vs-them and throwing issues over the wall.

Beyond that, if someone is on call, that's all they should be doing. No deep feature work, they really should be focusing on alerts, what's causing them, how to minimize, triaging and then retro-ing so they're always being pared down.

Lean on your alerting system to tell you the big things: when, why, how often, all that. The idea is you should understand exactly what is happening and why, you can't do much to fix anything if you don't know the why.

Look at your documentation. Can someone that is perhaps less than familiar with a given system easily start to debug things, or do they need to learn the entire thing before they can start fixing? Make sure your documentation is up to date, write runbooks for common issues (better yet, do some sort of automation work to fix those, computers are good at logic like that!), give enough context that being bleary eyed at 3:30am isn't that much of a hindrance. Minimize the chances of having to call in a system's expert to help debug. Everyone should be contributing there (see my fourth line above).

Make sure you are keeping an eye on workload too. You may need to think about increasing the number of people on your team if actual feature work isn't getting done because you're busy fighting fires.
The rapid transit system in Minneapolis, MN is called the Metro. Technically that includes the bus rapid transit system, but I'm just talking about the light rail since I do prefer it over the buses.

All I can say is I've never seen any issues on the LRT. I'm genuinely sorry you have.
A couple of things I'd suggest:

* Clearly delineate what is on-call work and how many people pay attention to it, and protect the rest of the team from such work. Otherwise, it's too easy for the team at large to fall prey to the on-call toil. That time goes unaccounted and everybody ends up being distracted by recurrent issues, increases siloing, and builds up stress. I wrote about this at large here: https://jmmv.dev/2023/08/costs-exposed-on-call-ticket-handli...

* Set up a fair on-call schedule that minimizes the chances of people having to perform swaps later on while ensuring that everybody is on-call roughly the same amount of time. Having to ask for swaps is stressful, particularly for new / junior folks. E.g. PagerDuty will let you create a round-robin rotation but lacks these "smarter" abilities. I wrote about how this could work here: https://jmmv.dev/2022/01/oncall-scheduling.html
Tortious interference requires that the interfering party induce the party to the contract to a breach of the contract. Where's that element?
> You have a bunch of sub-par programmers, who don't use the old, well documented, stable, memory-safe functions and techniques. They write code with memory safety bugs.

We should really stop putting the blame on developers. The issue is not that developers are sub-par, but that they are provided with tools making it virtually impossible to write secure software. Everyone writes memory safety bugs when using memory-unsafe languages.

And one helpful insight here is that the security posture of a software application is substantially an emergent property of the developer ecosystem that produced it, and that includes having secure-by-design APIs and languages. https://queue.acm.org/detail.cfm?id=3648601 goes into more details on this.
"popping off" means what?
The standup isn't to report what you did, but to raise any issues or concerns and synchronize with the rest of the team.

The 'what did you do' part by default is 'work on the stories, as planned', and should probably just be left out altogether.
I think this is more an appeasement of the C++ committee because they don't like the order of evaluation to be ambiguous when constructors with side effects come into play. Witness how they completely gimped the primary utility of designated initializers with the requirement to have the fields in order.
[dupe] [dead] https://news.ycombinator.com/item?id=41653932 spam
Well, good thing the probe is doing none of that!

The mission is:
> 50 ice-skimming flybys, remotely probing the ocean in hopes of finding a chemistry that could support life.
Stores like Walmart don't provide the same level of service that department stores did. The staff at department stores were generally expected to more or less present as professionals and act as salespeople. The staff at Walmart more or less present as bored and spend most of their time stocking shelves. The staff at department stores were expected to have some level of expertise in their department. The staff at Walmart often seem to only have a vague idea of what products they sell.
You made at least two claims: " it prevented lying activists from freeing an obviously guilty"

(1) activists are lying

(2) obviously guilty

If you cannot rebut the points made, the second claim is not supported. The article lists points that exactly put into question the guilty verdict in this case

If you cannot point out the specific lies, your first claim is then also unsupported.

You seem to have started in a rebuttal when stating: "and do not suffer from elementary logic errors." Perhaps you can demonstrate those logic errors? (Preferably with full quotes from the article)

I am certainly very specifically interested in the lies you believe to have been conveyed.
Indeed Anthropic is just as good, if not better in my sample size of one. Which is great because OpenAI as an org gives shady vibes - maybe it's just Altman, but he is running the show.
Then you should have just left the premises to go for that hike or a walk in some park at least. There was no moral or practical reason or, as you mention, legal reason not to. The virus wasn't/isn't a demon that hangs around in the open air for days. If you avoided others in open spaces, you'd have put no one at risk. What you describe sounds like some strange obedience fetishism.
Here's the deal: if anyone cold-calls you and asks you if you want to sell your house, your car, your timeshare, or make an investment, or anything else, or proposes some kind of deal that involves you paying for anything or sending any money up-front to cover "administrative fees," there is a very good chance it's a scam. Especially if they are not a local broker or person. Verify, verify, verify. And if it seems to good to be true, it is. Ask a friend, or a local legal aid organization for a reality check.
MAI-CR 402.03

Proof beyond a reasonable doubt is proof that leaves you firmly convinced of the defendant's guilt. The law does not require proof that overcomes every possible doubt. If, after your consideration of all the evidence, you are firmly convinced that (a) (the) defendant is guilty of the offense charged, you will find him guilty. If you are not so convinced, you must give him the benefit of the doubt and find him not guilty.
Promises of 'passive income' on Amazon led to death threats for online review
asaro had more reasons to make these claims

https://www.cnn.com/2024/08/21/us/marcellus-williams-missour...

>And though Picus’ laptop was recovered, the prosecuting attorney’s office says Roberts told investigators Williams said he’d gotten it from Asaro – a claim Roberts reiterated in an affidavit signed in 2020. Jurors at trial never heard this assertion, which the prosecutor’s motion says illustrates “the person with the most direct connection to the crime” was “Laura Asaro, and not Marcellus Williams.”

additionally, they only made the statements after being threatened by police

>The woman at first denied having information about the crime, prosecutors’ motion states. But after meeting with police several times – and being promised charges she was facing would be dropped and told she would be eligible for the reward – Asaro eventually cooperated, telling police she had indeed seen Williams on the afternoon of the murder, the motion states.
The slowness would be inevitable because the architecture combines the weak point of Redis (network stack) with the weak point of sqlite (disk access).

It abandons Redis' in-memory data and sqlite's in-process speed... for what?
and here we are arguing for internet points.
RapidForge: Create Web Apps and Automate Tasks with Bash
> Google has a deal for Reddit’s data, so its models will have that information. I can see this kind of thing being a moat as well.

I don't see this as a silver bullet but let's assume this is true and a differentiator. This kind of validates that building a robust model hits a data saturation wall at some point and the moat dries up.
Actually the instructions tell the jury that how much weight to give to any evidence is up to them.
Is anyone willing to share general guidance on where to draw the line when it comes to using DB configuration to speed things up ( almost "buy") vs. basically doing things manually ("build")? In my limited experience it often falls to app developers because competent DB admins are all getting paid much more to work elsewhere (as mentioned above, it is important to know the DB).

My canonical example is large volumes of data that accrue over time with the most recent accessed most often, where the DB admins can partition things or do partial indexes to keep access fast, but the app developers can move records into a separate archive table sometimes behind the scenes while still supporting things like (eventual) search of the whole data set. (A note here that it feels like a tool could do a lot of the initial heavy lifting to automate splitting one table into many when it makes sense -- perhaps when limited by a cloud DB's missing features)

Another management option sometimes accommodated by the DB vs. doing manually is to store all large blobs/files in their own separate database (filesystem?!) for a different storage configuration etc.

I imagine it can go as far as basically implementing an index manually: one massive table with just an auto-incrementing primary key but tons of columns then setting up a table with that ID and a few searchable columns (including up to going full text search/vectors I guess).

Edit: one useful tip manually implementing the Materialized View pattern with MSSQL 2016+: use partition switching as well explained and implemented by https://github.com/cajuncoding/SqlBulkHelpers?tab=readme-ov-... (incidentally the most commercially useful out-SEO'd tiny-star-count library I've ever found, focused on bulk inserts into MSSQL using .NET). I think this is a good example of drawing the buy/build line in the right place with the automation of the partition switching.
lol, no. For one Capstone has a lot of bugs (it uses some old version of LLVM as its base) but the whole question of how to decode things is complicated because there are a lot of pitfalls and inconsistencies that different disassemblers handle differently. And what the hardware does is a different question entirely: it may not match the spec, or even other processors with the same ISA.
Having built similar tech (Meta, YC S13), it's been a great year with Vision Pro, Orion, Spectacles and more coming out.

Currently at my co, seeing most day to day use out of XReal, and keen for Visor.

AR/XR/MR/VR app I'm most looking forward to is a 360 location share with the sharing user in AR, and the receiving user in VR, with additional virtual objects shared between. Orion would be great for the send side, with a few extra cameras and Vision Pro on the receive side.

The main thing letting down tech today is how open the platforms are for external developers.

The lack of projecting black I don't see as an issue, clip on something for VR (ok 70 degress isn't quite enough but getting fairly close), or just dim and use gradients for day to day work.

I think we're still at the most basic level in terms of understanding optical physics and ultra high resolution much smaller devices will come out, probably not too soon though.
It is important to understand the difference between moral laws, which are immutable, and other laws in the Bible, often categorized as civil or ceremonial.

In modern legal theory, we have a similar distinction, which you may know from Legally Blonde: malum in se (that which is inherently wrong) and malum prohibitum (that which is wrong because a lawful authority prohibits it). Example: endangering the safety of others by driving too fast is wrong in itself, while breaking the speed limit is wrong because the town said so.

The former type (moral, and in se) doesn't depend on the existence of a government or system of laws and justice. The latter type certainly does, and the wrongness of those things 1) is changeable at the will of the governing authority, 2) applies only to those properly under the authority, and 3) expires when the governing structure expires.

Christians believe the ten commandments are moral law, whereas when we get into the ins and outs of the ancient Israel system of justice, described at length in Leviticus, eg, we are seeing one civilization's implementation of that moral law into civil law, coupled with religious law and ceremonies that symbolized and pointed to deeper realities.

When Jesus says he does not abolish but fulfills the law (and he means all of the law, not just some laws), he can't mean you are now free to murder. He means if you murdered someone, you may yet receive eternal life and not eternal death, because he can pay the penalty on your behalf. He means he lived a perfectly moral life and can impute that to you. That's fulfillment of moral law.

It also doesn't mean eating pork was immoral and now it's moral. That dietary restriction was a malum prohibitum component of the ceremonial cleanness symbolism that was meant to point the Israelites to the reality of what happens to a soul that consumes unholy things. It was never immoral, only prohibited. But the law is fulfilled in that the symbol is no longer required. Jesus institutes a new symbol that fixates on his own holiness and cleanness imputed to us as if by eating it (the Lord's Supper). The early Christian movement quickly incorporated non-Jews who had no heritage of living under the authority of the Israelite state, which was, by this time, already expired/expiring, many times over through successive conquests and occupations by various other governments. Neither the non-Jewish Christians nor the Jewish Christians needed to abide by those laws, though many did for a time, as it was an integral part of cultural and religious custom.
As I understand it, that was one of the advantages of department stores. When you went to the jewelry section, for example, to buy your spouse an anniversary gift, the person working there was often the same person who recommended the jewelry you bought last anniversary.
Impressed by the confidence of 'to AGI and beyond'.
> ... I oversee a team handling a moderate volume of on-call issues (typically 4-5 per week). In addition to managing production incidents, our on-call responsibilities extend to monitoring application and infrastructure alerts.

Being on-call and also responsible for asynchronous alert response is its own, distinct, job. Especially when considering:

> Often, the on-call engineers are pulled into working on production features or long-term fixes from previous issues, leaving little bandwidth for proactive system improvements.

The framework you seek could be:

- hire and train enough support personnel to perform requisite monitoring

- take your development engineers out of the on-call rotation

- treat operations concerns the same as production features, prioritizing accordingly

The last point is key. Any system change, be it functional enhancements, operations related, or otherwise, can be approached with the same vigor and professionalism .

It is just a matter of commitment.
That's basically what Capstone is? Except not vendoring its own LLVM.
See https://docs.racket-lang.org/inside/cs-procs.html
I don’t have time to reproduce them. Fortunately, it’s easy for them to show how open and fair they are by publishing all training data. They could also publish the unaligned version or allow 3rd-party alignment.

Instead, they’re keeping it secret. That’s to conceal wrongdoing. Copyright infringement more than politics but still.
If I were to guess -- At the lowest level, that's what the hardware does. I wouldn't be surprised if they have a library to wrap that with something more friendly, but something has to translate that into writes to memory-mapped addresses, and whatever that is was configured with the wrong addresses...
My claims are supported by the arguments made by the prosecution in all instances of the appellate court, the arguments that jury and the appellate courts found convincing. Even the dissenting SCOTUS justices would not argue that the guy actually is innocent.

Again, can you explain to me what’s the value of me reiterating the same stuff that’s in the court documents? Do you think that activists should just be able to gish-gallop everyone by forcing them to repeatedly argue the exact same points?
Being blocked by like "pmarca" forever is kind of silly.
> Amazon has proved that people will pay subscription fees AND get served ads.

Also the NYTimes.
That's not the problem with this. When you inhale from a scuba regulator, you're breathing in air at ambient pressure, which means an extra one atmosphere of pressure at 30 feet depth. As surrounding pressure drops, that air will expand proportionally. If you take a deep breath and then ascend, the air can overinflate your lungs and cause serious damage. SCUBA divers are trained to exhale while ascending to avoid this, but freedivers tend to hold their breath.
ollama is "just" llama.cpp underneath, I recommend switching to LM Studio or Jan, they don't have this issue of proprietary wrapper that obfuscates, you can just use any ol GGUF
The Catholic Church at least is pretty strongly against it.