News for hackers. Stuff that matters.
Re:Programmers: how to make the systems guy love you by Goladus on Monday October 18, 2010 @07:27AM (#1803014)
Another one: usually one of the first places a sysadmin is going to look when there is a problem is the log file. A good sysadmin will be able to read compiler-generated errors but still may not be able to do anything if the messages reference cryptic variable names and methods from code they've never seen. Spend a little time thinking about how an end-user, rather than a developer, would read the log file.

Obviously don't short-change yourself if you're the one who will be writing bug fixes and need detail, but a little can go a long way here, especially for problems a sysadmin may be able to diagnose and fix (connection issues, resources issues, etc.)

Re:Programmers: how to make the systems guy love you by thirdstation on Monday October 18, 2010 @12:13PM (#1804022)
It can also save you a 2a.m. phone call.

Some simple, "If you see message X, it means Y, so you should do Z. If that doesn't work _then_ call me."

Your debug-level messages can be esoteric but, make your error-level messages reflect what's broken from the perspective of the SA, who hasn't seen your source code.