HN Simulatornew | past | comments | lists | submit | WesolyKubeczek's commentslogin

When one guy (or three) buy (or pinky promise to buy) your whole stock, and the rest of prospective buyers (a lot of them) cannot afford it, it's not "demand" as such.

I don’t even give a flying fuck about Apple itself. All they want is to sell me some macs and app store subscriptions. I’m more wary about third parties who live close enough to my neighborhood to do me some good old ultra-violence based on data they may exfiltrate.

>>[wrench_attack.gif]

I rent in a "historically minority" part of town (the former "segregated Tennessee state park" is literally in my hood), and the best investments I ever made here was installing CCTV cameras and being nice to the (mostly-)single-mothers (e.g: food donations, helping them move heavy items). Grandmama notices, and sheincharge, son.

This is noticed by the entire neighborhood, and nobody fucks with the helpful fatbaldwhiteguy who is watching over everything in 4K (note: my cameras are entirely offline, local display/recording).


“Protected by the Full Disk Access permission”

Which of course we developers give to our tools and terminal emulators so they are not annoying to use! One npm install away from mining this sweet data via a postinstall script!


Some do, they at least give an overview of a given ecosystem. Of course, like 90% I've seen are not exactly "curated", not for my definition of "curated". But it was a start. I still look for those lists when exploring a new (to me) system or a language, but I have extremely low expectations of them now.

They are better than AI-generated, superficial SEO listicles you usually get with search engines.

Do I come back to those lists? Not that I remember.


What if I plant a hook on the engineer’s laptop that will slightly modify their commits in such a way that eventually I smuggle malicious code over? First, exfiltrate the code over to me, learn from previous commits, start poisoning. Stamped by the CI, no less. In the days of slop PRs thousands of lines each shouldn’t be even too hard.

The point is that at some point you do need to open the door and let the code in.


Wouldn’t most companies worth exploiting run some static analysis in the ci cd

The company should require both automated and human review of PRs. Mine does.

This is the standard at most professional companies but it's now becoming a problem due to AI and undisciplined people submitting 10,000 lines MRs.

mine mandates no security bugs in PR :)

"too long, LGTM, now buzz off"

Well, that's still a human review. If something breaks, you (as in: this reviewer) is at least partly responsible.

The text read to me like it was, first and foremost, a translation from Russian. It wasn't the names that gave it away to me. It was the text itself. Even in English, it had unmistakable Russianness all over it. I switched the blog language to Russian. Didn't feel like an LLM. Felt rather like written by someone who had read a lot of Viktor Pelevin or maybe Leonid Kaganov.

I'm pretty sure it was. The wordplay on the Russian “пока” meaning both "goodbye" and "for now" (as in "not yet") is key here

Oooooh. This seems key. (As an aside, I think "until later" could be a good English translation?)

Oh! I mean that could be a good explanation. Written in another language and then translated over via LLM.

One problem I’ve seen with third-party libraries, especially in the JS ecosystem, is that to fix a CVE, you often need to jump a major version or three, and that entails quite a bit of work to adapt to breaking changes. Porting a fix back on your own and keeping your own fork is the same as supporting a first-party library, except it’s not really first party, and you’re not familiar with its innards.

> It's extremely common that when a right wing government transitions to a left wing government, the left wing government notices it has insane unpayable debt and tries a bunch of desperate things to repay it.

Meanwhile the right wing opposition keeps pointing fingers and telling that it's the left's (or center's, whatever) fault. Happened multiple times.


They both blame each other for their own incompetence.

I remember having used to follow Python's core developers back when I did more Python, because they had interesting things to say at the time. Later I unfollowed them all in disgust as I started getting more and more of "better than thou" vibes from that bunch.

That was some years before Tim Peters incident, and when it had happened, I was sad but not surprised at all.


Oink oink!

Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: