Observant readers may have noticed that the stream of articles on this site has been light lately. It is something I wanted to address since the Telerik Developer Network (or TDN as we call it) has been my professional passion for the past four years as its editor-in-chief.
Yes, the Telerik Developer Network has wound down to its end. But Progress and the Progress Developer Relations team, who frequently posted here, are still committed to bringing you great developer-focused content from our internal authors and talented third-party authors. You can still find this content on places like the Progress blog, Telerik blog, NativeScript blog and Kinvey blog. As you can see, we have a lot of outlets serving a lot of audiences – and that is partly why we decided to transition efforts away from this site. Hopefully you'll still choose to follow us on one or more of those sites that are most relevant to you – and we'll continue serving the same quality content we did on TDN!
Personally, I am moving on to work as a developer advocate for our Kinvey mobile-backend-as-a-service product, so you'll be able to catch some of my writing on the Kinvey blog. You can catch Ed, Tara, John, Sam and Alyssa blogging on the Telerik Developer Central and Jen, TJ and Sebastian on the NativeScript blog.
If you were an RSS or Telerik Developer Digest subscriber, here's what you can do:
Ok, so now that the "why" and the "how" are out of the way, I hope you'll afford me a brief trip down memory lane. First, I want to share with you why I cared so much for this site as well as some of our biggest successes.
When I joined Telerik four years ago, it was with the express purpose of helping to guide content and build TDN. I had worked on the Adobe Developer Connection and then launched my own popular site (called Flippin' Awesome). Telerik had a DevRel team filled with talented writers whose content was often being overlooked – the hope was that TDN would change that.
Since that day TDN has served well over 4 million unique visitors. Let's look at some of our top content of all time:
This is a career-defining article for John Bristowe – not because it is the world's greatest article, but because it seemed to have a life of it's own (it was in the top 5 most trafficked articles every month since the day he posted it). Bristowe has been coasting ever since. 🤣
Michael Crump (who now works at Microsoft) knew 5 ways to write articles – all of them were top 5 lists. 😉 This article is classic Crump (and the most popular of the articles that he wrote before he left) – it combines a top 5 list with a hot developer topic (i.e. mobile apps) and the .NET stack.
TJ VanToll has a talent for breaking down complex problems into concise, easy-to-digest chunks. Thankfully for him, however, remote debugging on mobile is a simple problem that required little of his talent to explain. Honestly, that this article still gets a steady stream of views to this day (nearly 4 years later) says more about the state of mobile development than TJ's talents at explaining it.
We learned a lot from Crump, most importantly that lists work! It was a lesson that that no one else on the team took to heart more than Sam Basu…and with great success. Being an overachiever, Sam took the top 5 list recipe and made it top 10s.
Jen Looper has a way of figuring out answering those questions that so many developers have but are afraid to ask for fear of seeing stupid. This is a prime example – webviews are something most developers think they understand but may never be quite sure that their understanding is correct. Plus, Jen frequently manages to pick the most off-beat themes and references (instead of the traditional geek references to superheroes or Star Wars, we get I Love Lucy).
Obviously, I left out literally hundreds of articles and tens of authors (both internal to the company and external). I could go on for days. If you've been a reader, what was your favorite article and why?
Oh, and if you have a favorite, don't worry – we are working to ensure that the content remains available as long as it remains relevant to developers. Thanks for reading!