Today, I decided to drop a 💣 and write my thoughts on why senior devs, tech leads and architects are afraid to code. Read more and send your feedback in the comments.
Strona głównaUżytkownik
oskar-at-net | użytkownik
Nazwa:
oskar-at-net
Punkty:
2 189,8
Ostatnio widziany:
282 dni, 16 godzin, 46 minut
temu
Zarejestrowany od:
30 listopada, 2011
dotnetomaniak.pl
![How to create a custom GitHub Action? - Oskar Dudycz]()
![Memoization, a useful pattern for quick optimization - Oskar Dudycz]()
![How using events helps in teams' autonomy - Oskar Dudycz]()
![How to enhance and configure your site search with Algolia? - Oskar Dudycz]()
![Events should be as small as possible, right? - Oskar Dudycz]()
![How to create projections of events for nested object structures? - Event-Driven.io]()
![How to get started with Open Source? - Oskar Dudycz]()
![How to successfully do documentation without a maintenance burden? - Oskar Dudycz]()
![How money in Cloud impacts Architectural decisions? - Oskar Dudycz]()
![Can command return a value? - Oskar Dudycz]()
![CQRS facts and myths explained - Oskar Dudycz]()
![Why Partial is an extremely useful TypeScript feature? - Oskar Dudycz]()
![How to set up a test matrix in XUnit? - Oskar Dudycz]()
![What's the difference between a command and an event? - Oskar Dudycz]()
![Saga and Process Manager - distributed processes in practice - Oskar Dudycz]()
![What if I told you that Relational Databases are in fact Event Stores? - Oskar Dudycz]()
![What texting Ex has to do with Event-Driven Design? - Event-Driven.io]()
![Sociological aspects of Microservices - Oskar Dudycz]()
![How (not) to cut microservices - Oskar Dudycz]()
Sztuka programowania 1084 dni, 17 godzin, 39 minut temu 144 źrodło rozwiń
Today I'm sharing a sneak peek of our dev/docs process at Event Store. I'm doing that on the practical example of the custom Github Action that cherry-picks pull request commits to the different (e.g. release) branches to keep them in sync.
Sztuka programowania 1091 dni, 17 godzin, 35 minut temu 21 źrodło rozwiń
Memoization is a simple programming pattern that can be useful for quick code optimization. It makes sure that the function logic is called only once and then remembered result is returned. Read more and see practical samples in my latest article.
Sztuka programowania 1098 dni, 17 godzin, 35 minut temu 100 źrodło rozwiń
Pragmatic about programmingStartCategoriesAboutContact🇵🇱 oskar dudyczEvent Sourcing Autonomy is the Holy Grail for teams management. At least that’s how it’s perceived. It’s not easy to get the right balance. In this post, I'm talking about inverted Conway's law in a good sense. I’m explaining how doing event-based systems can help in running autonomous teams.
Architektura 1104 dni, 17 godzin, 40 minut temu 46 źrodło rozwiń
This week I'm continuing the documentation topic. I'm giving insight on how we're using Algolia in Event Store for advanced search in our docs. I explained the whole flow with samples scraping the data and automating it with Github Actions.
Events should be as small as possible, right? It's not so simple as it may sound. If you take this principle literally, then it may get you in serious troubles. Why? Read more in my latest post.
Architektura 1119 dni, 15 godzin, 46 minut temu 72 źrodło rozwiń
Events projections may get tricky and complicated. I decided to tackle one of the non-trivial cases in my new blog post. I wrote about how to create projections of events for nested object structures? Comments are welcome!
Architektura 1125 dni, 17 godzin, 29 minut temu 41 źrodło rozwiń
As you may know, I’m an active Open Source contributor. I decided to write a set of thoughts and suggestions based on my experience on starting your journey with Open Source.
Sztuka programowania 1125 dni, 17 godzin, 29 minut temu 41 źrodło rozwiń
Developers like to complain about the lack of documentation. They complain even more when they have to write it. I gathered my advice on how to successfully do documentation without the maintenance burden.
It’s intriguing how our perspective on software development changed in the last few years. We transformed from the on-premise age to the cloud era. Cloud is no longer a “buzz word”. I wrote my (not) obvious observations on how money in Cloud impacts Architectural decisions.
Last week I busted common myths and explained facts about CQRS. Today I’ll continue my effort. I tackle one of the most common questions about CQRS: “Can command return a value?”.
Architektura 1153 dni, 17 godzin, 12 minut temu 121 źrodło rozwiń
I explained in my recent article the facts and myths of CQRS. If you heard you need: - 2 databases - to use a messaging queue - to be facing Eventual Consistency - use it with Event Sourcing and it's hard to apply and complicates the architecture. Then you should definitely read this post!
Architektura 1161 dni, 17 godzin, 33 minuty temu 110 źrodło rozwiń
Thanks to my colleague, I learned this week why Partial
Sztuka programowania 1167 dni, 16 godzin, 59 minut temu 73 źrodło rozwiń
Setting up the test matrix in XUnit is not so easy as it might seem. This summarises my struggles with adding System.Text.Json support to Marten and setting our test matrix to run the whole test suite for both serialisers.
Sztuka programowania 1171 dni, 16 godzin, 38 minut temu 46 źrodło rozwiń
Answering the question "What's the difference between a command and an event?" is not so obvious as it may seem. Fact vs Intent is not explaining everything. I went through the different aspects of this distinction in my new blog post. I also explain the consequences of those considerations.
Architektura 1175 dni, 16 godzin, 49 minut temu 95 źrodło rozwiń
If you want to know : - why I think that distributed systems are like Rocky Balboa. - the difference between Saga, Process Manager and Choreography. Here's my take on that together with the real-world samples.
Programowanie rozproszone 1182 dni, 16 godzin, 46 minut temu 148 źrodło rozwiń
Are you one of those people saying that Event Sourcing is detached from reality? Do you think that you don’t need such extravagance, as you have relational databases? Why go wild? What if I told you that relational databases use the Event Sourcing approach?
Bazy danych i XML 1189 dni, 16 godzin, 38 minut temu 53 źrodło rozwiń
What texting Ex has to do with Event-Driven Design? It appears that more than we would think. Read more in the blog post.
Architektura 1196 dni, 16 godzin, 28 minut temu 34 źrodło rozwiń
From my experience, sociological aspects of working in a distributed microservices environment give more risks than technical mistakes. Last week I technical part, this time I will talk more on how our non-technical decisions can impact our project. Read more on "Hype Oriented Programming", "Conway Law", "Cognitive Load".
Architektura 1202 dni, 6 godzin, 41 minut temu 43 źrodło rozwiń
These days dunking on #Microservices is getting easier, so I did it. I provided my rational take on how to (not) cut your system into microservices.
Architektura 1210 dni, 16 godzin, 35 minut temu 83 źrodło rozwiń
Polecamy
Najaktywniejsi w tym miesiącu
Nadchodzące wydarzenia
.Net
.net core
architektura
ASP .NET
asp.net
Asp.Net Core
ASP.NET MVC
Azure
C#
C# .NET
certyfikacja
certyfikat
cloud
csharp
daj sie poznac 2017
Daj się poznać
Daj Się Poznać 2017
dajsiepoznac
DDD
docker
dotnet
dsp2017
egzamin
Entity Framework
F#
git
JavaScript
jQuery
konferencja
Linq
mvc
MVVM
Narzędzia
performance
podcast
praca
programowanie
SharePoint
Silverlight
SQL
sql server
TDD
testy
Visual Studio
WCF
Windows
windows phone
WPF
Wzorce projektowe
Xamarin