design and debugging (for ENTJ's)
Feb. 8th, 2022 04:29 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kradeelavcame to the recent realization that my methodology for design and debugging are pretty much two sides to the same coin. (I say "ENTJ's lovingly and a bit toung-in-cheek here; my girlfriend, dad (small business owner), boss, and several grandbosses all most assuredly share a similar cluster of traits there.)
when debugging, ie being the general stand-in tech support for the family as a whole - my first two actions are to have them turn off/on the machine (so they feel immediately useful; people who are already on edge of being irritated at the thing being broken tend to be less annoyed in general if they're occupied), and to check if the platform is down on downdetector, while explaining to them what I'm doing. these types are no dummies - they may hate computers (and are frequent PEBACK offenders), but they think strategically and systematically. A simple rule-of-elimination process explained *and executed* to them will make sense, and give an immense amount of trust for when you're called in next time.
trust - I've found, is genuine gold for these types. most IT/design horror stories, I personally feel stem from a lack of trust between the suits and the developer/designer; you can't take risks if you haven't proven yourself to the suits, you gotta earn your stripes in their eyes. but when you do? shocking amount of leeway allowed.
when designing (or more accurately these days for me, being the "fixer") - again, similar process. ENTJ/suit-type is annoyed at a design, I'm called in to debug the process of why it's not working (not solving their problem), when is it needed (yesterday, always yesterday). other than the new design itself, the most requested ask is "explain why you think the new design is better" *so that way they can justify it to their superiors*. It's not questioning you, the designer on whether you're good or not (they wouldn't be asking you to fix the problem if they thought otherwise. ENTJ/suit types compliment you by interaction). It's that systematic thinking again, and how they can make both you and themselves look good to el jefe, numero uno, the big daddy.
it is fascinating to see when different systems or workflows work for other ones.
when debugging, ie being the general stand-in tech support for the family as a whole - my first two actions are to have them turn off/on the machine (so they feel immediately useful; people who are already on edge of being irritated at the thing being broken tend to be less annoyed in general if they're occupied), and to check if the platform is down on downdetector, while explaining to them what I'm doing. these types are no dummies - they may hate computers (and are frequent PEBACK offenders), but they think strategically and systematically. A simple rule-of-elimination process explained *and executed* to them will make sense, and give an immense amount of trust for when you're called in next time.
trust - I've found, is genuine gold for these types. most IT/design horror stories, I personally feel stem from a lack of trust between the suits and the developer/designer; you can't take risks if you haven't proven yourself to the suits, you gotta earn your stripes in their eyes. but when you do? shocking amount of leeway allowed.
when designing (or more accurately these days for me, being the "fixer") - again, similar process. ENTJ/suit-type is annoyed at a design, I'm called in to debug the process of why it's not working (not solving their problem), when is it needed (yesterday, always yesterday). other than the new design itself, the most requested ask is "explain why you think the new design is better" *so that way they can justify it to their superiors*. It's not questioning you, the designer on whether you're good or not (they wouldn't be asking you to fix the problem if they thought otherwise. ENTJ/suit types compliment you by interaction). It's that systematic thinking again, and how they can make both you and themselves look good to el jefe, numero uno, the big daddy.
it is fascinating to see when different systems or workflows work for other ones.
