|
|
|
|
|
by someweirdperson
1063 days ago
|
|
> Is that not a "model" because it is not necessarily graphical? For some people model==graphical, usually mechanical/electrical engineers, not software-engineers. Engineers maintain the holy "model", and the translation to lowly code is a job for the lowest-bidding software person. Maybe it wasn't clear, but I do not agree with that point of view, and tried to explain how I think people may have found their belief. I assumed the parent^4 was labeling their code model in an attempt to elevate themself to the ranks of the code painters. |
|
Best I can think in this direction, is UML? But that is an odd one, because it isn't that "models" are graphical, but those are specifically models of code artifacts. A model of another modeling language, as it were.
Reading back over the top comment, I assumed that the poster meant they started seeing their coding as modeling of a problem domain. Not that they weren't still coding, somewhat.
Disclosure, I was an EE way back when. We had plenty of numerical models for how things worked. We even had verilog to model circuits using what looks a lot like "traditional" software.
That all said, if I just haven't kept up and "model" is moving in meaning, I wouldn't be too shocked. :D