How to get where you want to go…it’s as easy as 1, 2, 3
“Alex, I have noticed you are running what amounts to a one man show on the API front, and tend to a lot of developer relations when I assume you would rather be developing. That said, is Twitter looking for someone to help manage the developer community (answer API questions, serve as liaison to development, etc…)? …”
1. Get involved with the community
2. Notice specific ways you can help out
3. Take a chance, prove your value, and hold on tight.
Later, Rinse, Repeat.
That’s why most designers make awful team members. It’s why, when the biz dev guy says “this is how our startup is going to make money,” our first inclination is to tear the living shit out of the idea.
But what designers need to understand is that nobody likes a negative blocker, and when we attack an idea, it feels personal to the guy with the idea, and invariably leads to us being left out, which is that last thing we want.
Fortunately the solution is simple: just force yourself to come up with an alternate solution. It’s a great mental exercise - think to yourself, “what’s the solution I want to see?” If I can’t come up with one, I won’t say anything. Better to be quiet and see how things progress than to be the negative blocker guy.„
via Derek Powazek’s “Things I Learned the Hard Way”
via Tim Ferriss
No permission required
Have had to remind myself of this lately…The Way to Learn X is to Do X.
Rather than waiting to get hired at your job of choice, start trying to do whatever it is you want to do on your own. Of course it’s easier said than done, but it helps to have a vision of a finished product to help you learn some new skills rather than picking up a bunch of manuals and plowing through them blindly.
Here’s an example from Louis Rossetto, talking about the creation of Wired:
Six months later, I created a second prototype on my own. Learned how to use Quark, Photoshop, and Illustrator in the same month — and juggle too.
Ditch the resume to get hired?
As usual, Seth’s got some interesting advice for those hoping to do interesting things…this time around it’s resume advice, or more accurately, advice on why you shouldn’t have a resume. Some notes:
I think if you’re remarkable, amazing or just plain spectacular, you probably shouldn’t have a resume at all. Here’s why: A resume is an excuse to reject you. Once you send me your resume, I can say, “oh, they’re missing this or they’re missing that,” and boom, you’re out.
Great jobs, world class jobs, jobs people kill for… those jobs don’t get filled by people emailing in resumes. Ever.
So, what should you have in place of a resume? How about…
- Three extraordinary letters of recommendation from people the employer knows or respects?
- A sophisticated project they can see or touch?
- A reputation that precedes you?
- A blog that is so compelling and insightful that they have no choice but to follow up?
(another option is think of your own idea that isn’t on this list)
Got any good examples of an un-resume?
update on 10/26: Came across a related link on 6 steps to Resume 2.0 which offers simple tips on how to make your resume more dynamic. But in addition to that, it talks about how even in this world of social media “all communication should really be crafted with the receiver in mind.” With that being said, I’m going to try starting this blog back up with one important receiver in mind….me :)