serguzest

StackOverflow moderation was hijacked by army of Sheldon Coopers

I don’t buy any of this. They released something extremely resource-hungry, slow, and token-intensive. In layman’s terms, it feels more like overclocking than a real improvement over Opus.

I suspect it was not sustainable to run it for millions of users without a huge price adjustment. So, before the IPO, they may have wanted to preview something “cool” and then stage some kind of legal force majeure.

Also, considering how corrupt the current U.S. government appears to be, it is not impossible that one of Trump’s sons has a partnership with Anthropic, or that some kind of backdoor deal is going on. In that case, this could have been done in cooperation with a corrupt government

We are in a similar situation, and here's what I did:

1) Learned the basic concepts of double-entry bookkeeping. 2) Told ChatGPT about my business domain and requested an example Chart of Accounts (CoA) tailored to it.

Feel free to reach out to me, I’d love to exchange ideas.

yes but consider this Jest code, replicating such in node testing is painful. testing code should be DSL-like, should be very easy to read.

            expect(bar).toEqual(
                expect.objectContaining({
                    symbol: `BTC`,
                    interval: `hour`,
                    timestamp: expect.any(Number),
                    o: expect.any(Number),
                    h: expect.any(Number),
                    l: expect.any(Number),
                    c: expect.any(Number),
                    v: expect.any(Number)
                })
            );

It is based on vite and a bundler has no place in my backend. Vite is based on roll-up, roll-up uses some other things such as swc. I want to use typescript projects and npm workspaces which vite doesn't seem to care about.

I love Node's built-in testing and how it integrates with VSCode's test runner. But I still miss Jest matchers. The Vitest team ported Jest matchers for their own use. I wish there were a similar compatibility between Jest matchers and Node testing as well.

One thing you should add to section 10 is encouraging people to pass `cause` option while throwing new Error instances. For example

new Error("something bad happened", {cause:innerException})

bu yazdiklarimdan onu mu anladin aq otistigi. Hepimizi geberip gidecegiz doga devam edecek

There’s a truth we’re rarely taught in school and I find it deeply poetic: The vivid colors we see in flowers, even those beyond our vision in the ultraviolet, and the delicate fragrances that drift on the breeze they're not for us.

They are nature’s love songs, composed to seduce insects. All this beauty is a grand performance, meant to charm bugs into becoming messengers of life, carrying pollen from bloom to bloom.

Bees, though precious, are just one part of this ancient dance. Moths, beetles, butterflies, each plays a role in this quiet symphony of survival.

And yet, this balance is being disrupted. Greedy and short-sighted actions are damaging ecosystems that are far more complex than we understand.

But here’s the humbling part: Nature will endure. She always has. She’ll shake us off like dust, heal in silence, and bloom again with or without witnesses.

Ravendb is trash. It can’t handle even 1/10 of this type of a load, it was trashed in jepsen testing too. I had to work with it 4 years and i disliked it.

It is not just a mainboard issue. I had an asus mechanical keyboard. After I started using it, Windows kept installing software and background services in system that is a listening port. I kept deleted it manually and no matter I did, windows kept installing it without my consent. It was really annoying.