846 karma · joined September 14, 2011
Thank you for this!
The problem is with bash itself.
We tend to undervalue ease of use and overvalue "cleverness."
Case in point: git. Very clever tool. Ease of use: terrible. But Linus wrote it and Linus is clever, so it must be us that's the problem.
We get what we value. Let's value ease of use more.
"I spend a lot of time designing UI for international users. In these circles, the issue you're talking about is referred to as 'BiDi' text input. If you would like to know more, ping me! Sometimes Googling isn't fruitful if you don't already know the lingo."
Maybe this sounds better to you, too. If not, maybe I'm wrong. It happens a lot. :-)
And he counts rhythms starting with zero. If you did this with any group of musicians, they would shout you out of the room. Imagine Mick Jagger yelling, "Zero, one, two, three!"
I'm not saying he doesn't have his reasons, but these sorts of things incline me to think he's not in the mainstream of musical culture. Which is fine, of course, but may be misleading to readers who think they're getting traditional musical information.
It was coupled, for my dad, with extreme frugality. He seemingly willfully deprived himself (and his family) of any fun or comfort by acquiring cheap versions of everything, or rigging up odd simulacrums of things, like the whole-house "air conditioner" he made from a cleaning bucket and some coffee cans. He bought a boat, then put such an underpowered motor on it that it was a joke. We had water skis, but they were rotted and just sat sadly against the wall, unusable.
Oh, my time's up? See you next week, doctor.
I just get sad for the designers who have to battle this stuff every day. No programmer would take "input" on their code from a nurse (say), but designers face "input" on their decisions and their craft at every turn. I've yet to meet a designer who was longing for a web form to input a bunch of numbers to generate some type sizes.
But I could be wrong. It happens a lot.
I've been a systems programmer, software development director at a well-known retailer, consultant, and (mostly) an entrepreneur who started four companies.
I still LOVE to code. Nothing like the satisfaction, though I enjoyed all the other things I did too.
Ageism is real in our industry. Note the comments below from 30-somethings who are worried their careers are over! Honestly, I'm pretty up-to-date with skills and knowledge. Plus I have so much experience, I know what works and what doesn't work, in the meta sense (architectures, organizations, etc.).
I recently even took on a side gig with a start-up. At our ages, you have to know someone who knows you and knows you'll be good. The good news is that, at our age, we know lots of people.
BTW, I founded and ran four companies and faced this very situation plenty of times. In my day (this was a while ago), we generally had to, or did, amortize development costs. I'm not saying I loved paying the tax bills, but the concept is neither farcical nor ridiculous.
Yes. Not sure what that has to do with this discussion.
> Can you provide the good arguments for capitalizing software development costs and not expensing it?
Yes. The well-established accounting principle of matching income and expenses.
> Can you explain the reasoning of charging taxes to a company that has revenue beyond merely 1/5th of its expenses (actually 1/10th in the first year, or 1/30th for international operations) and hence still heavily investing cash?
Yes. See the answer to your second question. Companies often have to make investments. If they buy a Big Machine, they don't get to write it off in one year. There's nothing nefarious about amortizing costs over their useful life.
There are a lot concepts being not very well defined here: employment, investing, taxation, salaries. It's not all one thing.
What is it that you think "we" are having both ways?
How can that be true? You only pay them once, not 1 4/5 times.