Personally, I have arrived at a similar set of ideas in my consulting gigs, though not the same technology stack choices.
I think it is the need to be maximally productive in the shortest amount of time. Basically, any time you spend fixing someone else's problem is time you aren't getting closer to the clients goals. It is not that the time isn't for the greater good, but the hours I have allocated to this problem are fairly tight to start with and I don't enjoy the "We are over budget. Here is why" talks.
I have reached the point where I have started using npm ls as a proxy for how much pain migrating a legacy app will end up being.
> I think it is the need to be maximally productive in the shortest amount of time. Basically, any time you spend fixing someone else's problem is time you aren't getting closer to the clients goals.
Yes, that is an important reason how I arrived at this way of working!
as a single dev, I decided to get rid of ORMs and Typescript because... if I can't figure out what I did between my comments and my Notion documents, I'm doing it really wrong...
I've realized the more time not spent on producing output in the shortest amount of time, I'm eating away at my work life balance
I think it is the need to be maximally productive in the shortest amount of time. Basically, any time you spend fixing someone else's problem is time you aren't getting closer to the clients goals. It is not that the time isn't for the greater good, but the hours I have allocated to this problem are fairly tight to start with and I don't enjoy the "We are over budget. Here is why" talks.
I have reached the point where I have started using npm ls as a proxy for how much pain migrating a legacy app will end up being.