Jimmy Bogard

I find it relatively easy to build "modular monoliths" by starting from "vertical slices"[0] at the outset. Vertical slices being primarily a feature organization strategy scales well pragmatically over time, IME. So when first starting out, you can keep it simple and just one monolith and one unit of deployment, but keep everything separated into their own feature folders with common things in a `shared` folder. When you get further along, it is possible to consider splitting things out by feature teams (if that's what works best) and still keep one runtime (just enabling/disabling different features at startup). The common bits can eventually be moved into a package dependency and referenced. Separate features if they become large enough can also be moved into separate packages, but part of the same monolithic codebase. In some cases, it can be easier still and just ship the entire runtime as-is (without any additional work to enable modularity) and simply route different endpoints (e.g. https://feature1.domain.com -> node set 1, https://feature2.domain.com -> node set 2) so you still have the option to monitor and scale the features differently based on their load profile and needs. This works great as long as cold starts are not a big concern (thereby adding a requirement for minimizing package size). I find this particularly easy on AWS, especially when deploying with Copilot CLI[1] because it makes it relatively easy to just route different sub-domains to…

Every time I've worked on a project that used AutoMapper, I've hated it. But I'll admit that when you read why it was created, it actually makes sense: https://www.jimmybogard.com/automappers-design-philosophy/ It was meant to enforce a convention. Not to avoid the tedium of writing mapping code by hand (although that is another result).

My search also turned this up: https://x.com/jbogard/status/1111328911609217025 If that link doesn't work, then try: https://xcancel.com/jbogard/status/1111328911609217025 Source (which will explain the joke for anyone who didn't get it immediately): https://www.jimmybogard.com/the-curious-case-of-the-json-bom/

The FAQ question about Jimmy is related to https://www.jimmybogard.com/automapper-and-mediatr-going-commercial/

I haven't thought about trying to earn from OSS myself, but I'm curious to see how Jimmy Bogard - who recently announced this intention - is going to handle it. - https://www.jimmybogard.com/automapper-and-mediatr-going-commercial/ - https://news.ycombinator.com/item?id=43558316

Indeed, this seems to be the insight around vertical slice architecture? https://www.jimmybogard.com/vertical-slice-architecture/

This reminds me of Vertical Slice Architecture by Jimmy Bogard. https://jimmybogard.com/vertical-slice-architecture/

Relevant additional reading: https://martinfowler.com/articles/distributed-objects-microservices.ht… https://www.drdobbs.com/errant-architectures/184414966 https://m.signalvnoise.com/the-majestic-monolith/ https://jimmybogard.com/the-false-dichotomy-of-monoliths-and-microserv…