3 ms·
This may be the majority of the industry, true. But some devs filter out employers to not feel miserable. Whenever I find an employer like this, either I try to
by siwatanejo 8y ago
This may be the majority of the industry, true. But some devs filter out employers to not feel miserable. Whenever I find an employer like this, either I try to change the status quo, or I leave.
- repomies68 8y agoThis. Don't except things to change if you happily stay in a workplace where things are done in a half-assed way. There's endless supply of jobs for software people nowadays.
- wDcBKgt66V8WDs 8y agoChanging the status quo is kinda fun in these environments. Low hanging fruit, easy work. As long as your head isn't on the chopping block. And everyone benefits. You, the employer, your colleagues, the fresh grads with starry eyes
- WrtCdEvrydy 8y ago'Wanna make some enemies? Try to change something'
- rectang 8y agoIt can be rewarding, but there are a couple caveats. First, management has to be willing to assign you to cleanup tasks, rather than have you work on new features. Second, cleaning up spaghetti code safely and turning it into something maintainable is often not easy -- it wasn't written to be maintained! No tests, missing documentation, ill-considered interfaces... It isn't enough to keep your head off the chopping block: management has to be fully on board.
- wDcBKgt66V8WDs 8y agoYeah in my case I've got my manager and architect on board and they love it. My more senior teammates might be threatened though. I found an impending any-day-now production down scenario last week and got it fixed while learning tremendously and fixing some incidentally related things. It feels amazing. No tests, no docs, no comments, total spaghetti, global variables everywhere, no logs, and I am loving it. What a job. Upper upper management is starting to keep tabs on the "productive" output of my team though. We'll see.