skysight-inc/HackerNews huggingface dataset:
The intelligence community is made up of people capable of holding grudges. I'm certain they've not forgotten if such evidence exists. I wouldn't be surprised if in the future someone gets a missile delivered through the rooftop of their vehicle. I don't think the side that has less scientists is going to win. But I'm pretty sure that if not 9/11, then some other terrorist attack would have taken place. The world is too big for perfection. If there was a room full of 100 Jesuses and a gun, I can't be certain someone wouldn't get shot. Perfect world has no existence. If you think there's a world that exists without murder, even unintentional, get out of here. These are not 'new normal', someone always wanted to kill someone somewhere throughout history, it's just that now with technology we can kill must more and much faster. Maybe like, ants or something, are capable of not caring, or a fly thinking to itself 'I really hate that guy trying to swat me'.
OpenWeb announces new CEO, but founding CEO refuses to step down
Comments and docs are lies that I dearly love. I want and need them, but I never forget that they're, at best, helpful lies. The code does exactly what's written, the comments adhere more or less, sometimes.
How do you distinguish these behaviors?
I wish I had had this years ago.

I one time wrote this fairly elaborate SQL generation thing that required pretty liberal use of recursion in order to fulfill all the requirements. It ended up being a lot of mutual recursion and the code was admittedly kind of messy but it was a necessary evil to do everything asked of me.

A more senior engineer ended up taking over the codebase, "fixed" all my code to be this iterative thing, made a point to try and lecture me about why recursion is bad in an email, only for his code to not actually do everything required and him reinventing effectively everything I did with recursion.

In fairness, he did actually apologize to me for some of the comments he made, but if I had thought about putting this comment on the top maybe we could have avoided the whole thing.
Where the Crops Grow
When I use `grep` in a code repository and it turns up pointless results in my `.git` directory, that also violates the "Principle of Least Surprise."

There's a reason why I don't follow the "Principle of Least Surprise" in any rigorous way, because everyone can be surprised by just about anything. I essentially never use that phrase in my writing or thinking because it's so vague and literally anyone can disagree with it about anything.

As I've already acknowledged, the default skipping behavior is a cost. And this is precisely why this behavior is mentioned extremely prominently in all of my materials about ripgrep.

The GitHub description:

> ripgrep recursively searches directories for a regex pattern while respecting your gitignore

The first two sentences of the README:

> ripgrep is a line-oriented search tool that recursively searches the current directory for a regex pattern. By default, ripgrep will respect gitignore rules and automatically skip hidden files/directories and binary files.

The first two sentences of `rg -h` and `rg --help`:

> ripgrep (rg) recursively searches the current directory for lines matching
a regex pattern. By default, ripgrep will respect gitignore rules and
automatically skip hidden files/directories and binary files.

The first two sentences of the description in the man page:

> ripgrep (rg) recursively searches the current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files.

Near the top of every release of ripgrep:

> In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches the current directory for a regex pattern. By default, ripgrep will respect gitignore rules and automatically skip hidden files/directories and binary files.

Like, I've gone out of my way to make is superbly clear what it's doing by default. I can't control how other people write about ripgrep or talk about it, and just because I can't control that doesn't mean I should just give up that default behavior entirely.

I'm not surprised if users miss this. I understand it. This is why I've acknowledged it as a cost. But I think the benefits outweigh the costs. I cannot tell you how many times folks are delightfully surprised (there's that principle again, but in the opposite direction, demonstrating again just how useless of a metric it is) when ripgrep automatically ignores all the junk they don't care about without them needing to think about it at all.

ripgrep is an object lesson in the idea that defaults matter. This doesn't mean it's an unmitigated win from every possible perspective. And this is why ripgrep also makes it extremely easy to disable the automatic filtering: `rg -uuu`.
Enforcement is part of regulation
Mike Pompeo told him it was a bad idea. Why would he do it this time? He'd pretty much have nothing to lose.
24/7/365 and the firstborn son for the 0.5% of stock in the company driven by conservative nutjobs. That's a nice trade offer, sure.
tbh consumer boycotts can be very effective for organizing. not having workers to serve your customers is a lot less scary to a business than potentially losing your customers
Some thoughts

- Planning for 7day weeks results in no slack for actual emergencies, because the baseline is emergency mode

- This is not sustainable from a quality or output perspective, but people trick themselves into believing it is by using the wrong metrics (butts on seat vs outcomes)

- This is not scalable as the company grows and as successive rounds of employees get less and less equity and thus less motivation for outsized success

- This is great when voluntary and self-driven and terrible if mandated.

- Even if done voluntary, nights/weekends work should focus on learning tasks rather than just increasing the volume of work.
A reminder of why it’s good to analyze your project’s binaries. Test data, famously, but also firmware blobs, etc.
Affirmative action at the companies I’ve worked at was hard to hire less qualified individuals into roles. Those folks were often under performing but marked as “meets” at request of hr. Now with economy and other factors, they are being performance managed out given a worse output/impact than peers at same level.
Military GPS modernization way behind schedule, audit finds
Exactly!

The author could have simply written nothing, convinced themselves they were right about staying closed source or...

The author could have just ignored all the feedback they got and stayed closed source or...

In the face of opposition, really dug in an tried to double down and further justify staying closed source or...

Take the time to sort the constructive criticism out from the negative garbage, digest it, and try to grow from it.

They should be commended for being open minded and putting in the effort to grow. And to directly address the GP's comment, in order to grow the conversation has to start somewhere. You learn/grow through experience/engagement, and that's exactly what the author is doing, and in a pleasant, tactful way.
I'm not too deep into CS theory so I'm not sure if this is an answer to your question but... SCC algorithms are useful when building routeable road networks from source data (like OSM) in order to filter out isolated sub-networks (like an airfield). We use dotnet but have something that looks possibly similar to what you wrote(?):

StronglyConnectedVertices(Vertex source) => ReachableVertices(source).Intersect(ReverseReachableVertices(source))

The methods ReachableVertices and ReverseReachableVertices are effectively depth-first searches on the graph.

The challenge - in terms of performance - is actually not finding a single SCC but returning the full set of potentially thousands SCCs in large networks. I originally implemented an iterative (imperative) version of Gabow's "Path-Based" algorithm but it was too slow on continent-sized datasets. We did some experimentation with a parallel variant of Tarjan which didn't improve things much.

Eventually I settled for something "good enough" - randomly pick a vertex, calculate the SCC with the above code, return it if it's large enough (>1k vertices) otherwise filter it out, keep going until I've accounted for >90% of the graph. The remaining <10% gets filtered out. That's basically imperative (using a while loop) but could probably be functionalised.

-----------------------------------------------------

EDIT I've taken a better look at the linked paper and what I wrote is definitely not an answer to your question. But I'll leave it in case anyone's interested.
It would be cool to use this as a voltage sensor, to check for live circuits, but the downside being you might not want to crane your wrist towards said live circuits.
Secret police and the maintenance and extension of power through internal/external covert ops seem to be an inevitable feature of government at any scale.

Rome had the Frumentarii, and there are examples from Persia, China, and Sparta.

These were overt empires run by emperors. What we've had since the end of WWII is a covert empire directed by an informal pseudo-government of oligarchs, hidden under a veneer of democracy.

In the UK the Crown never changed its mind about internal adversaries, as the recent "spycops" inquiry shows.

https://www.spycops.co.uk/
I built two products out of which one is live - Draftly[1]

We tried different LLM models but always returned back to Open AI.

[1] https://draftly.so
Intents: The Endgame for Computing Interfaces?
Since coding with Cursor, I’ve spent a lot of time thinking about how much computing interfaces have changed in such a short period of time.

Just as we saw a paradigm shift from imperative to declarative interfaces, LLMs have opened the door to new kinds of interfaces.

Intent-driven interfaces are already everywhere - from AI assistants processing raw data, to Arazzo for defining how APIs map to human-scale workflows, to agents capable of handling complex tasks.

While the doomer view is “robots will take all our jobs”, my optimistic take is we finally have a human-centric way of interacting with machines and it’s going to supercharge our abilities
Love this! I'd love to take the underlying data combine it with data like average income for a county and see which counties had the most affordable Taco Bell.
Infineon pilots first 300mm power GAN wafer technology
There are a lot of regulations. They were inspected. They failed inspections. Then the inspectors did nothing. All the additional regulations can be added that we want, but if the inspectors don't close the plant, they are meaningless.
We tried many things.

Our final diet for her was based on recommendations from her pediatrician, dietitian, and therapist.

While she might not have starved if we withheld chicken nuggets, she became extremely distressed and disregulated, which lead to other problems.

She has moved on from chicken nuggets, but her eating pattern is still the same. She will have only one food at a time that she will eat for proper meals, and that food will rotate every few months. After a few months of only eating one type of food, she will suddenly declare she does not like it anymore and move on to something else.

Her current food is actually Chicken Tikka Masala from one particular restaurant. Hopefully somewhat healthier than nuggets, although it gets expensive.
It's not a matter of incompetence, it's a matter of being very, very cheap.

Artistic endeavors are a unique blend of "extremely chaotic workflows nobody bothers to remember the moment the work is 'done'", "90% of our output doesn't recoup costs so we don't want to burn cash on data storage", and "that one thing you made 20 years ago is now an indie darling and we want to remaster it". A lot of creatives and publishers were sold on the promise of digital 30-odd years ago. They recorded their masters - their "source code" - onto formats they believed would be still in use today. Then they paid Iron Mountain to store that media.

Iron Mountain is a safe deposit box on steroids, they use underground vaults to store physical media. You store media in Iron Mountain if you want that specific media to remain safe in any circumstance[0], but that's a strategy that doesn't make sense for electronic media. There is no electronic format that is shelf-stable and guaranteed to be economically readable 30 years out.

What you already know works is periodic remigration and verification[1], but that's an active measure that costs money to do. Publishers don't want to pay that cost, it breaks their business model, 90% of what they make will never be profitable. So now they're paying Iron Mountain even more for data recovery on the small fraction of data they care about. The key thing to remember is that they don't know what they need to recover at the time the data is being stored. If they did, publishers wouldn't be spending money on risky projects, they'd have a scientific formula to create a perfect movie or album or TV show that would recoup costs all the time.

[0] The original sales pitch being that these vaults were nuke-proof.

[1] Your cloud provider does this automatically and that's built into the monthly fees you would pay. People who are DIYing their storage setup and using BTRFS or ZFS are using filesystems that automate that for online disks, but you still pay for keeping the disks online.
If the day comes that I can no longer avoid cars with user-hostile systems such as (but not limited to) "infotainment" ones, this is exactly what I'd do. Rip that shit out and replace it with something that suits my needs.
For certain types of work you'd be entitled to overtime, but professional-managerial class jobs like software development are specifically exempted from this part of labor law in most states.

https://www.dir.ca.gov/dlse/faq_overtimeexemptions.htm
It seems you don't understand the lawsuit. Most of the claims are based on the actual mechanics of how algorithmic price fixing does violate existing laws.
The Brutal Economics of Reaching Net Zero
Yeah, half of my Facebook feed is shit that is intentionally wrong so that people will interact with it because they get paid based on engagement.
Obviously emergency vehicles are needed and similar access for commercial and handicap vehicles makes sense.

Popular cities don't really need to compete to fill a bunch of commercial real estate. They have people who commute every day by public transport and residents who are competing for real estate with this property.

It's enough now with the cars, there are mall towns and cities happily lose 'business' to them because it is not worth wasting 30% of all land to attract a bunch of people who may never actually get out of their car in your city and then at most to a business that probably pays less in property tax than a correspondingly sized residence.

These businesses can't vote and if they aren't in town to complain the noise from them stops. There were also a lot of angry horse cart drivers once.
Modelica comes to mind.

https://media.springernature.com/lw685/springer-static/image...

https://en.wikipedia.org/wiki/Modelica
Take the job. Document der forced 7 day work week. Get burn out diagnosed and sue them.
"Sorry Grog, you weren't horney enough"
I’d be curious to plot this next to home prices. It looks like places that are more expensive to live have higher Taco Bell prices.. which kinda checks out.
I think that's widely understood and part of the job description of being a public servant. What's not widely understood is HR secretly selling your data while working at a private company.
It's ok. Not that great.
Something like half of of reported JavaScript vulnerabilities are "prototype pollution" because It's very common practice to write to object keys blindly, using objects as a dictionary, without considering the implications.

It's a very similar exploit.
I have to say I am pretty surprised to see the negative sentiments toward Pave and salary benchmarking data in general here. Why is the assumption that salaries would always be lower given this data? It seems just as likely to inform companies that what they had in mind is below market or that they are under-compensating someone in light of market changes.
> But that will be their water under someone else's bridge and as long as that water sill allows them to reap the benefits of their "not proudest moments" then it's just going to happen again and again with the next generations getting a minor point of conversation.

You are claiming at once that deepening our understanding of historic CIA misdeeds misses the forest for the trees, and then ignoring the trees to project current CIA misdeeds out 50+ years.

It's like the coastline paradox and the gambler's fallacy had a baby.
You're saying all big companies ban whole language ecosystem because somebody on the internet used one function in that language in knowingly unsafe manner contrary to all established practices and warnings in the documentation? This is beyond laughable.
Everyone is different, and what an adult can overcome is different than what a child can overcome.
Didn't they agree not to hire each other's employees? Which would serve to suppress salaries, even without sharing what anyone was getting paid.
The rocky road to upgrading Ubuntu Linux 24.04
> We work weekends, so it's 7 days a week, just want to make sure that's ok with you

This translates to "I am a bad manager"
My God, why would anyone decide to work(?) in this way? Even if you are a junior and are a desperate to learn new skills, this is a totally wrong direction. And even if they a huge salary (like 3 x above the average, which I doubt), is your health really worth that? That's insane!
You have heard of the Prison Indistrial Complex right? Our Prisons have been For-Profit for a long time now. Totally legal, government sanctioned privatized penitentiaries.
> Golangs stupidly verbose error handling forces you to constantly think about the unhappy paths. Every function is littered with error handling and it makes you aware of possible problems and rigorously forces you to not forget them.

That reminds me of this [1]:

> However, if you are going to make a lot of state changes, having them all happen inline does have advantages; you should be made constantly aware of the full horror of what you are doing. When it gets to be too much to take, figure out how to factor blocks out into pure functions (and don't let them slide back into impurity!).

[1]: https://cbarrete.com/carmack.html
> The issue is that some sites will not work until you made a decision in the cookie pop-up. So then I have to reload the page without blocking, reject the cookies, and then reload the page with blocking...

My solution in these cases is to leave the website in question and do something that doesn't involve getting abused.
what's the hostility against Ollama?
Not parent, but it’s a term of art https://en.m.wikipedia.org/wiki/Gender-critical_feminism
Trust me, I know. Some batches of nuggets were rejected based on being too crispy or too chewy.
I wouldn't. Your phone getting fried is just unfortunate.
> Yes, that's kind of the main difference between government functions and private companies

Perhaps that should change. Or at least it’s a reason to scrutinize and repeal laws that are used for price fixing.

> Are you saying the very idea of zoning strikes you as a problem? Or are you trying to call out the bad implementations which strangle urban prosperity in the US?

Zoning Rules! by William Fischel gives good a history of zoning. Zoning was originally for segregation within the city but to the question of prices, no it was not inherently problematic. It was not until the 1970s that zoning was used for growth control to make entire cities unaffordable.
Never really understood any company of any size that pushes for this type of workload. Do you really produce high-quality work on hour 100 of the workweek versus hours 0-40? For every startup that succeeds with this type of 996 dystopian work schedule, I'd argue more fail because of high employee churn, low worker motivation, and burnout even in a high-paid tech startup. In my opinion, even for those highly motivated, the human body simply can't do productive work in that type of environment. Some of the best startups I've seen are those with actual work-life balance. Not necessarily saying in and 9 and out at 5 on the dot, but certainly far from 996 or 997.
https://www.foodindustry.com/articles/list-of-direct-to-cons...

Looks like several exist.
XUL was a different stack. This is using the same stack.
I opened the link and filtered by executive.
Thirteen people there:
- 5 white men
- 4 white women
- 1 black man
- 2 black women
- 1 asian woman

Pretending that a sample size of 12 should exactly reflect the diversity of the whole population of the country is just weird to me.
"Orthorectified" (i.e. on a map) means both. It's corrected to a perpendicular to the observer view _and_ also corrected for scale distortion due to elevation (the top of a mountain is closer to the sensor and therefore appears larger than the valley beside it). For off-nadir imagery (i.e. not looking straight down) the view angle plays a larger role than the scale distortion part.

With that said, raw elevation matters too, especially when the imagery is off-nadir.

RPCs describe a view direction + lens distortion / etc. A completely flat surface at elevation will be in a different location than a completely flat surface at sea level. Things will also be a different _size_ as well depending on elevation.

Think of the RPC as a vector looking a specific direction (at a single pixel level, that's kind of what it is, though each pixel gets a different one). You're placing a point on the map where that ray intersects the Earth's surface. It intersects at a different point depending on the elevation of the surface. Projected (aka orthorectified) data needs to correct all of that to be able to place imagery on a map accurately.

If the airport is completely flat, then using a constant elevation is fine, but you still need to use that elevation and not assume it's at sea level. Otherwise it will be in the wrong place on a map and also a slightly incorrect size.
Obviously, this sort of information would always be used for good.
Kubernetes is really here nor there. It's the crashing of the app that is our focus. An app should not be crashing on expected behaviour.

That's clearly a bug, and the bug you need to fix first so that you can have your failsafes start working again. You asked where to start and that's the answer, unquestionably.
In fairness, I live in an "urban area" with 2 neighbors on the surrounding 100+ acres of land. A lot of people hear the census "urban area" and they imagine a dense downtown. That said there is no shortage of grocery stores and restaurants (if not especially high-end restaurants) around where I live.

I do suspect that most of the people who say they have no choice but to eat at McDonalds or wherever just don't want to make a meal at home.
Of course. They achieved their goal.

Director William Casey Quote: "We'll know our disinformation program is complete when everything they believe is false!"
I've never run a company and probably have a chip on my shoulder, but I also think that it's a reasonable assumption that most employers want to pay as little as possible.
Not sure about the fraud but recently we had a very heavy bill from AWS (6x of our usual AWS bill).

After much investigation I realised that one of my dev has setup complicated stuff using some Terraform config he found on Github.

I feel that AWS has very bad UX.
Taco trucks/taquerias are an entirely different cuisine than Taco Bell.
He would know. https://www.npr.org/sections/thetwo-way/2014/04/24/306592297...
> The great mathematician Aryabhata (476-550), in his masterwork composed when he was only 23, covers square and cube roots, the properties of circles and triangles, algebra, quadratic equations and sines, and contains a decent approximation of the value of pi at 3.1416.

TIL...