Browsing through an old project of mine which let you make 3D scans of a person with a Kinect and easily add it to a game.

I worked on it during my minor in Japan. It's such a clusterfuck of code and different pieces of software glued together. But man, I had _so_ much fun making it. Funny enough it brings back great memories of the time I spent there.

I'm amazed I was able to finish it in time, or at least something that resembles "finished". Literally the day before I went on a three week round trip I had to demo it. And it worked reasonably well. I'm so glad the professor didn't screw me over on that one. Then again the other person working on a project there only made a simple raspberry pi space invaders. Haha. What a lazy cunt. We were literally told we could do _anything_ we found interesting.
I don't blame him though, he wanted to spend (and did spend) most of his time partying and socializing while he was there. Good for him :)

I should post this baby up on Github, even though it's a shit stain of a project. I want to improve on it when I have time. Who knows, someone might actually view/use it once. That would make me so happy, even if he doesn't do anything with it.

This literally just happened: "Our network is down". No internet and backup seems to be failing as well. Thankfully I can still develop locally with git. Now to be able to focus. I'm not shitting you when I say a guy with a sandbelt machine is grinding down a door 3 metres away from me.

I fucking HATE testing JavaScript. It's such fucking bullshit. I've been struggling to test one simple functionality for multiple hours. It's probably one stupid thing I can't figure out, so I hope some sleep will grant me a fresh look tomorrow.

Also it's absolute bullshit the amount of libraries and dependencies you need to have to get some proper scalable tests going. Jasmine, Babel, ES2015, yarn/npm (because Jenkins is too fucking old to handle yarn). React, react test helpers, webpack. The list continues. FUCK OFF!

People seem to like these party parrots, so I thought I'd spread the love: http://cultofthepartyparrot.com/

Made a joke to my manager about implementing a party parrot (cultofthepartyparrot.org) puking panda as an eager egg. She promised me breakfast for a week if I actually did.

Welp... better get acquainted with Photoshop.

I knew it!

Not sure if it was 2016 or late 2015, but it's a fun story anyway (and if it's not you'll at least learn something from it).

Back at the time I was quite new to unit testing (weird how it has become second nature in a years time). I was writing some software that was supposed to send out some SMS to customers. Of course this had to be tested. However, it was a bit difficult to test (or so I thought) without actually receiving an SMS to know if it was sent. So I decided to use the live API key to make sure the sending of SMS was actually working correctly. I tried it a few times but didn't receive an SMS. So I kept working on it and running tests.

The testing setup I had at the time was just a continues loop that went through all tests to make sure it all still worked (I've moved to only checking on file changes now, but that is besides the point). Keep in mind I was still running these tests, in a loop, with the _live_ API key.

So the end of the working day arrives and I go home and sit in the train. All of the sudden I receive some test SMS. I was thinking "hey nice, it did work". Then I started receiving more. It soon turned out to be an alarmingly big amount of SMS. It stopped around 100, but don't think that was the end of it. Oh no. I had changed the number to send the SMS to from my own number to a different number (+31612345678 to be exact, which I found out later isn't an actual phone number. I really hope I was right about that). I was beginning to become nervous, but there wasn't much I could do.

The next day I returned to work and checked the API for sent SMS. Turns out I had sent a couple of thousand (I think between two and three thousand) SMS in a couple of hours. Most of them to the test number I had supplied.

This probably cost the company a couple of hundred euros. Luckily my colleagues and team leader all thought it was pretty funny, but did tell me not to do it again. And I haven't of course.

Lesson learned: don't use live API keys during testing (among other things :)).

So yeah that was probably my worst dev experience.

Feature request:

Some type of markdown style formatting. So we can use _italics_, `code` and ```codeblocks``` among other things.

I fucking _hate_ the inconsistency programs have with ctrl + y. For some it means "redo". For others it means "delete this fucking line right here".

Thankfully there it's always good 'ol ctrl + shift + z which is always redo. I've completely moved to it and shunned ctrl + y.

I have a colleague who has a fear of closing any window. He'll let his Mac run for months on end without closing any of the windows he's opened. He also has all kinds of browsers with tons of tabs open. He's a designer so I get his urge to not do all the technical bits and bobs every day, but for the love of zalgo restart your computer once in a while. Or at least close windows you don't use. It's come to a point where non of us want to help him, because helping him out takes forever with his slow as shit computer. We've asked/told/joked about it too him several times, but he just doesn't want to listen. At one point when I was helping him everything took so long that I decided to reboot for him. And of course Mac had to go and reopen every window that was open during shutdown, which took another good fifteen minutes. Shite OS. And naturally he spent the next hour fixing everything the way he liked it. He hasn't turned off his computer since (couple of months ago), except for when we moved to a new building a month ago.

Just had to get that annoyance of my chest.

This new guy started working/doing his internship when I had just finished mine. He asked a colleague for help, but had to wait a little. All of a sudden he got up, said bye to another colleague and left. All of the sudden the colleague asked where he was. Apparently he left because he didn't feel like waiting. Safe to say he wasn't welcome back after that.

I have this awesome StackOverflow mug, but I don't drink coffee. Or any hot beverages for that matter :(

Jetbrains IDE has this awesome shortcut ctrl + w that selects the entire word the caret is placed at. Ctrl + w on browsers closes tabs. I hope you understand my displeasure of this.

Just found out the beauty that is "git stash -u". This stashes all your changes, even the untracked ones. Why the hell isn't this the default?

Sudo me

Make a small contribution to a github project, with tests because that was one of the requirements set by the owner. Owner then comments why I've made a test for this change... well... Because you asked for it. Be consistent. Either write tests for all functionality or don't bother at all. Now I feel like I've wasted my time.

When git blame tells you name@example.com wrote the shitty code, but he is actually reusing the address that was assigned to a former colleague with the same name.

Colleague just found out that redislabs silently truncates passwords to 20 characters. Naturally our development department was horrified. It also explains why we couldn't access our account anymore. Who would even come up with such a thing?

That awesome feeling you get when you started with no inspiration, but after starting to work you get all kinds of awesome ideas.

After messing around with Laravel 5 for hours on end I finally got it working on production. Turns out everything was correct, but the random key generator command decided to literally put "RandomString" as the 32 character website secret... Wtf Laravel?

I just hate it when you're happily coding along when a colleague asks you to help him. You try to help him at his computer, but that thing is always slow as shit and has these weird workings. So you go ahead and try to do it quick on your computer. Then during the setup you run into problems. Being the good dev that you are you try and fix those along the way, but somehow you get sucked deeper and deeper into the rabbit hole. The next thing you know you've been working an hour on some shit which should have taken 5 minutes. To top it all off you want to return to what your were actually doing and say "screw it". But there's this nagging feeling and you can't help but finish what you started. Worst of all your colleague hasn't advanced one bit.

Somehow I always feel like a jerk afterwards. Either I quit and didn't help (and didn't fix what needed fixing), or I did help and it took too much time away from stuff I should have been working on :(

I love Mondays. Back to coding Valhalla!

Aww yis. Got emergency service call with only 10% battery left. Solved it with 6% left. Though I admit I don't like living on the edge. Where's my power adapter?

> Be me
> Be on 24-hour emergency service
> Post rant about stuff breaking during said service
> Forget to turn off notifications
> Get awoken in the middle of the night by phone
> Think shit is going down
> View message
> People are liking my rant
> Try not to cry

The past three weeks almost no issues during the 24-hour emergency service. My service starts at 10:01. Everything breaks.