HNHacker News
TopNewBestAskShowJobs

hmeh

159 karma · joined February 9, 2010

Contact: aaronjensen at gmail

Software Development Articles: https://github.com/aaronjensen/software-development/#software-development

submissionscomments
hmeh··on It's not microservice or monolith; it's cognitive load
Just read the author’s bio. This is a person that appears to have zero software design experience writing an article telling you to ignore software design and just respect your team configuration. I call this Conway’s Confusion.
hmeh··on It's not microservice or monolith; it's cognitive load
It’s hard to imagine worse advice. Software design principles lead you to good architecture. Focus on autonomy, proper partitioning, and sound design and you get what you get. If you target monoliths out of some misguided attempt to reduce cognitive load, you will only create unnecessary entanglement. If you try to target “microservices” with N services per team or other arbitrary target, you will end up missing boundaries you should realize or introducing ones you shouldn’t.

There is no instant pudding.

hmeh··on The big TDD misunderstanding (2022)
Dozen-ish person team, 3 year project so far, billion dollar revenue company (not a software company), >500k LOC, TDD since the beginning. Have been doing TDD for 18 years or so. Still getting better at it.
hmeh··on Ask HN: What are good books on SW architecture that don't sell microservices?
If you want to learn to build software well, I can’t recommend the Eventide community enough. Eventide is a ruby toolkit for event sourced autonomous services, but the people there have a proven track record of understanding, executing, and teaching software design and architecture.
hmeh··on Why Segment Went Back to a Monolith
I'm currently working with realntl on a transition to Eventide from a Rails monolith for a client project. We reached a point where the monolith was getting harder and harder to change. This is inevitable in my experience, no matter how careful you think you are.

Though the transition is still in progress, I can say that the path forward is clear and hopeful. This company had previously explored other "SOA" paths (distributed monolith) and it was clear that those were very problematic. Luckily, we were able to steer them to an actual evented architecture.

As I said, it's still early days for this particular project, but if you're feeling your monolith is getting harder and harder to develop on, you should start looking into evented architectures. Eventide (ruby)/messagedb (postgresql) are awesome technologies and would be the first I'd consider. Eventide also has a nice slack community filled with people that are learning and improving their software design skill both in the large (architecture) and the small (individual classes/etc). It's small, but they're good people.

hmeh··on Message DB: Event Store and Message Store for PostgreSQL
> That doesn't to seem to be characteristic of Microservices at all.

Many have their own "unique" definition, which is why "microservices" is bordering on no longer meaning anything. Some people say it and mean SOA—the characteristics you mention are pretty much characteristics of SOA when done right, though independent deployment isn't a necessity.

Martin Fowler attempted to codify a definition, and this is inline with the definition that sbellware is referring to. He (and others) refer specifically to smart endpoints and dumb pipes:

https://martinfowler.com/articles/microservices.html#SmartEn...

hmeh··on Ask HN: Simple tools/hack for small project management
Also check out https://helloepics.com which adds parent child relationships across boards to Trello. I worked on it, but I wouldn’t (and didn’t) want to use Trello without it.
hmeh··on OOCSS + Sass = The best way to CSS
I used to be in this school. It has some downsides. I'm now back to the twitter-bootstrap-many-classes-are-fine camp.

* your css can still get large in large sites. Even though you're not duplicating rules, you're still filling your rules up with lots of comma'd selectors.

* IE8 and lower have selector limits of 4095, we hit this because we used @extend on a fairly large site and had to split our css up more

* It creates more dissonance for developers that are comfortable applying ready made classes. Now they have to make up (sometimes it really is just making it up, there's no real semantic name) a class name for something, go to the sass file and add it. This is more steps than they need.

* Many of these things can be cleaned up by good usage of partials or their equivalent on the DOM side. You should be DRYing that up too, so I can't say I relate to the author's concerns about changing DOM.

hmeh··on Show HN: GPS + Calendar + Traffic = always on time
I actually patented this about 6 years ago. Now I just got to dig up the patent...
← PreviousPage 5 of 5