First Technical Paper
I'm in the process of putting together my first technical paper. In general it is about how you can use collaborative testing to test the user experience. I'm not sure what is going to happen with the paper, but I hope that once it is approved, I can share it here.
If you have any tips for me on writing a compelling abstract, an original and focused technical paper, and/or presenting based on a technical paper, this is my first time. I could use some guidance from the old pros.
In other news, I participated in my first every Pinewood Car Derby. My auto, based on a lipgloss theme, did well enough to make the finals, but did not win a medal. However, I stayed on the track and looked good doing it. For a first attempt, I'm quite proud. I know where to improve next time.
If you have any tips for me on writing a compelling abstract, an original and focused technical paper, and/or presenting based on a technical paper, this is my first time. I could use some guidance from the old pros.
In other news, I participated in my first every Pinewood Car Derby. My auto, based on a lipgloss theme, did well enough to make the finals, but did not win a medal. However, I stayed on the track and looked good doing it. For a first attempt, I'm quite proud. I know where to improve next time.
Cheers testy on putting together your first technical paper. Just be yourself and it'll be perfect. If I may make some suggestions that are
also for myself: keep structure and outline of the ideas in mind. You are creative and have so many rich, exciting ideas that at times can
confuse the reader. Try to put the text in proper format, numbered and develop each idea in depth. Be aware that the reader doesn't think and
know half as fast/much as you so spoon feed him your thoughts and conclusions. I hope tp read your first upcoming technical paper in a future
blog post. Maybe at the beginning of the abstract throw up some provocative ideas to catch the audiences interest and use metaphors that enable
the reader to visualize what abstractions and techniques of process improvement you are aiming at. You might want to reread the document structure
that James Bach uses. An excellent read. I'd like to thanks you for giving me the opportunity to read and comment you. it is a nice change from
my usual endeavours, plunged in the code base. I've observed that I think and talk alot about exploratory testing, automated testing, unit testing,
TDD and all that but I haven't yet fully implemented it in all my projects. Imagine that you taking me by the hand and us sitting down together and
doing some testing sessions would give me the final motivation boost to test first then write code, design by example. Unit tests are the ultimate form
of executable documentation, always up to date. Or as Dave Thomas from the Pragmatic programmers puts it: "if your program comes with tests, you should
sacrifice a small animal in gratitude." "All code that is not under test is legacy code and therefore obsolete." The importance of testing and not just thinking
about it all the time. Lipgloss theme auto, you made it into the finals, I am impressed testy. You are awesome and always believe in yourself. I believe in you. 100% code coverage. if it ain't tested, it's broken.
Reply to this