Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
You made a great point...oftentimes the answer to WHY? turns out to be "because that's how we always did things!" Or because the previous lead dev didn't want to learn anything new and insisted on using an ancient framework. I enjoy studying Zen Buddhism because there is so much of an emphasis on finding "a lamp unto yourself" and discovering the truth yourself...not because a popular blogger says to do it this way, not because it's a best practice (whose best practice?), and so forth.
Some people don't like change. I think that's a very human thing, I know I struggle with it. It's uncomfortable to see things in a different light and change your habits, but it is oftentimes well worth it. It took me years before functional programming finally clicked. I was reading and re-reading some great materials, but nothing stuck. The key concepts went right over my head. Then all of a sudden, one day I found myself nodding in agreement and I realized I had crossed the plateau. Then I proceeded to overabuse it and write lots of clever code, and I had a coworker challenge me to find simpler ways of expressing things.
I was pissed at first, he insulted my beautiful code! But he was right. I wasn't adding value with my code, I was making things much more complicated within a system that already took months to understand. So many things in life are about balance, and without being willing to fail and learn from our mistakes, we are bound to stagnate.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
I have heard that before form somewhere, 🤣!
"because that's how we always did things!" Or because the previous lead dev didn't want to learn anything new and insisted on using an ancient framework.
Change, is hard, but why? Because if we accept change, then all that we know will change too, until change is hard again and so all that we know will... I have caused a Stackoverflow in my head... The point I guess is that change represents that uncomfortable truth, that right and wrong is not finite but shifting all the time.
I might need to look into Buddhism a bit more, but I have a feeling with the life I have had, I may already be on that path.
"Then I proceeded to overabuse it and write lots of clever code, and I had a coworker challenge me to find simpler ways of expressing things."
Been there done that got the tshirt, still do it in private when nobody is looking, (because actually using clever stuff is not wrong if you know why it's clever and why people dislike it, (I used to think people thought I was a smart arse, not its just because Its not needed), but still I even write about the best of the worst, because know your enamy).
Take care Scott, I do love your comments :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You made a great point...oftentimes the answer to WHY? turns out to be "because that's how we always did things!" Or because the previous lead dev didn't want to learn anything new and insisted on using an ancient framework. I enjoy studying Zen Buddhism because there is so much of an emphasis on finding "a lamp unto yourself" and discovering the truth yourself...not because a popular blogger says to do it this way, not because it's a best practice (whose best practice?), and so forth.
Some people don't like change. I think that's a very human thing, I know I struggle with it. It's uncomfortable to see things in a different light and change your habits, but it is oftentimes well worth it. It took me years before functional programming finally clicked. I was reading and re-reading some great materials, but nothing stuck. The key concepts went right over my head. Then all of a sudden, one day I found myself nodding in agreement and I realized I had crossed the plateau. Then I proceeded to overabuse it and write lots of clever code, and I had a coworker challenge me to find simpler ways of expressing things.
I was pissed at first, he insulted my beautiful code! But he was right. I wasn't adding value with my code, I was making things much more complicated within a system that already took months to understand. So many things in life are about balance, and without being willing to fail and learn from our mistakes, we are bound to stagnate.
I have heard that before form somewhere, 🤣!
"because that's how we always did things!" Or because the previous lead dev didn't want to learn anything new and insisted on using an ancient framework.
Change, is hard, but why? Because if we accept change, then all that we know will change too, until change is hard again and so all that we know will... I have caused a Stackoverflow in my head... The point I guess is that change represents that uncomfortable truth, that right and wrong is not finite but shifting all the time.
I might need to look into Buddhism a bit more, but I have a feeling with the life I have had, I may already be on that path.
"Then I proceeded to overabuse it and write lots of clever code, and I had a coworker challenge me to find simpler ways of expressing things."
Been there done that got the tshirt, still do it in private when nobody is looking, (because actually using clever stuff is not wrong if you know why it's clever and why people dislike it, (I used to think people thought I was a smart arse, not its just because Its not needed), but still I even write about the best of the worst, because know your enamy).
Take care Scott, I do love your comments :)