20 March 2009

ALL I LEARNED

Hi,

I am dealing with JEE and Java Development since 2006 June, in a large-scale marketing&telco company.

Time to market companies have common property, this is speed.
This speed word, can harm software development soul therefore it is quite hard to be a soldier in such an army. But this teaches you; discipline should be your guide.

My experiences, mistakes, faults, successes teach me several rules, in this very short(or very long) time period.

I've decided to note tens of them on my web log. If you want to earn yourlife as a developer, at least you should read them.


1. Never give a deadline , until you understand what is your task.
2. Never start to code , until you pretty sure about your development plan.
3. Arrange meeting(s) to yourself for just thinking on exceptions after development ends, and while development continues.
4. Test it, Do Test it, Do Test What you create. Test Yourself.
Never, Never, Never Trust Your QA Member.
5. Documantate what is going on, with all details but with 0(zero) unnecessary information. Your document should not be documented at the end. It should be a living period. It should start at the first day and you will not say documentation is finished until you put your code to the production.
6. Never give any support until He or She(Analyst,Tester,Developer,Support Member,Operation Contact..) right to ask it.
7. Never forget to report, any unplanned task.(Mail,Defect,Question)
8. Feel free to remove any detail,that makes you un-disciplined
9. Be Cool, Never hurt any of your colleague. Please do not forget, any of us can make mistake. Mistakes are temporary, but words are long lasting.
10. Lastly, but certainly not the least; Keep Yourself UPDATE!!! Always search for innovation.

I know the question will come as; WHEN?
Believe, it is more expensive otherwise :)

2 comments:

ıvırZıvır said...

Most of the list is about the sotware development process that the company should provide :)

Tomasz said...

My friend to be honest i am really sorry to hear that you had such a bad experience with your team, at least that is what i got from reading your list...
Just few comments on your list:
1. If you are developer you should not be a project manager so you should not be responsible for planning (so you should not give a dead line but you just accept one from your manager)
2. Never start to code until your detailed design is ready :)
3. This point should be handled by project/team manager
4. Test only on very low level(unit tests) , developers should not test their own software unless you are working using XP approach
5. Here you are right. Documentation is very important and should be updated over all SDLC.
6. Always give support and try to explain everything ASAP. If you handle some information to somebody make sure they understand. Ask them to repeat what you told them to make sure they got you correctly.
7. I would say , report everything you can :)
8. That is personal (is removing boss part of this point ??)
9. Even the worst things can be said in the nice way. Sometimes it is necessary to remind your team mates that its not kinder garden and they should move....
10. Geeks never sleep :) as technology

Best,
Tomasz