I don't know why you are being downvoted. My father was a cop, went through the academy when I was 15. I distinctly remember him explaining to me about how they are taught to lie to get people to cross their stories up.
Police lie all the time, but this is police _implying_ a lie. To me it (clearly?) read as if they were keeping their cards close to their chest, not saying either way.
Grouping humans into 16 categories is pseudo science. The idea that we have traits and tendencies is not, and these things help us understand our own biases if we choose.
I won't say it isn't possible that someone might struggle with this—it's quite subjective, obviously—but I do think it's unlikely that anyone with a general understanding of both volume and surface area would struggle here.
Even just comparing two consecutive iterations, I feel confident that any child who has learned the basic concepts would be able to reliably tell you which has more enclosed volume or surface area.
I will happily concede that the part you quoted could be quite unintuitive without the context of the article or the animation included in it. :)
I think Gabriel's Horn is a great explanation of how this is counter-intuitive[1]. This is a shape which you could fill with a finite amount of water, say a gallon. Yet it would take an infinite amount of paint to paint the surface. Of course, part of the reason it's counter-intuitive is that there is no 0-thickness paint that exists.
So outside of coworkers that have a hard time collaborating in general, is it a problem for others that their coworkers will not apply context? That has not been my experience.
I don't understand the question... If someone has a strong opinion, and they have arguments for their opinion, but don't recognize the significance of the context in which they've formed their opinions, they have blind spots they aren't aware of. Is that a problem? I dunno, that's up to you and your environment.
> Only software engineers pretend best practices exist outside of any useful context.
I am not seeing this issue with programmers in general or with my coworkers, with the exception of those who in general have a hard time collaborating with others.
So my question was/is if you discount the above exception are people seeing a problem with programmers/coworkers not taking context in to account? I have not noticed a wide spread issue and I am interested in how prevalent you, and others, perceive the issue to be.
Aren't these discussions the evidence? The fact that the author wrote a blog post and we are here discussing it. I might be missing the point of your question. This is everywhere around us in the development world. Anytime people compare react to htmx, redis to postgres, TDD vs BDD.
I'd like to point out I never called it a problem. I said that was a judgement call for you to make. We all have harmless biases.
But yeah, it can be a problem. If I have an engineer derailing my team because of his insistence for svelte, and can't read the room: ie can't take any of the context of the business, stack, domain, team, into his consideration, then yeah, it becomes a problem. Time is money
(svelte isn't a good example, it's not a best practice per se. s/svelte/TDD/)
> But yeah, it can be a problem. If I have an engineer derailing my team because of his insistence for svelte, and can't read the room: ie can't take any of the context of the business, stack, domain, team, into his consideration, then yeah, it becomes a problem. Time is money
I would describe this someone who does not know how to collaborate, maybe they don't know the balance they need between give and take, maybe they do not know how to format their ideas so they are understood by the group, maybe there is some fundamental misunderstanding. Since the tool of collaboration is not working for them, they reach for other tools to leverage and achieve their goals, like argument by authority via a convenient best practice.
The best practice/standard was not the issue, lack of context for the best practice was the the issue, the lack of collaboration or ability therein is the issue.
That's a good point, but there's probably a bit of nuance in there considering NPM serves a solution space to the entire spectrum of developers using a technology, and Wordpress to users in need of web content management features.
When I started CS decades ago, our student passwords for our server accounts were all similarly generated. They were given to us on a slip of paper, of course, and I still remember the two I was given over 20 years later. I was (naively) bummed when I didn't see this practice in the industry after graduation
And when the bulk of the page is the table, it is very obnoxious to click into the window to focus, (or unfocus an input), and suddenly you are whisked away to another page
