James Hickey 🇨🇦👨‍💻

Principal Engineer, Microsoft MVP, OSS maintainer Author 💗= #eventsourcing, #ddd, #dotnet, #coffee

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

2018: "How to split your monolith into microservices"

2023: "How to consolidate your microservices back into a monolith"

[C# Advent @CsAdvent]

Second #csadvent entry today is from @jamesmh_dev: "Blazing-Fast Analytical Queries With .NET & PostgreSQL" - https://t.co/E6lxKKmyw3

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

@codeopinion It better be using a repository and a domain service or else.

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

@1ovthafew @maciejwalkowiak That article wasn't "do this all the time". It was "here's what aggregates are".

We're actually on the same page. I literally just wrote a rant article that says what you just said lol

https://t.co/ra7yqXmBrY

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

@1ovthafew @maciejwalkowiak I think we're on the same page here. The idea is to think about behavior before building your database model. Not ignoring database models.

Ex. should each user have 1 address? Or many? Keep historical addresses? You can't know unless you figure out the required behavior.

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

99% of the content you see about domain-driven design is wrong. Stop pretending to do #DDD.

https://t.co/ra7yqXn9hw

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

https://t.co/k2545FnWaE

#database #PostgreSQL #coding

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

Wrote about database indexes for saas developers. It's easy to get started with ORMs and skip learning about important database topics that really make a big difference - esp. when your user base begins to grow!

https://t.co/9An6xFXQ5s

#softwaredevelopment #databases #sql

[The .NET Dev @TheDotNetDev]

🔧 Learn to create high-performance CRON jobs in .NET using Coravel, Dapper & more. Boost your system's efficiency step-by-step. 🕐🚀

{ author: @jamesmh_dev } #DEVCommunity #dotNET
https://t.co/O3eJ3Fmlrf

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

@mikecedev Thanks!👍

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

Are you are .NET developer? You might like this article I wrote 👍 Let me know what you think!

https://t.co/xLch4lrmJS

#dotnet #csharp #softwaredevelopment

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

@_neonsunset I used to think the same thing. "Ah it's so easy, why can't everyone just do what I do?"

I've come to find through working with lots of other smart, experience people that they often get async wrong too...

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

Wrote a thing for #dotnet developers:

https://t.co/xLch4lqOUk

[The Modern .NET Show @dotNetCoreShow]

A fantastic source of advice for fellow .NET devs can be found in the tweet below 👇

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

Some (many?) problems can be solved by knowing SQL and how to write decently performing queries.

You might not need that new shinny new tech that disrupts (in a bad way) your entire engineering team and velocity after all.

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

Simple software architecture leads to simple PRs/changes leads to more (developer/product) velocity and reliable running software.

Complex software architecture leads to complex PRs/changes leads to less velocity and reliable running software.

Thoughts?

[BuiltWithDot.Net @BuiltWithDotNet]

Developer tool built with .net core and c# by @jamesmh_dev. "Coravel Pro is an admin panel for .NET Core.More specifically, it's a suite of backend admin tools that extended the open source Coravel library with many additiona…" https://t.co/ob4glMebvo

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

@CFDevelop My experience: design patterns implemented are vastly more complex than the business problems at hand 🤔

#ddd helps when dealing with *really* complex stuff, but more often than not solutions are convoluted. Mostly agree here. Most systems I've seen don't need it (but did it).

[Particular Software @ParticularSW]

Check out @nickchapsas video on using the Coravel scheduling library by @jamesmh_dev https://t.co/29pBXOBFxU

[James Hickey 🇨🇦👨‍💻 @jamesmh_dev]

"In short, the current emphasis on "going deep" and "getting into the details" is a reaction to an overreaction and overstretching of the org chart. So, it is time for a reset without over-reacting again."

https://t.co/hKcrBGOtrK

[Weekly Dev Tips @weeklydevtips]

Weekly Dev Tips:
Boundaries with guest James Hickey @jamesmh_dev https://t.co/MDrROYbK0A #DDDesign #SoftwareDevelopment #SoftwareArchitecture