Module 1



 Hello All! This is my first hack at any programming task ever, and I look forward to learning and growing a lot throughout the duration of this course. It took me way longer than it should have to complete this first assignment, but I now have a much better handle on the ArgoApps platform and am familiar with the file types we will be using in this course. 

The first step of this assignment involves accessing the ArcGIS online tool provided by the university. Only from that application can you access your S drive. It took me a little while to figure out how to implement the python script file and apply it into my S drive, but all that needed to be done once the file was copied into the S drive was to right click the CreateModFolders.py file and open it in IDLE. This step ran the python script and created the GISprogaming file and its constituent modules in the S drive.

The flowchart for converting radians to degrees was made using draw.io software and I guided the pseudocode off the book chapters and lecture notes. I ran the flowchart code on an IDLE window and it worked! A bug I had initially was not defining my variable before telling the code my conversion formula (that included said variable- rad for radian). So, I’ve learned that the order of operations is important and you have to define the variable before putting it into action.  

The Zen of Python: 

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

I love this programming mantra! It’s a great ode to problem solving and highlights the beauty of simplicity and user experience. The best line by far is “There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch.” Priceless. 





Comments

Popular posts from this blog

Module 5: Exploring and Manipulating Data

GIS internship: Post #4