oskardudycz

oskardudycz, 2 days ago to random

Some time ago, I wrote that I won't use .NET #Aspire for now, and now I checked it again. Result? It got better! Now I can finally use it! 😅 I faced some issues again, but non-blocking this time. It's clearly visible that the team is motivated and working hard to improve it.

I was really impressed by the response time, discussion on Discord with @davidfowl and quick turnaround for the issues I found. Much appreciated!

1/

oskardudycz, 7 days ago to random

I see the growing dangerous cult of pseudo-science. Many YouTube channels, and podcasts are inviting scientists that are not talking about their field of science study but their field of personal interest.

That’s especially dangerous, as many viewers are projecting authority in one field, assuming that the science title gives them more knowledge or rights to make bold claims.

That’s obvious charlatanry and dangerous, as it creates a mixture of commonalities and randomly picked science.

oskardudycz, 13 days ago to random

Now, the question is, what programming language is that? 🤔 😎

oskardudycz, 15 days ago to random

I just updated my #EventSourcing self-paced kit for .NET. You don't know what's that? I have a bit of a philanthropic rule: whatever code I do for my paid workshops, I'm open-sourcing it.

All backing exercises for my workshops are available for free, and you can try to do them on your own. They all have tests that will tell you if you made them well, plus some recommended solutions.
1/

khalidabuhakmeh, 29 days ago to random

Time to start up a VM, in an Emulator, in a Simulator, in another VM, in a sandbox, in a simulator emulator.

oskardudycz, 1 month ago to random

Git is the base tool for us developers, but it’s not user-friendly. Frankly, to this day, I'm sometimes scared using it in the console. I might be a noob, or I might be too lazy to learn it, but I think that's just not accessible. For instance, I was really scared to do interactive rebases in the console or even resolve merge conflicts without the UI tool. But now, happy end! I'm not scared anymore.

I’d like to give big KUDOS to LazyGit: https://github.com/jesseduffield/lazygit

1/

oskardudycz, 1 month ago to random

"I came here to get Rick Rolled, but ended up getting Dave Grohled"
True story!
https://www.youtube.com/watch?v=C5oeWHngDS4

oskardudycz, 1 month ago to random

Did you feel that you need to debug your mind? Did your (or your colleague's) biases impact your decision-making? How to improve it? How do you reason about the reasoning?

@noctovis shared with us practical thoughts and the results of their research backed by the history of her projects. She gave us the talk she gave as the keynote at NDC London 2024 as our #ArchitectureWeekly webinar. You can watch the recording now 👇

https://www.architecture-weekly.com/p/webinar-18-laila-bougria-debug-your

1/

oskardudycz, 1 month ago to random

Folks, I'd like to inform you that I'm no longer a Marten maintainer. As you know, sometimes in the project's lifetime, there's a moment when you need to settle things or make hard decisions. Unfortunately, the latter occurred here

I'm not happy that this is ending not as I hoped. Marten was a big part of my life: over 6 years as a contributor and over 5 years as a co-maintainer. Still, I'd like to thank @jeremydmiller and Babu for our past collaboration. I think that we built a unique tool.
1/

oskardudycz, 1 month ago to random

I really think that Event Sourcing, with its repeatable patterns and focus on business, can streamline development. Yet, learning it may be challenging. You need to learn both new approaches and tooling. That’s why I decided to publish Emmett to package safe defaults and my state-of-the-art. I don’t want to replace or compete with existing tooling but guide you through this journey.

1/

oskardudycz, 1 month ago to random

Have you heard about CRUD Sourcing, Property Sourcing or Clickbait Event? Those event modelling anti-patterns were the topic of my #KafkaSummit talk.

If you weren’t there, I prepared the page with all my articles on this topic. 🙂👇

https://event-driven.io/en/anti-patterns/

oskardudycz, 2 months ago to random

What's the most challenging in building Node.js or TypeScript applications? What's the most annoying for you or missing feature in current tools?

I have a few ideas on how to improve DevEx experience in #Emmett, but I wouldn't like to only base on my own bias. Any feedback counts 🙂

oskardudycz, 2 months ago to random

We're too often trying to show ourselves as busy bees. Sometimes it's a 21st-century fetish, sometimes it's accidental. In both cases, this can be dangerous as we may be putting pressure on other people who follow us. I wrote a short article on that for you and myself not to forget about that.

https://event-driven.io/en/keeping_overachieving_freak_on_a_leash/

1/

oskardudycz, 3 months ago to random

I want to introduce you to Emmett! Finally, I gathered the patterns around #EventSourcing and #CQRS I used last year and grouped them into a Node.js package.

Check the docs: https://event-driven-io.github.io/emmett/!

Why Emmett? Because I'd like to take your event-driven tooling back to the future!

The goal is to help reduce the boilerplate, enhance strong sides and help you skip common mistakes.

1/

oskardudycz, 3 months ago to random

I’ve made it! I taught bunch of folks how to build the worst Event Sourcing system at #NDCLondon. I hope that they won’t use any of those lessons! 😅

55 🟩, 25 🟨, and no 🟥! I thought that my lame jokes will offend at least a single person but didn’t make it. Yet, calling that a win!

Happy that I’ve made it as this is one of my hardest talks to give. As an introvert trying to be funny on stage is not easy. My adrenaline level jumped to the Himalayas and then reduced to Mariana Trench.

1/

oskardudycz, 3 months ago to random

Prepare 🍿 for the next epic idea from the .NET Team!
https://github.com/dotnet/aspnetcore/issues/53219

oskardudycz, 3 months ago to random

It always amazes me how easy it is to project our biases into general advice and best practice. It's hazardous if they're made into "just do X" or "don't do Y".

E.g. "just use trunk-base development", "don't do code reviews on feature branches". Is it really so easy? Is it "just"?

I remember trunk-based development done in SVN when code reviews weren't the norm. I don't regret that they're past.

1/