214 karma · joined April 25, 2008
Hell, Apple have made a fortune on this fact alone.
The capability a person has for listening to other people is a skill that very rarely gets acknowledged as a particularly genius trait. However, there is really nothing that can be done in this world if you aren't willing to listen at least as well as you talk.
I haven't dived into Arch Linux yet - haven't really found the need, and I guess I'm pretty much settled on the Debian way of doing things .. but one thing I have been thinking about lately is that it would be nice to have a stable-as-Ubuntu Linux system that has 100%, without fail, FULL SOURCE on-board, with everything configured so that if I find and fix something, it can easily go back into the sources as a patch or something.
Is Arch Linux going to provide that sort of configuration - full source onboard, easy to submit patches from whatever source I edit, etc? I might dedicate some time to checking out Arch in the future, and if it means I can configure my system to be 100% full source-onboard, I might do it sooner rather than later.
Of course, the idea of doing my own distribution based entirely on onboard-sources and instant patch contribution to a common public pool has also crossed my mind .. maybe BSD delivers in that regard? I really want my system to become a programmers paradise ..
No question about it: THEY KEEP YOUR DATA.
Nope.
There haven't been any mind-blowing awesome gems of answers in there that have caught my eye - mostly pretty mundane things, content-wise, and as a programmer looking for an interesting community, I don't really get that vibe from it much at all.
To me it just seems like a place for kids to go and get their homework done for them by lonely strung out alpha dogs looking to place some authority in the world.
For me, sites like this will never replace the good ol' USENET groups and subsidiary mailing lists. Once again (as is the case with Twitter), a web site springs up to try to capture an audience from the pool of people who are just not competent enough with E-mail to manage it properly and exploit the results ..
What I do remember is how quickly everything went by .. apparently my operation was 2 hours long, but I remember it going "bink" like that, and I was being wheeled through the hospital in what seemed like a lightning flash of time. Also, the nurses were hot.
But yeah, I'm with you on the don't-get-yourself-in-surgery-situations .. also, gunshot wounds: not funny.
Your problem only exists if we all have to be lumped into a group, together, so someone can sell us shit and control the whole thing.
In short, you clearly wanna sell lemons. There are other ways...
<-- grew up in Australia, was constantly healing my scrapes and bumps with Tea Tree oils and Manuka honey .. glad its all finally getting some science.
Words, on the other hand, require very, very little energy to be useful. That is the point - the effort and energy required to learn what "(void )func(void );" is useful for is equivalent to the energy required to learn what "jmp %ax" is useful for ..
You cannot compare word-working with hard working. Words are flat - they all require a similar environment in order to function, namely that of a fertile mind and the interest to watch them grow in the name of usage.
Words, on the other hand, require very, very little energy to be useful. That is the point - the effort and energy required to learn what "(void )func(void );" is useful for is equivalent to the energy required to learn what "jmp %ax" is useful for ..
You cannot compare word-working with hard working. Words are flat - they all require a similar environment in order to function, namely that of a fertile mind and the interest to watch them grow in the name of usage.
That said, I'm perfectly aware of how wrong my argument can be, but like I said .. works so far ..
Thus the effort required to use Assembly is equal to the effort required to use C or Python, with more or less equal boundaries in terms of the number of words and terms you will learn for any particular language. You can take two days to learn nothing but one language, and another two days to learn nothing but another language; the degree to which the progress of both of these periods is 'equal' is driven not by the words or language features themselves, but instead by your personal interest.
The average assembly programmer has to construct a taxonomy as equal in terms of effort as that of a Python programmer.
Now, bare with me here, because while I truly believe that 'all languages are flat', it is also a 'truism' that "personal interest drives the peaks in the effort curve".
That is to say, if you're not interested in Assembly, but you are interested in Python, it is your interest - not language features - that will be what drives the peaks and shallows in terms of the 'effort graph' in learning either Python or Assembly. This is not a function of the language, but instead of personal interest. I don't believe there are, for example "stupid people who can never learn Assembly and therefore must learn Python while there are 'more intelligent' people who easily become more proficient in Assembly" .. instead it is: "this person could learn either language, but their personal interest inclines them towards one over the other".
All languages are equal. Not all interests are equal. The degree of interest in a language drives its effectiveness in usage over that of another language.
http://www.critterandguitari.com/home/store/arduino-piano.ph...
I built one for fun, and ended up using it in jam sessions as a serious synth. Great!
My experience is this: either you waste a lot of time futzing around with computers, or you make them do the work they need to do and get on with your life. It has nothing to do with how old or young you are, or how many kids you have. I am a very happy Father now - in fact, this is the greatest startup, with the most rewards, I've ever been involved in - and I'm still applying the same fundamental policy to myself as a programmer: get things done, don't futz around with computers, make them actually do the work they're supposed to do.
It doesn't matter what "kind" of person you are, it matters only what kind of things you make. I know 50-year old grandfathers who can kick royal Assembler ass and still leave early at the end of the day, and I know 18 year old kids who put the keyboard down after 8 hours and go do something else instead, as well.
IMHO, this over-generalization about 'types of people' is a real curse. I would say, don't do it. There are no 'types' of people in the computer world, no matter how the ycombinator cultists want to pitch it to the world: there are people who get things done, and people who don't.
Get things done. Get your code written, working, tested, and in the hands of people who will actually use it. If you can't do this, then you will fail. If you can, then rock on .. may your kids, now and in the future, always appreciate this aspect of you as a person.