Be me first time using python forced into it.
Get frustrated with all the syntax errors you make and Python's cancerous horseshit syntax.
Chase a weird desync problem between C code client and Python raspberry pi controller.
Make 7000 changes to the code and run out of ideas because nothing makes sense anymore.
Decide to go ahead and write C code.
Find out you've been writing code to a different file and running an older version of the code.
I'm a retatd FML don't be like me.

sometimes I start working in Python, stop because of the cancerous syntax , start c++ , realise that I am too stupid for c++ and then come back to Python again

I've been there. I'm a C/C++ guy, and they put me on a Cython REST API. Each day is an agony to me

@Bl4ckb0ne same here i work in embedded really low level stuff C and assembly mostly C++ when necessary. working with python is torture and no one here wants to do it so better give it to the new guy motherfuckers x')

@liverreich give it time c/c++ are love they are life. python is cancer and the work of the devil

@Tychus it is , but it seems that errors are specifically meant to make me want kill myself. That thing is toi hard and sometimes has weird bugs (I think). One time I couldn't get the back of one queue directly. I spent 30 min watching that thing in the debugging window and everything was looking fine but I was still getting a random value after execution. I stored back of the q in the variable and everything worked after that.
It takes ages to do something in c/cpp and for my projects it's not really useful.

@liverreich true that's the key. use them when they are the best fit. that's was the idea behind me using python we wanted something fast to test with we could've written it in C/C++ but it would take more time. and yeah errors can be a pain but once you get the hang of it and know how it works you get by just fine