Live data from Hacker News

Dev Compass – Programming Philosophy Quiz

treeform.github.io

61–70 of 115 posts

Re: Dev Compass – Programming Philosophy Quiz

#61
Yeah I like the idea but the questions need serious work. I only got through a few before giving up because they're ambiguous or I want to say yes to multiple things. E.g. the question about comments - they're basically all true. Or the question about architecture - it's basically impossible to answer.

Re: Dev Compass – Programming Philosophy Quiz

#62
I'm not sure these are independent variables. I mostly care about concrete code or abstractions as a way to make the code more human friendly.

And isn't being human friendly while building performant enough solutions the whole point of code? If we didn't need the humans, we'd do machine code.

Re: Dev Compass – Programming Philosophy Quiz

#64

-11 concrete, +14 human friendly lol. > "You value clarity and directness in code. You prefer explicit, step-by-step solutions that are easy to understand and debug, even if they require more lines of code" Sounds about right.

Almost exactly the same score :)

Re: Dev Compass – Programming Philosophy Quiz

#66
post #53

I suspect this test gives central values to many test-takers because the internal consistency of the questions has not been verified. Anyone can come up with ten questions and claim "these measure a programmer's fondness for abstraction". Unfortunately, we cannot verify this claim. What we can do is check statistically if the answers to the ten questions correlate strongly enough that we think they measure the same t…

> I suspect this test gives central values to many test-takers because the internal consistency of the questions has not been verified.

Do you prefer to use:

1. Capital letters

2. Lower-case letters

3. Numbers

4. The characters required for the text I am writing to be correct and legible

Re: Dev Compass – Programming Philosophy Quiz

#68
Could someone help me understand the difference between:

    > Measure first, optimize bottlenecks only
And

    > Profile and optimize the critical path
The second seems to be a re-statement of the first?

Profiling is Measuring, and the "critical path" is the bottleneck.

Re: Dev Compass – Programming Philosophy Quiz

#69
post #10

I landed right in the middle - -1, -2. Which seems weird because I’m very opinionated about a lot of this stuff. I like a lot of the questions but a lot of my answers felt like I was arbitrarily picking something. That’s probably why. Eg for testing, do I want “whatever finds bugs most effectively” or “property based testing”? Well, property based testing is usually the most time efficient way to find bugs. So, yes b…

Ok. But then I took it 4 more times. I tried to maximize in any direction, and always stayed within the bullseye center-right. One time I was more computer, but I never made it out of the center 20% radius.

Maybe the message is that none of us are extremists, because we care? I like it

Re: Dev Compass – Programming Philosophy Quiz

#70
post #68

Could someone help me understand the difference between: > Measure first, optimize bottlenecks only And > Profile and optimize the critical path The second seems to be a re-statement of the first? Profiling is Measuring, and the "critical path" is the bottleneck.

I was also thinking between these two. Still see the diffrence: I guess "critical path" is single, bottlenecks are multiple.
Post reply on HN