Repeating Yourself Thrice Doesn’t Turn You into a 3x Developer

1

htmx

#Software Development #Javascript UI Libraries #JavaScript 68 social mentions

Hey Ophir here, I'm the co-author of the post. What you say is on-point, and we should have mentioned it in the post. The way I see it is: at the beginning, everything is repeated three times on the three layers. Then, as time advances, complexity grows, and you start having much more specific requirements that will need one of the layers to differ slightly. The common approach is to just duplicate everything three times at the beginning to be ready for the moment when something needs to diverge. What SQLPage [1] is saying, is: when you start, just think about the database. Make it the single source of truth, and iterate quickly to find out what form the data you work on will need to have. You won't get it right the first time, so it's crucial you don't find yourself having to do the work three times for every change. And then, when you need some frontend-specific feature, make just a react component for it and integrate it in the application. Then, as the app grows, you will progressively write a full frontend for it, and an external backend, but you will never have to re-do the work you have done in the beginning. This has allowed me to make some applications that I wouldn't even have thought I would have the courage to start before. [1] https://sql.ophir.dev.

#Developer Tools #Javascript UI Libraries #GUI Frameworks 19 social mentions