Treat kind definitions with respect (just like you do with implementation code) Jacek Tomaszewski
Treat kind definitions with respect (just like you do with implementation code)
Opis: We have dozens of practices on how to compose clear code, so that it can scale up without any problems. Yet, sometimes it feels like we don't apply those practices to 1 crucial part of code: kind definitions.
Have you always met a Typescript codebase that was well structured (with responsibilities, components, directories being separated clearly), yet it had this 1 giant "types.ts" file to which everyone was throwing everything that started with "type" or "interface"?
Have you always wondered if and how kind definitions should be defined, and where they should be located?
If so, come and perceive - I'll present a couple of ideas on that.
🔥 [4Developers 2023] https://4developers.org.pl/4developers-2023/
👉 [FB] https://www.facebook.com/4Developers
👉 [LI] https://www.linkedin.com/showcase/4developers
👉 [TT] https://twitter.com/4Developers
