Skip to main content

The Wanton Destruction of a Nintendo Switch Joycon

A torn apart Nintendo Switch Joycon; Neon Blue, sits on a piece of paper beneath a laptop; the paper says

I am a Nintendo household. I have every console from childhood - Some of the very oldest ones were my father's - except the Virtual Boy. I still have my GameCube, Wii, Wii U, and now the Switch. 

When I received the Wii U with two games loaded onto it - Smash Bros and something called Splatoon, I wanted it for Smash Bros, but as a long time Smash Bros. player, it felt too odd to have my hands a foot away on the large, ungainly controller. Muscle memory was too strong.

Since Splatoon was a new IP, it took less trouble to get accustomed to the controls - And I fell in love with the entire colorful, post-apocalyptic aesthetic of squids dressing terribly and slinging paint around.

A few days ago, Nintendo Europe released a video showing off the Splatoon 3 edition Switch, and it is gorgeous. It looks more colorful than the actual game.

Wish I made enough money consistently to justify getting one of these.
Want to help with that? See here and share.


I'm not super sure when these new ones (P/G) were made. They definitely represent the color motif for Splatoon 2, which came out in 2017,  and the specs page say they were first available in Jan. of 2018 - but I can't imagine these particular ones were sitting in a box for 4 years, especially with how hard they were to find for a solid 2 years, and they're still the release price of 80$.

The most recent ('first available') ones I found on Amazon were Fortnite-Themed, from 2021, and an extra 20$. 

I can't imagine anything but the components were updated to prevent what's known as drift - When the joysticks register movement that allows whatever on the screen to move without user input. It was a mild annoyance in Animal Crossing, and I know it would be a big hindrance when Splatoon 3 comes out in September of 2022 where I play with the charger (long range sniper) often, and it requires precision that I often don't have.


The problematic JC was the left blue one that originally came with the system. Let's tear it down!

Nintendo Switch Neon Red and Neon Blue joycons sit on a piece of paper

I use this IGN video; I usually fix my own devices whenever possible, but I've wanted the Pink and Green ones ever since they were announced. I have a little toolkit I've used to remove hard drives and memory sticks from PCs.


There is no sound in this video.

 0:00 - 1:39: Me fruitlessly trying to unscrew with a pointtip that doesn't quite work

1:39 - 3:05 unscrewing with a 1.0

3:16 - broke the cables; This thing isn't working anymore. Couldn't get one of the screws out. We can still learn!

05:15 - Popped out the battery connector and the battery. Cause for celebration! 

05:47: Took out the top left trigger button.

07:11 - Detached the cable from the large trigger button

If you're following the IGN video, godbless, because that went out the window around 05:47. But at about 07:16 is where I would put a piece of cardstock to put pressure on the joystick to prevent drift.

There's a tiny crack in the back of the red one - Look at the tiny screw - as well as years of dirt and gunk where it connects to the console. 


Nintendo Switch Neon Red and Neon Blue joycons sit on a piece of paper; there's a crack in the top of the red one
Gunk omitted for your convenience.

I very rarely detach the controllers, so that was a surprise to me. I'm sure it's been dropped a few times on soft surfaces in the past 5 years, and I have a tendency to pull slightly downward as I play. I'll have to be careful not to do so with these new ones. 

Nintendo Switch Neon Blue joycon sits on a piece of paper. Tools are strewn about. The blue joycon is disassembled

Overall, the Joycon got pretty sorely obliterated. It was cool to see all the components that make up the buttons. I kept the battery and the problematic element itself, the control stick.

I hope they don't come in handy.


Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl