Petar Radošević

Dad, husband, and soccer coach. Loves the craft of building software and mainly builds stuff with @elixirlang. Leading tech @workera_.

[Petar Radošević @wunki]

@antirez That is beautiful.

[Petar Radošević @wunki]

@artman The monday blues.

[Petar Radošević @wunki]

@badlogicgames @nateberkopec Have been thinking about this a lot lately. Maybe starting small with a blogging network.

[Petar Radošević @wunki]

@catalinmpit 👋 Based in Netherlands

[Petar Radošević @wunki]

My friend @WdeB released a book! So proud of him, go read it, designer or no designer, it will make you a better builder:

https://t.co/ll37dJlc6Q

[Petar Radošević @wunki]

@MartinSosic @SystemCrafters will keep you posted!

[Petar Radošević @wunki]

GitHub user from almost day one (#825), and I share Mitchell's frustration. Scale and slop are blamed, but it's the enshittification eating the whole web.

[Mitchell Hashimoto @mitchellh]

Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. https://t.co/DQDemHdytV

[Petar Radošević @wunki]

@signulll Hygiene became a lot more important so we standardized and formalized how we use Linear across every team.

Post that, I have my "Marie Kondo" agent running daily making sure that everything stays organized and clean.

[Petar Radošević @wunki]

@housecor System design. Not only does AI suck at it, but you need it for it to work well.

[Adam Jacob @adamhjk]

Bullshit. Winning teams have the psychological safety required to win - not because they coddle each other, but because they trust each other to perform, and hold each other accountable. It takes a *very high* degree of psychological safety to do that.

Don't forget the *actual definition* of psychological safety: the shared belief that the environment is safe enough to take personal risks. Everything about building winning teams is helping people get comfortable taking more risk - with the product, with their career, with their relationships to each other.

What those teams aren't is easy to build, or zones of swaddled comfort where nobody does a bad job and everyone gets praised. High performance machines care about psychological safety *because* they care about winning. You have to build honest, real trust - not the kind that comes from telling folks what they want to hear, but the kind that comes from *telling the truth and doing what you say you will do*. Then being judged on the outcomes of your choices.

I get that it's popular right now to say shit like this, but it's just bad advice. Even they don't actually believe it when you hear them talk about how people should behave.

[Petar Radošević @wunki]

@wesoudshoorn Ignore the haters. Praise to the builders.

[Petar Radošević @wunki]

@zeeg @viggy28 Agree, you can feel that it was built with care and thought

[Petar Radošević @wunki]

@wesbos @typecraft_dev haha, being Dutch, this was the first time I realized this, gave me a chuckle

[Petar Radošević @wunki]

@GergelyOrosz It may be that over time, you have internalized the phrasing and you recognize it more now 🤷

[Petar Radošević @wunki]

AI makes bad architecture fail faster. Clean abstractions aren't optional. Without them, the mess compounds at machine speed.

[Petar Radošević @wunki]

@zeeg Same! For our company I built Ampi, a Slack bot which has access connectors (Linear, Sentry) and Vaults.

Vaults are SQLite databases with proprietary data which have deep search (modeled after qmd from Tobi) and their own manifest (instructions for Ampi on how to use them).

[Petar Radošević @wunki]

i have a friend that had access to mythos

he went from being single, to retired and married with 5 kids in two weeks. what a model.

[Petar Radošević @wunki]

@badlogicgames Love it, sounds you found a great home for yourself and Pi

[Petar Radošević @wunki]

@thdxr go slow to speed up