We talk ourselves out of writing (or at least out of publishing) in all kinds of ways: It states the obvious. There’s no conclusion. No one will read it. Someone might read it! Well, so what? You never know how much that seemingly insignificant story of yours may be appreciated in the future—it could be one of a handful of search hits on an obscure issue; it could be a reminder of how you used to work 15 years ago; it could help people get to know you better; and best of all, it can definitely help you gain confidence in communicating. So give yourself permission to write what you know so far, because you’re the only one stopping you.
Decoupling your CMS can broaden your options for the presentation layer, let team members narrow their focus to what each does best, or provide data for iOS and Android applications along with a responsive site. Maybe the greatest benefit is that having to consider the relationship between the CMS and rendering layer helps break up assumptions about delivery formats, making you more future-friendly along the way. Mark Llobrera shares a couple of tales where headless was the right solution.
No matter what your dev job description is, you need a robust and reliable system for note-taking, bookmarking and—this part is essential—finding the information you’ve captured. Even before you’ve built up your skills, a mature process for managing the information involved in your work will help throughout your career. Mark Llobrera likes to keep his memory management method simple, searchable, and software-independent.
For some, Facebook’s Instant Articles is a sign that the traditional web stack is incapable of giving users a first-class reading experience. But the sluggish performance of the web isn’t due to an inherent flaw in the technology. That particular problem originates between the seat and the keyboard, where builders make choices that bloat their sites. For Mark Llobrera, Instant Articles is a sign that we need to prioritize performance like we actually mean it.