I think I’ve thought of the problem with the threading
function. There’s really no problem with
the thread function. The thread works
great. My expectations of what the
thread should do were wrong, though. I
incorrectly assumed the thread would run multiple times. It doesn’t.
It just runs once. And that’s the
problem with it. So it’s not the thread’s
fault I told it wrong. It is simply a
matter of me assuming the wrong thing about how it would behave.
Essentially, I have to remember that the thread is nothing
more than a function. The function runs,
and then the function quits. Bu nothing
ever calls the function again, so the numbers never change after the first
press of the button. Or at least I
think that’s the explanation.
On a second note, my reading has gone past 20%
complete. I should be done with
Security+ this week. As a general rule,
I’d say the book has good info but it’s so incredibly vague in most cases. This is not an action oriented book. This book is there to give you a gigantic
overview. From there, its’ up to the
user to pursue whatever interests them.
Which takes the focus out of the reading. I’m guessing a server book should go
next. At the moment, I’m not progressing
down the security path though. I’m
heading towards a programming path. Once
the programming path is done, then it’s back off to other things.
At the moment, I’ve read about 1000 pages of the 5000 I need
to complete my current goal. So that
leaves me with another 4000 or so to read.
Do I really want to schedule the next 10,000 pages when I don’t know
where I intend to go from here? I could
easily pick a number of books. A Cisco
Voice book probably needs to be in there somewhere.
For now, the examination of where I want to go is behind
4000 pages of physics, calculus, and artificial intelligence books and the last
50 or so pages of Security+. Towards the
end, I’ll probably have a better understanding of where I want to go. But now?
The schedule is set, I just have to follow it.
No comments:
Post a Comment