Your instructions are completely correct, but it might make more sense to look at the bands of metal rather than the insulator between them.
TRS stands for "Tip, Ring, Sleeve", referring to the 3 contacts on a TRS jack - one for the left channel, one for right and one for ground. TRRS as you might guess has an extra ring to provide a contact for the microphone as well. So you're looking for the metal tip, two rings of metal and then the metal sleeve.
Yeah, I think you have to acknowledge it or they'll feel (at best) incredibly awkward the whole time. Don't make a big deal of it though - say you're "sorry you ghosted her and no-one deserves that. If she wants to talk about it then you're willing, but otherwise won't mention it again".
I bought the JSAUX dock (from Amazon). Has been really good. It's a fair bit cheaper than the official one and there are a load of reports.of the official one having issues.
One more note on learning Rust: what Rust does is front-load the pain. If you write something in another low-level "direct control of memory" language you can often get something going much more easily than Rust because you don't have to "fight the borrow checker" - it'll just let you do what you want. In Rust, you need to learn how all the ownership stuff works and what types to use to keep the compiler happy.
But then as your project grows, or does a more unusual thing, or is just handed over to someone who didn't know the original design idea, Rust begins to shine more and more. Your C/C++/whatever program might start randomly crashing because there's a case where your pointer arithmetic doesn't work, or it has a security hole because it's possible to make a buffer overrun. But in Rust, the compiler has already made you prove that none of that is possible in your program.
So you pay a cost at the start (both at the start of learning, and at the start of getting your program going) but then over time Rust gives you a good return on that investment.
Context: I am an embedded software engineer. I write a lot of low level code that runs on microprocessors or in OS kernels, as well as networking applications and other things. I write a lot of C, I write some Rust, I write Elixir if I possibly can, I write a lot of Python (I hate C++ with a passion).
I don't think you want Rust. Python is unbeatable on "idea to deployment" speed. Python's downsides:
Painful packaging/distribution if you want to get a load of people who don't have Python installed to run your thing (e.g the GUI program we currently maintain for talking to our hardware)
Performance under some circumstances. There are some things that are not quick in Python. They're not always the things you expect because Python actually drops down to C modules for a lot of the number crunching that you might do. E.g. for ML you are basically using Python to plug a load of bits of fast C code together
Rust is good when you need at least one of:
High speed
Control over use of memory
Low level systems programming (drivers etc.)
Can't cope with a Garbage Collector
Compiling to a microcontroller
If you're doing one of those and so have become expert in Rust, then it is actually excellent for a lot of other things. E.g. you might build your data processor in it, and then distribution is easy because it's just a single binary.
One option you might look at is Go. You get a lot of performance, you get good parallelism if you need it, it's designed to be easy to learn, and it also compiles programs to a single binary for easy distribution.
Similarly I lose immersion when I'm going into a corner and I struggle to see the car on my inside. That's why I want to try VR.
I don't play with a shifter, just paddles on the wheel (driving F4 in iracing), so I don't think I'd have any trouble with where the controls are. Maybe the Apple Vision Pro will end up being the best racing headset though and solve your problem.
Black Skylands. A friend gifted me a copy on steam after he had a transaction error and got two copies. Thought it might be fun for a few hours but I've been obsessed.
It's an open world exploring game where you've got an airship and go from island to island, and it's a top down twin stick shooter. The mobility is really enjoyable with the grappling hook, the combat is fun with interesting weapons, tech and upgrades and you have an airship!
Joyhood Carrying Case Compatible with Steam Deck, Portable Travel Carry Case, Hard Shell Storage Bag Fits Steam Deck Console with TPU Soft Cover, Gifts for Men (Slim) https://amzn.eu/d/fj6lQNS
Like the sibling comment it feels the opposite way round to me. The Switch feels like a child's toy - light, small and not wildly comfortable to hold for a long period of time. The Deck feels much more ergonomic and solid to hold in my hands - I still enjoy the feeling of just picking it up (had it for 7 months) because it just feels like it fits.
Some of this is because I have big hands and the Switch obviously has to work for kids hands and the Switch being lighter is actually better for longer sessions but when I got back to the Switch now it feels cheap and flimsy.
Yeah, it can and should be a warning to studio heads, but as game consumers we absolutely should raise our expectations (and stop buying micro transaction crap). There are plenty of big studios with money who could buy the licence and spend years making the game, but those studios belong to the big publishers who optimise for profit not for game quality.
Your instructions are completely correct, but it might make more sense to look at the bands of metal rather than the insulator between them.
TRS stands for "Tip, Ring, Sleeve", referring to the 3 contacts on a TRS jack - one for the left channel, one for right and one for ground. TRRS as you might guess has an extra ring to provide a contact for the microphone as well. So you're looking for the metal tip, two rings of metal and then the metal sleeve.