Engineers should blog publicly when they have something to say. Something useful for their colleagues. Engineers shouldn't waste time forcing themselves to blog instead of work just to push their career forward: frequently they just expose they don't have anything to say in extremely unreadable way. What a waste of time for everybody. Soft skills helps you grow as an engineer, it's true, but I think it's important to…
Engineers Should Blog
51–60 of 130 posts
Re: Engineers Should Blog
#52Earlier quoted context omitted.
Jekyll is pretty great (just chuck a disqus block in your footer), there's a real risk of getting bogged down in setting up the 'perfect' system with it and never getting round to publishing anything. I think Wordpress still has one of the most outstanding install experiences, but keeping it up to date is a pain.
Cool, I may give Jekyll another shot(had a false start couple years ago). I have tons of experience doing hardened WP installs(and compromise root cause) but almost no experience USING it haha. I'd prefer not to go down that rabbit hole if something like Jekyll is sufficient.
Might not be right for you, but I had to bring up the easiest, the truly minimalist, hey, the original way to it.
Re: Engineers Should Blog
#53Engineers should blog publicly when they have something to say. Something useful for their colleagues. Engineers shouldn't waste time forcing themselves to blog instead of work just to push their career forward: frequently they just expose they don't have anything to say in extremely unreadable way. What a waste of time for everybody. Soft skills helps you grow as an engineer, it's true, but I think it's important to…
Also, writing is a skill. The more you write the better. That means you will sometimes write shit. Thankfully, you can go back and rewrite your early work when your skills improve.
I normally write short posts and then revise them afterwards as many times as required. In fact, I edited this post to add more info.
Re: Engineers Should Blog
#544. The topics I want to blog about are controversial.
That is, strong but controversial opinions on certain technologies are just as likely to help you get noticed as hurt you (i.e. get noticed in a negative way.) Even if the topic isn't technically controversial, it can still be a negative. Revealing that you helped {religious minority church} set up their network, or that you solved a problem with {porn website} can also put a mark on you that is not automatically good. Heaven forbid you worked for/supported {political organization} this election cycle.
So the answer is, of course, to self-censor. You have to strip out your opinion and context and only blog about technical details that you are very confident are correct. Keep your jokes gender neutral and your insights limited to your profession.
But that's boring. That's not blogging, it's writing a corporate memo. We've just ratcheted up the difficulty, limited the new thoughts you're allowed to think, and made you invisible to all hiring managers who can't recognize when your technical manuscript applies to their industry.
Re: Engineers Should Blog
#55I have been blogging for over a decade and have definitely had some positive experiences, including a co worker finding a post when searching for a solution and an interviewer checking out my blog and mentioning it. I have also had a small bit of work come to me directly because of my blog. (However my blog is pretty unfocused in part because I am a generalist and primarily wrote for myself. I am sure a focused blogger could do better.)
However, the most important thing is to get started with some kind of public presence. If SO or HN or github are what you feel comfortable with, start there. Don't be an anonymous programmer.
If you are looking to blog, I think you should plan to stick with it for at least a year. Nothing is sadder than the abandoned blog. Here are some motivational tips: http://www.mooreds.com/wordpress/archives/2129
Re: Engineers Should Blog
#56People like engineers and other folks with technical jobs have some of the best writing material to work with - all they really need to do is recount their day's work and the problems they've encountered, and any non-expert interested in the field can read and learn from it.
There is a plumber who lives in my state who publishes video documentation of every job he goes on. Since I'm not a plumber, I learned a ton from these videos. All of the things he did would seem basic to anyone in his field, but for a lay person like myself, his videos were extremely educational.
Re: Engineers Should Blog
#57Re: Engineers Should Blog
#58Oddly I love speaking at conferences...maybe because some nonzero audience is more or less guaranteed?
Re: Engineers Should Blog
#59I think this misses another equally important reason, which is to do your part to help build the gift economy upon which we all rely in our day to day work. Near every common solution and recipe has been written up by someone, somewhere, and we all make use of these gifts. When you learn to do something useful that other people will likely also have to accomplish at some point in time, write it up. Not only will it b…
While I agree generally with what you've written here, my only issue with it is that writing it up takes about as long as building the thing, and I'm pretty lazy. Also, if someone, somewhere, has written up nearly ever common solution, how do I know which ones are novel enough to put the effort in to publishing. Most of things I build aren't novel or new in any way, I'm fairly sure.
Re: Engineers Should Blog
#60I'm surprised he didn't encounter the 4th reason for not blogging: 4. The topics I want to blog about are controversial. That is, strong but controversial opinions on certain technologies are just as likely to help you get noticed as hurt you (i.e. get noticed in a negative way.) Even if the topic isn't technically controversial, it can still be a negative. Revealing that you helped {religious minority church} set up…
But you could look at the flip side of that and say that this is actually filtering out opportunities wouldn't be a fit. Much like qualifying leads in sales is something you want to do as quickly and easily as possible, doing the same for employment opportunities can help you focus on organizations where there is a culture fit.
With respect to your example, if an employer was offended by your support for a minority group or political candidate, is that an employer you'd feel comfortable bringing your whole self to work at?
I may be hopelessly Pollyanna, but I think I'd avoid that type of situation. If you are a software developer and those are the only type of opportunities you have access too, I agree, you should avoid blogging about such controversial topics. Or get good at remote work.