Damian Płaza
banner
raimeyuu.bsky.social
Damian Płaza
@raimeyuu.bsky.social
Problem Solver/Solution Problemer. Engineer, baptized in control engineering. Passionate about people, software design, and modeling. Functional-first thinker.
Big thanks for encouragement, @mathiasverraes.bsky.social 🙏

Session submitted 🚀
October 29, 2025 at 11:14 PM
Even though it might sound a bit weird, it is my "dream" to speak at DDDEU (or how they say - "it's on my bucket list")😅so definitely you enormously encouraged me, @mathiasverraes.bsky.social 🙏 along with @oskardudycz.bsky.social's "DO IT" 😅

I have some ideas, sourced from blogposts :-)
October 28, 2025 at 11:25 AM
@einarwh.bsky.social about "all models are equally wrong" and other proliferations of the original Box's quote - I like to "reframe" it into:

"All models are wrong (=imperfect)" and based on some observations - it invites differently to the whole journey 😅
October 28, 2025 at 9:21 AM
Hence deferring strategy to name "things" might be really desirable, as "naming is framing" - then "models" (of thinking) then are constrainted just by the act of "naming".

I tried to express some thoughts on that topic too talesfrom.dev/blog/the-amb...
The ambiguity of naming
Why naming is hard, and can even be dangerous?
talesfrom.dev
October 28, 2025 at 9:19 AM
We were taught to think about "models" in a technical terms, whereas in the context of "understanding things", what might be truly immutable, is understanding (we can get previous and current one?). And often, this "understanding" is framed by naming ⬇️
October 28, 2025 at 9:19 AM
Could you elaborate? 🙏
April 27, 2025 at 5:20 PM
In other words: don't try to decouple for the sake of "decoupling" but observe what pushes back attempts of this act and sends "diagnostic signals" suggesting that "keeping them together" is a natural trait?
April 3, 2025 at 9:30 PM