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

In Portugal: in a liquidation, they may loose first preference for back pay.

Back pay first, then social security, then taxes, then secured/privileged/unsecured/subordinated credits.


Filesystems can be much slower than SQLite for many (think millions of) small files.

They also mention considering this in the post.


I guess my squishy biological tokeniser and summariser missed it (i.e I read the TL;DR and skipped the post)

It actually was better than in Spain. Large portions of Spain were left without power for almost 24h, despite the help from France (initially) and Morocco (later).

Portugal was able to recover in 12h (still a lot) without any external assistance.


> About 16:00 CEST on 28 April, Spanish electrical operator Red Eléctrica de España (REE) estimated it would take "between six and ten hours" to restore service

> By 07:00 CEST (05:00 UTC) on 29 April, electricity had been restored to 99% of energy demand, and full restoration was achieved by 11:00 CEST (09:00 UTC) that same day.

The wikipedia references seem valid for this precise timeline, which is more informative than your remark.

https://en.wikipedia.org/wiki/2025_Iberian_Peninsula_blackou...


Power was fully restored in Portugal by 22:22 UTC on April 28: https://eepublicdownloads.blob.core.windows.net/public-cdn-c...

I'm not trying to win a pissing match, just trying to counter the very common miserabilist notion that Portugal did worse than Spain.

This specific problem was (1) caused in Spain, (2) fixed faster in Portugal, and (3) with little external help.

Portugal could've been the cause, and could've done better, for sure.

But it's just not balanced to write "In Portugal it didn't go that well" as a response to "It went remarkably well [in Spain]." Makes it sound much worse than it actually was.


Not bad: 2 in 3 are actual discounts, 90% don't leave you worse off.

You might not have bought an item if it wasn't supposedly on discount. Leaving you worse off than not having spend the money. Getting tricked/scammed is part of being worse off.

You misunderstand my point: not bad, because I was expecting worse.

Ah sorry, not a native speaker

Me neither. Maybe that's why. :)

If 10% of "deals" are actually worse prices it is bad indeed in any case. That number should be 0.

At least 10% of Amazon listings are outright scams.

The margin is too narrow to contain it.

I'm in the process of adding a few of these to my Go SQLite driver.

https://pkg.go.dev/github.com/ncruces/go-sqlite3/ext/approx

They work as window functions, and they also support creating roll-up tables, e.g. you have a table storing a sketch of daily active users and can use that to get weekly and monthly active users.

Same for quantiles (e.g. median and tail latencies) and next up top-K (e.g. most popular content, highest spenders, etc).


We could even use `ssh -X` to send it over SSH if that flag is otherwise unused.

I think it would make sense if it had a client-server architecture.

And for the ecosystem's sake, punish (harshly) GUI toolkit developers that use bitmap rendering (GTK4 and Qt Quick applications are slow on ssh -X).

A century? Since 1926? The FAA was created in 1958.

CL (change list) is Google speak for a PR [1].

So, likely: Gemini Flash, Argon, Carbon [2]; and Claude Opus [3]. Maybe more.

https://google.github.io/eng-practices/review/developer/cl-d...

https://blog.google/innovation-and-ai/models-and-research/ge...

https://www.businessinsider.com/google-finally-lets-all-engi...

The models are great, but the experience resonates. It really depends on what you're doing, and ultimately, how much you care. A 10k LoC PR that feels “tacked on” should help you guess the size of the code base.

So do you care about getting 10k LoC to review, in a 1M LoC code base? How about 3 such PRs? How about reviewing another half a dozen, from colleagues? And doing that 2 or 3 times a week?


> I can recognize within seconds if a PR is an easy merge or a 5 minute phone call.

I'm glad you can.

Even before agents, I'm pulled to work on at least a couple different projects a year, the successful ones with teams of 10s of people working on them. If I stay longer than a couple of months, I eventually become the expert on some of the things I did, so I get pulled years later to review something I haven't touched in ages, which has changed requirements, and grown a bunch of dependents.

That was the reality of working on a team with hundreds of people and dozens of related products.

Now agents are helping people increase complexity and velocity N-fold.

You can call it a problem in the coal mine, but there's no going back. GitHub simply has no choice but to handle this new scale.


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

Search: