Skip to main content

I took the scientific personality test

This is what the test results are:

Your result for The LONG Scientific Personality Test ...
ESTJ-The Supervisor
You scored 91% I to E, 71% N to S, 86% F to T, and 5% J to P!

Your type is known as the supervisor, as you are not hesitant to give your stamp of approval on others - or tell them how they are lacking if they are. You are surprised when others don't seem grateful that you have set them straight. Your type also belongs to the larger group called guardians. Experience is what matters to you, not experimentation or conjecture. You often take a lead role in the many groups and organizations you belong to. You worry a great deal about society falling apart, morality degrading, and what the world is coming to. You share your personality type with 10% of the population.
As a romantic partner, you communicate very clearly your strong opinions so your partner always knows where they stand. You are dependable, responsible, and rock solid. You can be rather infexible about giving up any control and insist on keeping a schedule, although you have great energy and enthusiam for planned adventures. You have difficulty seeing other's points of view and your biggest downfall in a relationship is dismissing your partner's feelings as illogical. You feel most appreciated for being trustworthy, efficient, and productive. You wish to be thanked tangibly for the ways you keep your lives on track.
Your group summary: Guardians (SJ)
Your Type Summary: ESTJ
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …