I love notes.
3 cites, 9 participants = two thousand, six hundred and thirty notes.
That my friends is glorious! Take a gander!
|
- stopped and pause separation
|
- stop should be stop, pause should be paused
|
|
- theres no outcome here that interests me
|
- its not going to do anything interesting here
|
- im more interested in the one app and the server traffic
|
- etherel views or system dump
|
- id like to see that in one of the views
|
|
- it would be very valuable
|
- i havent done much multithreaded stuff
|
- only the networked traffic is interesting to me
|
|
|
- boot strapping and kernel debugging interests me
|
- im not used to working with gui
|
|
- 3 i was puzzeled at times at what was happening
|
|
- it was fast until it did analysis with the kernerl, he smiles
|
|
|
|
- finding help, rare did we go looking
|
|
|
|
|
|
- least hes pondering heavily
|
- intergration with sam tools, version control, we dont even know that
|
|
Ahhh the joys of testing captured in a coded web of digital note entires and of course video. That my friends is where its at. You can just feel the user love here. "I DON'T do gui!" thats a great line or the "It didn't piss me off..." lol. Classic goodness. Notes people! Capture the moment I say and 2630 notes after two weeks of hard work, I can step right back into that moment at any time. That along with video, pics of scene and you can damn near re-enact the experience. What were we testing? A programming enviroment. Thats about as much as I can say really. Still good notes I love them. Nothing sucks more when ya get out of the field and you have nada for notes. Sure you were there, you heard that one guy say x, the other say y, but... ummm ya didn't write anything down. Suprisingly there are alot of research folks that do just that, lack of notes, or hard to transcribe notes. All these notes captured in danotes, an app a friend of mine, you know him as bob wrote. A simple app really that does one thing very well..... er two things.. ok three things. HA! Anyways, im just resonating here with all these notes. Now comes the part of coding them.
Quote, Workflow, Context, MySpeak, MyEnviroment, WeUse, EndGoal, Breakdown, DesignIdea, Terminology. Sometimes less codes are better, lately I've been using more to help me understand what happened with what. Ideally sometime in the distant future bob will grant me "auto code on export?" and I will say YES! and I'll teach the pc how to read my notes. Muahahahahah.
So what happens after coding? Start pulling our the patterns, reoccuring themes etc. Once those are out you go for quotes. Meaty quotes that give your client ammo in regards to the opposition they'll get just presenting yer findings. With 2630 notes.. we have OODLES of ammo. And most of it on camera. I can feel the changes happening already.
Sometimes I'll leave myself notes for later. Like:
or
|
|
- when u get home dan order some merrels, 14
|
|
- theres not much info here
|
- i wanted something generic so i could code it give to others etc
Yes I need new shoes. I plan on ordering some new Merrels tonight, size 14. |
|
|
- danotes crashed coding when i xpanded the script point window too far
|
|
Ahh ya see a little debugging of my own was happening. In all notes is a glorious experience. At times I'll admit it, I'll decline running a session to take notes. Its a mixed bag really. Sure I could run the session, but I'd worry about the notes. I'll be giving a little talk on better note taking this month to the gang here at work. Its one of those things that in my opinion can make or break a project. Its content really, pure and simple, you can never have too much content but too little and its like being caught with yer pants down, not a good thing. So get those drawers on ya know. As an added bonus 2630 notes.. will simply BLOW yer client away. The level of detail you put into it in advance as a "nuff said" will always blow the client away. You can't beat it. Just do it!