05-30-2018 01:39 AM
No i'm not trying to judge. I was just curious about how much time it's usually needed.
05-30-2018 04:34 AM
@AldhairGarza wrote:
No i'm not trying to judge. I was just curious about how much time it's usually needed.
You only get 4 hours. If you need more then 4 hours, you'll loose points on functionality, documentation or style...
How long it usually takes? 8-12 hours. So you need to double or triple your efforts for 4 hours . Seriously, work hard right from the start, you need to make every second count.
05-30-2018 07:05 AM
wiebe@CARYA wrote:
@AldhairGarza wrote:
No i'm not trying to judge. I was just curious about how much time it's usually needed.
You only get 4 hours. If you need more then 4 hours, you'll loose points on functionality, documentation or style...
How long it usually takes? 8-12 hours. So you need to double or triple your efforts for 4 hours
. Seriously, work hard right from the start, you need to make every second count.
I have to think the OP is not spending all day on one run-through. 😉
05-30-2018 07:21 AM
@billko wrote:
wiebe@CARYA wrote:
@AldhairGarza wrote:
No i'm not trying to judge. I was just curious about how much time it's usually needed.
You only get 4 hours. If you need more then 4 hours, you'll loose points on functionality, documentation or style...
How long it usually takes? 8-12 hours. So you need to double or triple your efforts for 4 hours
. Seriously, work hard right from the start, you need to make every second count.
I have to think the OP is not spending all day on one run-through. 😉
That is a training strategy: get things working with good quality, then work on improving the time to make it..
05-30-2018 09:31 AM
@billko wrote:
As far as I can see, you get all the points for functionality, but if I were to be nitpicky, I would say you need to give feedback to the customer that the high pressure wash was selected. It's not that difficult to do - just set the button value to false on startup. The idea is not to startle the customer. 😉
Note:
Instead of those humongous free labels that you have describing what is happening in each diagram of each structure, you can righ-click on the structure and enable submenus. This will give you a space right under the selector (if case or event structure) or just right under the top (sequence structure, FOR loop, WHILE loop). Makes it nice n tidy.
PASS. Easily.
Thanks Bill! Great feedback and suggestions. Thanks for taking the time to look at it.
05-30-2018 09:34 AM
wiebe@CARYA wrote:
@AldhairGarza wrote:
No i'm not trying to judge. I was just curious about how much time it's usually needed.
You only get 4 hours. If you need more then 4 hours, you'll loose points on functionality, documentation or style...
How long it usually takes? 8-12 hours. So you need to double or triple your efforts for 4 hours
. Seriously, work hard right from the start, you need to make every second count.
Exactly, at first I found my self unable to finish the test in a day, then I got closer to the 8 hour mark. I slowly cut down each test as my mental efficiency improved over time.
I found that on this run, writing pseudo code at the start may have actually shaved an hour off my time.
05-30-2018 09:43 AM
@billko wrote:
you can righ-click on the structure and enable submenus. This will give you a space right under the selector (if case or event structure) or just right under the top (sequence structure, FOR loop, WHILE loop).
Just for reference: those things are called Subdiagram Labels. Right click->Visible items->Subdiagram Label.
Good advice though!
06-02-2018 04:45 AM
wiebe@CARYA wrote:
@billko wrote:
you can righ-click on the structure and enable submenus. This will give you a space right under the selector (if case or event structure) or just right under the top (sequence structure, FOR loop, WHILE loop).
Just for reference: those things are called Subdiagram Labels. Right click->Visible items->Subdiagram Label.
Good advice though!
I must have been half asleep when I wrote that. 😄