Pragmatic tech leader

Brisbane, Queensland
Joined March 2019
The YABT is a unique project (though I'm biased as the creator 😀). It shows how to design a general-purpose document #NoSQL DB and how to code against it, applying #DDD and #CQRS in the #DotNET tech stack. Coming with a front-end and a pre-populated DB.
Want to learn how to build an awesome enterprise app in .NET from scratch? Join @_AlexKlaus as he guides you through the design and implementation of "Yet Another Bug Tracker" - a fun and practical project for this holiday season. 🎁

1
2
1,567
Alex Klaus retweeted
Build a new skill set in .NET & architecture this holiday season with the 'Yet Another Bug Tracker' series by @_AlexKlaus and RavenDB. This series will walk you through building a full-blown enterprise application on .NET. Click here: bit.ly/3GLuJMb #dotnet
1
2
486
Thanks to @kevin_chalet for providing OpenIdDict library used in the code examples. Kévin, I'd be glad to hear your feedback on the series if you have time.
1
1
2
315
The idea of phasing out modules in #Angular has been around since day 1. Finally, with v14 we're getting a hope 😀 Still not clear what pitfalls in DI resolution to expect and how to handle lazy loading...
With Angular Standalone Components, we don't need an Angular module to package coherent declarables. We can use an array of the exported declarables. This array then goes into Component.imports.
1
1
That's goood. A cheat sheet for simple & bullet-proof CSSing from @shadeed9 ishadeed.com/article/defensi…
2
It's a common sight these days - new projects with no problem definition but already with a budget for data scientists. Getting a budget for BAs, PO or devs is much harder than any AI-related field. And then analysis shows it's a non-ML task, PM has to utilse already hired folks
I've settled with Git around 10 years ago after many years of using SourceSafe, TFS, SVN and Mercurial. These days Git has been entrenched in devs mind to a point that an idea of using something else appears so surprising and revolutionary 😀
This Post is from an account that no longer exists. Learn more
I raise the notion of dropping the word "monolith" due to negative connotation in relation to architecture. It's a nudge to using "logical boundaries" and "bounded context" to provide more clarity. Instead of "Big Ball of Mud" say "mixture of bounded contexts" or "no boundaries"
A Monolith doesn't mean it needs to be a Big Ball of Mud. Most people equate a Monolith with a Big Ball of Mud because it's highly coupled and difficult to change. However, you can combat it by defining strict boundaries and logically decoupling. youtube.com/watch?v=VGShtGU3…