Writing for Engineers
I agree with this perspective of the world (that senior+ software engineers need to be able to express themselves more fluently to be able to be impactful) but… just as a thought experiment, I wish it didn’t have to be that way. Writing is hard and not much fun (to me). Building systems that do something is hard but its a lot of fun. I just want to spend most of my time doing the latter. I just don’t give a fuck about impact or convincing others to work on my idea. If you are building something cool, show a little bit of it to me, and I like what I see, I would <i>love</i> to be able to drop everything else and work with you to complete it. Or if I think of some automation to reduce toil, I just wanna go tinker without having to think it through too much. If I run into constraints when building it, so be it, its a learning experience, but even failing is fun.<p>Obviously a rant. I just didn’t become a software engineer to be a good writer. I always wanted to build first and learn the constraints through mucking around rather than giving it so much thought before a single line of code is written.