4 ms·
I've never really understood this mentality. It's probably a privilege thing, but I always argue for doing things the right way. I got fired for it once, but
by seph-reed 6y ago
I've never really understood this mentality. It's probably a privilege thing, but I always argue for doing things the right way. I got fired for it once, but I live below my means just in case that happens anyways. I don't need much, and don't take on debt.
IMO, the kind of devs who do this shit are like union scabs: they make things worse for everyone else because they don't have the ability to stand up for themselves.
- bayindirh 6y agoI can think of two reasons why this happened in the first place. - Either it was good enough in low resolution screens, and algorithm just considered mature and nobody think about it after that. - Or, it was implemented with "first commit which meets requirements wins" competition, and it just didn't get the attention it needed. I'm like you, a big fan of "do it once, do it right", but not everyone understands how well-polishing something presumably small affects everything like a butterfly effect. Some people just want to tick all the boxes and go home. There's no inherent wrong with this, but when combined with wrong constraints and incentives, these things happen.