Sometimes I wonder about code comments
-
Marco Bertschi wrote:
with a built-in computer and a built-in screen which already has been defined in the requirements before a single line of code was written...
So it is not just logically a closed environemtn: It is physically close too.Until the customer requests a different screen size and your BD say "Sure no problem!"... Then your stuck holding the bag because the code committed a faux pas and assumed a specific screen size. Have fun with that :laugh:
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
Collin Jasnoch wrote:
Until the customer requests a different screen size and your BD say "Sure no problem!"
They do not. This is medical business, changing something even if it is just a change at the monitor size does need a validation of the whole system and would cost millions. But this restriction will fall down anyways with the next SW version. The app will finally become screen size-innocent.
-
Collin Jasnoch wrote:
Until the customer requests a different screen size and your BD say "Sure no problem!"
They do not. This is medical business, changing something even if it is just a change at the monitor size does need a validation of the whole system and would cost millions. But this restriction will fall down anyways with the next SW version. The app will finally become screen size-innocent.
Marco Bertschi wrote:
This is medical business, changing something even if it is just a change at the monitor size does need a validation of the whole system and would cost millions.
This does not mean it does not happen.
Marco Bertschi wrote:
But this restriction will fall down anyways with the next SW version. The app will finally become screen size-innocent.
It also does not mean you will get to start over. That is often a decision not made by the dev team or even the first layer or 2 of management. There are usually politics involved and it is much more likely they will say "Take what you have and make it do XYZ". Even if you have an argument that starting over will make XYZ easier and more main-table it does not mean that will not choose the path of continuing development on a broken system. I work in the aerospace industry and it is also very slow moving... Yet I have just witnessed this happen and would like to slap some programmers around with my keyboard.
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
-
With closed environment like I mean: Even the screen size is predefined because the customer receives the medical diagnostic instrument with a built-in computer and a built-in screen which already has been defined in the requirements before a single line of code was written... So it is not just logically a closed environemtn: It is physically close too.
I thought the original comment was about the source code. Meaning you (yes, you the programmer, not the customer) would not be able to see the entire line of code in your IDE if you were using a lower screen resolution. Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
-
With closed environment like I mean: Even the screen size is predefined because the customer receives the medical diagnostic instrument with a built-in computer and a built-in screen which already has been defined in the requirements before a single line of code was written... So it is not just logically a closed environemtn: It is physically close too.
But the specifics of output device have nothing to do with the format of the source code.
-
I've just seen this wonderful comment in the "Other suggestions" section of one of our beautiful CPP-headers:
//Other suggestions:
//80x24 fetishists: This code is optimezed for 1920x1200 -> the stone age is over, really!Wow, an update from 80x24 to 1920x1200, that's great! Obviously, you had to give up MUMPS. Does your C++ code still resemble the original MUMPS code?
-
I've just seen this wonderful comment in the "Other suggestions" section of one of our beautiful CPP-headers:
//Other suggestions:
//80x24 fetishists: This code is optimezed for 1920x1200 -> the stone age is over, really! -
Wow, an update from 80x24 to 1920x1200, that's great! Obviously, you had to give up MUMPS. Does your C++ code still resemble the original MUMPS code?
No. And it is not just C++ code. It once was pure C code :^)
-
I've just seen this wonderful comment in the "Other suggestions" section of one of our beautiful CPP-headers:
//Other suggestions:
//80x24 fetishists: This code is optimezed for 1920x1200 -> the stone age is over, really! -
I've just seen this wonderful comment in the "Other suggestions" section of one of our beautiful CPP-headers:
//Other suggestions:
//80x24 fetishists: This code is optimezed for 1920x1200 -> the stone age is over, really!this is so yesterday! the new 1920x1200 is 1366x768 :mad: :((
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
I've just seen this wonderful comment in the "Other suggestions" section of one of our beautiful CPP-headers:
//Other suggestions:
//80x24 fetishists: This code is optimezed for 1920x1200 -> the stone age is over, really!And on laptops the stone age isn't over, really. Try getting a laptop nowadays with that resolution. Luckily I got mine 2 years ago.
Wout