4 ms·
I feel like the hardest part of modern software engineering is systems architecture. I've pretty easily picked up everything on this list that I've touched, but
by fouric 6y ago
I feel like the hardest part of modern software engineering is systems architecture. I've pretty easily picked up everything on this list that I've touched, but I still don't know how to organize systems. Is this just me? (if not, then I feel that this site misses the most important part of the discipline)
- neatze 6y agoAfter my first prototype(s) of system I start reviewing design patterns with goal to identify how my prototype(s) are similar to various design patterns, then I start looking at opensource projects with similar design patterns, eventually I see the righteous path.
- travmatt 6y agoThis is my approach. Except three days later I suddenly realize a cleaner approach and I wonder why my original plan was so ugly.
- bootloop 6y agoBecause that is the the part of software engineering which needs the most experience and general knowledge. There is no way around it. After all you need to know the constraints around a system before even building it and that is only possible if you have seen it before. It can help to study others people work before starting a project in a similar domain.
- travmatt 6y agoThese types of problems, ones which can only know how to solve by solving them, are known as wicked problems. Software design is well known to be a wicked problem.