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


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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi