Earlier quoted context omitted.
The "spiritual" word is often used in non-religious contexts to mean the mastery of the inner world. Meditation is often used as a way to take control of your thought processes (which are sometimes negative), so that's why it's often classified as a spiritual practice.
Huh, I don't think I've heard it used like that before, or didn't understand it that way in any case. "Spiritual" to me, being based on "sprit", always has connotations of external supernatural entities.
Non-programming skills every programmer should have
41–49 of 49 posts
Re: Non-programming skills every programmer should have
#42Writing (and perhaps presentation) is another skill we should develop. Writing is not just about communication, but it also aids in idea refinement.
On the other hand, even though I'm all for zen and all, I think spirtual skills are deeply personal and not necessary. Social skills are also very relative, and if you struggle with these your career as a programmer is not over! Same for biz skills, no one has to be a jack of all trades, but you'll probably absorb these skills at your own pace as you advance in your career.
Re: Non-programming skills every programmer should have
#43Earlier quoted context omitted.
I'd suggest that "spiritual skills" encompass an understanding that there are connections between ourselves and our surroundings that defy precise, scientific description. Whether that's a feeling of camaraderie with your teammates, or a sense that one's office is warm and inviting or cold and unpleasant, or an immediate response upon meeting someone for the first time that you can trust them implicitly--or that you…
All of those things you mentioned are to a large degree explained by science. Spirituality appears to require at least some belief in something beyond the material world. There are certainly things that can be taken from spiritual practises that can be useful but in most cases there is an explanation for this value that does not require any belief in the supernatural.
Just replace spirituality with custom, culture, emotion, and its not so anti-intellectual.
Re: Non-programming skills every programmer should have
#44If someone had all these skills, why would they be a programmer? :)
Re: Non-programming skills every programmer should have
#45A lot of people seem to be offended by this article when I think all the author was trying to say is that opening yourself to other, non-programming related stuff simply helps you become a better programmer as a whole. I honestly don't think he's suggesting you should be a pro at all those other points, just have a fairly good knowledge of them. I personally find that, on top of the points mentioned in the article, a…
It's one thing to say that programmers (and everyone, really) should have a hobby outside of work. This is a laundry list of vague ideas - 'Startup' is not a skill - that the author insists every person who programs for a living should be interested in. What exactly is 'looking beyond the code'? Can you give an example of a problem where two equally skilled programmers were faced with a problem, and one had an epipha…
And no, I suppose I don't have a specific example. I just notice that the programmers I know who are more than just coders are considerably more efficient, and come up with better, cleaner solutions.
This is, of course, only speaking from personal experience. And in regards to your "extreme underwater basket weaving club" example, well, maybe it does. I learnt Latin for a while and as useless as it may seem on a day-to-day basis, it did wonders to my logical thinking.
Re: Non-programming skills every programmer should have
#46Re: Non-programming skills every programmer should have
#47Earlier quoted context omitted.
All of those things you mentioned are to a large degree explained by science. Spirituality appears to require at least some belief in something beyond the material world. There are certainly things that can be taken from spiritual practises that can be useful but in most cases there is an explanation for this value that does not require any belief in the supernatural.
Relying on some kind of placebo or customs to enrich our lives is perhaps not very crazy. If we take everything at face value, the universe is vast in time and space and so our lives are very insignificant or meaningful; its hard to justify doing anything at all in that case. Just replace spirituality with custom, culture, emotion, and its not so anti-intellectual.
Re: Non-programming skills every programmer should have
#48Earlier quoted context omitted.
Because telling everyone that they have to have religion is such a strong compulsion that people can't even resist doing it in an article supposedly aimed at programmers.
He very clearly states its not about religion and that he isn't religious. Just a poor title.
This is just social pressure to conform to certain kinds of ideas. The fact that the word "spiritual" allows me to self-label as religious even if I don't belong to a large institution like the Catholic church is not very helpful if I am just not religious. And why should I have to be?
Re: Non-programming skills every programmer should have
#49It's funny how many programming jobs are designed explicitly to insulate you and not require any of these skills. Just code and let the adults do all the talking. In many organizations, it's easy to get caught in a catch-22 where to advance, you need nontechnical skills, and to develop nontechnical skills, you need to advance. For some, this means they get to do what they love without much hassle (see "do you still w…
I've found that even sitting at the kids' table you can make sure people in the rest of the business know that you're not just a code monkey. I try to ask questions, make suggestions, make sure people know me and that I contribute more than just lines of code to the business. Even though I have little desire to move up to the adult table I think it's good for your long-term career to be known as more well-rounded. Pl…
and it actually makes the coding easier. some of the most frustrating parts of development come from not being in control - you are very much dependent on the person above whose talking to the client. and it helps the client too, because with less buffer they can get faster feedback. which again helps you, because you can do faster iterations and understand more closely what the customer wants...