portsnadaptors's comments

I remember that day. As a more junior developer I was very confused as to what I had surely done wrong.

> And a lot of people underestimate the second degree impact of even the smallest of abstraction design choices

This is one of the hardest lessons I've had to learn as an engineer. Building extensible abstractions upfront is extremely difficult to achieve without building a lot of abstractions upfront that aren't extensible, and learning why.

> you cannot avoid them, you need to get good at them instead

I'm working on it!

I don't think building an abstraction over the data layer is just to make it easier to change your database. The abstraction can define the data access patterns upfront and minimize bespoke data access code. I've spent a lot of hours trying to untangle ORMs and other data access code from business logic. I've found that extending an abstraction to support a new access pattern (that you really need) is much easier.

and pretend that all your promises will come true