If you can disguise some code improvements by selling it to your colleagues as a speed increase or better functionality then you might get somewhere. But you'll probably have to demonstrate it working in some kind of test case to even get them interested. Bear in mind that making it easy to integrate into the existing code is a key factor. You could, for example, create some kind of caching component that speeds up spewing out those javascript arrays, that would probably have a big effect with a small amount of effort.
R
Russell_G_1
@Russell_G_1
Posts
-
Dealing with bad-code -
What mobile phone OS you like?I've been using a windows phone 7 phone since dec last year. Still a bunch of features missing but hopefully some of that will be fixed soon with mango. Overall it's a good OS, bit different from the competition. In terms of reliability, it probably gets rebooted every few months, very few problems.
-
Frustated programmersI used to work for a company where my immediate boss played with spreadsheets and ms project and had no idea what he was doing. His boss was in another country and ignored us. His boss was one of those that reads a book about a new buzz word and shouts about making something new and pointless. All in all it wasn't great. Current job is nothing like that.