Ask HN: Is there a better way to document complex software architectures?

Re:Ask HN: Is there a better way to document complex softwar... by taeric on Monday November 26, 2018 @10:10AM (#18533805)

This sounds like a large part of the reason is you deliver the code to others, but don't want to deliver the tool you used to make the code. This makes sense to me.

For the other cases you gave, that sounds like what Interfaces were made for. :) Granted, I think we are in a world where tooling not necessarily requiring language constructs is a better place.

Regardless, if you are seeing such success, I would be greatly interested in seeing you open up that tool.

[ Parent | on HN ]

Re:Ask HN: Is there a better way to document complex softwar... by jonathanlydall on Monday November 26, 2018 @12:10PM (#18534844)

Here a recording of one of our guys on a webcast and it also shows the tool in action: https://www.youtube.com/watch?v=vA3L8_DaECQ

"No lock in" is an important aspect for us. We know of some other big players with "RAD" type tools which "generate" code, but unless one continues using their tool, the code they're left with is effectively unusable. Their business models are also often around runtime licensing.

As devs, building a tool for other devs, we want our tool to continue to be used because people clearly find the value in it, not because they feel locked in.

[ Parent | on HN ]