It’s rarely the case. You rarely work in vacuum where your work only affects what you do at the moment. There is always a downstream or upstream dependency/requirement that needs to be met that you have to take into account in your development.
You have to avoid the problem that might come later that you are aware of. If it’s not possible, you have to mitigate the impact of the future problems.
It’s not possible to know of all the problems that might/will happen, but with a little work before a project, a lot of issues can be avoided/mitigated.
I wouldn’t want civil engineers thinking like that, because our infrastructure would be a lot worse than it is today.
“Not blowing up later” would be part of the problem being solved
Engineering for future requirements almost always turn out to be a net loss. You don’t build a distillation column to process 8000T of benzene if you only need to process 40T
I don’t love AI, but programming is engineering. The goal is to solve a problem, not to be the best at solving a problem.
Also I can write shitty code without help anyway
The issue with engineering is that if you don’t solve it efficiently and correctly enough, it’ll blow up later.
That’s a problem for HR if they have shitty retention.
Sounds like a problem for later
Flippancy aside: the fundamental rule in all engineering is solving the problem you have, not the problem you might have later
POITROAE
deleted by creator
It’s rarely the case. You rarely work in vacuum where your work only affects what you do at the moment. There is always a downstream or upstream dependency/requirement that needs to be met that you have to take into account in your development.
You have to avoid the problem that might come later that you are aware of. If it’s not possible, you have to mitigate the impact of the future problems.
It’s not possible to know of all the problems that might/will happen, but with a little work before a project, a lot of issues can be avoided/mitigated.
I wouldn’t want civil engineers thinking like that, because our infrastructure would be a lot worse than it is today.
That doesn’t apply to all engineering. In ChE, it’ll literally blow up later…
“Not blowing up later” would be part of the problem being solved
Engineering for future requirements almost always turn out to be a net loss. You don’t build a distillation column to process 8000T of benzene if you only need to process 40T
but you could design it to be easily scalable instead of having to build another even more expensive thing when you suddenly need to process 41T