The Cody Humpwhistle Blog

linux and crypto currency podcaster


It’s orange and wet.

It has to be said, it’s just too wet. Because it’s like a meal and shit, it comes with loads of stuff on it, mainly onions. And it’s this stuff that decreases your ratio of “chicken” or “lamb” as the majority of the ingredients used are onions (not sliced diced and fried, like big think soggy skin chunks), tomato (i think) and peppers and shit.

The spice level is good, I’ll give it that. A nice ping, doesn’t play on your stomach for the following 24 hours, and enough to wake the pallet up. But I can’t get over the wetness. I’m afraid it’s a not from me.

This post was sponsored by: why the fuck are you taking about an Indian at 7am in the morning?

Equal opportunities, that’s why bitch.

the controller and free flow stream of thought

During my more recent mindfulness exercises I’ve been observing two clear processes of thought. I’ve written about particular states before, and this isn’t necessarily an updated or more homed version of this observations, simply a more recent one.

When I begin the exercise I’m presented with two options: allow the free flow of thought to pass through the observer, or direct it.

Free flow is a relaxed state where you simply get to observe without distraction. It’s kind of like the mind already has queued up some thoughts it would like to process, and it comes very natural in the sense you don’t need to start the thread or direct the focus. I have observed however, towards the end of a thread it will begin to end it’s natural momentum and choice will be offered back:

  • continue flow, although the current will be much more weak, meaning the process of observation takes a little more effort to maintain.
  • direct thought – become the controller. This for me is a perfect opportunity to observe what you’re trying to avoid, controlling thought.

At this point you may think,

ahh the perfect time to address these concerns which have just surface, I’ll just think through them now and see if we can come to any kind of conclusion.

I’d advise against this. Now is the perfect opportunity to observe the weaker current flow. Observe.

Don’t steer, don’t take control.

Allow the background flow of information to surface and just go with it. You may feel something appear and have a moment of consideration for the solution. This is fine, go with the flow. They key is to not direct, not steer but be taken away and absorbed by whatever may present.

[random photo #459]

APU – The circle of life

Setup xdebug with remote php debugging – [phpstorm]

How about my life story, that would be a great introduction wouldn’t it? If you’d rather just see what the fuck I did to get this shit working, scroll down to the first embolden text (that’s text that is in bold for the stupid fuckers like me).

Okay, now they’re out the way, life-story time bitches’. A few years ago, I tried to get vim and xdebug working – as all the cool kids use breakpoints and step-through debugging (You’ve got to be seen in the terminal if you’re programming, right?). It was working, in a fashion. Vim – easy peasy, but xdebug, was a bit of a challenge. I could mark a breakpoint, start debugging and step through the code for the most part.

My development environment using git is hosted on the same remote server as the live php site, and when I commit the code, some git pre-commit shit goes down and merges it with the live site. That wasn’t a big deal, as I’m actually developing on that same remote site (via ssh) using vim anyway, so it was relatively smooth. That is, when the xdebug shit was working. After setup, I’d develop for a period of time without having to debug, and then when I came back to needing it to work, it just wouldn’t. Well, not in the sense I needed it to. Code wouldn’t be executing how I’d expect, I’d drop into debugging mode only to be met with screen tearing through tmux/vim, with CTRL-L just moving some random chars around the screen.

It “worked” but it just wasn’t making my job easier, and I’m already a slow developer – any slower and project would start going backwards. Anyhow, I reverted back to dump and die as my debug of choice and thought “fuck it, do what works for you, fuck the developer elitist who swear by these {standard} debug practises”. And I continued on my merry way.

Until recently, I’ve been working on something that would take anyone else an afternoon, but in typical Cody fashion I’ve been working on it for weeks. Got to a point where the code just wasn’t doing what I was expecting. And even after dropping a dump and die, I couldn’t figure out what was going wrong.

Now I have a friend who programs properly. And he mentioned he was looking at moving to a linux development environment and asked some tips and specifically mentioned stepping through code. Without going into a whole new story, the question was fresh in my mind. He gets paid to program, does it as a job. And he steps through code and thinks it’s important enough to add as a key attribute to setting up a new development environment. And here I am, selling vim and the terminal because it’s “cool”, and really, I’m not the one who’s ahead here.

So I’m scratching my head as my usual dump and die isn’t pointing me the way to amarillo. Fuck.

Could really do with being able to step through the code

Fuck it. What are the kids using these days? Now – the story’s being going on for far too long, but as you can probably guess, I settled on phpstorm.

How the fuck do I set phpstorm to work with remote debugging?

Painfully was the answer. Not because every guide online sucks, but because I just couldn’t visualise how it was all going to come together. So even when they were talking about remote port tunnelling with ssh, although I’ve done it countless times, I couldn’t see which way I was supposed to be forwarding ports. From local to remote, or do I need to forward my ports, scene as I’m the one running the phpstorm software.

Anyway, I got this bundle of joy working. And to help ingrain it in my mind, and get some cheap SEO points, I thought I’d detail the process here.

The How

  1. Follow whatever process you want to get xdebug setup, we want to end with something like this:
  2. Setup a remote SSH tunnel. Mine looks like this (I use mobaxterm, because I’m coool):
    1. Make sure it’s connected.
  3. Click the phone so it’s green both sides:
  4. Install a browser plugin that sends xdebug strings when you make a request:
  5. Set a breakpoint in your code within phpstorm
  6. Enable the xdebug browser helper addon after loading the webpage your debugging, for me it’s which links to the un-commited git code I’m still working on.

Bingo, bango, bongo. When refreshing the page it should catch the debug process within phpstorm.



methods of persuasion – short term

Some practical advice you can put into action.

APU. Read it as a word and say it out loud. APU – A poo.

A poo. A poo. APU.

  • Anchor
  • Prime
  • Unload

You’re just not going to find this shit anywhere else on the internet. You want short term results? Walk this way.

I’ve just finished methods of persuasion by Nick Kolenda, and you know what – it’s a decent book. But I came away with my own shortcut system for all the advice offered. If you want to persuade someone in a short amount of time, increase your chances with APU.

Let’s say we want to buy a new toy, but we anticipate resistance from the mark.

Anchor – You need to float your idea into the consciousness of the mark. It has to come across like an idea, can even come out half joking. If you put it as matter of fact, it will raise the defences of the mark and the game is over. “this car’s getting some miles on it now, would be cheaper getting a new one for the cost of maintenance” or “the telly’s had a better day, need a magnifying glass to see the screen”. Depending on time, you can anchor once and move to prime a short while later. But in the perfect world, the more you anchor WITHOUT raising the defences of the mark, the greater the chances when it comes to execution.

Prime – There are many examples and interpretations in the book, but I’m going to be precise. Have a conversation with the mark about someone recently having an open mind. For example, “I was talking to Dave today and he’s been pondering a career change, thinks he may be happy trying something new”. Or “Was talking to little Mike and he’s been listening to some freethinkers and has genuinely been questioning his faith”. Or any other countless example of someone being open minded. If you can use a real life example, even better.

Unload – The money shot. The foundations have been laid. Regardless of the result, our chances have improved, the final part of the job is a clean execution. By clean, I’m talking about presenting the idea as a serious idea. Without the joking, and without pressure. Just as a thought that just “popped” into your head and you’re considering out loud. “i’m thinking of low balling an offer for a car, would be a steal if accepted” or “could do with taking a look at TV’s today”. Simple, clean, execution. Just a statement slipped in from nowhere, with no conviction so no reason to question.

Of course an objection may be raised, and the key’s to play it cool, and if it’s looking like a no ball, switch it up to an anchor play. It’s your only option. It maintains strength longer term and means you’ve not lost any ground, only increased the chances for your next pitch.

And then of course there is the chance I’m talking absolute shit, and I’d probably put that ahead of this being something you can actually use in real life.

But who knows, it’s worth a shot.

episode number four five, technical stuffs – released today, don’t forget to comment, like, subscribe, follow, upvote, share, plagiarism, reinstagram

Pandora’s box (Recommended Reading List)

top recommended

  • Sapiens A Brief History of Humankind – Yuval Harari
  • The Selfish Gene – Richard Dawkins
  • A Short History of Nearly Everything – Bill Bryson
  • The Brain: The Story of You – David Eagleman
  • Homo Deus: A Brief History of Tomorrow: Yuval Noah Harari
  • On Tyranny Twenty Lessons from the Twentieth Century: Timothy Snyder
  • Influence: Science and Practice, 5th Edition – Robert B. Cialdini
  • The Obstacle is The Way – Ryan Holiday (audio)
  • Methods of Persuasion: How to Use Psychology to Influence Human Behavior – Nick Kolenda
  • Psychology of Human Behaviour – David W. Martin – The Great Courses (audio)
  • The Staircase – Netflix documentary
  • The Brain that Changes Itself – Norman Doidge

other recommended

  • Code Complete A Practical Handbook of Software Construction – Steve McConnell
  • No Place To Hide – Edward Snowden and Gleen Greenwald – Tv Documentary
  • The killings of Tony Blair – TV Documentary
  • WAKING UP WITH SAM HARRIS#83 — The Politics of Emergency
  • This Naked Mind: Control Alcohol – Annie Grace
  • WAKING UP WITH SAM HARRIS #107 — Is Life Actually Worth Living?
  • Spotlight 2015 film
  • The User’s Guide to the Human Mind: Why Our Brains Make Us Unhappy, Anxious, and Neurotic and What We Can Do About It – Shawn T. Smith
  • Lost Connections: Uncovering the Real Causes of Depression – And the Unexpected Solutions – Johann Hari

New ones will be added to the bottom of the respective list and I’ll also do a blog post to say a new one has been added, so don’t forget to comment, like and SUBSCRIBE!

[random picture #532]

New Podcast – Gym of Life – another one for your scuba gear

because it gets deep

Consciously discard the task

It’s okay to decide not to do something, but it’s important you make the choice, recognise you’ve made the choice then consciously discard it.

Let me give you a few examples:

Someone asks you to do something later on. Later on arrives.

You decide “I can’t be arsed” and you don’t do it – but the thought of inaction is taking up cycles.

Now try this tact instead; later on arrives, you can’t be arsed. You think about general consequences, i.e. friend thinking your less reliable in this regard, possible small hit on the relationship. And with that in mind you think to yourself – “I’m not doing it, I’m happy to accept the consequences.”

Another example, you’ve been asked to do something. You’re not going to do it. Think about the possible consequences clearly in your mind, then consciously make a choice not to do it.

It sounds like utter nonsense. And it could portray me as a lazy bastard – of which I won’t deny. But it’s not as black and white as that. Shit happens all the time for when you’re not going to act, or you’re going to let someone down in a small way. Control the choice, make the decision and move on. It makes you think about the consequence and longer term, you won’t let things just expire. You’ll think about them each time, and the ones with bigger consequences than you may have considered, have the option of being rectified before it’s too late.

And the things that you consider and decide against anyway, you get to forget about, rather than have them nagging away in the back of your mind.

Life hacks bitch.

podcast – talking about death