-
Looking for HSC notes and resources? Check out our Notes & Resources page
Process diary?? (1 Viewer)
- Thread starter ohyoonsk
- Start date
Ilikedrivingbymycarandthe
Member
Honestly, you shouldnt need a scaffold. Just have a topic you really enjoy/ r passionate about and researching naturally becomes fun. Diaries for major works generally should just have notes for your creative process + evaluations on research and your process, no dif from a normal work book. If it really helps, try using a smaller diary that can be finished quickly rather than a large binder, that way it motivates you to finish the journal therefore having sufficient research.I have to do a process diary/logbook for my major project.. does anyone have a good scaffold or idea/plan that they could share
Socialism
Well-Known Member
is it online or on paper? our teacher let us do ours on google docs or word...I have to do a process diary/logbook for my major project.. does anyone have a good scaffold or idea/plan that they could share
i have a template for ONLINE if you want it but its nothing special, just some headings
its like within our project documentation, for now ive just made a table with some date headings which I think is all i need to note down my progress and whatnot
wizzkids
Well-Known Member
- Joined
- Jul 13, 2016
- Messages
- 410
- Gender
- Undisclosed
- HSC
- 1998
Keeping a daily log book for software developers is an essential habit to adopt, and it will stand you in good stead in years to come. It doesn't matter if your logbook is paper based or electronic, but you do have to devote serious time to maintaining it. With so many design decisions having to be made, code samples to be compiled and tested, version control, references to resources etc etc you can easily get lost, waste time or off track if you don't keep a project log book.
I find my log book useful for unloading problems out of my mind.
If I record my problems in my log book at the end of the day, I can stop worrying about them. I know I can pick up where I left off without losing the thread or forgetting what I was thinking or doing.
You should have these fields in each record as a minimum: date; module; fileNames; version; variables; result; errors; nextStep
I find my log book useful for unloading problems out of my mind.
If I record my problems in my log book at the end of the day, I can stop worrying about them. I know I can pick up where I left off without losing the thread or forgetting what I was thinking or doing.
You should have these fields in each record as a minimum: date; module; fileNames; version; variables; result; errors; nextStep
Socialism
Well-Known Member
@ohyoonsk
Well, I can't compete with that
I find that this works well as it allows me to keep track of what i've done and what i'm planning to do. (And difficulties and solutions is good for keeping teachers out of your hair for plagiarism and ai)
but in terms of what has gotten me through software engineering in yr 11 and now year 12, I use the following format:
Well, I can't compete with that
I find that this works well as it allows me to keep track of what i've done and what i'm planning to do. (And difficulties and solutions is good for keeping teachers out of your hair for plagiarism and ai)
but in terms of what has gotten me through software engineering in yr 11 and now year 12, I use the following format:
| Date | Task/s Achieved | Difficulties & Solutions | General Comments and Reflection | Goals (If applicable) | References |
| here | here | here | here | here | here |
Study to success
Well-Known Member
When I have to do ongoing evaluation for DT sometimes I don't do them throughout the project and I just do it at the end and I just make up a bunch of shit and pretend stuff happened when it didn't