@thekitze 2 years later - “well, I wasn’t sure world was ready for everything I have to say, so I filtered out some stories… but here is my 3rd book with some hardcore stuff”.
@DavidKPiano My attempt to solve this https://t.co/XepPvVLZHh. Still the solution is after the fact. AI yet to get that smart to generate abstraction layers from plain code.
@ivanov_dev They increase complexity for reading code or making small changes but they reduce complexity when it comes to making big changes/refactoring/migrations etc. So one should choose wisely based on product size, stage of development or possible life time of the project.
@ivanov_dev Grouping files in directories based on product features really helps to make project feel way smaller than it really is (unless working on some core functionality). Also, VCS operations are much simpler, directories clearly show what should and shouldn’t have been touched.
Just released something cool I was working on recently - Codecrumbs App now supports integration with a local codebase directly in browser! It is even easier to get started https://t.co/BYDAvzQjhl 💪
Finally finished one of the old drafts! Well, @webpack released new version while I still was reading source code for previous one 🙈
#javascript#webpack
https://t.co/aNXl6gcDlN
@IGrabill That knowledge is abstracted layer that only exists in heads of people that understand how codebase work and can see “big picture”. So Codecrumbs help you to write down that knowledge, share it, use it while working with a codebase.
@IGrabill Exactly! Imagine when you are being onboarded into a new codebase, someone should sit with you and show all key points in code that define a feature. They can try to just explain you a feature but it never maps one-2-one to code.