problem-diagnosis-remedy-proposal
A clear, generally concise proposal format to win hearts and minds (by colindean)
awesome-technical-writing
:books: A curated list of awesome resources: articles, books, videos, tools, podcasts about technical writing. (by BolajiAyodeji)
| problem-diagnosis-remedy-proposal | awesome-technical-writing | |
|---|---|---|
| 1 | 4 | |
| 8 | 1,644 | |
| - | - | |
| 0.0 | 7.1 | |
| over 1 year ago | 4 months ago | |
| - | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
problem-diagnosis-remedy-proposal
Posts with mentions or reviews of problem-diagnosis-remedy-proposal.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-08.
-
Should devs manage dev environments
The trick is always convincing people that there is a better way. Because you have such a small team responsible for so much, you really need to establish consensus with some discussion and counter-railroading. I push the problem, diagnosis, remedy proposal model on a lot of my organizations whenever I see that there's not consensus or that there's not much interest in consensus or shared knowledge. Sometimes a "do what you think is right" carte blanche from the team is a good thing when you want to go fast, but when you want to go far together, having written artifacts of your intentions and the reasoning behind them is incredibly important. On a small team, you do not have the luxury of isolation or compartmentalization.
awesome-technical-writing
Posts with mentions or reviews of awesome-technical-writing.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-14.
What are some alternatives?
When comparing problem-diagnosis-remedy-proposal and awesome-technical-writing you can also consider the following projects:
lips - 📘 Lisk improvement proposals
Getting-started-in-Technical-Writing - A compilation of useful resources for anyone who wants to get started in technical writing.
proposals - Tracking ECMAScript Proposals
tilt - Define your dev environment as code. For microservice apps on Kubernetes.
garden - Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching
NIP - NEM Improvement Proposals
skaffold - Easy and Repeatable Kubernetes Development
problem-diagnosis-remedy-proposal vs lips
awesome-technical-writing vs Getting-started-in-Technical-Writing
problem-diagnosis-remedy-proposal vs proposals
problem-diagnosis-remedy-proposal vs tilt
problem-diagnosis-remedy-proposal vs garden
problem-diagnosis-remedy-proposal vs NIP
problem-diagnosis-remedy-proposal vs skaffold