Tag Info

New answers tagged

0

If things are properly planned generally you should experience very little stress in day to day work. Maximum stress to be tolerated At worse you should feel stress only when something unpredictable goes to hell. (Building fire, infrastructure failure, unusual loss on work hours due to sickness, etc.) The sort of stuff that no one could reasonably predict. ...


3

If your products are relatively complex, it will take a long time for newcomer to get a hang of it no matter what you do, but you can make it less painful with your active support. Not a long time ago I joined (and still work for) a company where we have: seniors teaching juniors our own wiki and documentation storage designated time for studying ...


1

If you haven't already got them, you desperately need:- A issue logging system. Every bug report and feature request goes in the log as a new ticket. Every change you make is logged against the relevant ticket, and nothing ever changes without a ticket. The log will say which tickets are new, which are in progress and which are done. You can even ...


0

I just drop down into the debugger and see what the code is doing as it is executing a specific example. I get a much better understanding of what the code is doing and it also ends up being much easier to track down what I need to modify because there can be hundreds of files that are completely irrelevant for the use cases I have in mind. In general ...


1

I often take notes while trying to understand other people's code, especially when I don't want to alter the source code itself in any way. At the moment, I keep my notes in a text file, but it's really cumbersome to continually flip between application windows, copying, pasting, and searching for identifier names, and relying on the same name appearing in ...



Top 50 recent answers are included