It’s no secret anymore that strong writers have become a hot commodity at tech companies–and I’m talking about writers of sentences, not code. But can a given writer write about…
By Piotr Gaczkowski, IOD Expert When I first started writing for IOD, my belief was that writing was optional for engineers. I’ve changed my mind. Even though your main responsibility…
By Ofer Prossner, VP Operations, IOD When people ask me if I like to write, I admit that writing can sometimes be a pain, especially if the assignment is one…
By Liz Heflin, IOD Editor In the 1937 film Shall We Dance, there’s a famous scene with Fred Astaire and Ginger Rogers sitting on a park bench quibbling over the…
NEXT WORKSHOP: APRIL 25, 2018
Have you always wanted to start a tech blog, but worry you can’t write well or, worse, fear you don’t truly have anything important to say? Well, you can and do. More and more technology experts — from programmers to data architects to operations engineers — are researching and developing original content, and getting paid for it!
By Tina Ornstein, IOD Editor
Blogging on technical topics for a knowledgeable audience is a little bit like tightrope walking — it requires incredible balancing skills and one false step sends you plummeting into oblivion. In other words, if you don’t find the right balance between technical expertise and audience engagement, then your blog will be ignored (which is the equivalent of oblivion in the content world.)
At IOD, we have developed and perfected our own secret sauce for helping our customers reach their target audiences. Our methodology is based on one simple mantra: “writers are not experts and experts are not writers.” Thus a successful technical blog, (i.e., a blog that gets traction with its target audience) requires the collaboration of an expert and a content person — either a writer or a proactive editor.
Although chefs tend to guard their secret sauces carefully, we at IOD believe in transparency and are happy to share with you the key ingredients of ours.
Writing articles and blog posts is a lot like writing code. First, you nurture an idea in your mind. Perhaps, the idea came to you in the shower, or maybe…
By Jen Maidenberg, VP, Editorial, IOD
In the time since I started a varied career that has always included some element of writing, the definition of “editor” has never been consistent. It changes depending on the publication or company I am working for, and has dramatically altered over the last 15 years as “features” have become “blogs” have become “content.”
By Jen Maidenberg, VP Editorial, IOD
One of the things I really love about working at IOD is our philosophy of transparency. Everything we do – including our communications with customers about the content we create – is honest and forthcoming. This works especially well for me. Why? Because I don’t have to pretend I know more about cloud or DevOps or cybersecurity than I actually do. In another setting, I might feel self-conscious about that. But at IOD, I don’t.
What I am an expert in is storytelling, editing, and messaging. I’m also really good at identifying and nurturing talent. I’m a bit modest off the page (another truth about me) so I won’t list all my credentials in those areas. But suffice it to say, Ofir, our founder and CEO, hired me because of my background in publishing, content marketing, and branding. Also I love getting to know and talking to new people. This is something I have to do often at IOD, as we’re always recruiting new freelancers to our team.