Rico Fritzsche

Building FACTSTR, a facts-first event store for command-context consistency | Helping other businesses implement modern development approaches & agentic coding.

[Rico Fritzsche @codewithrico]

Why Your Software Projects Fail: A Hard Truth Most Teams Ignore

The excitement of a new project: The team gathers, technical terms fly around, and everyone is eager to decide on frameworks and architecture.

Sound familiar?

[Rico Fritzsche @codewithrico]

If software is used through Commands and Queries, why attach those interactions to a centralized object model? The interaction can become the starting point, with context built locally from the facts required for that decision. #programming #ccc #ddd

https://t.co/D2ArkCdEXp

[Rico Fritzsche @codewithrico]

Domain Capabilities are autonomous internal processing units that encapsulate one specific business responsibility of the domain.
 Each capability owns the complete decision process for one domain request. https://t.co/xpkBdX9Trf

[Rico Fritzsche @codewithrico]

#eventsouring is an approach to persistence where every change in application state is recorded as an immutable event, rather than overwriting state in place.

Instead of storing the latest snapshot of each object, an event-sourced system stores a sequence of events that describe all state changes.

[Rico Fritzsche @codewithrico]

Consistency is managed per command, based on the context that command cares about.

#eventsourcing #eventmodeling #dcb

[Rico Fritzsche @codewithrico]

Stop thinking in CRUD.

It’s how we used to build apps:
•Model the data
•Add tables
•Expose endpoints
•Done

But CRUD flattens everything into database ops, event when it isn’t.

Pause a subscription? → Not an update
Reject a delivery? → Not a delete
Approve a refund? → More than a flag flip

We’re not building forms for data entry anymore.

What should we be doing instead?

✅ Automating behavior
✅ Tracking decisions
✅ Connecting workflows

The real world doesn’t CRUD.

So why should your code?

💬 Curious? I wrote more about this → https://t.co/vMyKZxzIs0

📷 Image credit: Nadezhda Kozhedub (iStock)

[Rico Fritzsche @codewithrico]

Great insides!

https://t.co/58IoJdCDou

[Rico Fritzsche @codewithrico]

Are you solving real problems, or engineering for imaginary scenarios?

Over-engineering is not "future-proofing"! It's the quickest path to unnecessary complexity, wasted effort, and frustrated teams.

Instead, focus relentlessly on what's right in front of you: the real challenges your users are facing today.

- Don’t optimize prematurely; optimize when your data shows a clear bottleneck.
- Avoid abstracting too early; solve today's concrete problem first.
- Let real user feedback guide your architecture, not theoretical perfection.

What's your approach to avoiding over-engineering on your team? How do you keep complexity under control while staying ready for growth?

https://t.co/arjxyxsIBZ

[Rico Fritzsche @codewithrico]

Real-world software has taught me that pragmatism beats dogma. We should focus on delivering business value, keeping things simple, and only introducing complexity (like abstractions) when proven necessary.

Thoughts?

[Rico Fritzsche @codewithrico]

https://t.co/R0lBcaq57x

[Rico Fritzsche @codewithrico]

I've been in the software business for about three decades now. That's long enough to see all sorts of trends come and go.

I feel that the industry has lost sight of what is truly important. Instead of solving real problems in a simple way, we keep piling on new frameworks and buzzwords.

We seem more interested in following the latest fad than in producing software that helps people and businesses.

Your thoughts?

[Rico Fritzsche @codewithrico]

https://t.co/R0lBcaq57x

[Rico Fritzsche @codewithrico]

Why Your Software Projects Fail: A Hard Truth Most Teams Ignore

The excitement of a new project: The team gathers, technical terms fly around, and everyone is eager to decide on frameworks and architecture.

Sound familiar?

[Rico Fritzsche @codewithrico]

@PLBompard Location intelligence for operational efficiency.

https://t.co/OIpdpND13K

[davidfekke @davidfekke]

Mastering PostgreSQL Row-Level Security (RLS) for Rock-Solid Multi-Tenancy by @codewithrico in @gitconnected https://t.co/yG5lqhyFFf

[polyglotengineer @polyglotengine1]

Mastering PostgreSQL Row-Level Security (RLS) for Rock-Solid Multi-Tenancy by @codewithrico in @gitconnected https://t.co/RnAcTzB64w

[Rico Fritzsche @codewithrico]

https://t.co/OUpgw7HndF

[Rico Fritzsche @codewithrico]

https://t.co/gzn3Sdo7y0

[Rico Fritzsche @codewithrico]

Rust’s Secret to Safer Concurrency: Practical Immutability Explained

Rust makes immutability the default, guiding developers to clearer logic and safer concurrency by design:

- Explicit mutability prevents accidental bugs.
- Pure functions and immutable data simplify testing and debugging.
- Clear data flows make concurrent code straightforward and performant.

Discover how Rust’s immutability makes your system simpler, safer, and more maintainable.

I'd love to hear your perspective. Please share your experiences below!

[Rico Fritzsche @codewithrico]

@_trish_xD Azure since 2010 😎

[Rico Fritzsche @codewithrico]

https://t.co/i2TzTMYYkQ

[Rico Fritzsche @codewithrico]

If there's one thing I wish I'd known earlier, it's that you can't wait for the perfect. There's no perfect time, no perfect code, no perfect idea. You need market feedback. You need people to pay for your product or service. That's how you learn what matters.