Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Comment Communication 101 for Developers (Score 1) 361

The more you communicate to your superiors before the meetings, the less time spent in meetings, too.

One way to achieve this is to make sure every time you commit code that you check it in against a ticket. If there isn't a ticket to check it in against, create one, and then check it in against the newly created ticket. This gives you transparency and accountability. Both of which managers love. This can all be achieved with various ticketing systems, but the one I find that is integrated with a versioning system quite well is Trac. It integrates well with subversion, git, and mercurial.

Just keep in mind that not all communication is necessarily verbal.

Programming

Contributing To a Project With a Reclusive Maintainer? 162

zerointeger writes "I am still fairly new to programming in C, but I was asked to extend an open source authentication module by my employer. The project is complete, testing has been done and it works as designed. The extension/patch I have created is fairly robust, as it includes configuration options, help files, and several additional files. The problem is that I have been unable to make contact with the current maintainer about having this feature added. I think the only reason I'd like to see this included is to prevent any patching of later revisions. A few others I have spoken with agree that the patch would benefit administrators attempting to push Linux onto the desktop, as we have done at the University that employs me. Has anyone else submitted patches/extensions to what seems to be a black hole?"

Slashdot Top Deals

"If I do not want others to quote me, I do not speak." -- Phil Wayne

Working...