itsjohncs / blog.johncs.com Goto Github PK

The contributions I made during that time were useful in a lot of ways and I should write about my experience making the contributions every day and why other people might like to do a similar experiment. Some good things that came out of it:

• It lets you say "I need some time to program" in a way that non-devs will understand (extremely awesome!)
• It keeps your mind constantly on your projects. If you drop something for too long you might have a really hard time picking it back up, this helps avoid that.
• It looks cool to people who are looking at your GitHub profile.

I'd like to keep it short since it's a bit of a personal post.

I'm thinking that "Blog by John Christopher Sullivan" might be clearer.

I might want to wait until I've done a little more work on it (supporting multiple languages for example). But it is pretty col, especially given the constraints of the program and it should make a pretty good blog post.

I think I'd like to focus on the optimizations above all else.

I've gotten compliments about this from just about everyone who interacts with me heavily at KA at this point. Others seem to think it's an awesome idea, and I know I think it's a great thing to do (thus why I do it).

I also don't really see it as a widespread phenomenon, so the post could be helpful as well as simply interesting, which satisfies my criteria for a worthwhile blog post.

I like to hear feedback abotu my blog posts. My blog on blogspot got a number of comments, a few of which were "omg thankyou this was so helpful" which is always nice.

Disqus (or however you spell that) seems to be popular and is used by a lot of sites. This'd probably be a safe bet. We'll see though.

I think I can improve the design by making it two columns. A list of posts on the left, and the content on the right.

Using the C preprocessor back in CS 61 (or something) in order to do cool assembly tricks was pretty neat. This is also a nice technical post which I greatly prefer to culture-type posts (mainly because I'm not terribly cultured).

There's a lot of content I can use here. I'd like to frame it more as "this is how an internship should be done" rather than a "come intern at Khan Academy!" because I think the reception will be better.

I like discourse, and now it looks like I can embed it. Boom

I have a solid grasp of how Python finds modules to import thanks mostly to my work on Superzippy. I've also used that knowledge during my first few days at Khan academy to both settle some problems I was having with my environment, and problems another person was having with their's (another intern).

I think a post detailing some of the more useful bits of how Python's importing system works along with real-world examples would be good.