You know you've been coding too much when...
-
Good god - you, too? I've been doing that since I was sixteen, and wishing I had 16 fingers to make it easier to handle large numbers. We didn't have calculators then, just these soft, heavy, and somewhat slimy clay tablets. I had to invent the wheel just to carry my books to school... I must admit that, although my first prototype using squares didn't work out too well, further refinements utilizing more sides in the polygon theme worked out a little better. Still, my early beta testers reported amazing weight loss results from using my prototype design, so it wasn't a complete failure.
Will Rogers never met me.
and here I thought the roundness was caused by the natural wear and tear of pushing the cart with the square wheels. ;)
Steve _________________ I C(++) therefore I am
-
During uni we still had COBOL. Got a nightmare two years in a row the night before the exam about COBOL code passing through. A small reminder, for COBOL you needed to divide the code in sections and start writing on the seventh character. For calculating values you needed to write "compute ... " etc... X|
V.
V. wrote:
For calculating values you needed to write "compute ... " etc...
Not necessarily. You could say ADD A TO B GIVING C or COMPUTE C = A + B You have forgotten your COBOL! :laugh:
-
V. wrote:
For calculating values you needed to write "compute ... " etc...
Not necessarily. You could say ADD A TO B GIVING C or COMPUTE C = A + B You have forgotten your COBOL! :laugh:
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
While coding you finish your prawns, start on the grapes and only notice by the third or fourth grape that you are still dipping them in the seafood dip.
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
Jacquers wrote:
You dream about writing code
Back when I was working on a framework day and night, I once woke up in sweat in the middle of the night. I dreamed that I was an object that got lost in the framework. It was pretty strange. :-)
-
V. wrote:
For calculating values you needed to write "compute ... " etc...
Not necessarily. You could say ADD A TO B GIVING C or COMPUTE C = A + B You have forgotten your COBOL! :laugh:
Vivic wrote:
You could say ADD A TO B GIVING C or
COMPUTE C = A + BOMG, I really did not need to see that. :laugh:
-
I feel like that with mvvm. I see the benefits of seperation of logic and things being loosely coupled, but it takes a lot longer than plain old code behind. It also feels a bit 'obfuscated' since you have to know mvvm to figure out just how things fit together.
Jacquers wrote:
but it takes a lot longer than plain old code behind
Perhaps. But consider needing to dive back into that code after 2 years to deal with a change request or a bugfix. I'll take the nicely structured code of MVVM over the spaghetti that is code-behind any day of the week. Not to mention that writing tests for the GUI layer is loads more efficient if you decouple the logic from the actual GUI.
Jacquers wrote:
It also feels a bit 'obfuscated' since you have to know mvvm to figure out just how things fit together.
Yes, to understand MVVM code, you need working knowledge of the MVVM pattern. Seems kinda obvious.
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
-
During uni we still had COBOL. Got a nightmare two years in a row the night before the exam about COBOL code passing through. A small reminder, for COBOL you needed to divide the code in sections and start writing on the seventh character. For calculating values you needed to write "compute ... " etc... X|
V.
IDENTIFICATION DIVISION
-
I feel like that with mvvm. I see the benefits of seperation of logic and things being loosely coupled, but it takes a lot longer than plain old code behind. It also feels a bit 'obfuscated' since you have to know mvvm to figure out just how things fit together.
Give it time and you will find that MVVM can be developed with similar costs in time. One of the benefits I love about MVVM is how reusable things are. If you can't do something via databinding to an existing property on a control, then you extend the control in question and add the properties you need. If you do it that way you then have a control you can use everywhere. Doing things in code behind which feels quicker ultimately can cost you more time.
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
-
I could do in a day, back then, what it now takes a month to do with modern languages. If Turbo Pascal had held the course, instead of fizzling out after v5.5, I might still be a programmer. It was easy to read, write, and maintain, well documented, extremely efficient, and fairly priced. Microsoft changed all of those facets of an entire industry, and all of us are poorer for it. That's not to say that a bunch of good people aren't doing very nicely financially as a result, of course. :-D
Will Rogers never met me.
SO you never considered Delphi?
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
I realized that I code too much for several reasons: 1 - As others, I sometimes dream of coding 2 - On free time, I sometimes think of code 3 - Most importantly, the way I think has changed. The decisions I take in my life have become just like logical algorithms, sometimes I even think on the way of case's, if's and while's. Scary thought.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
You want to end every line of text with a semicolon (;), without matter if you're writing T-SQL, HTML, Visual Basic, a letter, an email, or anything else :-D
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
... when you try to debug your deli sandwich in which you found a bug... :-\
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
-
You dream about writing code. And not even in your current coding language, but Turbo Pascal. It was a good language to learn programming in, but things took a long time to do compared to what we have available now. I'd be able to write something in a day that would have taken a week to do back then.
Back in the mid-70's I had a friend who did a lot of work with machine code on DEC minicomputers. One day he used his lunch break to go to the bank to straighten out a problem he had been having with his checking account. It turns out that he had been trying to balance his checkbook in octal.