Sunday 3 July 2022

Over Achieving as a Trauma response - My experience.

It hit me today that I have been an over-achiever, but there was no requirement for that quality as a human being to begin with. 

This is also nobody's fault because I remember faint instances of friends or family telling me to slow down. The frailty of those voices was attributed to a pair of (mostly in-ear, noise cancelling) earphones that was on me 70-80% of the time.


This thought was triggered two days after dusting off my CV for the first time in a while.


I realised that my struggle was balancing relevancy, accuracy & conciseness to fit a targeted position.


Once or twice, I felt as if the content would be mistaken for exaggeration and put to task to prove the narratives therein - this means technical exams during job applications, which tend to favour professional exam takers & not the real problem solvers. Problem solving, in my humble opinion, is more than just taking a one time evaluation. I had these moments when I though that my own CV was too much for the position, and that maybe I needed to downplay some of my achievements by omitting them from the CV. I now comprehend this experience to be what is called imposter syndrome.


I do remember sharing with friends and colleagues about this "imposter syndrome". We shared some TED talk links on the concept. My default response was to identify the signs in others - especially junior colleagues who would, by natural design, be at risk of experiencing it's reality and how it in turn affects me or my deliverables as a team member or friend. This group happened to be entry level engineers or more popularly - "Junior Devs". I imagined that I was effective at pointing out the imposter syndrome in team members who happened to largely determine my own deliverables.


Knowing about imposter syndrome was just but another dataset in my mind. A dataset I had to pay attention to so that my delivery was solid. Seeing how I lived in the reality of this phenomenal, would be comprehension and, ironically, humility.


The situation that kicked off my comprehension was when a family member sent me a youtube link about imposter syndrome.

I remember telling myself that I don't experience it, because I am well aware of what imposter syndrome is. "Why would I click the link? I was the guy who used to send others those links." - So my mind went.


The idea of putting myself under self scrutiny with the purpose of identifying any hint of imposter syndrome & how it affects me & others seemed like a crime against myself. The truth is, the universe had brought this concept to me because I was in denial about my own imposter syndrome all this time. I did not even realise how much imposter syndrome affected the relationships I had with others. I had risen my bar for relationships to an unrealistic set of expectations. A friend who I respected once told me that I should stop living in a bubble. The bubble I was living in was that of a version of me that was always possible in the future after I had achieved certain targets in life. I never accepted, nor appreciated my current unimproved version of myself. I never felt good enough, not in my career, not as a friend, not as a husband, not even as a father. To be honest, my palms were always sweaty and had constant butterflies in my stomach whenever my self worth in any form was externally or internally under scrutiny. The sad part was that I got quite excellent at masking this terrible experience by being a funny guy. I became excellent at small talk. I became an excellent manipulator so that I would divert any conversations about my self worth to other topics. Looking back, it was a terrible existence that no human should be made to live.


Updating your CV has the potential to get you into a mental space where you’re trying to match up expectations set by someone else who holds one key to your next pay check or career move.

No wonder, the temptations to lie, withhold relevant information, use intentional ambiguity to your advantage, can be part of the CV editing experience.

Would one be wrong to assume that the experience is usually more excruciating during oral interviews?
This means that you’re always matching yourself to a pre-defined role. Others always seem to need to see more achievements from you. More trophies. More certificates. More degrees. Few are willing to grow with you, more want to see you already grown up. Many want the finished product, not the product in the making. This is just the reality of the job market, and quite frankly the human experience in general.


This is by no means an online rant. 

It’s a call for awareness about general mental health issues attributed to the very nature of how we work & relate with one another. 


Imposter syndrome is a trauma response to constantly evolving (job/life) requirements. 


Think of someone who lost a job as a result of process automation, job role replaced by a computer (software, hardware, robot and recently - A.I Robots) & the impact on their view of self worth. 


Think of innovations such as Safaricom’s Zuri and it’s future impact on the customer care job market & people therein. 


I realised that I had based my self worth on employability & my ability to generate income. 


Unfortunately, the ideal skillset always seem to be out of reach. This feeling and state of constant need to improve to be competitive never left me since the first version of my CV. I can’t imagine what it’s like for others, but if the experience is anything like mine, I’d like to say it here that you’re not alone. Let’s face it, it’s a pretty predatory world out there where you have to either grow teeth, or be eaten.


That race for constant improvement came to a screeching halt in 2021 with what I now understand to have been the height of a mental breakdown. This shook all my relationships from family members, colleagues, friends & acquaintances. I had experienced depression for a very long time. The first time I felt the need to look into the issue was about 10 years ago when I took myself into a psychiatrist. I figured I couldn’t afford the professional fees since I was just starting my career and the pay at the time wasn’t enough for me to keep seeing a psychiatrist. I turned into good guy Dr. Google and over the years self medicated with anything google promised would work. I can say that among the many things I tried, mindfulness or (self) awareness and meditation seem to be a good solution. It helps you reconnect with your very being and remember what really matters - you.


When you wake up and breathe, that’s basically it - it’s another day you won the lotto of life. Just like you won that other lotto of a sperm cell among many to be able to have been born to read this. You’re living & everything else is extra. You’re also complete and enough as a human being. You really don’t need anyone to validate the idea of who you tell yourself to be.

When you can’t keep up with demands (explicit or implicit), you start falling off. I know this because I did & I would like to share this here for anyone who mirrors my own experience.


There is no requirement to over-achieve. There is no requirement to be perfect. Don’t even bother.


Here’s a thought provoking cartoon - "Happiness - by Steve Cutts" that I think goes well with this post. 






Saturday 8 November 2014

Debricking TL-MR3220 3G/4G Wireless N Router

There are many methods to achieve this, and you can check the OpenWrt Debricking guide for the other methods. However this post is a combination of all the bits of information and data I collected and hopefully it will quickly help someone out there with this particular problem.


Pre-requisites


  1. CA-42, DKU-5 or similar containing the PL-2303 chip and the drivers. This is for creating a USB-to-UART serial adapter. Image below
    Nokia CA-24 Cable. Make sure you get the drivers.
    Shouldn't cost more than KES 500
  2. 4.7k resistor (With MR3220 v1.2 and CA-42 you do not need any resistor) Mine was v2
  3. 2 Insulated thin wires about 6 cm long 
  4. TCP cable - crossover.
  5. Multimeter (or something to measure current continuity like battery and led)
  6. Putty/ You can download it from here
  7. TFTP server. You can download it from here
  8. Binary of the factory firmware for the router. Download that from the TP-link official site
  9. Soldering iron with a very thin tip.
  10. Solder
  11. Transparent adhesive tape - sellotape
  12. Screw driver, cutting tools (razor, wire stripper) and any other supporting tools that you may feel will make your job easier like protective gear.
  13. A positive attitude and patience if you've never done this before. 


Steps to follow

1. Open your router and solder joints TP18 to TP38 and TP28 to TP48 using the thin wires (mine were black) as illustrated below;



2. Prepare your USB-to-UART serial adapter. You can use these detailed instructions here to prepare the USB-to-UART serial adapter, or you can just use my instructions here;

- Cut your CA-42 or DKU-5 cable as follows - this enables you to map the pins to the wires; In my case, I had very different colors and you may as well not have the same colors as the image below. The most important thing to know is which wire goes to which pin. Use a multi-meter to measure the continuity of the pins to the wires.



- Map pins to the colors. The pinout looks like this; Your wires of interest are pins 4,6,7 and 8. Ignore the rest of the wires.

Copyright 2008 Timothy Small, Creative Commons licensed.
In my case, the pin-wire colour was as follows;

PIN 4 -> GREEN (3.3v out)
PIN 6 -> WHITE (RS232 - 3v phone RX Data
PIN 7 -> BLUE (RS232 - 3v phone TX Data
PIN 8 -> BLACK (RS232 - 3v GND

- identify where your serial joints are on the router. Mine were as below;

Courtesy OpenWrt.org


- Solder the CA-42 or DKU-5 to the serial as follows. Remember the exact pin-color mapping from previous section;


- Solder the 4.7k resistor between the first and last joint pint as follows; (you may not need this resistor - I tried to remove it and still the serial connection was still stable so you might not need it at all)


At this point you've prepared your router for debricking.

Plug in the USB-to-UART cable you just created to your computer's USB port. Important: I have only tested this on a USB 3.0 and a USB 2.0 port. Warning: Once or twice I got the BSOD on my windows 7 when i plugged in the router but most of the times there were no problems.
Be sure to have installed the drivers that come with the CA-42/ DKU-5.

Once you plug in the cable, go to the device manager and you shall see the "Prolific USB-to-Serial Comm port (COMn)" where n can be any number that your computer will assign your device. In my case, it was COM7 as shown below; Take note of the COM port, you'll need it for later.



Next you shall need to change the "Prolific USB-to-Serial Comm port" settings. Right click on it, go to properties, click on the "Port Settings" and set the following values;


  • Bits per second: 115200
  • Data bits: 8
  • Parity: none
  • Stop bits: 1
  • Flow control: none
Settings to match like screen shot below;




Click "Ok" and close the window.

Next you need to open putty and match those settings in your device as seen below;



Once you click "Open", then you should see the router's console.
While the router is connected to your computer using the usb-serial cable we just created, then power the device off, then on again, while device boots, (within 1-2 seconds) you need to be on the putty window typing the word "tpl". YOU MUST BE VERY FAST!! If you successfully log in, you should see the below screen;



Now you need to copy the factory firmware to the router. To do that, you need to use the previously downloaded tftpd server .


  1. Rename the downloaded firmware to "code.bin"
  2. Use a TCP cable to connect your computer to the router (any eth port but not the wan port - i think... double check!)
  3. Give your computer a static ip: 192.168.1.27 (for MR3420/MR3220 versions v1.x) or 192.168.1.100 (for MR3420/MR3220 versions v2.x)
  4. Start the tftpd server and make sure the code.bin file you renamed in step 1 is being served by the tftpd server. I failed a few times as you can see on screen shot below, but once you succeed, you should see the message "Sending code.bin to <IP> " where <IP> in my case was 192.168.1.11.


See short video of that process of copying the code.bin file to the router.

Now you will have successfully debricked your TL-MR3220. You can use the factory firmware or any other that works to move on from there.
I got most of the steps and technical data from this openwrt page, refer to it and the links therein for any clarification.
This method should work for any other compatible non-factory firmware e.g one from OpenWrt.

Just to mention - probably for another blog, you can boost the reception of the 3G signal by creating an "antena" for the MF 192 modem. See video here.

Enjoy!



2016 Update!


There is a less tedious way to debrick these routers.  I got this from a commenter named "vivoizer dialer" on my youtube video on the same. 

See his solution here:

"I gone through brick issue as configure the openwrt for testing, the TL-MR3420 TP-link router, but recovered through TFTP server it quit easy no need for console port an, use the solarwinds TFTP(i am using since 15-18 years now) TFTP server, now change the firmware name to mr3420v2_tp_recovery.bin, connect router and computer on single Ethernet straight back-2-back cable, change ip address of computer 192.168.0.66/255.255.255.0 without putting any gateway address, now switch-off all the computer firewall options on the computer Ethernet port, as TFTP required udp 69 port to access, but anyway if the firewall is not blocking the port then it is ok. Setup from solarwinds TFTP menu, the server directory where file mr3420v2_tp_recovery.bin is saved. Hold the Tplink router rest button before switching on the Tplink router router and you will see that 192.168.0.88 will access the file after you see message on the TFTP with name of the file mr3420v2_tp_recovery.bin recovered, then release Router rest button, change computer ip address to "obtain Ip address" switch off the router and switch it on, and here you are getting the new ip address on the computer and router LED will be stable now you can login with the new ip address through web. 
I did it these by wireshark it shows me the router is looking for TFTP server recovery file with ip address 192.168.0.66, the file name mr3420v2_tp_recovery.bin I read some time back from some form for another tp-link router recovery, it took all about 12 hour to search read configure and solve. I thought if someone is having the same problem so it can help little.
Regards"