That's a very unspecific question.
Do you want to know which questions you should ask a potential employer before he hires you? If so, take a look at the Joel Test. Or maybe the other way round, how to test Perl knowledge with interview questions?
Or do you want to know what should be communicated during the {design,implementation,test} phases? If so you should tell us a bit more: is it a big team? is there are separate architect? etc. | [reply] |
Sorry, I did not make myself clear. This is not about interview questions. I don't have big team. Just me and my boss But there are other people working on the same applications. As you said, I like to know what should be communicated during the various phases. They may include architecture, design, implementation, test, maintenance etc.. Apart from these any other information that they know about the application in bigger picture and related information.
| [reply] |
There are various levels that have to be communicated:
- coding standards
- source code organization (in which file do I put $x?)
- build system
- testing policies
- documentation policies
- design
- APIs
- schedule
- infrastructure like bug tracker, source control etc.
In the end what's important is that you know what to do, and how to do it. If you don't know it, it can has two reasons: it's a hard problem and needs research, or you're not clear about some conditions, design questions or APIs. In the first case you likely just need to sit down and work on the problem, in the latter you need to ask your boss or cow-orker.
So what needs be communicated is "all you need to know".
There are various books out there that cover software project management. If my meager answer is not enough for you, you might read one of those books (though I can't recommend one in particular; but I'm sure some other monks can).
Perl 6 - links to (nearly) everything that is Perl 6.
| [reply] |
It depends on both the employee and the boss - what technical level are they at?
For example, my boss does not care in the slightest about Perl - he just cares that I get the job done on time within budget (I'm actually quite lucky in that regard). Some bosses are far more hands-on and want to micro-manage everything. Then again I have a reasonable track record so the boss trusts me: if you are just out of university then you have to expect the boss to be breathing down your neck. It's a trust thing.
Then there is how much I tell the boss - enough so he can do his own job, much the same as he treats me. | [reply] |
Perl should be your first choice. :-)
| [reply] |