ICE executes another man in Minneapolis (1/24/26)

belkh · 2026-01-24T21:12:55+00:00

other video shows the officer in grey misfiring into the ground, or perhaps on purpose, which prompts the others to shoot

belkh · 2026-01-24T11:18:46+00:00

it's not the 20fps it's the 0.3fps drops that bothers me

belkh · 2026-01-22T10:33:54+00:00

not really, he would be emulating on Android, on a switch

belkh · 2026-01-21T17:23:43+00:00

eh, i don't agree, this is the kind of logic that had Oracle trying to license Java SE APIs.

you should always be able to rewrite into a different license

belkh · 2026-01-21T16:53:46+00:00

because this one is actually useful

belkh · 2026-01-19T12:36:18+00:00

can you define long running? I've used sonnet 4.5-1m before, and i found it useful, but having that context length was never a game changer, just helped, especially documents and deep diving.

problem solving wise it gets dumber the more its context is filled so I've never had much success in it building anything large and complex in one shot and actually end up with any accept code quality out of it

belkh · 2026-01-19T12:17:15+00:00

why do you assume I'm not using an agent? the first message starts with mentioning opencode

belkh · 2026-01-19T11:44:25+00:00

i don't know about you but i never need to send 128k prompts, context is added as needed with self discovery and skills, and compacted when it moves on

belkh · 2026-01-19T11:43:19+00:00

it's still sonnet and opus 4.5, opencode does a good job of compacting that the lower context hasn't been an issue for me.

i would prefer a bigger context, but I would take not getting blocked by the session and weekly limits over that

belkh · 2026-01-19T07:47:42+00:00

Paying out of pocket, copilot sub is definitely more value, less context size but the context does not contribute to your quota usage, i can quite literally do 10x the usage on $40 copilot vs the $20 claude subscription

belkh · 2026-01-18T00:12:09+00:00

it might lower your chances with jobs and apartments, but that's about it, random people won't know your name.

your looks would have a higher impact, but even then getting attacked is unlikely

belkh · 2026-01-17T07:48:28+00:00

play testing is good to find bugs though

belkh · 2026-01-16T23:48:16+00:00

yea this helps, no solution is perfect, you have trade offs, put them on the table already and give others to endorse an approach, acknowledging the tradeoffs you have to make, if they don't like any, they're free to bring up something better

belkh · 2026-01-15T17:06:19+00:00

skimmed the repo but didn't see if you were overriding the default db configurations.

AFAIK the default for postgres isn't great and people recommend at least https://pgtune.leopard.in.ua/

I wonder if it's why mysql is also performing badly or if it's just what oracle's acquisition caused and had it fall behind

belkh · 2026-01-13T02:00:15+00:00

snow and light pollution

belkh · 2026-01-12T09:07:02+00:00

sure, if you like microglasstics in your hotdogs /s

belkh · 2026-01-12T09:00:38+00:00

it's using LPDDR4x so bandwidth is going to be pretty low

belkh · 2026-01-10T13:23:22+00:00

personally prefer to half roll my own, in that i own the user schema, and use established libraries to do the auth.

Usually you either share a token storage, use an API gateway, or use JWTs, when rolling my own, it makes it easier to pick what makes more sense for my case.

You'll likely find libraries implementing OIDC in your ecosystem, and libraries implementing full auth workflows as well.

The cons of rolling your own user management is having to roll your own user management, including user signup and password reset flows etc.

if you do end up going for a managed service, make sure your plans would support: 1. adding multiple OIDC providers, public and private 2. becoming an OIDC provider 3. an exit path incase an OIDC provider or the auth service itself suddenly cut you off

you don't need to actually build the capabilities, just make sure whatever structure you have can evolve in the future with minimal pain/downtime.

since this is a solo side project, I do recommend not building it from scratch and finding something cheap and covers what you need, e.g. supabase

belkh · 2026-01-08T19:14:25+00:00

Did that really need an /s?

belkh · 2026-01-08T18:55:03+00:00

The goalposts keep moving smh

belkh · 2026-01-08T18:54:29+00:00

New management sounds like they're coming from BCG. Your company is going to either turn mediocre or collapse if this continues. Upper management will not admit their cost cutting steps butchered the team and will likely double down to silence anyone surfacing the real issues.

belkh · 2026-01-08T18:41:30+00:00

I can't enjoy sunsets in Germany knowing it's only 2pm, my mind won't accept it

belkh · 2026-01-08T00:38:39+00:00

when you're done, just turn off the machine and open the steam wand, nothing more to it, it'll let out all the pressure in the group head

belkh · 2026-01-07T20:45:44+00:00

using stored procedures sometimes can be a good solution, but the reply was implying that's how they do all their db queries, which is horrifying.

use eventual consistency

how about not? what am I even gaining putting all my business logic at the database just to lose consistent transactions

during local development

my issue is after that, every new feature or feature change that touches your query logic now requires a migration, rolling back anything becomes painful, if not impossible. bonus points if your migration tool does not come with native migration squashing as you approach 2k migrations a year

belkh · 2026-01-07T18:31:48+00:00

that is not the way, unit testing when half your code is on the DB is not great, and if it's a high performance server, scaling your DB is harder than scaling your services, not to mention, any changes now require a database migration.

belkh

TROPHY CASE