only
its more about writing software with c++
how should we design our program
and think about architecture,
folders structure,
modules,
namespaces,
classes and their relationships in design solution.
i mean if i analyze a business requirements and want to design it components independent of language and tools can i write it with c++ and then port to other languages ?
how much my design or implementation deffer related to an specific language ?
Study your requirements and apply Design patterns for your project. So first you can make a architect diagram, class diagram and so on
In my experience the less relationships the better, so the more directly you can get to a solution, the easier it is to port later, I would try to avoid classes where standalone functions are better, and less code / less logic is generally better
Обсуждают сегодня