1,666 karma · joined February 11, 2010
i'm jrrrheard at gmail
it's totally a night-and-day difference, i used to be terrified of planes and now they're just a mild irritant.
http://blog.jrheard.com/watercolorbot
http://blog.jrheard.com/python/passwords
http://jrheard.com/blog-staging/python/caesar.html
I'm excited to see how the rest of this school year goes - by the end of it, I'll have a suite of projects that beginners to Python might find very useful!
If you're strapped for cash and don't want to pay the $800/term, you could definitely learn these things on your own using free online resources. If you don't mind the price, though, I've found this course worth the time+money+effort so far. [they're not paying me to say this :)]
I tried a couple of coworking spaces, found one that I liked, and have been going there regularly since - my employer paid for my membership at the time, but I quit my job a year ago and it's still worth it to me to have a space where I can go every day to get out of the house and be _around_ humans, even if I don't socialize with them as much as I could.
I've always identified as an introvert, and used to fantasize about the idea of e.g. working in the top room of a lighthouse for a month - assuming you had a good Internet connection, you could get so much coding done there! - but it seems that being around people is much more important than I'd given it credit for, particularly in the winter when it's pitch black outside at 4pm and you're already kind of depressed by default.
Your second point is absolutely correct, but I still think that my comment answers the root question - how did you set things up such that you're automatically being given money for free on a regular basis? - in a way that is simple, requires very little effort, and has a very good chance of working for many people who are able to try it.
I do like programming, and I plan to spend my productive time on this Earth programming on projects that interest me and help humanity in some way, but I just absolutely 100% have no plans to start a business. I admire your excitement about the idea, but I think that maybe not everyone feels the same way :)
(I also recognize that maybe not everyone feels that automatically saving+investing as much of your income as possible is a good idea - I'm mainly attempting to reach those folks who do think it's a good idea and just need a little bit of prodding to actually set it up.)
[Somewhat related: http://www.mrmoneymustache.com/2012/01/13/the-shockingly-sim... ]
I'm hopeful that we'll see lots more blog posts written in this interactive style in the future - the KLIPSE plugin I use is extremely simple to set up, and has support for a ton of languages including Python and Ruby (not to mention regular old JavaScript!). http://blog.klipse.tech/klipse/2016/09/09/klipse-languages.h... is a gallery page that has examples of all of the languages that the plugin supports.
I literally wholesale copy-pasted the Rakefile in http://ixti.net/software/2013/01/28/using-jekyll-plugins-on-... in order to set this up, it was very easy thanks to that great article - all you have to do is run `rake publish` at the command line, and your site builds locally and the finished product is deployed to your github pages repo.
Could you talk more about this? I have little to no anxiety about public speaking, but hosting a meetup sounds like a lot of work and stress to me. Are you talking about putting a new meetup group together from scratch, or asking a preexisting meetup group if you can MC for them one night, or some third thing?
> This would further the centralization of the internet, which is a disaster waiting to happen. It's easier, it's cheaper, but it's also wrong.
Sorry, honest question - I don't understand what you're saying here. Could you please explain?
For "10 minutes figuring out where I was", I can just look at the end of my last diary entry, where I've often left a note like "this is what i'm working on: foo" or "do this next: foo, bar, baz" or "currently stuck on baz". And if I haven't left a note like that, I can usually deduce one by scanning the last few paragraphs of the last day's entry.
For "15 minutes researching how to do that next bit I want", that has to happen no matter what, but I like recording that research in my dev diary so that I can search through it later if I run into the problem again or want to remind myself why I settled on a particular solution - and I find that forcing myself to write down my analysis of this research helps keep me on task during the research process and helps prevent me from getting distracted.
You get the idea. I don't have any written-down rules about how to keep a dev diary, what goes in there and what doesn't, best practices about solving X software engineering problem by implementing certain dev diary techniques - I just have a freeform text file that I write my thoughts into every day when I'm working on my project. It seems to be a useful technique for me, maybe it'd work for you!
I used to do the don't-break-the-chain jerry-seinfeld thing, but I find it too stressful, it starts to really affect my quality of life (and the quality of the work that I do!) when I've got a chain going that's more than a month long. Plus, if the point is to prevent thoughts/state/meta stuff around the program from slipping out of your mind over time, writing it down seems to me like a good (better?) way of solving that problem.
When I find a problem that recurs in my dev diary without me coming up with a solution, or I have an idea that I'm not going to work on now and which I worry will be lost in the folds of my diary, I find an issue tracker like GitHub's (eg https://github.com/jrheard/voke/issues ) helpful.