Some notes

By @lucasdicioccio, 357 words, 0 links, 0images.

dependencies in OOP and IO



About OOP hiding states. It's pretty common to bundle all dependencies in the object, say a Summarry object. Then there is no distinction between methods that make use of none, some, or all of these dependencies. Even when internally-occurring as private methods. Turns out it makes code-auditing and code-reviewing painful. As time passes, objects accrete more and more dependencies for single new methods. We should have more fine-grained

write an article?

lack of elegance can be simple



Sometimes having a brutalist solution is good because you can use it all the time with little second thoughts. Our desire to do things right wants us to use parcimony and elegance. However being nit-picky, extra complications arise due to combinatorics. Imperfect on many aspects but no-brainer to use and understand (see: bell-curve meme).

example of optim



good-fast-cheap triangle is a good example to discuss about pareto-optimality

encoding info in URLs



discussions on seem to tell that one should encode information in the hierarchy, seems like a failure to encode information in the page `meta` headers

golang after 1year



after around a year using it, I still sincerely think that Golang power/weight ratio is pretty bad and doesn't feel modern. Pro: it compiles fast Con: but while doing so it checks so little and provides no affordance Perf-bound, I'd go for Rust, else a member of the ML-family.

tweet that?

need for tools



- a tool to help with API diffs - and a tool to help with templating live

write a POC?