Thank you for sharing. I can relate. This is my first “real” full time job, and I’ve now been there 10 years with little to show for it, and not for lack of trying. Software engineer for a small company, report directly to the owners. Repeatedly, I pour my heart and soul into a project that I believe in, only for ownership to trash the project for superficial reasons. I’ll do small things and get overly patronizing p…
Thank you for sharing, I've gone through similar and can absolutely relate. I'm curious—do these business owners you work for have any software or management experience in tech? I've sometimes seen managers do this when they don't know what to do with an employee or don't know what career progression for an employee looks like. This doesn't at all justify shitty behavior, but I've found it useful to identify motivati…
I suspect they are partially motivated (as other commenters suggested) by not changing too much of what they themselves built personally.
Partially out of a fear of change, but also partially out of a “if we find ourselves without employees and need to run the whole show on our own again, we can’t have a bunch of code we don’t understand” fear.
Which I understand. But fact is, we have customers and internal users who are overworked and have needs. Needs that we aren’t meeting because we never deliver the “right” solution in full, in part because so many parts of the system just seem unofficially “off limits”.
I’ve offered many times to start a regular engineering training and sharing session where I can help make others aware of how I’ve been building things and how they can help maintain them, to try to make everyone more comfortable with the front end, but that also has met the same friction as my projects.