3 ms·
When I was a younger developer I thought tooling solved all problems. As I grew more experience I slowly changed my mind that some problem spaces require not on
by infecto 3y ago
When I was a younger developer I thought tooling solved all problems. As I grew more experience I slowly changed my mind that some problem spaces require not only tooling but process change. I am firmly in the camp that you don't need yet another documentation tool. The problem is a human/process one, documentation/knowledge bases need to be part of the process. As long as you can search it and its easy to update/create, I don't think the tool is solving much for you.
- Freak_NL 3y agoFriction frustrates processes though. If working with a tool is constant pain, then the process is going to suffer.
- infecto 3y agoTotally agree. Have definitely seen a bad tool used but largely the problem in my experience has been human.
- sdfghswe 3y ago> When I was a younger developer I thought tooling solved all problems. As I grew more experience I slowly changed my mind that some problem spaces require not only tooling but process change. Lets take it one step further. You start out thinking everything is tooling. As you grow more experienced you realize that everything is process. As you grow more experienced still, you realize that the world is really messy and rarely ever anything is everything.
- infecto 3y agoOf course the world is messy and there are many variables. I still sit in the camp that documentation is a human problem that requires both tooling and process. I wish Outline luck but on the documentation side, its largely a human/process one.
- flappyeagle 3y ago> both tooling and process so better tooling helps then?
- infecto 3y agoSure? The problem is largely a human/company culture/process problem and sure tooling can help remove friction but it does not fix the larger problem.