... and as expected, it's always the manager, not coding types that state this so aggressively. I know the servers are beefy at OmniTI, so I suspect there might be a code problem related to handling the load.
If I see sloppy code, or have to write sloppy code, I move to another company, and will continue to do so. So how's that employee turnover rate (hint, use the internet archive and check the about us page)?
I am a coder type, and I mostly support the sentiment.
Over the years, I gradually drifted from doing things the Right Way to doing things that are good enough. Doing things elegantly in practice unfortunately adds zero flexibility for non-trivial changes in business direction: you simply can't foresee everything. One swift decision at mid-management level and your elegant framework suddenly becomes an unwieldy Titanic impossible to put into a quick turn.
Now arguably works-for-today kind of solutions are not inherently any more flexible. However, they don't take nearly as much investment in the first place.
(Should also point out that quick and simple is not equal "sloppy code": I check my return values and handle errors just fine, it's just that my code makes no attempt at establishing world peace).
> Doing things elegantly in practice unfortunately adds zero flexibility for non-trivial changes in business direction: you simply can't foresee everything. One swift decision at mid-management level and your elegant framework suddenly becomes an unwieldy Titanic impossible to put into a quick turn.
Yes and no. If you're writing very elegant statically typed functional code like in Haskell or ML, you're going to have to be elegant at the design level, and yes, you might have trouble adapting to new requirements. But if you're in a domain where requirements aren't always set in stone, you're probably using a more dynamic environment where you don't have to be what the OP called "elegant" at the design level (e.g. his unrealistic caching layer example), but you can still write elegant code at the micro level (within functions, classes, etc.), which will almost certainly lead to substantially less technical debt and shouldn't cost much if any more time than quick hacks at the micro level.
Nah, the time has passed for stuff like that. It's time to wait for a reset. The intelligent people tried to warn the rest of us long ago, no one cared then, fuck the rest of you now that it's too late. I'll only do anything to speed up the reset... and I doubt the rest of 'you' will be ready for that until things have once again gotten so bad that something else will needed for success.
#edit hellban request denied then, I guess. Thanks idiots, it's your site afterall.
God, someone can post 'Seriously?' and get a hellban and I cannot? Look in the mirror you sad fucks. I still have 312 "points" from you idiots. Try harder.
Better to just make them feel 'naturally' unwelcome in this sick ecosphere of over-socialized nerds? Systems of re-enforcement like this are akin to the worst kind of intellectual inter-breeding.
I would like to request a hellban for my account, please? I think it's what I've wanted from this site all along, to be able to feel like I've address this sad group of over-engineering fools without the social consequences.
A racial slur is typically thought of as a slur that is about race. Pasty-faced is not about race. It's about not getting enough sunlight. Race is implied because darker colored people do not look anything like paste when they don't get enough sun. But that race is implied does not mean pasty-faced is any more a racial slur than the negative use of "pale."
What he said is true. Heck, it might have even prevented people from (re-)electing Obama if more people realized this. I have no idea what your problem is.
