Vocation-specific MBTI test for programmers

[Ghost of the dead horse]

I know programming well so I thought to loan the MBTI speak for a programming test. Let me give you an example.

How is this

int main() {
Editor ed();
ed.interactive();
return 0;
}

a better c++ main than

int main() {
Editor ed();
return 0;
}

or if not, which one would you prefer, having a short backstory of what the function does?

So, the questionaire would be full of these kinds of questions. And analysis of it would give your programming style. I could include c++, c, java, assembly x86 & c64, scheme, general lisp, python, javascript, php, and others, being a veteran in IT.

Programmers, what say you?

Non-programmers, what say ye?

 

[Bush]

Programmer. This is a great idea.

I can see it now. "Does the following make you anxious, or does it make you feel motivated?

@P=split//,".URRUU\c8R";@d=split//,"\nrekcah xinU / lreP rehtona tsuJ";sub p{
@p{"r$p","u$p"}=(P,P);pipe"r$p","u$p";++$p;($q*=2)+=$f=!fork;map{$P=$P[$f^ord
($p{$_})&6];$p{$_}=/ ^$P/ix?$P:close$_}keys%p}p;p;p;p;p;map{$p{$_}=~/^[P.]/&&
close$_}%p;wait until$?;map{/^r/&&<$_>}%p;$_=$d[$q];sleep rand(2)if/\S/;print"

I don't understand the poll, though, at least in relation to the OP.

 

[Poki]

Programmer. This is a great idea.

I can see it now. "Does the following make you anxious, or does it make you feel motivated?

@P=split//,".URRUU\c8R";@d=split//,"\nrekcah xinU / lreP rehtona tsuJ";sub p{
@p{"r$p","u$p"}=(P,P);pipe"r$p","u$p";++$p;($q*=2)+=$f=!fork;map{$P=$P[$f^ord
($p{$_})&6];$p{$_}=/ ^$P/ix?$P:close$_}keys%p}p;p;p;p;p;map{$p{$_}=~/^[P.]/&&
close$_}%p;wait until$?;map{/^r/&&<$_>}%p;$_=$d[$q];sleep rand(2)if/\S/;print"

I don't understand the poll, though, at least in relation to the OP.

Reminds me of regular expression spaghetti mess

 

[Poki]

I know programming well so I thought to loan the MBTI speak for a programming test. Let me give you an example.

How is this



a better c++ main than



or if not, which one would you prefer, having a short backstory of what the function does?

So, the questionaire would be full of these kinds of questions. And analysis of it would give your programming style. I could include c++, c, java, assembly x86 & c64, scheme, general lisp, python, javascript, php, and others, being a veteran in IT.

Programmers, what say you?

Non-programmers, what say ye?

That second one makes me cringe.

 

[Ghost of the dead horse]

I don't understand the poll, though, at least in relation to the OP.

It needs to be replaced

Edit: Shit, there's no poll edit tool

 

[Ghost of the dead horse]

That second one makes me cringe.

Putting all of the big object's functionality to it's constructor doesn't fit my idea of OO paradigm either

 

[Poki]

Putting all of the big object's functionality to it's constructor doesn't fit my idea of OO paradigm either

No, it may works, but where is the ability to expand, grow, and improve. Its like saying, I created a ball and they will all bounce THIS way ALL the time. If you dont like what it does then tough shit, you want a ball that rolls before it bounces then go make your own.

As opposed to here is a ball and it CAN do all these things. This is how to make it do these things. Have fun, i gotta run.

 

[Bush]

Changed up the poll as per Unit's request.

I like the general idea of testing programming style. Could also have questions on "how would you prefer to implement the following pseudocode" etc., some questions that indirectly test whether you like working with an IDE, etc. You know more than I do on that stuff.


For the question at hand, in most cases I can think of, I prefer the second. If Editor.interactive() needs to be called every time an Editor is instantiated else things would fuck up, or if not "setting Editor to interactive (?)" is extremely rare, I'd call Editor.interactive() within the constructor. In the latter case, I'd also have.. uhm, Editor.notInteractive()..?

And just think if you needed to call 10+ Editor.interactive()-like functions every time you instantiated an Editor. That'd be a damn mess in code. I prefer my code to be simple and to the point, though also with comments.

 

[Ghost of the dead horse]

Just finished refactoring some code of an experimental miniature software synthetizer, and I find the end result thoroughly pleasant:



It's a sound and music editor. It's input is from user, and save/load features from disk. No command line input at the moment, but I'll add there a functionality to run it without interactive mode from command line to convert tracks to music.

The editor is the creator and owner (CO) of the synth and sheetmusic class. Synth is CO of channels & wav, channels are the owner of sound etc. Everything is neatly organized. So, this is an example of what is highly appealing to me

 

[Ghost of the dead horse]

Calling all programmers. Tell me your ideas of worthwhile programming habits to test. I haven't created a public test before but this is the first, I'm putting hours to it, so tell me your ideas and how to arrange for maximum amount of ideas to be gathered for this project.

Initial ideas:
-Adherence to best practices in Object Orientated paradigm
-Idealism in programming vs pragmatism
-Software vs people centered
-Intererst in programming competitions
-Intereest in business projects
-Interest in startups
-Interest in academia