Got the time header image

Got the time


When modeling time, we can use a batch job-oriented approach, or what I like to call the ticking time bomb model. Or we can flip the responsibilities and use messages for our future selves to achieve the results more efficiently and effectively. Let's see how to model time using NServiceBus sagas and messages.

Continue reading...

Lifehacking 101: journaling as a continuous learning process


Brainstorming alone is painful for me. Questions like 'what can I improve?' or 'what's going wrong?' hardly get answered. Journaling is helping me in shaping what's next.

Continue reading...

Lifehacking 101: without data we're blind


Your day is a mess. By the end of the day, the predominant feeling is that you probably got nothing done. Before trying to address any problem, it's essential to understand which issues we're facing.

Continue reading...

Lifehacking 101: I'm bad at to-do lists, now what?


When it comes to to-do lists, I'm terrible. How do I get better at managing my activities and time? Context switching seems to be the real culprit. I'm pretty sure I won't get any better at to-do lists.

Continue reading...

Please welcome Attribute Routing to ServiceComposer


Attribute routing is a great MVC feature. However, endpoint routing is the game-changer. Library authors can plug in custom route handling and benefit from all the attribute routing goodies. It's easier than ever.

Continue reading...

I'll be back


Time from the perspective of systems design has many nuances and complexities. There are clock drift issues and design issues related to modeling the passage of time. Shall we model the passage of time as a clock does?

Continue reading...

Do not trust the user mental model: Model behaviors, not data


When designing systems, we say how important it is to model the system following the user mental model. Nonetheless, it works. However, it's not necessarily always the right choice.

Continue reading...