# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 3
# self = https://watcher.sour.is/conv/7rwp7gq
> how can we concretely think about "Complexity Budget" and define it in terms that can be leveraged and used to control the complexity of software dns ystems?
Not exactly on "Complexity", more on UX, although I use this book as a reading material for design courses, on how finally the user receives all that complexity with tragic consecuences:
https://www.tragicdesign.com
And on that "complexity" that the user doesn't see, usually I go with "Software Architecture: The Hard Parts"
https://www.oreilly.com/library/view/software-architecture-the/9781492086888/
@eapl.me Cool! 👌 I shall have to have a look into these. If you've read both before, perhaps you can share short excerpts or your own thoughts and experiences?
@eapl.me Cool! 👌 I shall have to have a look into these. If you've read both before, perhaps you can share short excerpts or your own thoughts and experiences?