26 7 / 2010
13,000 readers later - Lessons from Blogging
It has been 1 week since I quit my job, and jumped 100% into learning how to program.
This morning I received an email from a reader asking:
Questions:
- How many people came back organically?
- Did “narrative” posts work better than “technical” posts?
- Anything else I should know about how to leverage the experience?
Answers:
- Total 13,000+ (Yeah, it has blown me away too!) 300 per day organically.
- I am not sure. It seems people are interested in the blog for a few reasons.
Quick survey - Why do you read this blog?
- Interested in my story
- You want to quit your job or change careers too
- Are a programmer looking to help
- Other?
Please leave the answer in the comments! Thanks!
And to the final question- there is a lot to ‘leveraging the experience!’ Here are the lessons I’ve learned:
- Google analytics doesn’t automatically track outbound links, ex. to Twitter. Solution here
- #3 on Front Page of HackerNews brings over 7,000 visitors. Anywhere on the front page brings about 1,000 visitors
- Make a link to your Twitter account very prominent - http://twitter.com/emilepetrone
- There is also a Twitter account for just blog posts, but I do not highlight that account on the blog - http://twitter.com/proudn00b
- Track RSS feeds with Feedburner
- Things will break, just roll with the punches
- Taking a big leap, does bring big traffic.
- After a link on HackerNews gets a lot of traction, you will have a big drop in traffic. 90% do not return.
- Track your analytics with Ego (iPhone App $1.99)
- People need to understand your blog instantly. Have a short description in the header.
- Get into a posting rhythm - same time of day, with a certain frequency.
- People will contact you in every possible way (Twitter, Email, Facebook, Linkedin, Comments, etc). So have all of those accounts up to date!
- As for learning how to code- you will have interruptions. Just roll with them and go with the flow. (Friday got totally wrecked after Borders made me go all the way to Palo Alto to just return a book bc I didn’t have the receipt. Goodbye day!)
- Breaks are good for (required) reflection. Took this weekend off to decompress & analyze the traffic, feedback, and take stock of where everything is. Changes to the design are coming & bought the CSS Cookbook for just that.
- Get out of the house! Go to grab some lunch or meet up with friends after a long day. Not having to go to the office, is a good & bad thing. You miss the social interactions that comes with.
- Selfcontrol is a required app. It will keep you focused.
- Setup multiple inboxes in Gmail to filter out messages from Twitter, Facebook, Linkedin, etc. It will keep your inbox organized when a post suddenly takes off.
- Tweetie is great for maintaining multiple Twitter accounts & the @ messages to them.
- Random lesson, but I go to the grocery store much less frequently. I am out of food!
- If you can’t post from your laptop, make sure you can post via your phone. Only for emergencies..
- You will get haters. Just brush em off, and ignore their comments.
- I wish there was a way I could track my blog comments, HackerNews comments, @ replies all in the same place. Any recommendations?
- On learning, start with what you know. Get very broad & slowly work your way down to a niche. It will give you a base of knowledge, and open you to new ideas you hadn’t explored (or even knew about!)
- If you don’t know something, just ask! IRC #python & Twitter have been great for fast answers.
- Stay organized! This is critical. Ex. I have a folder for links, throw everything in there & read them at the end of the day.
- Disqus is pretty great for managing comments.
- Design is critical. Initially I heard a lot of noise on the font used & way I displayed links. I learned that lesson! More changes on the way…
- Blog posts take about 3 hours to write, review, and rewrite.
- 1% of your readers will follow you on Twitter. Out of 13,000 readers, I’ve seen a bump of about 130 followers.
- Strangers are awesome - if they find you, they will help.
- If you are wrong, readers will let you know! Just learn each time!
- Figure out a structure for each post. I haven’t figured that out just yet, but that is the goal.
And on that- yesterday I posted I will not be posting daily. After all of the feedback, let me make a small correction to that policy. I will post small, technical updates daily & save longer posts for maybe once a week. Smaller posts will hold my feet to the fire, and keep me focused. The longer posts just take too long to do on a daily basis.
So there you go- I think 32 lessons is a good place to stop. Thanks guys for an awesome Week 1! Here’s to you guys! Oh, and if you could also answer the survey question too, I’d appreciate it :)
Follow me on Twitter here: http://twitter.com/emilepetrone
Permalink 1 note