The context here is unlike bridges, it's impossible to understand a whole codebase, and you can't rediscover legacy code without the institutional knowledge. Is that really true though? Not the code, the bridges. Are bridges super different from codebases in this manner?https://twitter.com/stevekrouse/status/1083909608262041600 …
-
-
One issue with a lot of software process work/ideas is the idea that software is unique and needs to throw away wisdom from other industries (of course this isn't unique to software and people in other industries also think that their industry is uniquely hard and interesting).
-
I've noticed this, too. One project I'm planning on doing (once I learn some of the prerequisite skills) is interviewing people who've done both software engineering and another form, who can compare and contrast them from personal experience. Alright if I ask you about it later?
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.