Posts

This profile is from a federated server and may be incomplete. Browse more on the original instance.

clobrano, to random
@clobrano@fosstodon.org avatar

How does anybody get good in writing software design docs? The more I try, the less I feel confident 🙄

underlap,
@underlap@fosstodon.org avatar

@clobrano That's a great question. Some suggestions:

  1. Find and read good design docs.
  2. Ask people to provide feedback on the design docs you write.
  3. Search the web for checklists of topics to include.
  4. Add your own topics relevant to the area you work in.
  5. Work on your general writing skills, e.g. read "The Elements of Style" by Strunk and White.

1/2

henrikjernevad,
@henrikjernevad@mastodon.social avatar

@clobrano I find it helpful to think about what you want to achieve by writing the documentation. Who is it for? What do you want them to understand? Then think about what you need to say to do that.

Try to put yourself in the shoes of the reader. If they did not know anything except that which you have written, would it make sense? Have you introduced all terms before using them? Do you consistently use the same words for the same concepts? Is each paragraph conceptually coherent?

clobrano, to random
@clobrano@fosstodon.org avatar

ASSUME THAT I CAN | World Down Syndrome Day 2024

https://youtu.be/9HpLhxMFJR8?si=iojifWx1_28NFvYW

  • All
  • Subscribed
  • Moderated
  • Favorites
  • normalnudes
  • khanakhh
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • GTA5RPClips
  • tacticalgear
  • Youngstown
  • thenastyranch
  • slotface
  • rosin
  • kavyap
  • ethstaker
  • mdbf
  • JUstTest
  • Durango
  • Leos
  • provamag3
  • cubers
  • ngwrru68w68
  • everett
  • modclub
  • cisconetworking
  • anitta
  • megavids
  • osvaldo12
  • tester
  • lostlight
  • All magazines