Some tactical and strategic tips for writing effectively as a software developer.
Undervalued Software Engineering Skills: Writing Well
I have been coaching several experienced software engineers to further grow professionally, since transitioning [https://blog.pragmaticengineer.com/things-ive-learned-transitioning-from-engineer-to-engineering-manager/] to being an engineering manager. I have noticed a few skills that people often underestimate the importance of developing. Skills that add a
As a developer, my most important tools are a pen and a notebook
Writing code is a part of being a software developer but often more important question is to figure what code to write and how and that I like to do away from computer with my notebook.
Docs as Code: The Best Guide for Technical Writers
Recently, my work has involved writing a lot of documentation and. Doing this has introduced me to...
Stack Overflow
Use Stack Overflow Insights and get information required to understand, reach, and attract developers.Improve tech hiring, recruiting, developer marketing, and and planning initiatives.
The 10 Best Practices for Remote Software Engineering
At face value, when we think of developer productivity we might think of effectiveness in time management, communication, and task completion.14 Although we are drawn to personal workflow or time management tools, and learning secrets to improving our productivity, ironically this quest for the holy grail can sometimes take us off course and be a detriment to our productivity. The problem is that accomplishing tasks or having a filled up schedule does not necessarily equate to productivity. Creating a formulaic working strategy, as was common in the last century, does not either.a,8,13 Productivity is less a quality that can be easily measured,b controlled, or improved directly with tools, but instead is a human element that manifests from developer happiness.
What Is Open Source Strategy? — Open Tech Strategies | Blog
There is a lot of documentation out there on how to do open source well at the project level. Historically, many projects have been started by developers, often on their own initiative, and the first non-technical questions they faced tended to be about project coordination (like "What collaboration tools shall we use?" or "What will our code review practices be?") and about community management (like "How do we decide who has commit access?" and "How do we integrate newcomers smoothly?"). Because developers hate to solve the same problems over and over, there is a wealth of detailed and varied material addressing those sorts of questions (we've even written some ourselves, but it's just a drop in the bucket of what's available). Taken together, this literature thoroughly answers the question "How do we execute the best tactics for developing open source software?"
Writing design docs – Ceejbot's notes
How to figure out what to do and tell your colleagues at the same time
Why writing matters in remote work — Tim Casasola
In remote work, we communicate primarily through writing. We send messages in Slack. We document projects in Notion. We send meeting invites with a written description of the purpose. We’re writing all the time. Many organizations are working from home at the moment. Thus, writing is even
Learning To Write Software… Is Hard - Zicklag's Leaflets
But it's also good — Musings about the last year of Roomy development, and more.
Habits of High-Functioning Teams
I often struggle to explain what it means to be part of a high-functioning software team. Sure, there are mountains of literature, and an entire genre of LinkedIn thought leadership that professes all kinds of guidelines and heuristics about what makes teams work, but in my experience, it’s hard to internalize these ideas and follow someone else’s model if you’ve never seen what good looks like.
Software developers are not okay
Writing at the end of the world, from Hveragerði, Iceland
A Guide to Measuring Engineering Team Performance
“You can’t manage what you can’t measure.” While software development practices constantly change, there will always be a tier of truly top engineering teams who stand above…
The traits of a proficient programmer
Bridging the gap between competence and proficiency
How finishing what you start makes teams more productive and predictable
Hot takes and cold truths on software, startups, and the lies we tell ourselves.