Writing is how engineering scales past the size of a single head. The post-mortem you did not write will be re-written from memory, imperfectly, the next time the same bug happens. The decision doc you skipped will be re-litigated in six months when someone new asks why we chose Postgres over Mongo.
Engineering culture talks about writing as overhead. It is not overhead. It is the only compression algorithm we have for organisational knowledge. Without it, every piece of hard-won context has to be re-derived by every new hire, and the half-life of institutional memory is measured in quarters.
Three kinds of writing are load-bearing for any engineering team: decision documents, post-mortems, and design docs. Decision documents capture why we chose this over that. Post-mortems capture what we learned when something broke. Design docs capture what we plan to do and invite pushback before we spend the money.
All three are boring to write. All three pay dividends for years. If your team is not writing them, the next generation of engineers is going to re-discover everything you already know, and they are going to make the same mistakes you already made.