u/Desperate-Piccolo420

Why did they add this as next in step option after you select face.

Why did they add this as next in step option after you select face.

Actually why was it added.

It's a pain in the ass coming from create, plane, mirror, select bodies and miss that it's broke habit.

Happened 2023/24/25, still annoying as fuck.

It's the interweb lemme QQ.

u/Desperate-Piccolo420 — 3 days ago
▲ 5 r/PsychologyTalk+2 crossposts

I’m trying to find the right cognitive science framing for a certain type of person.

Not asking for a diagnosis. Not asking Reddit to play psychiatrist. I’m looking for frameworks, research terms, or models that explain the pattern.

The contradiction is this:

This person can be extremely capable inside complex real-world systems, but inconsistent with basic linear execution.

They can understand mechanical systems, business pressure, money, timelines, customer expectations, design constraints, social dynamics, workflow failures, and practical execution all at once. They notice bottlenecks, missing responsibility, bad incentives, technical debt, weak accountability, and hidden failure points faster than most people around them.

But simple task lists, repetitive admin work, routine scheduling, paperwork, and “just do the next obvious thing” can be weirdly difficult.

From the outside, this can look like laziness, avoidance, arrogance, or overthinking. But internally, it seems more like they are trying to map the whole system before acting.

They don’t want to solve the visible problem if the visible problem is only a symptom. They are looking for the root constraint, the real sequence, the cleanest path, and the least wasteful way to solve it without creating ten more problems later.

Once the structure becomes clear, they can execute hard and fast. Until then, they may look stuck.

That’s the part I’m trying to understand.

The material itself almost doesn’t seem to matter. If information can be translated into a structure this person can actually consume, they can go from looking completely lost to understanding it at a very high level almost immediately.

That is what people seem to misread.

They see the first stage and assume incompetence. They don’t see that the failure is often in the format, not the person.

Give them disconnected instructions, vague authority, bad documentation, fake process, or a checklist with no visible system behind it, and they may look like an idiot to it.

But give them the underlying logic, the constraints, the purpose, the failure modes, and how the parts relate, and they can suddenly operate at a very high level.

It is not that they cannot learn.

It is that they do not absorb information well when it is presented as isolated tasks with no meaningful structure. Once the information is connected to a system, it becomes usable.

That creates a weird contradiction from the outside:

They may fail at a simple explanation but thrive inside a complex system.

They may ignore a basic instruction but understand the entire process once the real reason behind it is shown.

They may look slow when the material is fragmented, then become faster than everyone once the pattern snaps into place.

They may seem undisciplined in routine work but highly disciplined in high-complexity, high-pressure, self-directed work.

They may appear unmotivated until the problem becomes real enough, complex enough, or urgent enough to fully engage them.

This is not “lazy” in the normal sense, because they will work themselves into the ground when the problem matters.

It is not “stupid,” because they can integrate complex variables quickly.

It is not “just procrastination,” because the delay often comes from too much context, not too little.

It is not “lack of responsibility,” because they often become overloaded precisely because they are carrying too much responsibility without matching authority.

It is not “lack of discipline,” at least not cleanly, because they can show extreme discipline when the work has meaningful structure.

It is also not simple giftedness, because there are real executive-function costs.

The background probably matters.

They struggled with traditional school structure and attention consistency, but became deeply absorbed in competitive games, online systems, mechanics, scripting, forums, CAD/design, fabrication, and practical problem-solving. A lot of their skill came from obsession, failure, pattern recognition, and having to reverse-engineer systems without formal instruction.

They seem especially strong at:

  • finding system constraints
  • predicting failure paths
  • connecting technical and human problems
  • identifying when a process is fake structure instead of real structure
  • spotting when authority, responsibility, and accountability are misaligned
  • building complete solutions instead of surface fixes
  • learning very quickly once the structure behind the information is visible

They seem especially vulnerable to:

  • chaotic environments
  • vague authority
  • emotional pressure
  • poor accountability from others
  • repetitive admin work
  • disconnected instructions
  • being expected to execute without control over the system
  • burnout from becoming the person who remembers everything

The strongest version of the question is this:

What kind of cognition requires context, structure, and system logic before information becomes accessible?

Is this systems thinking? ADHD-style executive dysfunction with high pattern recognition? Compensatory cognition? Trauma-adapted environmental scanning? Divergent thinking? Predictive processing? Cognitive load mismatch? Giftedness with weak task initiation? Complex problem-solving ability paired with poor routine regulation?

I’m not trying to romanticize dysfunction. The costs are real. Burnout, inconsistency, frustration, and social misunderstanding are part of it.

I’m also not trying to excuse bad behavior. I’m trying to understand the mechanism.

How can someone be genuinely strong at complex, high-context problem solving while still struggling with basic consistency, routine, and linear task execution?

I've spent a lot of time attempting to capture the truth of this thing, probably more effort than most have crying about life not being fair.

**Edited in response to u/EvenaDemon **
This person does not seem like one clean category.

They show pieces that could be interpreted through autism, ADHD, anxiety, trauma adaptation, obsessive patterning, giftedness, executive dysfunction, oppositional behavior, burnout, or even personality-style conflict depending on who is observing and what they want to emphasize.

But none of those alone explain the whole thing.

The person is not just “autistic.”

Not just “ADHD.”

Not just “anxious.”

Not just “trauma-adapted.”

Not just “gifted.”

Not just “difficult.”

It feels more like a full-spectrum cognitive adaptation.

A person shaped by natural wiring, chaotic environments, self-directed obsession, mechanical problem solving, games, social pressure, failure exposure, and repeated responsibility without clean authority.

So they may display traits that resemble multiple diagnostic categories, but the core mechanism seems bigger than any one of them:

They interpret everything through structure, constraint, consequence, and system failure.

That means they can look disordered in simple environments and highly capable in complex ones.

They can look irrational when the context is missing, then suddenly become extremely rational once the full system is visible.

So I’m less interested in which DSM box can technically claim pieces of the behavior.

I’m interested in what cognitive model explains a person who seems to span multiple categories because the adaptation itself is broader than the labels.

reddit.com
u/Desperate-Piccolo420 — 10 days ago

alt+shift
My dumbass: "ok bring back that front vent membrane info. im quantizing it."

GPT GOES BRRRRT.

(i’m pulling this back into a usable quantified spec instead of the usual “air goes somewhere, vibes happen” engineering folklore.)

Thought for 6s

(front vent membrane info, quantified)

use this as the working spec:

item spec
vent type supported eptfe membrane sheet
location long front cabinet intake / exhaust slot
slot length ~54.7 in
membrane support perforated metal / stainless mesh backing
sealing epdm or silicone perimeter gasket
clamping bolted flange frame, membrane captured only at perimeter
do not do stretch membrane, leave unsupported, glue as only retention

airflow estimate by clear slot height:

clear height open face area rough membrane airflow capacity
1.00 in 54.7 in² ~208 cfm
1.25 in 68.4 in² ~260 cfm
1.50 in 82.1 in² ~312 cfm
1.75 in 95.7 in² ~364 cfm
2.00 in 109.4 in² ~416 cfm

rule of thumb you were landing on:

for 4 × 120mm fans, assume real useful system flow around:

fan setup practical flow
quiet / restricted 120–160 cfm
normal cabinet airflow 160–220 cfm
aggressive airflow 220–280 cfm

so the front membrane slot should be:

minimum: 1.25" clear height
better: 1.5" clear height
ideal / low restriction: 2.0" clear height

because apparently air also wants dignity and cross-sectional area, the entitled bastard.

stack-up concept:

outside → louver/perf guard → air gap → eptfe membrane → support mesh/perf plate → gasketed clamp frame → cabinet wall

important quantized design note:

do not count the whole decorative opening. count only the actual free membrane area:

actual airflow area = slot length × clear height × open-area factor

example:

54.7" × 1.5" = 82.05 in²

if support mesh/perf is 60% open, effective area becomes:

82.05 × 0.60 = 49.23 in²

so if you use heavy perforated guard, bump height toward 2" to avoid choking the system like a genius with a zip tie addiction.

my clean call:

make the front membrane opening:

54.7" long × 1.5" clear minimum, with a design allowance to open to 2.0" if the perf/louver stack is restrictive.

that gives enough intake/exhaust area for the electronics cabinet without turning the fans into tiny screaming politicians.

110%?

Thought for a second

(yes, 110% as a working design direction.)

(the only thing not 110% is the exact airflow until we know the actual membrane permeability and fan curve static pressure, because manufacturers love hiding useful data behind marketing confetti.)

lock this in:

front vent membrane target

  • 54.7" long
  • 1.5" clear height minimum
  • 2.0" clear height preferred
  • supported membrane, not free-spanning
  • 60%+ open backing/perf
  • gasketed clamp frame
  • serviceable/removable membrane cassette

hard quantized version:

clear opening gross area at 60% support open area
54.7" × 1.5" 82.05 in² 49.23 in²
54.7" × 2.0" 109.4 in² 65.64 in²

my actual recommendation:

(standardize the cutout around 54.7" × 2.0", then visually reduce/control it with the clamp frame if needed.)

(that gives airflow margin, membrane area, less fan strain, and a cleaner future-proof spec. designing it at 1.5" works, but 2.0" stops future you from inventing new curse words when the membrane/perf stack restricts more than expected.)

u/Desperate-Piccolo420 — 10 days ago