“Splitting by layers is just like splitting co-workers by profession instead of splitting them into organization teams.” packages Imagine this ridiculous situation: , and , where the will only have and no , or ; Managers company, Programmers company Human Resources company Marketing company Programmers company programmers managers marketeers human resources Packaging stuff together by what it is, and not by what it does, will only make you jump 10 times to the place you are looking for. Gains and Benefits By at the structure you can already tell what the app is all about (figure 1); looking Higher modularity; code navigation; Easier Higher level of abstraction; Separates both and layers; features More readable and maintainable structure; More cohesion; Much easier to scale; Less chance to accidentally modify unrelated classes or files; Much easier to add or remove application features; And much more reusable modules. Do you concur? What is your approach? is how hackers start their afternoons. We’re a part of the family. We are now and happy to opportunities. Hacker Noon @AMI accepting submissions discuss advertising & sponsorship To learn more, , , or simply, read our about page like/message us on Facebook tweet/DM @HackerNoon. If you enjoyed this story, we recommend reading our and . Until next time, don’t take the realities of the world for granted! latest tech stories trending tech stories

Facebook

Too Long; Didn't Read

 Add passwordless user experiences to your app

HackerNoon Mobile

Package by features, not layers

Too Long; Didn't Read

Company Mentioned

@cesarmcferreira

RELATED STORIES