I'll have to second MS. I'll have to check out these individuals, but for sure some of the teams have been putting out really good reads. Recently with the chakra and DOM articles for edge, and I also enjoy the TypeScript and .Net blogs on a regular basis.
Depends what you want to get out of them. I find some are mostly focused around some of the more unique/cool challenges they come across (Google[1][2], Slack[3]), and others are more about how they solve the engineering challenges they face through software and/or about their dev process (Uber[4], Twitter[5]). Some are mix of the two (Dropbox[6], Netflix[7]).
What are peoples' thoughts on the marketing effectiveness of quality relative to quantity in blogging? We have recently started publishing what we consider to be very high quality material (the majority of them have front-paged on HN if that's any indication). Most of these have been published on [1] so far but we're in the process of transitioning to a more official company blog [2].
A close friend who really knows his way around marketing has been advising us to write more fluff pieces. We're really torn over this because we strongly dislike vapid content as consumers. I would be really curious to hear any anecdotes on the relative merits of the different strategies.
The answer to this depends entirely upon who you're trying to reach with your tech-blog-as-marketing approach. If it's primarily recruitment-oriented marketing, or you're marketing a tech product (apologies, I haven't checked the link - but it's not relevant for this general advice).
If it's recruitment-focused or you're a tech provider marketing to technical customers quality is probably more important. The intended audience is educated enough to spot and dismiss fluff outright and anyone that doesn't isn't a recruit or customer you want.
If your goal is marketing to non-technical people who buy your product a technical blog is probably irrelevant at best and potentially destructive at worst. If the customer is non-technical and doesn't understand the material you present publicly, they may be scared off. Fluff pieces that demonstrate knowledge with lots of buzzwords that appeal to middle-upper management will be more effective with this audience.
Thanks, that meshes well with my thoughts on it. We're less concerned with hiring right now than with acquiring more clients, but our customers are generally developers at small to medium sized startups. We fall into that category ourselves so we've felt like things that would appeal to us would also appeal to our customers (and vice versa).
From marketing standpoint, you might want to study the sharing pattern of your readers. Some people are excited about headlines and link baits. These people also have short and shallow attention. Some people like deep domain specific information. They might be your target audience.
You want your messages to reach the right audience organically.
Put your really impactful content in your blog and your fluff pieces into its own section/knowledge base. (stuff people will probably search for but wont share). People who find your blog will just see the impactful stuff and will want to subscribe.
Awesome, I really love meta-analyses too! Our product involves web scraping so it's a natural fit to write articles about scraping and analyzing data in general. A few of our articles so far [1,2,3] would probably be classified as meta-analyses and we have some more in the pipeline! Feel free to sign up for the newsletter in the footer of http://intoli.com if you would like to read those articles after they're published :-).
Perhaps you can use web scraping to build bots to read and classify these tech blogs. I am sure the API to these metadata graphs will have strategic values to VC, recruiters, tech consultants, etc.
Not an "engineering blog" in the traditional sense. Percona has been posting deep-dive high-quality pieces about database performance and the inner workings of InnoDB since around 2006, so more than 10 years now. If you've ever had to troubleshoot a weird performance issue in MySQL as an Ops guy or DBA, you've probably ended up finding this in your Google results:
Haha, basically all the big names :) There are some gems spread out across them all for sure; such as "The Log: What every software engineer should know about real-time data's unifying abstraction" from LinkedIn.
Came here to upvote DO. Most of the companies mentioned here write articles about their products, infra & engineering marvels.What makes DO different is that their articles are written for the end user.They have some of the most helpful articles on setting up servers, from start to end, with examples. Although not all posts are written by their own engineers [1] (nothing wrong, just saying).
Their posts rank well, higher than Stack Overflow for 'how do I install this on Ubuntu' articles plus you know the instructions are highly likely to work without excessive featuritis (certain how to perfect server guides spring to mind).
Along the way one is likely to get a free-ish 'droplet' at some time and the combination of the articles and the occasional droplet use makes one a customer almost by a process of osmosis - it becomes hard to not like Digital Ocean.
I do feel that they may have lost the momentum on the articles though, or maybe I am just not doing so many Ubuntu setup things, whatever the reason I have not used their articles a great deal over the last year.
Does anyone else think they need a bit of a reboot and to update/crank out more articles?
I have to agree that the posts I've read from DO have all been of the highest quality regarding ops-stuff. I think the bigger companies could use same kind of dedication to user-friendliness and focus more on making their communities better.
i've never been interested in video game development but one day i saw an article they posted giving a technical overview of their graphics pipeline [1] and i couldn't stop reading.
They run a pretty modern cloud stack using fun technology like terraform, which gives me serious envy as well as inspiration. They also have some ridiculously high quality posts with open source code included such as:
https://segment.com/blog/the-segment-aws-stack/ (highly recommended reading).
Thoughtbot, in addition to having a really good blog, is at least in the running for one of the best names (Giant Robots Smashing Into Other Giant Robots).
Disclosure: I'm an Editor at the Toptal Engineering blog.
Toptal has extremely active and wonderful blog for developers[1], designers[2] and finance experts[3].
The reason I can make that claim is because Toptal's blog posts are contributed by members of our network, all of whom are verified experts in their fields, and we guide them through the entire process to help them write the perfect blog post.
We publish new articles almost every day! We invest a lot of love into maintaining our publication and try to publish the most useful content for fellow experts.
...a pretty mixed bag with some product & PR posts inside, but the gems inside (especially SRE / CRE life lessons) are pretty awesome.
Also, we're getting started ourselves with some quality tech material - not too much there yet, but our Debugging Postgres post got a lot of love from the community: https://www.justwatch.com/blog/
Unfortunately there doesn't seem to be an index of the posts on one page! There are links to relevant posts on the sidebar and both of those have good relevant links.
These guys I worked with for a long time, to get my post out! It kind of stung a bit when the v1 PAAS was officially deprecated before I got to put it online. But in terms of support, the newer solutions are only better. The lessons learned putting this post out are still valid, even if the specific product of the tutorial is no longer relevant. (I used this process to create my own CoreOS bare metal cluster, and I don't actually use DigitalOcean in my day-to-day work.)
But the other content on the blog really was a good, focused introduction to Kubernetes and friends for me. Deis is the team that created Helm and it was subsumed into Kubernetes (and Helm Classic, which was another iteration before it was part of Kubernetes proper.)
This is an American company that strips SSL from many, many medium value targets; if they aren't thoroughly owned then the surveillance state is being negligent.
A paranoid man would go even further than that and assume that monitored DDoS-proofing goes hand in hand with targetted, state-sponsored DDoS attacks.
I don't dislike them because of shitty services or customer support or anything. In fact, in those regards they are pretty awesome. It's just a privacy thing. For details see the other responses.
Disclosure: I work there and have written articles for the blog.
At the moment we mainly blog about our experiences with Golang (our language of choice right now). But really it's open to any topic someone in our engineering team is interested in writing about.
The Caktus team has a great technical blog with many posts about Python and Django. I've also really enjoyed visiting with their people at PyCon over the years.
FittedCloud is a small start-up that does automatic cloud resource optimization. They post regularly and go into topics ranging from technical details of machine learning to cost optimization for AWS resources (EBS, EC2, DynamoDB, etc).
As far as I can tell, they are the only company around that can automatically scale up and down EBS resources in a way that the customer only pays for what he or she uses, rather than paying for over-provisioned, unused storage...all without downtime or performance hic-cup. These guys know a lot about the cloud and storage.
They have a blog where they share many things, for example their database incident when an engineer deleted the backup and production databases : https://about.gitlab.com/blog/
We recently started an engineering blog at Doximity [1] that I think is good (though it has less heavy technical content than others). I'd be really interested in what you all think is effective for both blogs-as-recruiting-tools and for giving back to the community. For our particular product, basically (users)∩(blog readers)=∅ so content is created solely for the software community.
Why do people insist on calling these dumps of all links they can find/get submitted in PRs "curated"?! It has almost 600 entries, with no extra content or structure...
Agreed. Personally I think asking for general blog recommendations is not helpful. I just google topics I'm interested and start to create that list myself.
Also - I think the idea of creating blog followers is becoming less popular. I use aggregators like this to help collect the content and I can filter on my own.
Knewton (where I once led marketing) flew mostly under the radar as a tech company because (a) NYC and (b) education, but the data science shop it built up a few years ago was killer, and the people who left went on to top tier companies. As a result of that talent, the tech blog there -- modeled after Netflix -- was solid.
Awesome answers here.
Some self marketing - I developed a parser for some engineering blogs. I did it for myself, and created a simple web app to serve content - http://kubiq.co. I'm going to add more companies soon. Enjoy!
Shameless plug for my company's blog: levvel.io/blog
Lots of DevOps focus currently but also contains some stuff we're working on with machine learning, blockchain, and we are working on a much broader range of content.
We just started a blog a few months ago at our company on a variety of topics such as mobile & BE development, as well as design [1]. Hopefully it's of use to the community :)
Raymond Chen's blog[1] in particular was good enough to get me to buy his book (which definitely did not disappoint).
Other ones I subscribe to are the Microsoft Edge Dev Blog[2] , Mark Russinovich[3] and Games for Windows and the DirectX SDK[4]
And there's a few that have unfortunately not been updated for a long time, such as Larry Osterman[5], or have come to an end, such as Rico Mariani[6]
[1] https://blogs.msdn.microsoft.com/oldnewthing/
[2] https://blogs.windows.com/msedgedev/
[3] https://blogs.technet.microsoft.com/markrussinovich/
[4] https://blogs.msdn.microsoft.com/chuckw/
[5] https://blogs.msdn.microsoft.com/larryosterman/
[6] https://blogs.msdn.microsoft.com/ricom/