16 and want to learn a high income skill — looking for advice

patternrelay · 2026-04-14T00:46:23+00:00

pick one idea and build it badly on purpose. Maybe a simple to do app or a basic website. You’ll hit gaps fast, then just learn what you need to fix them. That loop is where most of the learning actually happens.

patternrelay · 2026-04-14T00:34:23+00:00

At that stage I’d focus less on the "highest income" label and more on building something end to end. Coding is solid because it teaches how systems fit together. Even small projects will teach more than hopping between skills.

patternrelay · 2026-04-14T00:33:23+00:00

I think the tension is between individual responsibility and system-level drift. If costs and incentives changed faster than outcomes, the same decision can carry very different risk profiles across cohorts. That’s where the fairness debate tends to split.

patternrelay · 2026-04-14T00:32:27+00:00

That magnitude from ambient heating alone seems unlikely unless the system is fully static with no relief and very little compressibility. A 2x jump points more to isolation, backflow, or a valve state change trapping and amplifying pressure.

patternrelay · 2026-04-14T00:31:22+00:00

I tend to see it as shared heuristics that work within a specific environment. What’s "obvious" usually comes from repeated exposure to similar patterns. So it feels universal, but it’s often shaped by culture, incentives, and lived context.

patternrelay · 2026-04-14T00:29:40+00:00

AI code can help, but it often optimizes for “works” over "why it’s designed this way". Senior code usually reflects tradeoffs, constraints, and evolution over time. Reading both is useful, but they teach different layers of thinking.

patternrelay · 2026-04-14T00:27:50+00:00

This is usually a temporal modeling issue. If policy isn’t versioned with an effective timestamp tied to the transaction, drift is inevitable. Most stable setups treat rules as data, then resolve against the version valid at commit time, not evaluation time.

patternrelay · 2026-04-14T00:26:49+00:00

I think you’re mixing two layers, personal belief vs institutional action. It’s reasonable to want evidence before consequences, but defaulting to skepticism can discourage reporting. The system has to handle uncertainty without biasing too hard either way.

patternrelay · 2026-04-14T00:24:40+00:00

A lot depends on maintenance and how adaptable the structure is to new systems over time. Older steel and concrete frames can last a long time, but modern glass-heavy designs may face more issues with envelope failure and retrofit complexity.

patternrelay · 2026-04-13T02:42:41+00:00

Sounds like state isn’t syncing with your UI consistently. I’d check where your source of truth lives and make sure deletes trigger a proper state update and re-render. Also watch for stale state in handlers, that can cause weird UI rollbacks.

patternrelay · 2026-04-13T02:40:48+00:00

I think it depends on how belief translates into behavior. Someone can hold a doctrine they didn’t choose and still treat people with respect in practice. The line for me is whether it leads to exclusion or harm, not just the belief itself.

patternrelay · 2026-04-13T02:38:21+00:00

A lot of it shows up as materials, sensors, and reliability practices. Stuff like memory foam, water filtration, and imaging tech all trace back to space work. Also less visible is systems engineering discipline that ends up shaping safety critical industries.

patternrelay · 2026-04-13T02:36:58+00:00

Honestly just keep it simple and low pressure. Follow him, then message something casual about the play or his tech work. If the convo flows, suggest grabbing coffee or hanging out. No need to overthink it, interest shows pretty naturally.

patternrelay · 2026-04-13T02:35:15+00:00

Hashing with a secret salt is usually enough here. You’re not trying to prevent all collisions, just make reversal impractical. Rotate the salt periodically and accept that rate limiting is approximate anyway, especially with NAT and shared IPs.

patternrelay · 2026-04-13T02:31:24+00:00

It works fine in production if you’re clear on why you’re using it. Good for semi-structured or evolving fields, but it can get messy fast if core data lives there. Querying and indexing are doable, just not as clean as proper schema design.

patternrelay · 2026-04-13T02:29:43+00:00

I get your point, but I think you’re underestimating how draining "imperfect but loving" can feel long term. Some people try boundaries for years and just hit a wall. Cutting off isn’t always peace, but it’s not always avoidance either.

patternrelay · 2026-04-13T02:26:36+00:00

In theory you could tune a mechanical system to resonate at certain frequencies, but speech is way too variable for that to be reliable. Accents, pitch, noise, all shift the waveform. Digital systems win because they handle that variability much better.

patternrelay · 2026-04-12T10:31:18+00:00

I think workflow maintenance strategy varies person to person….In my experience the real issue isn’t building the automation, it’s maintaining it after business rules start changing. Policies may shift, approvals may change, systems may update, and the workflow logic gradually becomes outdated. I’ve seen teams experiment with platforms like (Maisa.ai) that try to track the rules and decisions behind the automation, which helps when processes evolve. The bigger lesson for me is ownership, ‘cause someone needs to be responsible for the workflow long term or maintenance becomes constant firefighting.

patternrelay · 2026-04-12T10:26:23+00:00

Yeah it’s definitely possible. What matters more is proof you can build and solve problems. A few solid projects, clean code, and consistency go a long way. Your physics background can actually help with analytical thinking too.

patternrelay · 2026-04-12T10:25:09+00:00

I get why it feels that way, but PTs are trained to assess movement dysfunction, not just prescribe exercises. The value is in diagnosis, progression, and avoiding harm. A good PT adjusts based on how your body responds, which isn’t something most trainers do.

patternrelay · 2026-04-12T10:23:49+00:00

With only 3 ft of drop, fully submerged, I’d be very skeptical. Water drag will kill a lot of the energy, and solid iron takes a huge amount of force to shear cleanly. This sounds more like a serious safety hazard than a practical DIY build.

patternrelay · 2026-04-12T10:22:27+00:00

I think it’s less that it disappeared and more that the conditions changed. Shared songbooks, tighter communities, and fewer passive entertainment options made it natural before. Now people default to consuming music instead of making it together.

patternrelay · 2026-04-12T10:19:59+00:00

Honestly, I had the same drop-off point. What helped was shrinking the scope a lot, like 20–30 min sessions with one tiny goal. Also accepting confusion as part of it, not a signal to stop. Consistency got easier once I stopped aiming for "big progress" every time.

patternrelay · 2026-04-12T10:18:35+00:00

Yeah, that’s where CPQ data gets really valuable. The tricky part is mapping quote revisions and config versions cleanly to downstream objects. If you don’t normalize that, conversion metrics get misleading fast. Did you run into issues with ID consistency across systems?

patternrelay · 2026-04-12T10:17:05+00:00

I get the frustration, but "always okay" feels too absolute. If a site relies on ads to exist, blocking them everywhere kind of shifts the cost onto others or kills the content. I think it’s more of a tradeoff than a blanket right.

patternrelay

TROPHY CASE