hey all it's
welcome welcome everyone.
I wrote out about half a post before I deleted it due to a collective bad attitude vibe I was catching. From myself.
What's up guardians of the hash tag. It's ya boi.
Sometimes we can be pretty immature and have bad attitudes. You wake up and you don't want to make a decision about anything or you just downright feel like this.
Today I tried rewriting something I initially wrote for a client but the project went in a downward spiral after I psyched myself out. Things have changed though and now web pages look different and it sure was nice to have some automated workflows, you know what I'm saying????
So I tried a little last night, and a little today and it didn't really work out and this is the constant battle I fight.
Do I do this thing manually, with this brilliant piece of mechanical wonderdom, the ThinkPad ( T430 - I knew you were wondering what model )
ahem. What I am saying is, how many times do I approach this task like this before I decide to set aside four hours to write a script for it. Without knowing that I actually mean four but initially think five minutes.
Well. I couldn't quite figure out the script today. It was a lot more work than I remember and I am pretty impressed by that. I was having quite a damn good week too so I thought I would really be able to mash it together over the weekend but nope. Cool to find out about yourself you know?
I wasn't really writing it for my client. It was more for my own workflow. Also more free time for me is better for everyone. Seriously. I want to be paid for doing what I do here, just more complex awesome things. Researching things so deeply it's like I hand in a dissertation once a week for my job.
I love programming because of it's complete absurdity and abstractness. You can start at the very smallest thing and make it bigger so easily. And then make more on top of it.
It actually took me awhile to understand that I wasn't really a beginner anymore but that I actually knew how to program. When I learn something, I'm not sure that I've learned it especially if the information came from a single dimension from which I could learn about that subject.
Most of what you're actually learning how to do when you're programming is use a bunch of tools that you don't really know how to use and it all happens from the very start of introducing yourself to programming and you didn't even know it.
The other thing I couldn't really wrap my head around was the whole "find something you love and use programming on it" or something. People are always like..
"how do you learn programming?"
"oh here, I have a map"
Yeah. That's how you learn anything right? You just have a map.
I first started programming because I wanted to be able to request information and have returned a bouquet of resources, artifacts, whatever, all at my finger tips. Is that a thing? Yeah it totally is a thing but there's no way I could build that day one of being a newbie.
But I did learn how to scrape.
File "<ipython-input-1-bfbc4e905957>", line 1 But I did learn how to scrape. ^ SyntaxError: invalid syntax
but ... me learned how to scrape? wait..oh no, I can't start a sentence out with "But". It's inappropriately placed, butts come at the end.
Anyway. I didn't know what to build because I literally couldn't imagine how it might be built. So I never really knew what to build. I just wanted to learn what was useful. I did all sorts of things with Python but nothing I was super interested in, because I didn't know what I was interested in. I knew the basics of web mining but I didn't really know what to search for. So I just assumed that I was still a noob because if I had no inspiration to build anything then I must not know anything at all.
What I had were the tools. I just didn't know how to use them together.
So I just copied tutorials. Over and over and over. I would buy learning resources whenever I had extra cash (still do sometimes but have slowed that roll considerably by getting +3 library cards) and then I would fall off a resource onto something I thought was better but then eventually come back to the original resource because it one I've always wanted to read.
The first program that I ever "wrote" on my "own" I used about 15+ different tutorials to write. I am building things now that I just watch Youtube video tutorials and then tweak a few things here and there or completely augment the thing to work differently somehow, lost in a line of other mangled lines of code.
My only interest was ever to learn how to code just to really enhance my own workflow, to get more out of what I do with every minute of my work. And to cut out the waste in my workflow because I honestly love working and producing things and I want to do it efficiently and productively. Sometimes I think work is my art and with coding, it's shaping how I personally think about getting things done.
I can't remember why I started writing this post. I think to avoid (more) coding for the night but it is unavoidable at this point. I found a dope youtube api tutorial I'm going to do. I love this guy's tutorials, I've only just started watching them but definitely pretty good.
# let me end with it with this import this
The Zen of Python, by Tim Peters 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!