I'm a DLSC...you?
-
I'm a DLSB. I reckon question 12 made me different to you Question 12: What is the 'better' implementation: int main() { printf("5+6=%d", 5+6 ); return 0; } //////////////////////////////////////////////// // AddNumbers // param1 firstParam - The first value to add // param2 secondParam - The second value to add // return - The firstParam added to secondParam // int AddNumbers( int firstParam, int secondParam ) { // Here is some info int theReturn = firstParam + secondParam; // Now return the value return theReturn; } // Entry for program int main() { // Initialize variables int firstParam = 5; int secondParam = 6; // Call the function int returnValue = AddNumbers( firstParam, secondParam ); // Print out the value printf("%d+%d=%d", firstParam, secondParam, returnValue ); return 0; } I said the second because I like to see things refactored into small, reusable methods. I wasn't so keen on all of example 2, it had way too many comments. 'Initialize variables' ? Give me a break, if you can't work out that's what's going on, you should turn off the computer, or at least stop reading code.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
Your programmer personality type is: DHSB You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a High level. The world is made up of objects and components, you should create your programs in the same way. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a liBeral programmer. Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need.
"Okay, I give up: which is NOT a real programming language????" Michael Bergman
"Well yes, it is an Integer, but it's a metrosexual Integer. For all we know, under all that hair gel it could be a Boolean." Tom Welch
"Let's face it, the average computer user has the brain of a Spider Monkey." Bill Gates
-
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a High level. The world is made up of objects and components, you should create your programs in the same way. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a liBeral programmer. Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need.
-
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
-
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
-
:) Your programmer personality type is: DLTB You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Team. A good group is better than the sum of it's parts. The only thing better than a genius programmer is a cohesive group of genius programmers. You are a liBeral programmer. Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need.
DHSB.
-
DLSB :)
You are a liBeral programmer.
Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need.I bet Stan's gonna call me a Marxist coder. :->
Me too. I got annoyed that the C# IDE removes spaces so
fred( 3, 4 )
becomes
fred(3, 4)
but I'm starting to get used to it.
-
Me too. I got annoyed that the C# IDE removes spaces so
fred( 3, 4 )
becomes
fred(3, 4)
but I'm starting to get used to it.
I use spaces (in combination with tabs!) to make pretty layouts. :-D (My white space style is the latter of your two examples)
-
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
You're a Planner. You may be slow, but you'll usually find the best solution. If something's worth doing, it's worth doing right. You like coding at a High level. The world is made up of objects and components, you should create your programs in the same way. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a liBeral programmer. Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need.
______________________ stuff + cats = awesome
-
You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a High level. The world is made up of objects and components, you should create your programs in the same way. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a liBeral programmer. Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need.
-
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
DHTB You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a High level. The world is made up of objects and components, you should create your programs in the same way. You work best in a Team. A good group is better than the sum of it's parts. The only thing better than a genius programmer is a cohesive group of genius programmers. You are a liBeral programmer. Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need. Interesting test, but, for my money, the questions are too extreme in their answers... I'd prefer question with 'on a scale from...' Tim
-
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
I dunno about the D part, but the rest is me too :p Instead of a Doer, I think I am an obsessive thinker, so I can code less and more correct, yet expose more functionality (wow that almost sounds like marketing lingo :p)
**
xacc.ide-0.2.0.57 - now with C# 2.0 parser and seamless VS2005 solution support!
**
-
I'm a DLSB. I reckon question 12 made me different to you Question 12: What is the 'better' implementation: int main() { printf("5+6=%d", 5+6 ); return 0; } //////////////////////////////////////////////// // AddNumbers // param1 firstParam - The first value to add // param2 secondParam - The second value to add // return - The firstParam added to secondParam // int AddNumbers( int firstParam, int secondParam ) { // Here is some info int theReturn = firstParam + secondParam; // Now return the value return theReturn; } // Entry for program int main() { // Initialize variables int firstParam = 5; int secondParam = 6; // Call the function int returnValue = AddNumbers( firstParam, secondParam ); // Print out the value printf("%d+%d=%d", firstParam, secondParam, returnValue ); return 0; } I said the second because I like to see things refactored into small, reusable methods. I wasn't so keen on all of example 2, it had way too many comments. 'Initialize variables' ? Give me a break, if you can't work out that's what's going on, you should turn off the computer, or at least stop reading code.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
Me too - DLSB
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
B for my liberal use of whitespace (the older I get the more I need).
- S 50 cups of coffee and you know it's on!
-
I'm the same category as Marc? Woo-hoo!:cool:
______________________ stuff + cats = awesome
-
I took this programming evaluation and I'm a DLSC Clickety[^] You're a Doer. You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money. You like coding at a Low level. You're from the old school of programming and believe that you should have an intimate relationship with the computer. You don't mind juggling registers around and spending hours getting a 5% performance increase in an algorithm. You work best in a Solo situation. The best way to program is by yourself. There's no communication problems, you know every part of the code allowing you to write the best programs possible. You are a Conservative programmer. The less code you write, the less chance there is of it containing a bug. You write short and to the point code that gets the job done efficiently.
-
B for my liberal use of whitespace (the older I get the more I need).
- S 50 cups of coffee and you know it's on!
-
I use spaces (in combination with tabs!) to make pretty layouts. :-D (My white space style is the latter of your two examples)
I also get pi$$ed off with the way C# reorganises my carefully aligned equals signs. :mad:
-
I also get pi$$ed off with the way C# reorganises my carefully aligned equals signs. :mad:
My blood would be boiling!!!
-
I'm a DLSB. I reckon question 12 made me different to you Question 12: What is the 'better' implementation: int main() { printf("5+6=%d", 5+6 ); return 0; } //////////////////////////////////////////////// // AddNumbers // param1 firstParam - The first value to add // param2 secondParam - The second value to add // return - The firstParam added to secondParam // int AddNumbers( int firstParam, int secondParam ) { // Here is some info int theReturn = firstParam + secondParam; // Now return the value return theReturn; } // Entry for program int main() { // Initialize variables int firstParam = 5; int secondParam = 6; // Call the function int returnValue = AddNumbers( firstParam, secondParam ); // Print out the value printf("%d+%d=%d", firstParam, secondParam, returnValue ); return 0; } I said the second because I like to see things refactored into small, reusable methods. I wasn't so keen on all of example 2, it had way too many comments. 'Initialize variables' ? Give me a break, if you can't work out that's what's going on, you should turn off the computer, or at least stop reading code.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
Christian Graus wrote:
I said the second because I like to see things refactored into small, reusable methods.
See, that's why I like functional programming - everything's a function - even operators - and they're all composable. So, if I wanted to apply summation to a list of numbers, I can use
sumNumbersor, taking advantage of partial function application,
sumNumbers = foldl (+) 0gives you a function that'll take a list of numbers. Want to read numbers from strings and sum them? Easy:
sumNumberStrings = sumNumbers . map (read :: String -> Integer)(the
:: String -> Integeris there because my favourite functional language, Haskell, is strictly typed, andreadis polymorphic). OK, I'll shut up - I'm just a (dis)functional freak.
