Ah, one more transformation...
Sep. 11th, 2017 01:25 pmFor this work project, I am slowly, painfully making myself work effectively as a beginning visual designer. This is not a thing I expected to see happen.
And yet it turns out if you have to pick up a particular skillset and use it often enough, for long enough, you'll start to understand the skills behind it.
As a side note, I pick up a given skillset *much* better if I don't think of myself as a person-who-does-that. That is, I pick up dance faster if I'm not trying to be a dancer and visual design faster if I'm not trying to be a visual designer.
No clue on the programming stuff. I'm already a programmer. But then, I've picked up difficult specialties like distributed systems and artificial intelligence without considering myself a specialist in that area, and it *has* worked well. So maybe the same is true there.
I'm too old a programmer to pick up a specialty and say "this is what I am" any more. Even Ruby, which has been a nine-or-so-year love affair and my primary thing for years, still gets hedged phrasing like "I work mostly in Ruby these days."
And yet it turns out if you have to pick up a particular skillset and use it often enough, for long enough, you'll start to understand the skills behind it.
As a side note, I pick up a given skillset *much* better if I don't think of myself as a person-who-does-that. That is, I pick up dance faster if I'm not trying to be a dancer and visual design faster if I'm not trying to be a visual designer.
No clue on the programming stuff. I'm already a programmer. But then, I've picked up difficult specialties like distributed systems and artificial intelligence without considering myself a specialist in that area, and it *has* worked well. So maybe the same is true there.
I'm too old a programmer to pick up a specialty and say "this is what I am" any more. Even Ruby, which has been a nine-or-so-year love affair and my primary thing for years, still gets hedged phrasing like "I work mostly in Ruby these days."