Strengths, weaknesses

[azurelunatic]

Strengths:

Good at troubleshooting, narrowing down to specific problem, good at reporting exact symptoms of problem.
Good at communication: explaining things to non-computer-users, getting information from them.
Good at keeping my cool in emergencies. (smoke in electronics class, bleeding kids)
Attention to detail.
Safety-conscious, ability to work to standards.
Technical knowledge of networking.

Weaknesses:

Harnessing the power of my procrastination.
Occasionally am too high-energy.
Occasionally am too laid-back.
(can we say, possibly bipolar?)

Comments

[sithjawa.livejournal.com]

The Virtues of a Programmer

[azurelunatic]

Thaaaaaaaaaaaaank you. :)

[azurelunatic]

Hm. So.

Arrogant -- I don't want to be associated with something that performs badly, so I would likely get all up on to make it work.

Occasionally I do comprehend things that I can't explain yet. I will try over and over to explain them; design documentation happens as a side effect.

[sithjawa.livejournal.com]

Hubris! ^.^

[juuro.livejournal.com]

I have been contaminated. I can not see the words "strengths" and "weaknesses" in close juxtaposition without a shudder at the thought of interminable SWOT analyses we had to do for management courses.

Attention to detail is good. However, being a customer representative who needs to maintain attention on the whole system, I sometimes worry that the programmer may devote too much attention to some detail that is fascinating and can be tweaked closer to perfection, when really effort would be needed at some unglamorous bit.

But your ability to work to standards should mitigate that.

[azurelunatic]

I am the sort of person who doesn't consider something working until it actually works, not just looks like it works.

And I can look at whole pictures, though I don't shift gears easily.