James Hickey 🇨🇦👨‍💻

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

Second #csadvent entry today is from @jamesmh_dev: "Blazing-Fast Analytical Queries With .NET & PostgreSQL" - jamesmichaelhickey.com/analytical-que…

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

"Use X because it's more performant than Y." Which is true by one nanosecond... and you're building a CRUD app that has 5 users.

@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 jamesmichaelhickey.com/stop-pretendin…

@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.

What Are Domain-Driven Design Aggregates? by @jamesmh_dev 👉jamesmichaelhickey.com/domain-driven-…

99% of the content you see about domain-driven design is wrong. Stop pretending to do #DDD. jamesmichaelhickey.com/stop-pretendin…

dev.to/jamesmh/databa… #database #PostgreSQL #coding

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! jamesmichaelhickey.com/database-index… #softwaredevelopment #databases #sql

🔧 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 dev.to/jamesmh/high-p…

@mikecedev Thanks!👍

This looks pretty cool: "Coravel: a near-zero config .NET Core library that makes Task Scheduling, Caching, Queuing, Mailing, Event Broadcasting (and more) a breeze." docs.coravel.net @jamesmh_dev

Are you are .NET developer? You might like this article I wrote 👍 Let me know what you think! jamesmichaelhickey.com/top-dotnet-blu… #dotnet #csharp #softwaredevelopment

@_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...

@jamesmh_dev I agree with the rest of the points but the commentary on Tasks, Parallel and HttpClient is straight-up harmful.

Wrote a thing for #dotnet developers: jamesmichaelhickey.com/top-dotnet-blu…

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

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.

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?

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…" builtwithdot.net/project/203/co…

@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).

Is it just me or is Domain Driven Design (DDD) the one unassailable habit that almost everybody loves, and nobody criticizes? It's more or less responsible for microservices and other overcomplicated approaches, but people don't seem to question the wisdom

Check out @nickchapsas video on using the Coravel scheduling library by @jamesmh_dev buff.ly/3w44kXN

"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." cutlefish.substack.com/p/tbm-268-goin…

Weekly Dev Tips: Boundaries with guest James Hickey @jamesmh_dev bit.ly/3RNiOE2 #DDDesign #SoftwareDevelopment #SoftwareArchitecture