The learning rush
-
I'm 56, and still have the learning itch. The problem is that there are many more claims on my time than there were when I was young, single, and childless, so the pile is growing at the bottom faster than I can clear it at the top. :sigh:
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
I'm sorry. I am older (than I was at least) married and childless so I have less claims on my time. I suppose I'm blessed in that, but I can also only deal with so much so it's for the best. :sigh:
Real programmers use butterflies
-
I'm 67 and still have the learning itch
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
I love seeing your sig flash by me in my notifications because even though I can't see all of it in the little blurb it gives me i immediately know the reference and mentally recite it in Johnny Depp's Hunter voice. (say what you will i thought the movie did HST justice)
Real programmers use butterflies
-
I did read that article though, and the main point is the same one I think you made, that what if:
if(foo)
bar();
baz(); // always executedTo which I respond that this has never happened to me that I can recall, in part because VS autoformats code and I hit Ctrl-A,K,D regularly. So it's a solution in search of a problem, at least with my personal code. When I am working on a team I code differently, but it also takes me longer and irritates me.
Real programmers use butterflies
I just found an abomination, purely by coincidence, that had me confused for a moment.
if (something &&
somethingElse)
DoStuff();
else
DoOtherStuff();The indentation doesn't help here! Needless to say, I wanted to add braces and added them above somethingElse, which broke the code :sigh: The point you make has actually happened to me before. I inherited someone else's code and I had to make a change. For some reason, the original programmer added two lines with the same indentation (and VS didn't change it back for me, I think this was VS2010). I added a (conditional) third, but to my surprise it was always executed! Took me a while to find that one :doh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
I just found an abomination, purely by coincidence, that had me confused for a moment.
if (something &&
somethingElse)
DoStuff();
else
DoOtherStuff();The indentation doesn't help here! Needless to say, I wanted to add braces and added them above somethingElse, which broke the code :sigh: The point you make has actually happened to me before. I inherited someone else's code and I had to make a change. For some reason, the original programmer added two lines with the same indentation (and VS didn't change it back for me, I think this was VS2010). I added a (conditional) third, but to my surprise it was always executed! Took me a while to find that one :doh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
awwwww. Well maybe its your else statements that are the problem! Don't use else {}[^] :laugh:
Real programmers use butterflies
-
awwwww. Well maybe its your else statements that are the problem! Don't use else {}[^] :laugh:
Real programmers use butterflies
Having multiple return statements in a function is another pet peeve of mine. I'm fine with it at the start of a function, like if (parameter == null) return, but not somewhere halfway. I read some code at the top, miss the return statement in the middle, and think I'm getting a wrong result at the end. Only when I actually run the code (and somehow my breakpoint won't hit!) will I see the error in my thinking because the functions returns on me halfway. I recently read some sample code that had like four return statements in some 20-25 line function or something, that's just plain not readable! X| Also, what if my else branch doesn't have to terminate the code? :confused:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
Having multiple return statements in a function is another pet peeve of mine. I'm fine with it at the start of a function, like if (parameter == null) return, but not somewhere halfway. I read some code at the top, miss the return statement in the middle, and think I'm getting a wrong result at the end. Only when I actually run the code (and somehow my breakpoint won't hit!) will I see the error in my thinking because the functions returns on me halfway. I recently read some sample code that had like four return statements in some 20-25 line function or something, that's just plain not readable! X| Also, what if my else branch doesn't have to terminate the code? :confused:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
To be fair I don't agree with that article. But I also feel like creating workable (as in readable/maintainable) code is an organic process. If you try to force it it impedes productivity and becomes counterproductive. I think at least, unless you need (and are willing to spend the overhead) to work in a mid to large team it's different, but on my own or in small groups it's in my experience best to let experience teach you how to code, and say screw the thinkpieces that people write simply to make themselves seem smart. For different people what maintainable readable code looks like is going to be different, but find something that works well *for you* and do that. I never get tripped up on braceless ifs, so it's not a peeve of mine. I however, *loathe* over factoring, such as using design patterns just to use them, or creating a class where one function would do. Why? Because I find it impossible to navigate. But you know what? That code can map directly to a UML diagram and my code can't, so I should drink a tall frosty glass of STHU because that code has its advantages. I also don't like interfaces i am expected to work against to come without XML DOC COMMENTS!! But that's because i have to work with that code. Otherwise I could not care. My point is, we all have our peeves, and different styles and such, but unless i have to code against your work I don't care what it looks like. I hope *you* do though, if that makes sense.
Real programmers use butterflies
-
I'm sure most of you get it or you wouldn't be developers. We're always accruing new knowledge not just to keep up but to get ahead. I don't know about you but I'm a sponge. I sustain myself on learning things. It's such a rush to challenge myself to do something new or something better. I went from not being able to wire up a 16-pin hitachi interface LCD to building IoT gadgets with them, all the way to doing it for money in under a month, drawing from a hobby I abandoned for programming back when I was a kid. Now I'm doing both. It's seriously challenging me. I haven't used my brain this much in years. It's one thing to learn more in a field you're already familiar with, like when I learned parsing theory. It's another to learn a different, even if related field. That's what I'm doing now. It's all very fun, but now I worry I'm going to get lost in it to the expense of everything else. Can it be an addiction? I wonder.
Real programmers use butterflies
One of the interesting things I have found after becoming really old is there is so much one could learn that you can be rather selective about what you choose to learn. Unfortunately I don't have the time to learn everything I want to.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
To be fair I don't agree with that article. But I also feel like creating workable (as in readable/maintainable) code is an organic process. If you try to force it it impedes productivity and becomes counterproductive. I think at least, unless you need (and are willing to spend the overhead) to work in a mid to large team it's different, but on my own or in small groups it's in my experience best to let experience teach you how to code, and say screw the thinkpieces that people write simply to make themselves seem smart. For different people what maintainable readable code looks like is going to be different, but find something that works well *for you* and do that. I never get tripped up on braceless ifs, so it's not a peeve of mine. I however, *loathe* over factoring, such as using design patterns just to use them, or creating a class where one function would do. Why? Because I find it impossible to navigate. But you know what? That code can map directly to a UML diagram and my code can't, so I should drink a tall frosty glass of STHU because that code has its advantages. I also don't like interfaces i am expected to work against to come without XML DOC COMMENTS!! But that's because i have to work with that code. Otherwise I could not care. My point is, we all have our peeves, and different styles and such, but unless i have to code against your work I don't care what it looks like. I hope *you* do though, if that makes sense.
Real programmers use butterflies
"We are what we repeatedly do. Excellence, then, is not an act, but a habit." - Not Aristotle, apparently That only goes for my style though. The actual program tends to change and I change my view of how I want my code to flow. For example, a program I made three years ago still has the traditional three tier architecture. It's completely over factored I think (now, it made sense three years ago). I have one tier that gets entities from the database and puts it in domain classes (not entities, those are DB specific) and then the middle tier passes it on to the controller and the controller translates it to a view model. The middle tier is completely empty most of the time and the domain classes don't do anything either. It's just there because X| To make things worse, since it's all pretty much the same code, I've created some generic base classes that create generic expression trees, so that my data layer can generically query any entity. I may have gone a bit overboard on that one :laugh: My code from last year follows a simpler design, entities are translated directly into view models (and vice versa) and it all happens in the controller. I still have some generic code, but not in my database code. I prefer copy/paste and seemingly duplicity in the name of maintainability. My past project has taught me that just because I have the technical know-how does not mean I have to use it :laugh: I've also been told ex-coworkers (especially the anti-learn) still struggle reading my code (so it's totally worth it!) :laugh: :D The fun part is, that when you look at my naming conventions, member placement, project and class layout, etc. nothing has changed in those past few years :D
honey the codewitch wrote:
unless i have to code against your work I don't care what it looks like. I hope *you* do though, if that makes sense.
I know what you mean. I do care about what your code looks like. I go to bed with it and I wake up with it. Those darned braceless if-statements! :laugh: Or maybe that wasn't what you meant... :rolleyes:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azu
-
"We are what we repeatedly do. Excellence, then, is not an act, but a habit." - Not Aristotle, apparently That only goes for my style though. The actual program tends to change and I change my view of how I want my code to flow. For example, a program I made three years ago still has the traditional three tier architecture. It's completely over factored I think (now, it made sense three years ago). I have one tier that gets entities from the database and puts it in domain classes (not entities, those are DB specific) and then the middle tier passes it on to the controller and the controller translates it to a view model. The middle tier is completely empty most of the time and the domain classes don't do anything either. It's just there because X| To make things worse, since it's all pretty much the same code, I've created some generic base classes that create generic expression trees, so that my data layer can generically query any entity. I may have gone a bit overboard on that one :laugh: My code from last year follows a simpler design, entities are translated directly into view models (and vice versa) and it all happens in the controller. I still have some generic code, but not in my database code. I prefer copy/paste and seemingly duplicity in the name of maintainability. My past project has taught me that just because I have the technical know-how does not mean I have to use it :laugh: I've also been told ex-coworkers (especially the anti-learn) still struggle reading my code (so it's totally worth it!) :laugh: :D The fun part is, that when you look at my naming conventions, member placement, project and class layout, etc. nothing has changed in those past few years :D
honey the codewitch wrote:
unless i have to code against your work I don't care what it looks like. I hope *you* do though, if that makes sense.
I know what you mean. I do care about what your code looks like. I go to bed with it and I wake up with it. Those darned braceless if-statements! :laugh: Or maybe that wasn't what you meant... :rolleyes:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azu
You are too funny. I mean that. Too funny by half. ;P I want people to take pride in their own code. If they do, and they respect the craft their code will reflect that, style differences aside. That's what I meant.
Real programmers use butterflies
-
You are too funny. I mean that. Too funny by half. ;P I want people to take pride in their own code. If they do, and they respect the craft their code will reflect that, style differences aside. That's what I meant.
Real programmers use butterflies
Believe it or not, but I actually knew what you meant. I'm just trolling you :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
Believe it or not, but I actually knew what you meant. I'm just trolling you :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Enough of this gabfest! Don't you lads have any work to do? And for the record, @code-witch, I'll also use a braceless
if, and evenif-else, but it depends. A simpleif(condition)
statement1;
else
statement2;is perfectly clear to me. I'm so thoughtful, injecting new life into your thread. :-D
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.<p><a href="https://github.com/GregUtas/robust-services-core/blob/master/README.md">Robust Services Core</a>
<em>The fox knows many things, but the hedgehog knows one big thing.</em></p> -
I'm sure most of you get it or you wouldn't be developers. We're always accruing new knowledge not just to keep up but to get ahead. I don't know about you but I'm a sponge. I sustain myself on learning things. It's such a rush to challenge myself to do something new or something better. I went from not being able to wire up a 16-pin hitachi interface LCD to building IoT gadgets with them, all the way to doing it for money in under a month, drawing from a hobby I abandoned for programming back when I was a kid. Now I'm doing both. It's seriously challenging me. I haven't used my brain this much in years. It's one thing to learn more in a field you're already familiar with, like when I learned parsing theory. It's another to learn a different, even if related field. That's what I'm doing now. It's all very fun, but now I worry I'm going to get lost in it to the expense of everything else. Can it be an addiction? I wonder.
Real programmers use butterflies
Not at first, but eventually, I found out what my aptitudes. They had been expressing themselves since, well, always - but it was accepting what they were and what they weren't that took a while. They more or less fit well with the latin phrase:
Quote:
Aut viam inveniam aut faciam - Hannibal
It has two faces: you can find someone more proficient than I but you will not easily find someone who's better at solving your problems. Basically a lifetime stream of inventions (whether as inventive solutions or actual physical objects). The 'Necessity is the mother of invention' thing does play into it but it isn't always necessity - or maybe better put - it becomes a personal necessity . . . . . . and that's the greatest fun. Coding is fun, but it's somewhat indirect. By the time my fingers start their dance on the keyboard they're following a path already worked out and still evolving. Putting imagination into practice - relaxing; absorbing - playing! Learning new things is a part. Reusing old things in new ways is a part. I'm not even sure there's truly a difference. Something possibly explained when someone tells me I "think outside of the box" and all I can think of as a suitable reply is "what box" ?
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
I did read that article though, and the main point is the same one I think you made, that what if:
if(foo)
bar();
baz(); // always executedTo which I respond that this has never happened to me that I can recall, in part because VS autoformats code and I hit Ctrl-A,K,D regularly. So it's a solution in search of a problem, at least with my personal code. When I am working on a team I code differently, but it also takes me longer and irritates me.
Real programmers use butterflies
if(foo)
bar();
baz(); // always executedIn Python not... :rolleyes: :laugh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Enough of this gabfest! Don't you lads have any work to do? And for the record, @code-witch, I'll also use a braceless
if, and evenif-else, but it depends. A simpleif(condition)
statement1;
else
statement2;is perfectly clear to me. I'm so thoughtful, injecting new life into your thread. :-D
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Greg Utas wrote:
Don't you lads have any work to do?
On a Sunday? No :D
Greg Utas wrote:
I'm so thoughtful, injecting new life into your thread.
But do you really want to get involved? Too late for that, you're a part of this now. Prepare to be pitchforked! :D
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
I love seeing your sig flash by me in my notifications because even though I can't see all of it in the little blurb it gives me i immediately know the reference and mentally recite it in Johnny Depp's Hunter voice. (say what you will i thought the movie did HST justice)
Real programmers use butterflies
I prefer the book but Depp did pretty well in the film - the special effects weren't my experience ( mine were much worse ) when I dabbled in taking that stuff but hey ho. We are coming into bat season very soon...
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
-
Believe it or not, but I actually knew what you meant. I'm just trolling you :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Oh I know. It's much more difficult for you to if I treat you like you're not. :laugh:
Real programmers use butterflies
-
if(foo)
bar();
baz(); // always executedIn Python not... :rolleyes: :laugh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Perhaps ironically that's actually the reason I will not use python. I'm serious.
Real programmers use butterflies
-
Not at first, but eventually, I found out what my aptitudes. They had been expressing themselves since, well, always - but it was accepting what they were and what they weren't that took a while. They more or less fit well with the latin phrase:
Quote:
Aut viam inveniam aut faciam - Hannibal
It has two faces: you can find someone more proficient than I but you will not easily find someone who's better at solving your problems. Basically a lifetime stream of inventions (whether as inventive solutions or actual physical objects). The 'Necessity is the mother of invention' thing does play into it but it isn't always necessity - or maybe better put - it becomes a personal necessity . . . . . . and that's the greatest fun. Coding is fun, but it's somewhat indirect. By the time my fingers start their dance on the keyboard they're following a path already worked out and still evolving. Putting imagination into practice - relaxing; absorbing - playing! Learning new things is a part. Reusing old things in new ways is a part. I'm not even sure there's truly a difference. Something possibly explained when someone tells me I "think outside of the box" and all I can think of as a suitable reply is "what box" ?
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
W∴ Balboos, GHB wrote:
when someone tells me I "think outside of the box" and all I can think of as a suitable reply is "what box" ?
I can understand that. I have a gift in that area as well but in part because I cheat. I went mad. It helps.
Real programmers use butterflies
-
Enough of this gabfest! Don't you lads have any work to do? And for the record, @code-witch, I'll also use a braceless
if, and evenif-else, but it depends. A simpleif(condition)
statement1;
else
statement2;is perfectly clear to me. I'm so thoughtful, injecting new life into your thread. :-D
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing."are there no workhouses?" Alright Scrooge, it's Sunday!
Real programmers use butterflies
-
I'm sure most of you get it or you wouldn't be developers. We're always accruing new knowledge not just to keep up but to get ahead. I don't know about you but I'm a sponge. I sustain myself on learning things. It's such a rush to challenge myself to do something new or something better. I went from not being able to wire up a 16-pin hitachi interface LCD to building IoT gadgets with them, all the way to doing it for money in under a month, drawing from a hobby I abandoned for programming back when I was a kid. Now I'm doing both. It's seriously challenging me. I haven't used my brain this much in years. It's one thing to learn more in a field you're already familiar with, like when I learned parsing theory. It's another to learn a different, even if related field. That's what I'm doing now. It's all very fun, but now I worry I'm going to get lost in it to the expense of everything else. Can it be an addiction? I wonder.
Real programmers use butterflies
