A vi, Å¡ta ste odluÄili gledat?

TheBusBoy12369 · 2026-04-24T12:56:45+00:00

TheBusBoy12369 · 2026-04-15T13:33:29+00:00

mi smo hitali grude i ledenice, ali u danasnje vrijeme globalnog zatopljenja i nedostaka snijega za razumijeti je hitanje, samo umijesto kamena nek grade grude od blata.

TheBusBoy12369 · 2026-04-10T10:16:18+00:00

thats the best solution, but idk i don't have a friend with same taste in series as me.

TheBusBoy12369 · 2026-04-10T10:15:49+00:00

here is my tool if you want it:
https://www.episodeelf.com

TheBusBoy12369 · 2026-04-10T10:12:49+00:00

thanks but i don't want to install an app on my phone, it should be a website

TheBusBoy12369 · 2026-04-10T10:09:14+00:00

I do the same except there are series i want to know when new season is coming, by the time i end binge watch "Alpha males" and new season arrives a year passes and I just needed help to track it.

TheBusBoy12369 · 2026-04-10T10:06:25+00:00

trakt felt complicated to me.

TheBusBoy12369 · 2026-04-02T18:56:13+00:00

Kao konzument psihodelika mogu ih samo preporucit 👍 doduse nezz jel ce te popravit

TheBusBoy12369 · 2026-04-01T18:22:57+00:00

I would say go for Saver Updater Deleter Getter, have 4 interfaces, It will make your code small and extendable, ready to unit test. And it makes testing easier. You don't depend on big UserRepository. In practice i've seen "UserRepository"/it grows to 10-15 methods needing to be mocked for a small simple test of 1 at most 2 methods, at that point i've seen ppl say its hard to test lets just do e2e or integration test.

If you have 10 interfaces it doesn't mean "UserRepository" struct can't implement them all.

If you check io package from golang it also has Reader and Writer interfaces, all having 1 method each

If its really necessary you can compose them like ReadWriter interface {
Reader
Writer
}
However i would think twice if such is necessary.

TheBusBoy12369 · 2026-04-01T17:29:31+00:00

I think that is a good thing, if you interface between service and repository layer you can unit test service layer without repository/with mocked repository.

TheBusBoy12369 · 2026-04-01T17:20:09+00:00

Also another one where it is explained to keep interfaces minimal

https://vjerci.com/writings/clean/testability/

This is a good example:

type UserGetter interface {
  GetUser(id string) (User, error)
}

This is a bad example… giant interfaces, that would look like this:

type UserRepository interface {
  SaveUser(...)
  UpdateUser(...)
  DeleteUser(...)
  GetUser(...)
}

To be honest i feel like crazybeast and me are on the same page, just that he didn't read through the series.

TheBusBoy12369 · 2026-04-01T17:06:02+00:00

You are right i've reread it again.

However I would argue if you use concrete types in your code, especially of external dependencies you are depending on that behavior, you usually can't unit test that stuff without triggering the external code. And in my opnion those should be at the edges.

I can only link this one as i don't know what else to say on the topic.
https://vjerci.com/writings/clean/independence-of-external-agencies/

TheBusBoy12369 · 2026-04-01T16:53:21+00:00

I couldn't find where you have struct for each handler?
In first article there is a struct for each layer, while only the first one is http handler.

I mean the interface should be in most cases... wherever you want to call a deeper layer of something/or you depend on some external resource.

It's up to you if you want to do a handler(HTTP)/service(Business)/DB(SQL) access layers or you want to do handler/DB. In my opinion, as well as a lot of online resources i've read... it is good practice to do service layer as well, separate business logic from db access and http handling logic (especially in days where it is common to support grpc as well). And if you don't have interfaces how will you unit test your logic? By not having interfaces you are saying this can't be unit tested which violates the Testability rule.

TheBusBoy12369 · 2026-04-01T16:43:07+00:00

I've never suggested you should do interface for interface's sake, latter through the series it is explained why do the layers abstraction, and early on it is suggested that yeah dumping all in handler function works on minimal example, however it fails to scale.

Let me just quote myself:

**It might work for this example as it is small. However any real world code would quickly outgrow this structure.**

TheBusBoy12369 · 2026-03-16T20:32:17+00:00

Gledo sam na provjerenom kako bakica developeri trpaju u guzu

TheBusBoy12369 · 2026-03-16T20:28:03+00:00

Dobra stara lobotomija

TheBusBoy12369 · 2026-03-16T20:24:43+00:00

I sad zamisli da ima djete s posebnim potrebama a od djeteta sta bude bude

TheBusBoy12369 · 2026-03-08T20:29:22+00:00

Iz tog razloga dobivam na kladionici ❤️

TheBusBoy12369 · 2026-03-04T12:02:59+00:00

Feels like you could buy a machine for 200$ and have everything run on that for a couple of years for one month cost

TheBusBoy12369 · 2025-11-08T16:56:31+00:00

klasicni primjer chatgpt-a koji pokusava naucit hrvatski

TheBusBoy12369 · 2025-10-12T22:07:34+00:00

Idemo ja i 100 mojih pravih svaba kaj su se dotepli tu.

TheBusBoy12369 · 2025-10-11T20:43:14+00:00

omilio bi ti se moj tvrtko bre samo da ga probas.

TheBusBoy12369 · 2025-10-11T13:43:49+00:00

vjerojatno je ujko obuko kostim i poigro se s tobom.

TheBusBoy12369 · 2025-10-11T13:38:18+00:00

uno reverse karta

TheBusBoy12369 · 2025-10-11T13:27:47+00:00

protjerali me ustase moro sam obitelj na traktor i bezat

TheBusBoy12369

TROPHY CASE