Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
norden.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Moin! Dies ist die Mastodon-Instanz für Nordlichter, Schnacker und alles dazwischen. Folge dem Leuchtturm.

Administered by:

Server stats:

3.4K
active users

norden.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#productdevelopment

1 post1 participant0 posts today
Public
Krisztina Hirth

Call to action, attendees of flowcon.io/ and anyone having a good idea 💡

I am looking for** interesting problems, goals** which can be used for the Impact Mapping workshop.
The method works with any kind of goals of a company or a team or personal. The example should be one around product development and it should be easy to relate to.

I usually describe an imaginary company and problem but why only because I need some time to prepare everything.
#productDevelopment #flowcon

Speaker Krisztina Hirth Staff Architect at PayFit 1-2 April 2025, Paris Impact Mapping Workshp "Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and stakeholders visualise roadmaps, explain how deliverables connect to user needs and communicate how user outcomes relate to higher-level organisational goals." (source: https://www.impactmapping.org/) Impact Mapping is a unique technique (described in a book by Gojko Adzic) which enables every organisation or team facing a new problem, a new challenge to not only find unexpected ideas but also to make sure that these ideas address those challenges instead of fulfilling other interests. By following the steps, Impact Mapping helps find ways to experiment, innovate, and compare possible ideas by focusing on the outcome rather than the output. It gives the group the means to verify the progress the whole time - to fail fast or stop investing because they have reached their goal. In this workshop, we will discuss and map a fictive problem. At the end of the workshop, you will know how the technique works and when to use it, how much fun such Impact Mapping can be and how creative people are when the only constraint is time :)
Public
Yuna

Product vs Tech: The Endless Battlefield

The war between Product & Engineering? It's not inevitable. It's a choice. A choice to overload engineers with business problems instead of letting them solve technical ones. A choice to force cross-functional teams without aligning timelines.

And the result?
❌ Slow product development
❌ Fragile systems
❌ Burnt-out engineers
❌ Sky-high costs

We tell engineers to "understand the business".
But we never ask business to "understand engineering".

We train engineers to sell priorities instead of owning their craft.
Software development becomes a negotiation instead of an engineering discipline.

And then we wonder why systems rot. 🤦‍♂️

"You Build It, You Run It".
"You Code It, You Ship It".

Buzzwords that actually mean:
🤑 "You Do Everything, We Cut Costs."

Would you hire an musician to cook, clean, and build your house?
No? Then why expect engineers to be full-stack, infra experts, DevOps, security pros & business strategists simultaneously?

💡 Specialization isn't old-fashioned. It's necessary.
💡 Engineering, UI/UX, Infrastructure. They are services to each other.
💡 Stop mixing worlds. Let experts master their craft.

🛑 Hiring isn't broken because of a "talent shortage".
It's broken because of delusional expectations.

You want quality products?
✔ Let engineers engineer.
✔ Let designers design.
✔ Let infrastructure teams handle infra.

If people aren't drowning in work that isn't theirs, they will naturally grow beyond their roles.

But force it?
You'll get:
❌ Burnouts
❌ Legacy code
❌ A team that stops caring

I grew up in tech step by step. The enforcement to do everything at once blocked & blinded me for years.

Fix the environment or enjoy the chaos you created. Your choice. 🎤

a hiring manager holding a paper with a drawn unicorn, standing next to a simple cart while rejecting fast-running horses that could also do the job
#Engineering#ProductDevelopment#TechLeadership
Public
Yuna

Companies Fail Tech Talent
Growth Needs Patience, Not Force

Telling tech people to "learn on the job" while drowning them in tasks is like giving someone a book 📖 and setting their chair on fire 🔥.
Spoiler: they won’t finish the book.

👨‍💻 Non-tech people evolve freely.
⏳ Tech people? Trapped in deadlines, ticket counts, and feature delivery. No time. No space. No iteration.

⚙️ "Agile", "Self-organized", "Cross-functional"… Great buzzwords. But without leadership, it's just a Buzzword Bingo 🎲.

🎓 What's the point of training when there's no time to apply it? Like learning to weld while your house is still made of straw.

🔧 Fix it:
✅ Treat tech as a service, not a feature factory.
✅ Let them own the tech product.
✅ Request technical, not just business-driven, features.
✅ Give space for scalability & maintainability.
✅ Allow growth to happen naturally, not by force.

💡 Make tech people proud of impact in their field, not just yours.

Men sitting on a burning chair, trying to read a book
#TechLeadership#EngineeringCulture#productdevelopment
Public
Yuna

💡 Resilience. Reliability. Reusability.
Always wrong investments…

If you think bugs, tech debt & maintenance are “normal,” do the world a favor: resign. You’re part of the problem.

MVP/PoC ≠ Done.
It’s a candle - fragile, short-lived.
Real engineering = the light bulb: robust, lasting.

But devs & managers stop at "it works."
Why? Because real engineering demands more.
More thinking. More iterations. More uncomfortable truths.

💀 Fragile systems = endless maintenance.
💀 Seniors wasted on babysitting.
💀 Knowledge stagnates.

🔍 Product & Tech - Two worlds, but only one is visible.
Mixing them = slower, costlier, dumber.

🔥 Resilient systems don’t break.
🔥 Reliable systems don’t fail.
🔥 Reusable systems don’t get rewritten.

Start building like you mean it.

Pigs proudly celebrating their straw triumph while the inevitable storm begins its demolition
#Engineering#TechDebt#Resilience
Public
Yuna

💡 Whole Company on a Raspberry Pi Cluster

Once, I had a team that took down a monolith.
Not with brute force, but with precision.

In months, we erased 90% of the code—no migrations, no breakages.
Stripped the bloat, cut dependencies, and ended up with something wild:

🚀 A Raspberry Pi cluster running the entire system.
Five tiny machines. Millions of requests.
Features built in ~90 minutes, not months.
No "senior" devs needed. No we needed. Pure engineering efficiency.

PROD needed bigger iron for scale, but the lesson stuck:
✅ Less code → Less complexity → Less maintenance.
✅ Running 10+ years - never turned into legacy.
✅ PMs even tweak features via ugly but effective XML (DX > UX 😅).

This is real engineering.

4 Raspberry PI computer as a cluster. Connected through a switch
#DevOps#EngineeringExcellence#Minimalism
Public
Leonid

Warum fokussieren sich Firmen bei Agilität so stark auf „wie“ und nicht auf „was“? Heute wieder Unternehmen kennengelernt, bei denen die Anforderungen vom Product Owner kommen und sich niemand dafür interessiert, wie sie/er darauf kommt. Und ob die Ideen in einer sinnvolle Richtung zeigen oder eher Verschwendung erzeugen.

Scrum scheint Product Discovery auch nicht vor so langer Zeit entdeckt zu haben..

scrum.org/resources/blog/produ

Scrum.orgProduct Discovery for Scrum TeamsScrum Tools, Part 2: From Design Thinking to Lean UX to User Story Mapping
#agile#productdevelopment
Public
Yuna

Struggling in product development is trendy now, so why bother improving? Let’s embrace the mediocrity. It’s mainstream. A circus of borrowed frameworks, questionable dependencies, and collective delusion. If we can’t get our own code right, what makes us trust everyone else’s? Same with business processes. Are we keeping ourselves randomly busy? A small hint: Using fewer thing means also fewer headaches 😇 Get back to basics.

Witness the pinnacle of overreaction—a fly survives, yet the house crumbles. A masterpiece of misplaced effort and unintended consequences. Relish the irony
#KISS#YAGNI#DRY
Public
Leonid

Wenn unfähige Programmierer sich an die Arbeit machen, kommt so ein Müll heraus: Ein Menü bestehend aus Buttons. Vollhonks. Usability aus der Hölle, man kann keinen "Link" im neuen Fenster öffnen.

#ux#productdevelopment
ExploreLive feeds
About