3 ms·
"Just because somebody has a blog or a twitter account it doesn’t make them a good developer or expert. It just means they shout louder." Exactly. 99.9% of dev
by greenyoda 13y ago
"Just because somebody has a blog or a twitter account it doesn’t make them a good developer or expert. It just means they shout louder."
Exactly. 99.9% of developers' blogs aren't worth reading. They're full of articles like "I just wrote my first Go program, and here's what you should know about it!" Please, if I wanted to learn about Go, why would I read something that was written by someone who just admitted he knows almost nothing about it? I'd rather go to golang.org and read the tutorials written by the developers of the language.
- elwell 13y agoWith that said, such posts may benefit the author most; teaching others is a great way to learn.
- CGamesPlay 13y agoMany posts along the lines of "my first Go program" are just forays into blogging. Many will never get past that, but eventually an author will be able to solve difficult problems and then blog about those. For example, Joyent's blog post from a few months ago about building video analysis for Mario Kart was great. It summarized the steps and methodologies used to find the solution, and demonstrated how a reader could do the same. Additionally (since it was a company blog post), also worked in an advertisement for a service they provide. Search for "joyent kartlytics" to find the blog post I'm referencing. Crappy blog posts are crappy, but some are stepping stones into better ones.
- FuzzyDunlop 13y agoSounds elitist. The only crime the author would have committed there is choosing a linkbaity title for their post, because something like that could cover any amount of interesting topics. "Understanding Go and Coroutines as a PHP developer" for example might be useful, and it wouldn't suffer from being written by someone who hadn't absorbed the living spirit of Rob Pike before they wrote it.
- greenyoda 13y agoIf preferring to learn a subject from someone who knows it well (and has spent days or weeks rather than minutes editing their prose) makes me an elitist, then fine, I'm an elitist. Your hypothetical article about Go and coroutines could be very useful, provided that the author has had some significant experience with both Go and PHP (e.g, they've written and maintained non-trivial programs in both languages). Otherwise, it's likely to be full of misconceptions and even errors.
- Arnor 13y agoCool, someone _does_ read my blog :) I've been feeling like a bad developer because I never write. Then when I try to write, I think wonder why anyone would read what I'm writing (because it's about my first Go program) and I give up. Even when I come up with something relatively novel, I usually just get the info out via StackOverflow. The point: those useless dev blogs with posts that don't matter to anyone are there because many devs (i.e. me) without much to share, feel obligated to write.
- rfnslyr 13y agoKeep a notebook handy and whenever you have thoughts worth writing, write them. Expand on them later. Write drafts, expand on those, iterate, rewrite. Once you feel you have a concrete idea or article down, publish it. A lot of these developer blogs read like spur of the moment publishing. Unorganized, baseless rambling.
- mikeash 13y agoThat's really weird. Feeling like a bad developer because you never write would be like feeling like a bad racecar driver because you never bike. Totally different activities.
- saraid216 13y agoInstead of blogging, I use things like Google Plus. It's not shocking for me to post something silly and inconsequential and completely egocentric like "My First Go Program", but it's also public and discoverable on the off chance I do something flabbergastingly amazitastic without the overhead of an entire blogging platform. (And no, before you go looking, I don't identify primarily as a programmer, so my G+ is not full of random code snippets.)
- jared314 13y ago> why would I read something that was written by someone who just admitted he knows almost nothing about it? You are not the target market. Those posts exist for the same reason people create a Github account, but never contribute to open source projects. It shows exposure, and a history of interest, to interviewers who google you five minutes before the meeting. Everyone can argue the merits of different interview techniques and quality indicators, but, without a verifiable history of success, you have to start doing something to publicly show merit.
- rietta 13y agoThat has been my impression too. Dark matter developers are people who work in software development in the employ of a company. Their employer may - and usually does - have a blog and a twitter and may well have dedicated marketing and sales teams. So even though these developers may not personally market, their employment depends upon these non-dev activities. For me, personally, blogging and going to conferences is pure marketing. It works too. It results in me and the guys who work with me to have an income, thankfully. It's about demand creation for our services. Many people who are awesome computer scientists and programmers are not looking for that lifestyle. They work for good companies that pay them well to code. They do not have to worry about the non-coding tasks that need to happen for there to be that coder job. Sometimes I envy their situation, but I am now personally addicted to self-employment, business, and startups. I love coding and do it for my livelihood, but I do not feel that I am called to work as just a programmer for a company. I do like the analogy still. It's like the dark matter halo that presumably encircles our galaxy. It's unseen but is vitally important for all of our existence.
- lightblade 13y agoI would argue that those that blogs demonstrates their written communication skill, whether it's good or bad is another matter. But I would definitely more likely to hire people that can demonstrate this over those that are unknown.