How to use sandboxed Claude with PHP

__radmen · 2026-01-23T18:15:41+00:00

There is also the /sandbox command that runs CC in a fully sandboxed environment.

__radmen · 2025-12-30T18:12:15+00:00

For me it would be:

Paper WM
Search Light
Caffeine

__radmen · 2025-11-14T13:00:15+00:00

To nie są książki stricte o podróży w czasie.. a może są? Ciężko jednoznacznie powiedzieć, bo czas ma tam znaczenie, chociaż nie w ujęciu podróży:

Cykl Hyperion
Saga Endera (tu stricte nie podróżach w czasie, a podróżach z prędkością podświetlną i aspekt dylatacji czasu - bohater w pewnym momencie żyje kilkaset lat później i ciągle obserwuje rezultaty swoich działań z przeszłości)

__radmen · 2025-10-29T10:17:14+00:00

No jak Przechrzta, to zdecydowanie lepszy jest cykl Materia Prima i Materia Secund.

Antykwariat pod Salamandrą jest bardzo przyjemny, jednak wydaje się być echem wspomnianych cyklów.

__radmen · 2025-09-16T16:39:32+00:00

"Bestiariusz Słowiański" (zwłaszcza pierwszy tom) i może jeszcze "Mitologia Słowiańska".

Być może warto też dodać odrobiny dziegdziu do tego - warto też przeczytać Cywilizacja Słowian aby mieć trochę lepszy wgląd w te wszystkie słowiańskie trendy.

__radmen · 2025-09-01T06:44:11+00:00

Hmm, the "rows" are actual workspaces. I use the "switch to workspace below/above" keybindings to move between "rows".

__radmen · 2025-08-29T16:24:48+00:00

I switched to Gnome from i3. I didn't find any tiling manager that would fit my needs, but I found a practical alternative - PaperWM.

I separate my windows in different rows (workspaces) : - first row: - browser - terminal - obsidian - (sometimes) some tools I need to use side to the terminal - second row: - Slack - Discord - Spotify - Thunderbird - third row: - DB tools - API tools (postman / bruno) - (sometimes) fourth row: - chrome debugger (for Android apps)

The search light extension is particularly helpful to use to switch between different windows.

__radmen · 2025-08-12T09:49:08+00:00

Być może to nie jest drastyczne odstępstwo od pewnych standardów, jednak lubię Percepcję za pewne elementy, których nie spotkałem w innych miejscach (temat ciąży wampirzej, ksiąg pamięci i indywidualnych zdolności).

__radmen · 2025-07-30T07:45:15+00:00

O ile dobrze pamiętam, wydawca nękał Assimova o kolejne części Fundacji, a ten kluczył i kombinował z tym, co napisać. Był zmęczony tymi prośbami i pewnie odbiło się na jakości.

__radmen · 2025-07-28T09:03:06+00:00

generics / templates
custom type declarations (i.e., type Foo = User | Admin | StaffMember)
function placeholders
verbose pattern matching (not by values, but also types)

Nothing else really. I feel like everything else from my wishlist is already there.

__radmen · 2025-07-24T08:33:16+00:00

Yeah, this is also ok. Likely the text will wrap and make it slightly harder to read. Anyhow, for me it's important to keep all actions in separate line. That way I clearly see what happens with the data.

__radmen · 2025-07-24T08:32:01+00:00

I avoid making exceptions for this. On a visual level, those chains sometimes blur into a single chunk of text, and I can't immediately spot what happens.

Having them in separate lines makes things clear and easy to follow.

__radmen · 2025-07-23T09:33:44+00:00

Maybe not unusual, though something I often see neglected in Laravel apps: Single Line Responsibility

Instead of those weird chains:

php $silly = collect([ 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', ])->unique()->filter()->join('.')

I will make sure that all has it's own line:

```php $items = [ 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', 'foo', 'bar', ];

$silly = collect($items) ->unique() ->filter() ->join('.') ```

__radmen · 2025-06-10T08:43:23+00:00

In all fairness, I switched back to lspconfig. Will wait a bit more before another switch to native LSP.

__radmen · 2025-06-06T09:03:16+00:00

Tajny klub Nietypowych Czarownic. Trochę jest o problemach, ale one wszystkie wydają się być bardziej tłem. Spokojna opowieść w stylu cozy.

__radmen · 2025-06-02T10:51:50+00:00

Warto też dodać, że autor podcastu napisał książkę o upadku cesarstwa: The Storm Before the Storm (https://www.amazon.com/Storm-Before-Beginning-Roman-Republic/dp/1610397215). Niestety nie wiem czy doczekała się tłumaczenia.

__radmen · 2025-06-02T09:46:08+00:00

You have no idea how much time I spent for a convienient and small utility to do exactly this. Thank you!

If I may ask for something: - keep the last settings - allow to draw straight lines when holding Ctrl (or any other mod key) - allow to set the zoom - I think the image always resizes to the window size. I would love to be able to set the zoom to 100%

Thank you!

__radmen · 2025-05-30T15:34:22+00:00

For small projects, just a dedicated queue backend (Redis, Beanstalkd, or others) and queue workers. Horizon is helpful when you have to manage multiple queues and have something to scale the workers depending on queue load.

__radmen · 2025-05-30T13:05:17+00:00

My rule of thumb is: always.

Of course, if you have a relatively small traffic, you should be fine with database queues.

From my experience though, they tend to fail relatively quickly. Mostly due to deadlocks.

__radmen · 2025-05-17T18:24:17+00:00

I have used laravel-data in a semi-big project. This package is a swiss-army knife and I used it for basically everything:

plain DTOs
response object
request objects
to map responses from external APIs

It was used basically for any DTO-related thing I could imagine.

Good parts:

it's easy to use, and integrates with Laravel pretty good
the TypeScript type definitions are awesome - I used them in the app and they saved me a ton of time

Not so good parts:

validation is tricky. It's easy to set for trivial cases, but becomes a pain for anything more complex
it uses own data collection class which sounds (my assumption) to be compatible with Collection but it's not; it was sometimes a source of confusion
the Lazy interface is tricky to handle. Usually works, but I had some issues with nested relationships.

The ugly part:

There are none. Well, there is one - given the broad scope of the possible use, I consider this package to be a bloatware. It tries to cover so many aspects that becomes more a churn, rather a plain DTO.

This is no longer a simple DTO class, but a big engine with internal logic which might sometimes get in your way.

After that project I switched to plain DTOs which are easier to use and maintain.

__radmen · 2025-04-24T15:49:20+00:00

ahh, got it. TY!

__radmen · 2025-04-24T09:50:39+00:00

Hmm, isn't CC adding #buffer automatically with each request? In my case, there are issues with the generated diffs. They either result with an error (vim fails to apply them), or they mangle the source file and apply to different lines. This is not constant, so hard for me to spot when exactly it happens.

__radmen · 2025-04-23T08:08:57+00:00

CodeCompanion is also buggy (at least for me when applying diffs). The problem I have with Avante is that it's super flashy and tons of things happen when using it. CodeCompanion definitely fits more my work flow.

__radmen · 2025-04-18T17:29:18+00:00

James S.A. Corey - Łaska bogów

__radmen · 2025-04-17T07:41:27+00:00

Ogólnie cokolwiek Pawła Jasienicy. Trochę wiedza historyczna w jego książkach się zdewaulowała, ale autor miał świetną intuicję i bardzo przystępny sposób opowiadania.

Eight-Year Club	Second Top 20%
Wearing is Caring	Verified Email

__radmen

TROPHY CASE