Not really a rant but I'm just happy so I must share it.

Two days ago I uploaded a new project on github and today when I woke up I saw it on github trending! Only the C# section though, but still.

Feels weird as I'm usually not upload anything and the ones I have usually sit around 5-20 stars forever.

Is there anything worse than bugs that you can reproduce easy but lack exception/error messages so you can't fix it?

I'm working on a hobby project for Android and I can't solve a bug and it's killing me (the whole project depend on it). I went through all phases:

1. I notice the bug early but couldnt reproduce it so I let it be.
2. I notice it happen a lot when I started to use the framework for real. Decided now that I need to fix it.
3. Found the exact way to reproduce it.
4. Trying different ways to fix it, nothing works.
5. Write question on stack overflow, no answers.
6. ???

It feels like if you can reproduce the bug 100% of the time it should be easy to fix right? Well hell no - no exceptions, no error message and adb hangs until I stop the procedur. The last kick in the balls? When I stop the procedur I get all logcat messages back and everything look like normal. Just give me a damn error message! Tell me what you're doing or what I'm doing wrong!

You know what you shouldnt do? Leave your bag with your work laptop at the stairs.

Woke up as normal today and helped the kids down the stairs without checking. Then I just heard how I stepped on something.

Lets say its a big crack in the middle of the screen and you see shit. But gladly it work with work with external screens so its just the screen that are damaged. So tomorrow I must either:

- Work as normal with an external monitor and simply wait to call the boss for fix until after christmas.

- Or call the boss and tell him how stupid I am and hope its okay and I van get a new one/fix this.

Right now I feel for the first one.

Normally I just read rants but my new assignments is just to much and I have to vent a bit.

So I was assigned on a new company to help them with their automated tests (I'm normally a developer) which was fine for me. Especially when they said a guy that have 10+ years of experience have worked on the framework for a couple of weeks so it should be fine and ready. So I though it would be a quick deal.

But then I got there and... it's the worst C# code I have ever seen. I can live with the overuse of static, long method and classes and overally messy classes that doesn't really seems to fit (it's bad but not unusual in test code it seems). My biggest problem is overuse of the damn "dynamic" keyword.

Don't get me wrong, dynamic can be good and it have it's uses but here they use "dynamic args" in every single method, every one! They don't care if the method only require one value or ten values, they use dynamic args. Then you follow this "dynamic args" parameter going in to sub method after sub method and you have no idea what they use.

And of course they don't know if anyone use the methods correctly (as you have no damn clue what to use without checking the source code) so in 75% of the methods they convert the dynamic to an object and check if it contains "correct argument".

So what I have here is a code that isn't just hard to use, it's a hell to maintain.

So I talked with this with other testers on the team and they agree, but as most of them lack experience they couldn't talk back to the senior that wrote it. So I hope to sit down with him this week and talk this through because it would be fun to hear the arguments for this mess.

/rant