PROGRAMMING
When you check out code you wrote time ago, what's the main difference with respect to code that you write nowadays?
I am always trying to be a better programmer. I look at old code and can always think of ways i can improve on it but remember the adage, "if it ain't broke, don't fix it.". I've also been pleasantly surprised to go back to old projects and know that they were done the best I could and also well commented!
More comments now, and often a better grasp of the problems I'm working on. I'm better at aiming for a solution rather than adding code because I thought of other cool features that won't get used...
The more junior my code - the more I do. Generally the scourge of being junior is over-engineering.
Not much. I think the biggest difference is clarity. I want everyone to understand the code I write so I litter my code with comments and favor simple code over needlessly complex code.
I name variables a lot better now and I have learned a lot about performance optimization.
Most times when I look at my old codes and logic, I laugh because It has been greatly improved. And a few times the old modules could be so deep and I would wonder if I actually wrote it.
I end up thinking how I could make small bits of it more efficient :(
now, I'm not a fundamentalist of OO.
I'm always trying to learn new features of the language I'm coding in.
So when I read older code, I usually end up saying "Holy crap! those five lines should really be one", or "that's inefficient. I really should have used here"
Over the years I learn new techniques, better ways to handle things. The more I work in an area, the easier it is to think in the appropriate structure. |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 |
<< PREVIOUS NEXT >>
| |
|
99760 interviews created
INVITE YOUR FRIENDS