6 ms·
Seems like a reasonable effort and we probably need more of this kind of stuff. But still I think the industry should focus more on educating developers to prev
by gwn7 4y ago
Seems like a reasonable effort and we probably need more of this kind of stuff. But still I think the industry should focus more on educating developers to prevent them from introducing mostly unnecessary accidental complexity to today's typical apps rather than inventing new layers to manage it.
Related:
https://twitter.com/garybernhardt/status/1603498230125588480 https://twitter.com/garybernhardt/status/1603498230125588480
https://twitter.com/garybernhardt/status/600783770925420546 https://twitter.com/garybernhardt/status/600783770925420546
https://geekandpoke.typepad.com/geekandpoke/2011/03/architectural-best-practices.html https://geekandpoke.typepad.com/geekandpoke/2011/03/architec...
- specialist 4y ago#2 - I once spent 18 months convincing my teammates to move our hottest data set from DynamoDB to RAM. Next time, I won't bother. #3 - Heh. The "N+1" architecture. However many layers your architectural design methodology has, ours has one more. (h/t Spinal Tap). Is that Twitter you? Good stuff. Like the unique URL for posting CSVs.
- gwn7 4y ago> #2 - I once spent 18 months convincing my teammates to move our hottest data set from DynamoDB to RAM. Next time, I won't bother. Yeah, don't bother. People don't want simplicity. The majority of our tribe are masochists haha > #3 - Heh. The "N+1" architecture. However many layers your architectural design methodology has, ours has one more. (h/t Spinal Tap). Exactly > Is that Twitter you? Good stuff. Like the unique URL for posting CSVs. Oh no I'm not Gary, sorry =)