Discussion Forum > Excursions into AF1
Yes, I'm wondering that too.
January 4, 2012 at 19:32 |
Mark Forster
Mark Forster
LOL!
January 4, 2012 at 20:24 |
Seraphim
Seraphim
I'm starting to think the FV is a devilishly clever MacGuffin
( http://en.wikipedia.org/wiki/MacGuffin ) concocted by Mark and designed to trick us into coming up with the ultimate AF1 solution...it's working pretty well so far ;)
( http://en.wikipedia.org/wiki/MacGuffin ) concocted by Mark and designed to trick us into coming up with the ultimate AF1 solution...it's working pretty well so far ;)
January 4, 2012 at 22:38 |
Frank
Frank
I'm betting more that FV is more defined by the objectives than the rules. The objectives are relatively constant, while the rules are secret so who knows if they stay the same or change? In any event, Mark is clearly aiming to get us hapless forum fellows to develop our thinking patterns closer to his own.
January 4, 2012 at 23:07 |
Alan Baljeu
Alan Baljeu
Yes, maybe he is manipulating some of you guys. So what?
I don't think anything is being derailed with these new threads.
The human mind naturally tries to make things too complicated. Without the benefit of MF insight, etc., I think we would try to have too many +entry points+ (capture, hot, today, tomorrow, this week, cool, project-related, contextual, someday, dated (hard), dated (soft), etc.), especially when things get 'busy'. The key word here is "simplicity".
Secondly, I think one of the keys will have to do with what Alan and others have already hit on with "Actives". If you can clearly see at a glance what has been started today (and yesterday), great things can happen with momentum, continuity, etc., and many of our problems we have had in the past will disappear.
I don't think anything is being derailed with these new threads.
The human mind naturally tries to make things too complicated. Without the benefit of MF insight, etc., I think we would try to have too many +entry points+ (capture, hot, today, tomorrow, this week, cool, project-related, contextual, someday, dated (hard), dated (soft), etc.), especially when things get 'busy'. The key word here is "simplicity".
Secondly, I think one of the keys will have to do with what Alan and others have already hit on with "Actives". If you can clearly see at a glance what has been started today (and yesterday), great things can happen with momentum, continuity, etc., and many of our problems we have had in the past will disappear.
January 5, 2012 at 6:46 |
BKK
BKK
BKK:
<< The key word here is "simplicity". >>
Yes, no one seems to have really taken in the fact that I said I arrived at my latest AF1 improvement by making it simpler, not more complicated.
<< The key word here is "simplicity". >>
Yes, no one seems to have really taken in the fact that I said I arrived at my latest AF1 improvement by making it simpler, not more complicated.
January 5, 2012 at 13:31 |
Mark Forster
Mark Forster
Frank:
<< I'm starting to think the FV is a devilishly clever MacGuffin... concocted by Mark and designed to trick us into coming up with the ultimate AF1 solution... >>
I think it's more to trick _myself_ into coming up with the ultimate AF1 solution.
<< I'm starting to think the FV is a devilishly clever MacGuffin... concocted by Mark and designed to trick us into coming up with the ultimate AF1 solution... >>
I think it's more to trick _myself_ into coming up with the ultimate AF1 solution.
January 5, 2012 at 13:38 |
Mark Forster
Mark Forster
"making it simpler, not more complicated."
Unfortunately, making it simpler is more complicated than making it more complicated. I'm trying and flailing. :-)
Unfortunately, making it simpler is more complicated than making it more complicated. I'm trying and flailing. :-)
January 5, 2012 at 14:35 |
Alan Baljeu
Alan Baljeu
BKK wrote:
<< If you can clearly see at a glance what has been started today (and yesterday), great things can happen with momentum, continuity, etc., >>
I haven't read all the recent threads, but like to note how I achieved the above in my SF/AF1 digital list (Android iRT GTasks Outliner).
(1) When I first enter a task it'll be white background and single lines.
(2) After first action on the task, I"ll change its background colour and note action taken/date.
(3) The background colour is one of 4 or 5 projects associated colours, the date/action is displayed on smaller second line.
(4) So tasks I've started are eye catching and date last action are easily seen.
<< If you can clearly see at a glance what has been started today (and yesterday), great things can happen with momentum, continuity, etc., >>
I haven't read all the recent threads, but like to note how I achieved the above in my SF/AF1 digital list (Android iRT GTasks Outliner).
(1) When I first enter a task it'll be white background and single lines.
(2) After first action on the task, I"ll change its background colour and note action taken/date.
(3) The background colour is one of 4 or 5 projects associated colours, the date/action is displayed on smaller second line.
(4) So tasks I've started are eye catching and date last action are easily seen.
January 5, 2012 at 14:59 |
sabre23t
sabre23t
Alan:
<< Unfortunately, making it simpler is more complicated than making it more complicated. >>
More difficult perhaps, but not more complicated.
<< Unfortunately, making it simpler is more complicated than making it more complicated. >>
More difficult perhaps, but not more complicated.
January 5, 2012 at 15:09 |
Mark Forster
Mark Forster
Adding a rule tends to mostly preserve the system's behavior. Subtracting a rule tends to blow everything up because there are no surplus rules. So this requires a whole additional process of deeply thinking through the effects and trying it out, while considering what to do about the hole introduced into the system. It's definitely more complicated.
January 5, 2012 at 15:27 |
Alan Baljeu
Alan Baljeu
Alan:
The simplicity we want is in the practice of the system, not in the rules of the system. This simplicity does not necessarily involve subtracting rules.
The simplicity we want is in the practice of the system, not in the rules of the system. This simplicity does not necessarily involve subtracting rules.
January 5, 2012 at 17:42 |
Mark Forster
Mark Forster
Alan: Some very good comments, as usual, over the last few days. Regarding complexity, and your discussion with Seraphim, could you see a type of waxing and waning Actives/Day Plan?
The Actives page would start with nada, and wax (grow) throughout the day. This would serve as a daily record and also have other benefits as discussed recently.
The facing page would contain the must-do's for the day, and would be closed (with new/urgent tasks below a line), and would wane throughout the day (to zero). They would be crossed out as they are actually started and transferred over to the waxing side.
The Actives page would start with nada, and wax (grow) throughout the day. This would serve as a daily record and also have other benefits as discussed recently.
The facing page would contain the must-do's for the day, and would be closed (with new/urgent tasks below a line), and would wane throughout the day (to zero). They would be crossed out as they are actually started and transferred over to the waxing side.
January 5, 2012 at 18:15 |
BKK
BKK
It's a reasonable idea BKK. However, as a feature it gets in the way of other features peculiar to my implementation. So I won't.
January 7, 2012 at 15:47 |
Alan Baljeu
Alan Baljeu
(1) taking away from FV development work?
(2) dovetailing with FV development work - really along the same lines of what FV was doing anyway?
(3) an interesting side trip that may yield insights into finalizing FV?
(I'm referring to the new AF1 start-of-day instruction; the idea of "action threads"; the forum discussion on AF1 improvements; etc.)
Just curious... :-)