Free software junkie (i.e. speech not beer), keyboard jockey, Coonass libertarian, how bah dat baw? Laissez les bon temps rouler - mais’ wea
- 0 Posts
- 11 Comments
When I learned python I did by building some protocols I had a solid understanding of in the twisted python framework and it was a nice way to learn about other fundamentals that the “learn to code” guides don’t really go over. I’d look for libraries that other projects are leaning on and start from there. Libraries will have solved the challenges that slow down a beginner. You can always go back and learn how those libraries do it well after you’ve mastered using the libraries. Often because you need a particular feature or behavior.
you don’t start coding and are granted a vision by the god of logic about where your journey will lead you.
What is Agile for $200?
From the article:
There are times when I’m writing software just for myself where I don’t realize some of the difficulties and challenges until I actually start writing code.
I get what you’re saying but regardless if you have them upfront or along the way coding is modeling those requirements as we best imagine or understand them…even accidentally when following practices learned from others we may not even realize what requirements our modeling has solved.
Often I use git and just edit my repo files with the GitHub app and then git pull the changes from the server that needa the file. If you’re already familiar with git it’s probably easier than learning vim. You can probably do it directly to a repo behind ssh. If not then I’d learn vim before git.