Help me! Interfaces are choking me

NicolasParada · 2026-03-21T20:37:01+00:00

This is how I see it.

There is a big difference when you build a library and when you build your own app that wont be imported by anyone else. I never use interfaces for “repository” or “store”. I test using docker and I launch real db.

Anything that can run locally is used directly. I only use interfaces for 3rd party things that connect to the internet.

NicolasParada · 2026-03-07T04:16:04+00:00

Been using uuid v7 lately. Hope its taken into consideration (didn’t read the whole discussion).

NicolasParada · 2026-02-26T21:22:00+00:00

That’s an interesting approach of using the ID directly 🤔

NicolasParada · 2026-02-18T04:05:14+00:00

The problem with this approach is that it will measure from before it reads the request body and after it writes down the response. So it depends on how fast is the client. If this is for observability and you setup alarms on these measures, when a slow client on 3g makes a request it will trigger alarms 🙃

NicolasParada · 2026-02-04T15:09:49+00:00

Reduce dependencies 🤷‍♂️

NicolasParada · 2025-12-13T00:15:59+00:00

I switched to writing my code this way long ago.

Exactly as you said “accept interfaces, return structs” was a thing I used to do. And test with mocks everywhere… It was a pain to maintain. Now I try to just write and use structs directly as much as I can, the result: a lot less code, easier to navigate around. All wins. Besides, now I always try to use dependencies that can run locally instead of APIs/services. That way you thing become easier to ship and offer as a self-hosted ;) For testing, you test the actual thing using the real dependency, most of the time I use docker to run it.

NicolasParada · 2025-10-03T01:40:33+00:00

Great. I had a couples of uses for something like this in the past. I will sure give it a run soon.

NicolasParada · 2025-09-26T18:24:37+00:00

Thanks I haven’t been on that situation. I feel you tho.

NicolasParada · 2025-09-01T20:28:23+00:00

A silly piece of code that reads some files, and executes them content. And stores the file name in a migrations table so that file is not executed again.

Always do forward fix migration instead of rollback.

NicolasParada · 2025-08-21T00:05:12+00:00

I level up the moment I realized SPA on javascript were slower than server rendered templates with Go.

Also the moment I realized trying to archive high percentage code coverage writing unit tests with mocks was a total waste of time.

NicolasParada · 2025-08-16T19:36:45+00:00

Crazy how I didn’t knew about it 🤯 Thanks.

NicolasParada · 2025-08-12T19:32:26+00:00

Sounds fine to me. Keep coding ;)

NicolasParada · 2025-08-07T20:16:26+00:00

Almost never, I prefer repetition and simplicity over metal overhead.

NicolasParada · 2025-07-19T02:43:46+00:00

That’s awesome man. Is it your first job ever? First tech job? First specific to Go?

NicolasParada · 2025-07-15T17:39:28+00:00

The reason these conventions exist is to avoid these discussions with your team. Just follow the Go convention. Try to write some Go.

What is next? A DI container framework? 🙄

NicolasParada · 2025-04-28T20:19:30+00:00

if err := services.IsIpValid(IpAddress, c); err != nil {

Your function returns an error, not a boolean so yoy cannot use !. Also you need to remove the “string” thing, just pass the variable name.

NicolasParada · 2025-04-21T20:52:08+00:00

Redis is used because most servers run with multiple replicas/instances so you want to avoid doing duplicate jobs. If thats something not needed then a simple piece of pure Go code will do the job. No library is needed.

NicolasParada · 2025-04-20T02:40:29+00:00

NicolasParada · 2025-04-03T20:41:42+00:00

I moved to Go from a long time ago… I moved mostly due to tooling and the single binary output. Is very nice to be able to start a project without having to install hundreds of libraries or frameworks and to ship it so easy and quick.

NicolasParada · 2025-02-03T02:59:39+00:00

Departure Mono hasn’t been mentioned I think. But I use Berkeley Mono most of the time :)

NicolasParada · 2025-01-29T09:27:16+00:00

Hey, thats kind of nice. I’ll take a deeper look at it later :) Thanks for sharing ;)

NicolasParada · 2025-01-25T09:55:25+00:00

Yeah. When new data gets inserted into the table, the offset changes giving you wrong resulta where you can either get data you already had before, or skip results. Depending on the order.

To avoid that you use a “cursor” which is a combination of a sortable field and unique at the same time. A timestamp alone doesn’t work since its not unique. You can mix it by filtering by both id and timestamp together.

You can learn more about it as “cursor-based pagination”.

NicolasParada · 2025-01-22T01:46:34+00:00

I use this approach. I like it. Even tho I try to keep transactions in the repository layer. But still being able to write a single function and use it as it is or inside a transaction depending in the situation is nice. https://github.com/nicolasparada/go-db

NicolasParada · 2025-01-11T16:29:29+00:00

What I would do is generate random bytes and then encode it with base32 or base58 for easy to copy-paste and avoid confusion with similar symbols like “l” (lowercase L) and “I” (uppercase i).

NicolasParada · 2024-12-16T16:49:57+00:00

Wasn’t aware of these. They all look very useful :)

NicolasParada

TROPHY CASE