Re:Software designers, not engineers: An interview from alte...
by bcrl on Tuesday April 20, 2021 @08:54PM
(#26884105)
The projects I have been involved with tend to have high level design discussions at the beginning. Working in a team has that as a necessity, otherwise we can't figure out how to partition the work of actually building the software. Yes, we figure out what data structures we need to use at a high level and then grow the code incrementally to tie it all together after that. But maybe that's fallout from working mostly in the system / embedded / network protocol space for most of my career where frameworks are not really a consideration.
I think bot good engineering and good desin practise is the opposite of developing a picture. It is really iterative process, trying to factor in as many of the important aspects as possible and try to get the one solution where all of these aspects don't fight each other, but strengthen each other.
Many software developers I met are just focused at what framework/language/design pattern/etc they are going to throw at the next problem. Of course that is all exiting, but what if the thing you are tackeling could be solved so much better, if you just killed your darlings and tried to find the best solution?
Sure you cannot learn $framework you were curious about on the way, but finding elegant and good solutions is itself a skill that needs training.