PDX Critique

Testing twitter tools

Back in April I got about half way through a review of a play I saw. I had decided that it would be good to begin posting my opinions for things I had experienced. I chickened out. I plan on finishing it and hitting “post” before the next PDX Critique meet.

I mulled over what happened and realized that while I’m good at throwing out verbal opinions in a group setting like PDX Critique where people can tell me directly that it’s ludicrous there is a hesitancy to put these opinions out in solid form. Partially because I know that through discussion I can be convinced that maybe __ wasn’t insipid.

PDX Critique is a comfortable environment to brainstorm ideas. It’s a back and forth with people exchanging and growing. I don’t know if the blog can capture that same sense but I’d like it to.

We’re meeting again on Friday, 8/28/09. I’ll post my theater review at least two days before that. Please don’t just read it and take it as script. Treat it like we do anything here at PDX Critique and speak your mind.

This could become a new way for people to present written work for feedback that is less tied to being able to make it on a day of the week. Since our next meeting is about the future of PDX Critique let’s experiment with this and see how it goes.

Next post within eight days…

We will be meeting at OSBridge on Thursday, June 18, 2009 from 7:00 – 8:30pm in Marquam, more details can be found here: http://opensourcebridge.org/sessions/285

See you there.

CubeSpace has hosted the PDXCritique meetings since our inception. We are truly grateful to them, not only for hosting us, but for fostering such a great community here in Portland.

Now the time has come when they need help from the community they have helped create. Let’s show them just how much we care.

Please donate at either of these places:
http://savecubespacepdx.com/
https://cubespace.tofinoauctions.com/rentparty09/

For the back story: http://cubespacepdx.com/node/2012

On Friday, April 24, 2009, I saw Crazy Enough at Portland Center Stage.

I have to say that going to the theater is not unusual for me. I’ve been to all but one of the plays at PCS this season, including Christmas Carol. I also see two to three plays a year at Northwest Children’s Theater, at least one a year at Artists Repertory Theatre, the occaisional work at Miracle Theatre Group, some jaunts to the Oregon coast for small stage fun, shows in whatever city I’m traveling to, and season tickets to the opera in Seattle as well as the occasional PSU opera or Portland opera. Needless to say I not only like live performance but I also like the post-performance discussions.

Seems about time to try writing about it. Not just because it’s fun to hash out the details through criticism but because I may improve as a writer. So here come opinions, not just of the plays I see but maybe the museums I visit, the botanical gardens, the hikes. Who knows! Feel free to critique my critiquing.

The Guardian Critics’ advice on Critiquing

Job interviews are a necessary evil. Prep for them by reviewing answers to these three frequently asked interview questions. After that, Google “top interview questions” and prep some more. Most interview questions have a subtext. It helps to know the subtext so you can fully answer the question.

1. Where do you see yourself five years from now?
Subtext: How ambitious are you? This question is pretty straightforward, how you should answer it depends on what the job is, what the growth potential of the company is, and most of all: what is true for you.
Appropriate answers
“In a job similar to yours, where I’m supervising a team of bright, talented workers.”
“In a job that provides opportunities for me to realize the fullest potential of my creative skills and talents.”

2. Tell me about a challenge you resolved successfully.
Subtext: Aside from the fact that this isn’t actually a question, what your interviewer wants to know is how you solved a problem.
Appropriate answers
You need to rehearse this one. The most appropriate answer is one in which you state a challenge and your solution. The trick is to keep the problem statement neutral and spin the solution positively.

Bad Example
“The idiot Business Analyst couldn’t draft a requirements document to save his life. In massive frustration, I took to having my video camera with me at meetings so I could record his stupidity and try to make some sense of it.”

Good Example
“I needed to make sure I had complete requirements from all stakeholders prior to design development. I instituted a launch meeting for each new feature developed and recorded it on video.”

This particular question has a lot of cousins, like “Tell me about your most disappointing experience, Tell me how you overcame adversity in your life.” They’re called “stress questions” because they’re designed to trip you up. The guiding principle in answering them is: stay unemotional and look for the positive spin you can provide.

3. What are your weaknesses?
Subtext: What are you willing to say negative about yourself?
Appropriate answer: Pick a negative that the employer will see as a positive.
Examples: “I’m a workaholic. I’ve had to hire a dog-walker to care for my pet during the day.” Will the hiring manger see through that? Sure. It’s a stupid question, and it’s pretty easy to come up with an answer that will let the interview move on.

At some point in the interview, likely towards the end, you’ll get this question:
Do you have any questions for us?
Subtext: Do you give a hoot about us? Or are you just applying for every job that comes your way.
Wrong answers: “No”, or “What is your vacation policy?”
The best answer: Whatever questions arose as you researched the company. (You did research the company, right?)
Old favorites: What opportunities for growth are there in this position? Where do you think this company will be in five years? (Yeah, you can flip that one right back on them.) I take a notebook with me to job interviews and jot down questions that occur to me while we’re talking and hold them to the end so I know I’ll have SOME question to add.

Good luck, and happy hunting! What is your least or most favorite interview question? Post it in a comment!

I find the most beneficial part of running a user group happens long after the meeting has ended. It’s the time spent when I sit down at my computer to implement feedback I received or heard about someone else’s project that I knew was applicable to one of my own. There is one project in my life and most everyone else’s that is ongoing. My resume.

Over the years I have gained a great deal of feedback and tips on improving my resume. I wanted to share some of those here.

• Edit your resume for every job you apply for. Tailor it to the needs and keywords of the job posting.
• Create multiple formats. Word, PDF, Text only, are a few good ones to start with. Always submit in the format requested by the job posting. If none requested, I opt for PDF.
• Print it out. Look it over, make sure it prints correctly and quickly. Be sure to also print a copy in black and white, even though it may look snazzy in color and on a computer screen. If you land an interview, I assure you, it will get printed out and most often in black and white.
• Keep it down to one page. This is a general rule, some people have enough applicable experience to make 2 pages, but usually one page will work just fine.
• Don’t put your picture on your resume or any other personal information, such as race, gender, etc.
• Don’t put down previous salaries.

I am sure there are a million more, please comment and share your own tips.

Open Source Bridge is a conference that, at it’s most basic, is looking to start a conversation around the question of what it means to be an open source citizen. The format is going to be OSCON like, with multiple tracks, different speakers, and lots to learn. It’s also a summer conference, June 17–19 at the Oregon Convention Center, here in Portland. That said, one big difference is the price, $150 if you sign up before Mar 31 (and only $250 after Mar 31). So why do I bring this up on a critique blog?

Well many reasons, first off I’m involved and I would for you to be too.  At the heart of this convention are the people, everyone that gives a talk, everyone who volunteers, everyone who attends, were all in this together. At PDXCritique we have had many great conversations about many topics, and would love to see what would happen when these conversations become amplified in a much larger space with many more participants.

As I see things, these conversations could take many forms, from talks given with slides to interactions in the halls. In the end I am just very excited about the idea that they will happen. We are a wonderful collection of people that can make this conference very exciting. So I would love to see there.

Here are some more links for more info:

• All about Open Source Bridge
• Register to Attend
• How to propose a talk, and what has been submitted, hurry though things close Mar 31!!

Monday, February 23rd
7:00 pm to 9:00 pm
CubeSpace
622 SE Grand Ave.
Portland Oregon 97214

Sign up for a slot to show your stuff here »

Due to the Holidays and craziness that ensues with travel and family, we have opted to not have a Decemeber meeting of PDXCritique. Please stay tuned for information on our plans for January and beyond.