Marin Peko

Passionate Software Engineer

[Marin Peko @peko_mp]

@KoalaQuillHQ Well that's where the AI agent's intelligence comes in. If you set up access rules well, this won't happen.
So specifically for agents accessing servers or cloud environments, you create users and roles for those agents and limit their actions.

[Marin Peko @peko_mp]

Every business has a “where.” So why do we still understand so much of our data through spreadsheets?

I wrote about why every business will eventually need a map - and made an example with https://t.co/1xxKHSfZ2I.

https://t.co/Ngby58qxTQ · https://t.co/0KgYSySBIM

[Marin Peko @peko_mp]

Mappt: https://t.co/0KgYSyT9yk

[Marin Peko @peko_mp]

Medium post: https://t.co/Ngby58qxTQ

[Marin Peko @peko_mp]

@layerlens_ai @OpenAI @xai @Kimi_Moonshot @AnthropicAI Putting my vote behind Anthropic Opus 4.8 for this one ⚽🤖

[Marin Peko @peko_mp]

@lemire @dendisuhubdy What's the difference between permuted and linear congruential generator? Latter is available in C++

[Marin Peko @peko_mp]

@mazeincoding Not surprised at all... AI in coding is very helpful to people who already know how to distinguish between good and "evil"

[Marin Peko @peko_mp]

@TAbrodi I would actually vote against using named return parameters: explicit > implicit

[Marin Peko @peko_mp]

@meijer_s Tailwind actually made frontend work way more fun for me - I get to focus on the product and engineering part of the project, instead of spending time naming classes, organizing CSS files, or jumping back and forth between HTML and stylesheets.

[Marin Peko @peko_mp]

@robj3d3 Absolutely agree. Reviewing PRs made by engineers extensively using AI is painful. Lots of meaningless code, lack of greater picture of the software...

[Marin Peko @peko_mp]

@windsurf_ai - this is something you could level up when generating tests:

• Simulate actual usage
• Validate failure paths
• Catch regressions

We don’t just want coverage — we want confidence.

[Marin Peko @peko_mp]

When your AI pair programmer writes tests that confirm water is wet 💧

"Let's assert that the thing we just hardcoded... is the thing we just hardcoded."

Thanks, robot. Truly groundbreaking.

[Marin Peko @peko_mp]

And then someone drops this into a PR like:

"Added unit test coverage 🚀"

Meanwhile the test:
✅ Confirms structs still hold values
✅ Assures hardcoded strings remain hardcoded
10/10 coverage, 0/10 value.

[Marin Peko @peko_mp]

🧠 Please, don’t create interfaces prematurely in Go.
Large and bloated interfaces not only add complexity—they leak implementation details and lead to fragile tests.
Build interfaces when needed, not "just cuz".
#golang #SoftwareEngineering

[Marin Peko @peko_mp]

@foonathan CRUXTable - Create Read Update X Table

[Marin Peko @peko_mp]

@mlyar @BarryRevzin or simply switch to rust :)

[Marin Peko @peko_mp]

@odoruhako @BarryRevzin ok that's true. Thanks

[Marin Peko @peko_mp]

@NoahAttwood nice work @NoahAttwood but having a compile time specified expression is the same as having a single function receiving an object and checking it's data members in an if condition, right? I guess there is no need to build the whole tree then

[Marin Peko @peko_mp]

@knatten https://t.co/3TCz2zIxWM looks neat to me