Bilateral Inguinal Hernia Surgery Jan 16 2023


Over Christmas I had bilateral inguinal hernia laparoscopic (keyhole) surgery and documented my recovery to help anyone else to might find themself in a similar position.

How I noticed

For about a year I had been noticing strange changes to my well-being that I put down to old age such as…

  • back pain
  • acid reflux
  • left hip pain
  • strange stomach noises from left groin

It hit me that something was actually wrong when I was running along the cliffs (fairly normal for me - not eventful) and had the most painful stitch I have ever had in my life. It didn’t feel right. After getting home my testicles felt incredibly swollen for 24 hours and I noticed my groin was sticking out on the left side.

I went to the doctor, had a scan and it turned out I had a large hernia on the left and a small one on the right. It took about 9 months from going to the doctor to finally having the surgery.

Over this time I became unable to sleep through the night, the acid reflux got much worse, some days walking would hurt, etc.

Below are the notes I wrote on the day of and days following surgery.

Surgery Day

Arrived at hospital, put on the sexy see-through pants and tights. Had my hands numbed and went for the general anaesthesia.

Waking up from the general anaesthesia I believe my first-word was ‘pain’. The nurse helped with morphine but the massive ache would not subside. My testicles felt like I was suffering ‘blue balls’ x10 and my stomach filled with 3 Christmas dinners. The following 2 hours was probably the worst of my life, I was unable to get comfortable in any position. I refused my first attempt to stand after trying to sit: the pain was too much. Once I eventually did and attempted to do a wee I began burping, burping and burping until eventually most the aching left my body. The final relief was the removal of the drain (pipe sucking blood out my tummy). I did not like the drain or the removal process. After that I felt great, munched and drank until home time. Apparently all this pain is due to the gasses they fill you with by doing laparoscopic surgery.

I stayed up until 10pm at home in order to take my next medicines. Sleeping was harder than expected, I kept waking every 2 hours largely due to acid-reflux. I was very hot and did many wees.

Day 1

Woke up at 6am. The surgery site is more painful than before, which was not unexpected. Took more meds.

Pretty uneventful day, I managed the pain using the supplied painkillers.

The main achievement today was passing a fart. For whatever reason I just couldn’t control or feel the muscles required to do it until late afternoon.

The pain ramped up in evening so I increased by dose from moderate to severe pain.

One of my testicles is at least twice the size of the other and very delicate to touch or movement. The sack also feels like it had some liquid in, presumably blood.


Day 2

Slept much better. Woke once at 3am and then up at 6am. Decided to try laying more flat and found it was now more acceptable for my body. Sideways doesn’t work yet though.

Testicle issue remains. General pain is less.

Day 3

Able to sleep sideways on my right, the left does not feel right yet.

Testicles still enormous and black.

We had guests over (it is Xmas eve-eve) and was able to do deliver drinks to people, etc. Normally sit on the floor for guests but requested a seat on the sofa on this occasion.

Day 4

Probably would have slept fine if not for the toddler having tummy ache in the night.

Testicles less swollen, still black. I would probably say I am “fine” now. I am slightly slower to move, stairs are a little sore, probably couldn’t walk 5k yet but just sitting and moving around the house are fine.

Days Following

Pain generally decreased daily after this but was still very much aware I was ‘delicate’ for at least the two weeks.

I stopped taking Codeine after a week or so.

This was the first surgery I’d had removable stitches for and would like to report that it was barely noticeable having them out.

The only lingering side effect, which stopped at 4 weeks was my body telling me I needed to wee and poo via pain, rather than that “full” feeling.

I was able to walk and cycle 5k at 3 weeks and able to run 5k at 4 weeks. Possibly could have done both sooner but very much did not want to risk having to go through this all again by mucking the recovery up!

Stitches 1
Stitches 2 (very swollen belly)

Things I did

  • Ice pack 4 times a day for 20mins
  • Slept and rested sitting up with special triangle pillows
  • Did very little getting out of bed for the first 2 days
  • Took laxatives from day 2 (had surgery before and it was horrible not being able to go to the toilet)
  • Took pain meds exactly how instructed


All the original symptoms have gone. I can even sleep through the night again now!

New Computer Oct 24 2022

I’ve recently built a new PC to replace my 9 year old one. Other than GPU upgrades and switching to solid state nothing major has been done to it. Quite a good innings for a computer used daily for both my job and gaming purposes.

I’ve been planning to upgrade for a while but it has been hard to justify given the cost and the fact I can still happily game on it at 3440x1440 resolution. The ultimate trigger was Docker which it struggled to run, usually running out of RAM, which was impacting my work.


I purchased the parts over a couple of months to spread the cost out. The parts are listed below.

Generic Part Cost
Motherboard Asus ROG Crosshair VIII Dark Hero £374.99
CPU AMD Ryzen 9 5950X £416.66
RAM Team Group 8Pack Edition 32GB (2x16GB) DDR4 £166.66
PSU Corsair CP-9020139-UK HX1000 1000 W 80+ Platinum £129.17
Case Corsair 7000D £180.62
CPU Cooler ARCTIC Liquid Freezer II 420 £111.26
NVMe M.2 Samsung 970 EVO Plus 2 TB £126.24
Total Total £1,505.60

I have not upgraded the GPU because GPU costs are still firmly in crazy-times. I had a couple of objectives for this new build…

  • Mainly to keep it as long as possible (like the previous one) so my plan was to high-end
    • PSU should last more than one PC
    • Case should last more than one PC (possibly until I expire)
  • I didn’t want it to be noisey so the case is massive and houses 11 fans (of different sizes) which run at slow speeds. It also fits extremely large CPU coolers

PSU and Fans

The case empty and open
PSU installed below
Front 3x140mm fans
420mm AIO CPU cooler installed at the top
420mm AIO CPU cooler installed at the top


CPU goes here. Please work
It's in!
Little bit of paste
CPU cooler attached. Please work...



AMD Ryzen Precision Boost Overdrive (PBO)

I had a little go enabling PBO after some reading about it on the Internet. It is an AMD CPU thing for overclocking. I recorded my benchmarks with/without below. I ended up turning it off, maybe one day I’ll revisit but the PC is plenty fast as is.

Without Precision Boost Overdrive
With Precision Boost Overdrive


Great success!

You can’t tell the PC is on when idle it’s so quiet. How long it lasts will be a question for another day.

I have given my old PC to my wife and child 1 for work/play, so it will live on yet. Bonus excuse to buy another GPU in the near future…

Automating WinSCP to Deploy a Site Part 2 Sep 10 2022

In the last post I’d made WinSCP script to copy a local folder to a remote folder to deploy my website. I’ve made some improvements since. Instead of using put to copy the files across I’ve used synchronize to do so.

synchronize remote -criteria=size C:\Path\To\New\Site\

synchronize basically makes one folder the same as the other. You could switch out remote and use local to download changes from the remote. The critera part tells how we compare files between local and remote. As I’m using Hugo, the timestamps get binned when the site is compiled so I only have the sizes to go by.

Another issue I’ve had is with Hugo itself not copying assets that aren’t directly used (e.g. images). So I’ve bunged an xcopy together with the above to make this handy batch file.

Wheel in jasemagee.bat

xcopy /E /i /y C:\Path\To\Site\assets\img C:\Path\To\Site\public\img

"C:\Program Files (x86)\WinSCP\" /log="C:\Path\To\WinSCP.log" /ini=nul /script="C:\Path\To\Sync website.txt"

Automating WinSCP to Deploy a Site Sep 9 2022

This is just a snippet of code to automate the deployment of a website (Hugo, Jeykll, etc.) by using WinSCP. I’m using WinSCP because I need WebDAV. I want the script to connect to remote, change to the websites directory and upload the new website version from a folder (overwriting everything in the process) before disconnecting. Here is the script.

open davs://

cd /path/to/website/directory

put C:\Path\To\New\Site\*



This was the first attempt at running the script. It worked but the terminal did not wait for the command to complete, which wasn’t ideal. The only way to confirm it had finished was by reviewing the log file.

"C:\Program Files (x86)\WinSCP\WinSCP.exe" /log="C:\Path\To\Script\WinSCP.log" /ini=nul /script="C:\Path\To\Script\Deploy website.txt"

WinSCP also provides a .com file for scripting, which will cause the terminal to wait.

"C:\Program Files (x86)\WinSCP\" /log="C:\Path\To\Script\WinSCP.log" /ini=nul /script="C:\Path\To\Script\Deploy website.txt"

Git Dubious Ownership Aug 31 2022

I’ve just setup a new computer and have been running into this dubious message when using git.

fatal: detected dubious ownership in repository at 'E:/seeker'

 To add an exception for this directory, call:
        git config --global --add E:/seeker
 Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true 
 and run again for more information.

Note that tools using git (VS Code) may not work or give any feedback about this fatal error. You have to use the terminal to get at it.

If you DuckDuckGo the message sites will tell you to add the directory as a safe place or turn off this security feature completely in git. This seems a bit silly. The error is telling you that the directory is not owned by the current logged-in user of the machine. I keep my development code on its own SSD which I’ve migrated to the new computer and so Windows had no idea who the owner actually is.

To fix this the best thing you can do is simply change the owner of the directory.

  1. Right click the folder
  2. Click Properties
  3. Go to the Security tab
  4. Click the Advanced Button
  5. At the top on the ‘Owner:’ item, press the Change text at the end
  6. Type part of your username into the name field, Click ‘Check Name’
  7. Ok, ok, ok, ok, etc.
  8. No security issue for git anymore
  9. Make cuppa

Previous Page: 1 of 12 Next