# 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 4
# self = https://watcher.sour.is/conv/ry6bqda
@felixp7 Yeah I agree with some of the statements and opinions here. Often-times you cannot really avoid just copying a piece of code, because you _actually_ do risk over generalising or worse adding so many layers of indirection you actually make it worse to reason about and later debug if things go wrong. Finding a balance between principles like DRY and SOLID programming is hard (_and I really wish we didn't have to keep coming up with these silly acronyms all the time!_)
Good read 👌
@felixp7 Yeah I agree with some of the statements and opinions here. Often-times you cannot really avoid just copying a piece of code, because you _actually_ do risk over generalising or worse adding so many layers of indirection you actually make it worse to reason about and later debug if things go wrong. Finding a balance between principles like DRY and SOLID programming is hard (_and I really wish we didn't have to keep coming up with these silly acronyms all the time!_)\n\nGood read 👌
@felixp7 Yeah I agree with some of the statements and opinions here. Often-times you cannot really avoid just copying a piece of code, because you _actually_ do risk over generalising or worse adding so many layers of indirection you actually make it worse to reason about and later debug if things go wrong. Finding a balance between principles like DRY and SOLID programming is hard (_and I really wish we didn't have to keep coming up with these silly acronyms all the time!_)\n\nGood read 👌
@felixp7 Yeah I agree with some of the statements and opinions here. Often-times you cannot really avoid just copying a piece of code, because you _actually_ do risk over generalising or worse adding so many layers of indirection you actually make it worse to reason about and later debug if things go wrong. Finding a balance between principles like DRY and SOLID programming is hard (_and I really wish we didn't have to keep coming up with these silly acronyms all the time!_)
Good read 👌