how to blog about code and give zero fucks

I’m frustrated right now. I’ve been looking for someone to write about a technology that tons of people have no doubt used and am coming up short. Really, this is my own fault, because I was hoping I’d find someone who wasn’t a white male to address the topic. There’s nothing wrong with a white male addressing the topic, but I’ve been recommending a lot of white males to write about technologies and I was hoping to put my money where my mouth is in terms of my hopes for the diversity of the field in which I work.

I checked a bunch of related repos on GitHub and found that the maintainers were white guys and the committers were white guys and the people filing issues were white guys. So I checked the Following lists of related Twitter accounts and found.. more white guys. The few women I found either didn’t blog or had Tumblrs full of inspirational quotes and cupcake photos and shit. (Which is fine. But not what I happened to be looking for an expert on.)

And so this is how I became frustrated, because I don’t want to hit up people I know over and over again, and I need a way to know people are interested in and knowledgeable about certain topics, and the internet was giving me fuck-all.

Which brings me to the subject of this post, which is that you, developer in an underrepresented group who hopefully received this link somehow through the magical machinations of social media, should be blogging more. I need you to blog more. Little future developers who look or act or dress or think like you need you to blog more. Your slightly confused and defensive developer community needs you to blog more. Please please please please. And if you are like, “I give zero fucks about what those people need, I need to get off work at six and build charming birdhouses or customize my bicycle or something,” the best part is giving zero fucks is totally fine.

See, if you were an ambitious type, you wouldn’t need me to prevail upon you to blog more. You would be doing that and speaking at conferences and merrily on your way to becoming the next Marissa Mayer and that would be just fine for everyone. But there are a lot more not-Marissa-Mayers in the world than there are Marissa Mayers and those people need representation, lest we get it into our obsessive little developer heads that if you are not constantly being the very best at everything you should just go home. We need blog posts that aren’t about big fluffy TED topics like programmer diversity and are instead about that fucking stubborn and reprehensible bug you spent five hours on today because you couldn’t find a goddamned thing on StackOverflow.

So here are some simple guidelines for blogging about code while giving barely any fucks at all from someone who used to do exactly that and still has a job and outside interests too and it’s fine:

no quality control

Fuck quality control. If you wanted a code review, you’d put it on GitHub, amirite? It’s an idea, or a solution, or just a list of links. If you start thinking for even one second that isn’t valuable, try to picture you yourself finding such a thing when you started your day this morning and all the agony and yak-shaving it would have saved you. The internet is full of horrible crap! If your horrible crap is at least well-intentioned, it’s probably a step up from the other horrible crap. You don’t have to be perfect, or convert your glorious tabs to spaces, or even spell-check the damned thing. Just hit Post. The worst that will happen is nothing. Which brings us to..

assume no one will ever see it

People don’t click every link they see in a Twitter bio or a GitHub repo. I don’t even normally do that, which probably half explains why I can’t find you right now when I need you to write about this really important thing. This is great! It means there’s nothing for you to be embarrassed about. It means no haters will leave you nasty comments about how you should indent with spaces. It means your blogging is a nice record for you of all the problems you struggled with and overcame that, believe me, you will completely forget ever happened if you don’t write them down. If you don’t want it to, it never has to be anything more than that.

write like yourself

Writing is not fun if you have to stress over it, but if you can entertain yourself with it, it can be. So, I apologize for the excessive-even-for-me sweariness of this particular blog post, but I will also tell you that it is getting written a shitload faster than things I try to write in a professional and grammatically correct voice. If you want to “write” a whole blog post that is nothing but code examples and reaction gifs, that is valid as heck. Write it without capitalization or apostrophes. Who cares. They say you should write drunk and edit sober, and the thrill of getting something written down really quickly and in a way that amuses you is not unlike drunkenness. But also..


Or if that’s not your vice, eat ice cream. Have America’s Next Top Model playing on the TV in the background. Reflecting on your work shouldn’t have to feel like being at work. Take your pants off. Get comfortable.

actually write about code

I don’t know why, but I think it makes you feel like a better coder. It’s good to be able to explain things, or at least lay them out in snippets so it’s clear how they work together. It’s fun. And if it’s something you already coded, it means that shit is already mostly finished.

moderate comments

If you are currently averaging 0 comments per blog post, it might seem validating to accept each and every potential future comment immediately so at least someone is responding, but don’t. Statistically, the internet is 97% trolls, and you would think that trolls would not bother with a blog where there are normally 0 comments but that would be incorrect. Speaking from experience here, the thrill of seeing a new comment appear only to find out it’s baseless and nasty is far, far less than the thrill of seeing a four-page screed about Bitches Need To Stay In The Kitchen; And Also Impeach Obama in your moderation queue, considering all the time that went into writing it, and hitting Delete. Remember, this is your blog, and no one asked Hacker News for its feedback.

don’t hit post immediately

If you want to not worry about what might happen if other people someday see your blog, do yourself a solid and never post anything in the heat of the moment. Save it as a draft and come back and reread it in the morning. And if you like it in the morning, it’s good! Moreover, if you like it in the morning, you are good at blogging. If you can amuse yourself when you just woke up and you heard all the jokes about the text selection API last night, you have done a good job. And if you can’t, fuck it, leave it in the drafts and don’t worry about rewriting it. Do you want to know how many drafts I have saved on this blog? It is a lot. But not rewriting it is also very important. If you thought it was kind of a piece of shit the first time and you sit down to write it again thinking, “Don’t write a piece of shit. Don’t write a piece of shit,” you will write an even worse piece of shit. Write it later, when a new angle or really clever hack suddenly inspires you. Or not at all. Some blog posts make really good first drafts.

promote it. or don’t.

You might like having a little secret blog where you quietly explain all the things that are wrong with contenteditable that you never ever intend on filing a bug for. Or you might eventually begin to desire some recognition. Both are fine. I mean, please link to the damned thing somewhere, but you are not obligated to tweet once per timezone to alert the internet that You Have Written a Thing. However, if you write a thing and you feel pretty certain it’s brilliant or hilarious or just really elegantly executed clickbait, you don’t have to feel weird about sharing it. The internet is huge. There’s probably at least one other person out there who will feel the same way.

just please please please do it

The same goes for putting your stuff on GitHub, and speaking at your local meetups, and going to your local meetups in the first place, but those can be a lot more intimidating. All joking aside, our communities need to hear from people who aren’t the maintainers and conference speakers and web celebrities. We need to hear from people who give zero fucks, who never worry about their Klout scores or how many people starred their repo. The big names create an echo chamber where ideas are safe and popular and failure and being wrong are covered up so no one else can learn from them. We don’t really badly need any more of that crap. We need you.


70 Responses to “how to blog about code and give zero fucks”

  1. Gersande Says:


    I like this post.

    So here’s a comment! 😀

  2. Matt Says:

    Okay, you just convinced this white dude to start a dev blog. Thanks for the lols and the great advice :)

  3. warper Says:

    I do like this post. And so I comment and retweet.

    @Warper (another white guy)

  4. Pantalaimon Says:

    I think this is a lovely post about posting about code, and I hope a lot of people see it and take it to heart.

    I feel like your pining for more diversity in the field is admirable, but at the same time, I always feel like the way to combat this is to give less of a fuck… about who is giving less of a fuck. A person’s gender, ethnicity, social leaning, sexual preference, favourite bands or taste in socks does not really factor into my wanting to read their code snippet commentries… or anything for that matter.

    I am willing to concede though that I do not know which approach will in the end deliver the desired goal (more diversity, better writing, better stuff).

  5. chillfinn Says:

    F-in A dude, this is a (wake up) call.

  6. Jase Says:

    The only special group I can claim is “bearded half arsed devs” as I am in fact a white male. And that particular group is not very small. But I do give no fucks at all, and I like what you have to say. That’s the end of my story.

  7. John Saddington Says:

    this. blog. is. fucking. epic.

  8. Bob Cochran Says:

    Hi Garann, I wonder if all the developers you are interested in reaching out to are actually in better-paying high-tech careers? Take my dentist for example. She has plenty of tech skills and I rather think is paid better than me by a large margin. That may be true of my architect and various medical technology people. There are probably plenty of women auto mechanics, aircraft pilots, mechanical and professional engineers and all paid better than web developers. Perhaps the market is saturated with too many skilled programmers and compensation levels are in attractive? I have doubts that software development is compensated as well as a professional engineer is.

  9. Tom Davenport Says:

    Excellent writing advice on any level.

  10. wizonesolutions Says:


    To people who think the F threshold on their blog may be higher than 0, just start a Tumblr. I did: Compare that to my Actual Blog. The Tumblr is where I occasionally dump my, “wtf, I can’t figure this out, tell me how to please world” or “I had this idea I’m never going to implement, please steal and send me a link, here is a spec” (not in those words) ideas.

    Would love to see more. Even though I am a dude. I’m only half-white, maybe that counts?

  11. Greg Ward Says:

    When did quantifying the precise number of fucks one gives about something become a thing? I like it!

    (And why always zero? Can’t I give 2.3 fucks about something I care a bit about?)

  12. Terry Karney Says:

    This is good, about anything one might want to write about. Thanks, I’ve been remiss.

  13. Niki Brown Says:

    Just the nudge I needed – thanks!

  14. Lukas Eder Says:

    Heh, this sure made my day. In case your problem was about Java or SQL, it might’ve been answered in this blog of mine:

    Otherwise, after all that ranting, you still haven’t told us what you were actually looking for… 😉

  15. HCL Says:

    if only I had a real blog!
    but I only got a tumblr.

  16. Chatman Says:

    This is a fantastic post. And you’ve made a few points I’ve never given much thought. I mean, I do write posts occasionally about what I’m using or building, but I never thought it mattered if I did or didn’t. I just like building things. Even though I have said it to myself over and over, it never quite sunk in that my little experiments and fixes as I learn were bloggable. After this, I’m kind of questioning the idea of what bloggable means.

    Also, you’re completely right about the echo chamber. I respect the hell out of the more experienced and active developers, but it does seem like the same ideas and technologies are being endlessly aped. Do you have any idea how hard it was to find any information on Wintersmith? Sure, there are examples to learn from, but without context we’re kind of walking blindfolded through a repo.

    I can’t speak for anyone but myself, and part of the reason I’m reluctant to blog is some fucking irrational fear of not being good enough. Part of my problem is that I may give too many fucks about the code I write and jealously guard it from dissection, so it’s hard to let people see the rough edges of my growth as a developer.

    Though, if the alternative is a room where everyone agrees with each other and no new ground is broken or ideas are too sacred to challenge, then those of us who aren’t saying much probably should say more.

  17. Edie Says:

    thanks you for the (virtual) kick in the pants.
    I promise to get back to my blog (which has only one post from almost a year ago.)

    – a programmer chick who should be making more noise.

  18. hairmare Says:

    Thanks alot for this refreshing post. This might just have been the needed input I need to start blogging again while giving zero fucks. Next time some social media manager (how is that even a job title) tells me i need to blog better I shall merrily send them to your blog whilst throwing in a reaction gif.

    For the record, I’m another commenting white guy.

  19. Molly Says:

    I’m a designer, not a developer, but this is the most inspiring blog post I’ve read in a long time! I need to make more noise.

  20. Clemente G Says:

    Haha. Made my day.

    And if that doesn’t work

  21. John Haldson Says:

    Great article Garann! I’d love to write more about my favorite programming language, JS, and have came close many times but never went through with it.

    I will make no excuses about it or deny the truth, the biggest reason for me is fear of the backlash if I make a mistake or two. If you are writing about an advanced topic, the JS community can be very harsh – there is a certain brigade of well respected, smart and talented JS leaders in the community who will take the time out of their day to literally pounce on you. I won’t say names, but I am sure there is a lot of people here who know exactly who I am referring to.

    I am not saying that incorrect information should not be pointed out and corrected, it’s for the greater good. But it’s the manner and tone that people can take that I find very discouraging and downright unprofessional.

    So a lot of it for me is to weigh out the risk/reward. Is it worth it for me to write with the risk a making a mistake, then have my name and writing associated with the negativity that I am potentially going to receive from the community?

  22. Teresa Says:

    would you call me every day and tell me this, please?

    particularly this: “The internet is full of horrible crap! If your horrible crap is at least well-intentioned, it’s probably a step up from the other horrible crap.”

    and this: “This is great! It means there’s nothing for you to be embarrassed about. It means no haters will leave you nasty comments about how you should indent with spaces.”

    especially since i’ve seen so, so, so, so, so many things posted by white guys that have been hated on by other white guys… and i’ve seen lots examples of women being treated as second-rate programmers or being sent the message that they can only be programmers if they’re in the “hot chick programmer” group…. that results in me thinking i’ll have to be _perfect_ to put anything out there about programming.

    p.s., @chatman, you speak for me, too.

  23. haliphax Says:

    Full disclosure: I am a white dude. :)

    Damn straight; my blog is almost 100% focused on dumping code that solves problems I’ve encountered. I love that there are people out here like you, Garann, who are willing to put in the effort to also write about social inequality, anecdotes, policy, and the like, but I also dig that I can just dump the PHP script I finished onto my blog with a brief explanation and be done with it. If more of the women in (or aiming to be in) the tech sector would do at least that much, I think it would get the ball rolling for them to go further with it.

    I hated blogging of any kind until I had a few posts under my belt; at that point, I came to realize the benefit of having this historical record of my hair-pulling problems and their eventual solutions.

    Cheers for the great post. Love your blog!

  24. Samson Says:

    Splendid post. Last time I checked I wasn’t of the white persuasion, I blog, and half no fucks to give.
    Happy coding!

  25. andy Says:

    Awesome – thank you!

    Admittedly, I am a white dude but a white dude who left a decent paying (soul crushing) corporate gig to make websites because I love the work. I’m also self-taught, so the sense that I’m an outsider looking in, is ever present. The industry can be intimidating in that way, so this post was a nice a slap in the face. Thanks again

  26. Angela Says:

    Good job! This is so encouraging. I always want to be a know-it-all, and I REALLY am learning so the idea of exposing my ignorance through a blog is uncomfortable. The choice for blogging about our mistakes is either have a thick skin for the trolls, select no comments or publish privately. Recognizing these machinations, the Ada Initiative is financing GitHub accounts for women, who want to start off by writing code privately.

    It’s great you are championing non-perfect exposure.
    Instead of being pro Pixel Perfection we should all be pro Pixel Fuckup.

    I came across some code I wrote last year, and I have made huge improvements. I wouldn’t have known that if I didn’t have the record.

    Today, I’m stumped about the whole clearfix, flexbox, display:inline and whatever other technique there is for fixing positioning issues. Feel free to offer an opinion. There can be TOO much information and dated approaches on stack overflow.

  27. Natalie Says:

    I am a woman and used to work as a civil engineer (I am now a software engineer) and from my 5 years doing my MEng and my 10 years working as a highways engineer, I would say that women are under represented in that field and other “traditional” engineering fields too (I work at British Airways at the moment and there aren’t many women pilots and mechanical engineers).

  28. Katherine Says:

    All right, you’ve convinced me. I don’t have a blog at all, and I haven’t even blogged elsewhere for well over two years. This from someone who makes her living writing a platform that lets anyone spin up their own website. I will go remedy that.

  29. Jo Says:

    This is a pretty entertaining post, with a great message!

    I’m just starting out and I figured that to start blogging about code I need to master development first or at least have a few years under my belt. Especially since there are a lot more skilled and experienced people out there.

    But this is definitely something to think about, moving forward.

  30. R. Mullen Says:

    Oh man, You hit it on the head. I’d starting writing about code like 20 years ago, and then just stopped… I LOVE code and would write about it all day, but it always took back place to…eh…a similar fascination with yaks. OK, it’s a deal: it may suck, but gonna do it!

  31. angelaflangela Says:

    Ok. I will, why not! Why the fuck not.

  32. Mike King Says:


    “I don’t normally blog, but when I do, there will be zero fucks given.”

  33. Amy Says:

    Wanted to add my “thank you” for writing this. I’ve been meaning to write out a web dev essay/article I thought of at 3am one night, but honestly figured no one would care. It’s not about topics I see very often and I’m not an expert speaking at conferences.

    Thanks again for the inspiration. I still love the web community.

  34. John Says:

    I’ve taken Garann’s advice and started blogging. Anyone have any tips on posting readable code that doesn’t take 20 minutes of fiddling around with formatting?


  35. Andy F Says:

    Ahh man it always brightens my day to see one of your posts show up in my Feedly 😀

    (sorry, I don’t really have anything constructive to add, although I guess I could mention how this post has inspired me to write more about dev stuff in my mostly World-of-Warcraft– and photography-related blog)

  36. SteveL Says:

    I do occasionally write about code, but sometimes it is documenting essentially futile suffering that I think that I would probably put anyone of any gender or ethnic group off ever touching a keyboard and taking up a career more satisfying in the fast food industry.

    Maybe that should be one of the issues: only write about the extreme suffering parts of coding if provides entertainment to the audience.

    Oh, and never include the error text from any windows popup in a post except as a screen shot. This is to keep away from google-referred support posts coming in five years later.

  37. Lindsey Says:

    Once upon a time I had time to blog about things I loved (design, CSS mostly, WordPress, web dev stuff). There isn’t a single day that goes by when I’m working on a project and I do something really, REALLY cool and think – holy shit I have to write a tutorial on this, or provide examples to those who were once like me and needed to learn by example, or for the lazy/short-on-time dev who really could just use a solution to an issue that may take them hours otherwise.

    But, like you said, I fall into the “I work XYZ” hours a day and by the end of it I don’t have the energy or drive to write that post. (Mostly because even if my coding-work ends, my household responsibilities do not).

    But I definitely agree with you – I remember a bunch of years ago when things were changing so fast in development and design and everyone and their mom had a blog about it and I learned so much, connected with so many people… and now, it seems people have substituted those long thoughtful/helpful blog posts with crappy tweets or links to other people’s blogs who took the time to write it up (I’m guilty of this, of course).

    I think I will start carving time out at least one, maybe two days a week to write up those awesome ideas I have. To work on a tutorial that I know people could really use. To share code snippets that took me forever to find/write/bugfix. . . to be a part of the community again…

    PS: I’m a white female, who works freelance full time (and then some) with 5 kids 😀 Time is something that is very much at a huge deficit in my life.

  38. Andy F Says:

    @John: depends how you’re storing your posts. If it’s Markdown, formatting’s pretty simple (albeit not syntax-highlighted unless you add further complications), but if you’re writing posts in plain HTML you just need to wrap everything in a set of <pre><code> tags </code><pre> and make sure to escape any < , > and & characters.

    God I hope those HTML entities work as I intended.

  39. John Says:

    @Andy The tag works pretty great. I’m still having issues with tabs in my code being much larger on the page, and therefore causing word wrap. Do you know of a way to define how much space a tab takes up?

  40. Pat Ulrich Says:

    I’m not saying I’m gonna blog but I am a 50 year old woman who has been coding going on 16 years. I’m honestly not sure I have the ambition at this advanced age to even try. I did write a online HTML tutorial last year ( but quickly lost interest so my track record isn’t stellar.

    Lately, I’m stuck doing SharePoint development and I’m pretty sure that no one gives a fuck about that. I know I don’t but have learned a few tricks over the years to make it less painful. I guess I could share (get it?) this knowledge. Might keep someone from committing suicide. I’ve come really close a couple of times.

    Love your blog! Austin rocks and I would live there if it wasn’t in Texas.

  41. Sonia Says:

    Thanks for the inspiration – This is the kind of motivation I need just about now!

    — Developer from two underrepresented groups, female and latin. :)

  42. Rose Says:

    Fantastic stuff. Keep kicking us in the pants, Garann. Maybe I ought to blog about times when I totally fucked up, just to get the fear of looking like a fool out of my system.

  43. LoriW Says:

    So, you’re saying that you can’t find my Tumblr*, eh? :)

    -Not Male, only half white, never expected anyone to take a look, haven’t updated in a while, but mostly because I’ve been doing other stuff.

    *I’ve surprised more than one individual by having a tumblr with just text, no pics.

  44. dlminton Says:

    What a fucking great piece of writing!!!! This essay (and that is what it is, a damn fine one, too) goes SOOOO far beyond just the issue of writing about code.

    As a 65 yr old who, at 50, learned to hand code his HTML and PERL (yes, PERL and it still works) by apprenticing myself to some obnoxious young shits, I have found the tools of “thinking programatically” as valuable as ANY learning skills I had previously acquired in my half century of being an auto-didact.

    So soon I will write something about how frustrating and cool it is to discover the “bit drool” when a linux command,( specifically the word “concatenate”) is used in one of my client’s screeds via my CMS PERL progam will break a heretofore perfect CMS script (and if they refer to a CD/DVD, too, but not a DVD/CD).

    But now, I think I’ll tweet this to the 12 followers I have and suggest it as a general cautionary tale of good writing and blogging, irrespective of topic.

  45. Arash Says:

    You inspired me to finally take the first step after thinking about doing it for years.


  46. Karen Morrill-McClure Says:

    Great post. I get most of my inspiration & solutions from the web and blog posts are my favorite format (thank goodness for news readers!).

    I just started blogging more about HTML/CSS & teaching on my blog.

    It was actually a coder’s laziness that prompted me to get blogging: I was tired of repeating the same explanation to my students 50 times. Much easier to say it once then point them to the blog if they have any questions.

    If you’re interested in front-end web development, UX, teaching & sometimes gaming & movies, stop by:

  47. Heidi Says:

    I don’t keep up with my blog because I agonize over every word and it takes me forever to write anything. I think I’ll take your advice and start giving 0 fucks + drinking + not posting it immediately but reading it the next morning.

  48. Doc Deuce Says:

    I’m black and I’m on the way. Thanks for the kick in the pants.

  49. Oscar Pagani Says:

    Very nice post Garann!

  50. Kris Black Says:

    I started my own blog about customizing Squarespace sites. Unfortunately, for the topic of this post and not because I think I’m unfortunate but, I’m a white male. Hope that’s okay. Maybe being a developer and designer that exclusively uses Squarespace is enough to be considered a minority of sorts.

  51. Susan Says:

    Okay, I will do et.

  52. Elizabeth Meyer Says:

    I love this post. Thanks for the inspiration!

    *white girl from South Africa – I’m sure that counts*


  53. Ilinca Hallerg Says:

    Just the kick in the butt I needed to actually start the blog I’ve been thinking about for quite a while. Thanks for that!

  54. Anthony Teo Wei Pin Says:

    Asian male. Frontend guy. Blogs even while no one is reading.

    Enough said. :)

    (Oh, and of course – nice post.)

  55. Sheelah Says:

    Thanks for this! It kicked me into action and I finally put a new post up on my blog on something that I’m definitely still learning about — AngularJS.

  56. Alexandros Spyropoulos Says:

    I love this post. I really loved this post. You convinced me, but I’m a white dude…

  57. Alexandros Spyropoulos Says:

    And I feel it applies outside bloging for code too.

  58. Hannah Says:

    I’m a woman and you’ve inspired me to write about code. Now, to actually follow through….

  59. Mark Says:

    You should blog about the trivial stuff you couldn’t find an answer for on the goog like using the samba tool suite to print from your web app on Linux. Save the rest of us five hours of yak shaving. It’s usually free and easy too… check out wordpress.

  60. Alan Says:

    I also blog, and I’m not a white male.

    I’m far from being a celebrity, but the number of followers grow by the day, although my blog in spanish because it serves my niche minority (hispanics).

    That said, this post is awesome and if you don’t min I’d love to translate it to share it with my audience.

  61. Susan Says:

    I feel like tech is the next boys-club field that is in for a shake up. My sister faced the same pressures becoming a surgeon in the 80’s and 90’s. I have been through programs in ceramics and philosophy (both of which are also dominated by men) but I feel like the novelty of being female is most palpable in technology. It’s like if you’re there you’d better be one of the best in the room or you’re summarily dismissed.

    We definitely need a more visible presence, and a stronger voice. Thank you for posting this! Maybe I could start a tiny blog…

  62. David Y Says:

    Jamaican and truthfully should blog more. Inspirational article!

  63. Steve Jones Says:

    I like the post, and thanks. I agree with most of what you wrote, but I’d disagree that you shouldn’t pay some attention to grammar, spelling etc.

    This blog represents you and in some sense, represents your communication. Swearing, bringing out some of who you are is great, but if you can’t communicate well, and can’t write English sentences, I’d worry about your skills in this area at work.

    It doesn’t have to be academic or formal, but at least be readable.

  64. Ben Says:

    Thanks, this is really motivating. I’m gonna start writing.

  65. Ryan Says:

    So I had been thinking about doing this very thing. I give very little [****]s, but not exactly zero.

    However, I feel motivated to post some of the issues I have been working through that I could not find any info on google, stack-overflow, or server-fault.

    Unfortunately for you I am a white male.

  66. Amy Mac Says:

    This post really motivated me to start blogging more about the code I’m working with. Thanks a ton!

  67. Szymon Wojcik Says:

    Thanks for blunt and honest words that will keep my will to blog about code. If anyone’s still considering starting and haven’t done this – make up your mind and start.
    If you don’t give a flying fuck about anything else but your passion, you’ll be surprised how much you can learn by blogging.

  68. Scott Says:

    Thanks for that kick in the pants. I have been away from the community for too long now. Thinking that there are no new ideas and someone must have already written/talked about that is crap. There are always new ideas and new folks to the community who think everything is new and refreshing – I need to look at it more from that angle.

  69. Mariam Says:

    Hi there!

    Thank you, good points in your post! I recently started blogging, and this article was really useful!

    I am indeed white, but otherwise not the stereotype, as beeing a female, webdesigner and a muslim woman wearing hijab. And I post about code :)

  70. Barbara Shaurette Says:

    Here’s the bind I find myself in: I’m doing a lot of good Python/Django work right now. If I had time, I could sit down and blog for days – weeks, even – on topics code-related. I’m exactly the kind of person who should be blogging about code.

    But as one of those rare women who’s been in the field for a really long time, I’m also answering the call to teach, mentor, organize, try and help other women in whatever way I can. And it takes so much time. I’m overextended as it is. I never get out anymore.

    So I have no idea which thing I’m supposed to drop in order to start doing this other thing. I’m not not-blogging out of lack of concern or laziness or anything like that, I promise. :) This is one of the reasons we need more women – if I could, I’d clone myself.