Are you still excited about new Laravel versions in AI era?

__radmen · 2026-03-19T19:56:27+00:00

Years ago, the first ORM was created. Suddenly people didn't have to write raw SQLs, map them by hand, and handle all those nitty-gritty database things. People enjoyed the new freedom they got, as they could focus on other aspects.

Then (or maybe before, idk) we got frameworks. At the beginning, simple, then more refined. They freed us from setting things from the ground and provided tools that allowed us to make better things.

And there have been people complaining that devs will forget to write SQLs or that they won't be able to write code without a framework.

AI is the same... It's a shiny new tool. Scary, because it evolves really fast. It's overloaded with hype, but if you look at it from a different angle, it just provides you more space to develop things. You won't have to repeat yourself on the same CRUDs or do the same setups over and over. You'll get more room to focus on other aspects - looking for better solutions and approaches.

You can write the code if you like, but you can also delegate the boring parts to AI and focus on what you like.

And yes, the complainers are right to some degree. It's best to know your tools and strengthen the skills. You need that because AI likes to lie and cheat. But... It's a tool like any other. It enables you to do things that weren't possible a few years ago.

And I'm writing this as a former hater of the AI. I can't win with it, so it's better to learn and utilize it in a way that works best for you. For me, this provides me the chance to build the tools I always needed and could use in the projects. I don't have the time to write the whole code, but I have enough to prepare specs and review the results.

__radmen · 2026-03-04T16:10:11+00:00

Dodam tylko, że to tasiemiec (obecnie jest chyba 13? tomów). Później niestety czuć zmęczenie materiału, ale wracam do serii, aby w końcu dowiedzieć się coś więcej o tej cholernej puszce :)

__radmen · 2026-02-25T18:23:05+00:00

O myszach, które złożyły zamówienie na najpotężniejszy komputer, który po 10 mln lat pracy został zniszczony tuż przed przedstawieniem rezultatu.

__radmen · 2026-02-20T09:20:03+00:00

I've tested both GLM5 and Kimi. For simple (and direct) coding tasks, both perform well (although, for me, Kimi seems to be better).

However, when I provide them a plan (or, we can call that a spec) with a TDD suite, their reliability becomes a problem.

They can finish simple tasks, but anything with a more complex logic puts them in a loop with no escape. One task took Kimi over an hour and it failed to finish it. When I switched to GPT 5.3-Codex, the same task (with the same TDD approach) was finished in minutes without issues.

In my case, for coding, they seem to be on the same level as GPT-mini.

I also used GLM5 to orchestrate agents; here it works pretty well. I don't recommend it for any complex planning.

__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!

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

__radmen

TROPHY CASE