What Is Your Most Valuable Life Skill?
-
I was lucky enough to be raised as bilingual English/French. I have not used the French much as an adult and street French itself has changed a bit since the 70s - however I still have the accent, can speak a bit and enjoy watching French documentaries/films. It's been really useful because it's also made it easier for me to pick up and speak other languages as some French phonemes are very different to English phonemes. Once you get a feel for different phonemes it makes speaking other languages easier - I still cringe a lot at how most English speakers pronounce the word "croissant" :laugh: It's opened up a whole other world to me and I am grateful for having this facility.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
On lighter side... my first for pay job in US was maintaining "industrial size " sawing machines... their product was variety of plastic and "natural fiber " 50 pounds or smaller bags.. their byproduct was unbelievable oily fiber mess clogging everything... I did learn skills and respect of operators for not being too concerned getting " down to get dirty "... and since I used screwdriver , instead of hammer , as my "teacher " Ernie ... I guess my learned life skill is being able to "look things over " and use the right tool to get the job done. but sometime Mikey mouse wins...
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
Knowing full well that no matter my coding skills there are people with far more knowledge and I can learn from even the junior-est person in the team. Having absolute zero ego about what I can do and ask for help when I don't understand something.
Zen and the art of software maintenance : rm -rf * Maths is like love : a simple idea but it can get complicated.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
-
I think my most valuable skill is spotting patterns, and when they're broken. I've always been able to look at a problem, see how it is meant to work, and identify what needs to be changed to make it work, even as a child. It has been curse many times, and I didn't have a lot of friends growing up, as this is considered to be a bit spooky to some, and being a smartass to others.
Will Rogers never met me.
Roger Wright wrote:
a bit spooky to some, and being a smartass
A bit 'tetched, eh? :-D
Software Zen:
delete this; -
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
Being able to laugh at myself.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
Adapting, improvising, and overcoming obstacles/challenges. I learned and honed this life skill as a Navy nuc, starting at 17 years old. I found it useful in successfully shifting technologies over the years (nuclear power to industrial controls programming/engineering to writing n-tier software to writing cloud native software today). Our line of work as software engineers changes over time because the technologies and tools change, and because where we apply them changes, and the needs of our users changes. The “adapt/improvise/overcome” skill requires a solid base of deductive reasoning. Just solving programming and systems issues or projects with yesterday’s “recipes” is grossly inadequate. Solving software engineering issues and projects for what they uniquely are (as well as what they have in common with other issues and projects) requires the skill set I mentioned. While my instance of that skillset was learned and matured one way, how you, the reader, either obtained that skillset or can acquire it, may be different. I see so many developers, when given a new project, or trying to fix a bug in existing code, just reach into their recipe box to see what most closely fits, then try to hammer that round peg in a square hole. The results of that approach are too often mediocre to a flat failure. By applying this skillset, which any developer of at least average intelligence, from any cultural background can acquire with intent and practice, they can figure out any issue or project in a way that results in quality, performance, reliability, and it “just works well”.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
Becoming adaptable to ever changing paradigms in life. It's a life skill to stay patient during times of change, and evolve with the change.
-
Adapting, improvising, and overcoming obstacles/challenges. I learned and honed this life skill as a Navy nuc, starting at 17 years old. I found it useful in successfully shifting technologies over the years (nuclear power to industrial controls programming/engineering to writing n-tier software to writing cloud native software today). Our line of work as software engineers changes over time because the technologies and tools change, and because where we apply them changes, and the needs of our users changes. The “adapt/improvise/overcome” skill requires a solid base of deductive reasoning. Just solving programming and systems issues or projects with yesterday’s “recipes” is grossly inadequate. Solving software engineering issues and projects for what they uniquely are (as well as what they have in common with other issues and projects) requires the skill set I mentioned. While my instance of that skillset was learned and matured one way, how you, the reader, either obtained that skillset or can acquire it, may be different. I see so many developers, when given a new project, or trying to fix a bug in existing code, just reach into their recipe box to see what most closely fits, then try to hammer that round peg in a square hole. The results of that approach are too often mediocre to a flat failure. By applying this skillset, which any developer of at least average intelligence, from any cultural background can acquire with intent and practice, they can figure out any issue or project in a way that results in quality, performance, reliability, and it “just works well”.
THIS. ☝️💯
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
-
Roger Wright wrote:
a bit spooky to some, and being a smartass
A bit 'tetched, eh? :-D
Software Zen:
delete this;Yep, so it would seem.
Will Rogers never met me.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
As a computer engineer, I assume every other computer engineer is as competent. That said, one inherited habit and one acquired, persistence and humility should be deemed essential. In the pursuit of happiness, life throws many curve balls, so sometimes you have to do what's necessary to outlive a situation. Gotta eat and sleep before you conquer the world.
-
Translating what the customer says they want ("customer" includes "manager" for those that may remember when TQM / ISO-9000 was all the rage) into what they actually need. This can be generalized to any relationship. ;)
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkI was also going to say "translating." I was thinking more of between groups of my "internal customers" in the company. Translating desires between laser physics folk, marketing, mechanical engineers, firmware/software engineers, electronics engineers, R&D management. And then there's translating field failure reports into something useful.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
Somehow people talk to me, telling me all sorts of things that are important to them. Maybe because I listen.
-
I had the same thought. 1. Allowing heart to beat 2. Breathing 3. … Breathing is key to stress release! I use it multiple times an hour at work.
-
Does breathing count?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
Kindness
Paul Sanders. If I had more time, I would have written a shorter letter - Blaise Pascal. Some of my best work is in the undo buffer.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
Hmm, it's multiple, all related to building and fixing things. It's a curse, too, because I somehow can't get out of the rut/feeling that I should/must? repair and build EVERYTHING that breaks or that I want/need in life. That is, I basically have not, in my half a century+ of life, ever called a plumber, electrician, auto mechanic*, appliance/lawn & garden/heavy equipment mechanic. . .or for any home improvements. :sigh: :sigh: :sigh: *there were 2 times where I had some more time consuming major repairs needed to a vehicle but had no indoor location in the winter months to work on it and/or it was when I had small children/family + full time job where I just didn't have the time to tackle it myself. So yeah, I guess this would entail the skills in woodworking, construction (excavation/concrete/framing/siding/roofing/wiring/tiling), welding, small and large engine mechanics, some electronics.
-
As software developers, I think we can agree that our coding skills are universally applicable. In my experience, there have been more than a few instances where my work has evoked comments from others expressing disbelief. It's funny because you hear the same things over and over again. "Woah, how did you do that?", and "Where did you learn to do that?", and of course the "You suck" comments. Knowing how to code is certainly a very valuable life skill to have. But, what about other skills? In what other areas do you have knowledge or experience with? What are they, and how do you use them? How are they of benefit to you? Is it worthwhile for others to learn these skills? Why, or why not?
>
Quote:
In what other areas do you have knowledge or experience with? What are they, and how do you use them?
The thing that made a colleague go "Woah - how did you do that?" was when his car broke down in the company parking lot with a snapped clutch cable, and I drove it all the way to his home without once needing the clutch[1] even though I worked it through all five gears, both changing up and changing down. [1] Stalled at every stop, started with a jerk after every stop.
-
Hmm, it's multiple, all related to building and fixing things. It's a curse, too, because I somehow can't get out of the rut/feeling that I should/must? repair and build EVERYTHING that breaks or that I want/need in life. That is, I basically have not, in my half a century+ of life, ever called a plumber, electrician, auto mechanic*, appliance/lawn & garden/heavy equipment mechanic. . .or for any home improvements. :sigh: :sigh: :sigh: *there were 2 times where I had some more time consuming major repairs needed to a vehicle but had no indoor location in the winter months to work on it and/or it was when I had small children/family + full time job where I just didn't have the time to tackle it myself. So yeah, I guess this would entail the skills in woodworking, construction (excavation/concrete/framing/siding/roofing/wiring/tiling), welding, small and large engine mechanics, some electronics.
Kent K wrote:
Hmm, it's multiple, all related to building and fixing things. It's a curse, too, because I somehow can't get out of the rut/feeling that I should/must? repair and build EVERYTHING that breaks or that I want/need in life. That is, I basically have not, in my half a century+ of life, ever called a plumber, electrician, auto mechanic*, appliance/lawn & garden/heavy equipment mechanic. . .or for any home improvements. :sigh: :sigh: :sigh:
That's a great set of skills to have. I'm not just referring to building or fixing things, but I'm referring to any mechanical system. Air compressors, phones, power tools, cars, and various other things. As time progresses, technology advances and I've come to find that it gets more difficult to repair these things on your own. Taking something apart is easy, but knowing how to reassemble the item after repairing it requires more and more obscure tools, as well as sophisticated knowledge. I'm glad we have YouTube, because the knowledge needed to repair more advanced systems can't be done without it. I used to be able to do this stuff through basic mechanical skills, and intuition. The one exception where I have failed (epically failed) is in fixing the rotating control knob on an old clothes dryer. Sounds simple enough, right? Ha! Nope. After taking it apart, I was glad to see that I could go about repairing it without dealing with any electronics. Little did I know that the nested arrays of metal pins allowing the knob to operate the functions of the clothes dryer were extremely complex. I gave it a try, but soon realized I needed a trained technician with the proper tools to do the job.