What do you do after the project finished?
-
Resume writing itself is a skilled art. The first introduction or the first profile that crashes inside to a potential employers desk would be like an advertising brochure showcasing your world-class projects. Then slowly, when a call comes along, you would show up your prowess and potential, opening each one, one at a time or '
Flood-Gates-Opened' as the case may deem fit appropriately. :)Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
You could have used ghost doc also
_________________________ "When the superior man refrains from acting, his force is felt for a thousand li." Sun Tzu
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
start the documentation :sigh: Steve
-
start the documentation :sigh: Steve
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
Just pulled out my mobile from my bag and just thought there is one thing to add. Connect the headset enhancement and Tune into '
Big 92.7 FM' (http://www.big927fm.com/[^]) with Nokia 6030.Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
Just pulled out my mobile from my bag and just thought there is one thing to add. Connect the headset enhancement and Tune into '
Big 92.7 FM' (http://www.big927fm.com/[^]) with Nokia 6030.Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
Visit CP!! and wait for QA to email me with :rolleyes:'Well done all Passed!':rolleyes: try and have a rest before i start a new project, read up on whats new in the world of programming. i put coding document as part of the project:sigh:
Code Project Lounge 101 by John Cardinal :beer::bob::beer:
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
-
After project finished I don't have vacation And I don't want to write document... And I don't drink beer... And my code is perfect without bug... So I will post shareable code to CodeProject! :)
-
Visit CP!! and wait for QA to email me with :rolleyes:'Well done all Passed!':rolleyes: try and have a rest before i start a new project, read up on whats new in the world of programming. i put coding document as part of the project:sigh:
Code Project Lounge 101 by John Cardinal :beer::bob::beer:
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
If the testing is complete and signed off then you certainly do not touch the code - or the testing would have to be done again. If there are gaps in the documentation now is a great time to do them because you're going to need them when the project is released.
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
"Finished"? It's never finished. Go back to the first part you wrote and see whether or not you can write it better. Also, keep your head down and look busy.
I am 100% agree. I work for kind of in house systems and the systems don't have anything to say that we are complete or this project is over. I work simultenuusly in 3-4 projects and after 6 months of one project had been finished we do bug tracking and improvement.
Jwalant Soneji (BE IT) (India) Mobile: +91 9969059127 At Winodows Live Spaces At Yahoo! 360 At BlogSpot
-
If the testing is complete and signed off then you certainly do not touch the code - or the testing would have to be done again. If there are gaps in the documentation now is a great time to do them because you're going to need them when the project is released.
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Documentation should be PART of the project, not something tacked on after it. If your PM isn't giving you time to document as you work then give him a slap for being unproffessional. As for finishing projects; A smart person only ever starts projects, hand over to someone else and start a new project way before anything could hit the fan :-D
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
Wander aimlessly / have a little look for possible refactorings / help comrades who are having troubles / wait for more requirements to be added to the project... / wait for next project :P In my last job, we did pair programming and it was a small team (about 8 programmers) where we had a board for user stories and tasks. When finished a task, we'd move it to the "done" area, then switch partners if another team has finished around the same time, and then take another task (randomly or easiest available :P) from the "todo" area and start work. When a project was deemed complete (i.e. all tasks and parent user stories are done), we would all start the next project together or maybe spend an iteration (week) refactoring, checking for/fixing new bugs, sometimes adding to the user-acceptance tests, and probably idling. A few people would be involved with long-running (i.e. dirty) projects which would get new stories/tasks once in a while.
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
**
WuJunyin wrote:
**After the project finished -> means coding and test were completed.
- Tanslate it in 5 languages.
- Write documentation in 5 languages.
- Prepare the setup & live update.
- Wait the lashes of the boss
- Begin again
It never ends......
**
WuJunyin wrote:
**What do you do if no task assign to you?
Impossible, when it's finish, it begins the real bug fixing, updates for customer, otherwise i must clean the wc, after the boss'car and so on.
Dr.Luiji Trust and you'll be trusted.
Cryptography API: The Next Generation (CNG) - How to crypt documents with C++ programming, here.
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
WuJunyin wrote:
After the project finished
Well, given that I have a backlog of contracts, this really isn't a problem. However, you can always improve documentation, hit up your customers for ideas (pro-actively seek update possibilities), find out how your customers are using the software, in what ways does it work well, in what ways does it not work well. Seek and you shall find. It may be optimistic of me (which would be a first), but most of my customers are very glad to have a say in possible updates and ideas, and are tickled pink (okay one is, the others don't like pink) to seek their ideas come out as an update.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Resume writing itself is a skilled art. The first introduction or the first profile that crashes inside to a potential employers desk would be like an advertising brochure showcasing your world-class projects. Then slowly, when a call comes along, you would show up your prowess and potential, opening each one, one at a time or '
Flood-Gates-Opened' as the case may deem fit appropriately. :)Vasudevan Deepak Kumar Personal Homepage Tech Gossips
Vasudevan Deepak Kumar wrote:
Resume writing itself is a skilled art.
Not just that, but Resumes should be directed at a specific job. Back in the day :rolleyes: school taught me that you make 'one' resume, and then a specific cover-letter to each company. Not bad, but I would add one more to it. Jobs can have sub specialties and a different focus/direction than another even though they are all programming positions. IF you are just cold-sending a resume for an off-chance offer, the advice above is pretty good. BUT, if you really want "THAT" job, because it sounds sooooo good, customize the resume too! Some people will say, "but it is the same jobs, same education, how can you customize a resume? Lie?" No, never lie, focus! Change "General programming, training, and documentation for accounting related software" to something like, "Focused design changes on improving work-flow and reducing redundant operations. User Interface changes improved operator efficiency such that part-time additional help was no longer necessary. Created new software applications for Bank Reconciliations, Payroll and Accounts Receivable such that the company could illiminate one accounting position without overloading the computer data-entry and operations." Focus the details. If you want a job that deals with UI's and user-efficiency, focus the wording for that job. If you want a job dealing with hardware interfaces, focus your experience on that. Find what you did that fits the job you want, and focus the experience, without lying, such that the person reading the Resume believes you are exactly the right fit for the job.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Go have a beer.
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
Chris Austin wrote:
Go have a root beer
corrected for the teetotalers among us. ;P and for those of us losing (almost mispelled that one!!) weight, diet root beer. :-D Don't forget the frosty mug too!
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
After the project finished -> means coding and test were completed. What do you do if no task assign to you? Write coding document? or Write refactoring ? or others... -------------------------------------------------------------------- We are drawing flow diagram for important event, like button click... Does this helpful in the future?
Plead with management to schedule into the NEXT project all the change requests which were deferred from the current project.