Week Thirteen: Argle bargle bargle.

Process is all I have for this week.

Reading up on ECMAscript. Reading up on Python. Reading python code with a tutorial open. Reading C code, going back over the hello.world examples. Trying to find a level of abstraction I am comfortable with  and productive using.

Reading up on the ATmegas and ATXmegas, I really feel like I was lost without a compass.  I spent a lot of time in Eagle: editing library packages for the LMNOP44 chip package, connecting pins to components, adding all the extra components necessary for a working board, watching complexity mount to the point of negative return.

My sixth design returns to the ATtinyWE in what feels like defeat. After making the two boards, tempsense and fandrive, and made them talk to the PC, I’m feeling more optimistic.

So much reading and absorbing material with no expectation of getting anything done; in a dazzling moment of clarity, remembering how I was never into programming.  But now I keep opening the editor and trying code.

Python versus javascript.  If you’ve been there, done that (Python), and have moved over to javascript,  it seems a different choice than a beginner might make.  I have some experience with software, but I never managed to get the example python code to run. Not a lot of room to mess about with application programming if the interpreter crashes every time it runs because it can’t find some library it needs; was it a bad path, or version mismatch, or the wrong install order?  The permutations ate my homework.

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>