Love the mobile UX of the developments I do, to make sure that I'm doing something that a user will like to use and considers it user friendly and intuitive.

At my first professional experience, just coming out of university and with no experience on Android. And the company put me doing a port of a VoIP lib of a Desktop application in C++, to be used as a mobile lib for Android app. At that time C++ wasn't supported by the Android ndk.
So my work was learning about android ndk, learn about jni, find out a solution for the non supported C++ in the ndk and learn about a proprietary lib for VoIP.
3 months later and with a lot of help I was able to put it to working (forget about performance). Still they told me my work wasn't good enough and I should have done a better job. For a noob developer that was hard to take.

It was quite a rough begining of 2016... having to give the context of a 7 team members project to 5 new team members, that replaced 5 teammates that left the company...

At this moment a great project would be something eSports related integrated with Google assistant on Android.

MyMethod(Class clazz)

That meeting about the integration of a new service in your app and you know more about the service to be integrated than the guy representing the service to be integrated and none of your questions about the integration issues were answered... One of the worst time wasting meeting.

I don't really remember... That can mean one of two things... It was to long ago... Or don't know how to do it yet... I do remember my first programming class, when my teacher said, "you just need to do a printf ..." And I asked, "what is that?" He looks at me, eyes wide open, for a huge amount of time, and then left without answering...

a side note, it was university class.

Worst enterprise software... Maybe almost all manufacturer bloatware installed whitout being asked if you really want it or what it is usefull for, when you buy a new laptop or phone.

That moment when you're hired as expert of technology A, and the first thing that is asked of you, is to do a PoC of tech A integrated with tech B... and then they assume that you are expert at tech B... and to be as fast as working on thech A

That fealling when your in a social dinner with friends (non programmers or techies) and everyone has great histories about work situations... and then you try to tell your history... and then you think about it.. and then you give up because no one will be so excited about some major bug you solved

Some advice:
- Be careful with the snack;
- Be moderated with your daily dose of caffeine
- And please, please comment your code even you will not know what were you thinking about when you wrote that 500 line method

That moment, in a meeting when you are trying to show a technical flaw in a manager idea... And suddenly you have a déjà vu moment from the "The Expert" comic sketch...

That fealing when someone that picked from the graves an old project that you've started when you were just a noob developer... and then you look at the code... and then the shame.

Once on a project the authentication request for a service was done... through http... with the username and password as parameter in the URL... in plain text

That feeling when you've done a major refactor on you project and it's going to run for the first time... Then you hope it will have no problems/bugs/crashs but you already know it will

That moment when your project manager says to the client "That is clearly possible". After that he asks you if that is in fact possible to do, you say: "is possible with major limitations" and then he understand they screwed up but in the end the one that is screwed up is you.