And also... I have learned to avoid friday deploy for my own sake

That we all fail and for every time you think someone else is stupid or falls into mistakes, you will fall into your own mistakes and be stupid in front of someone else, no one is perfect, we are all humans and at the end our work is to tell machines what to do and if they do it wrong, it's because we told them to do it that way and we are wrong.

A guy who thought the only way to access data was through a relational data base and the only way to access a data base from java was JPA

Soooooo last week was a long week, we have until the end of the month to achieve a big goal and this week was all about going to bed at 3 am or so and begin the day at 7 as usual, the weekend that I ussually take to rest and sleep was at the office too, if we dont get to the goal I will be more dissapointed than ever before

If a frontend dev asks for screens, mocks, designs or whatever, all the company pushes for it and gives it to them, but if a backend dev asks for a set of input/output samples for a feature, the same people claim "its so hard to think about the cases"... Wtf are they thinking?

It's almost all the time but specially when there is a stupid bug i find out in production after all the efford i put on testing before release, or even worst, when the bug is not stupid, is random and just hard to tell why the fuck everything is fucked up

So we released a new version of a core system on friday trusting everything was fine... Saturday morning everyone reporting problems and we run as fast as we can to find out a super important field was never assigned after unserialized 🙃

Thanks!!!!!!!!! It was awesome to find it when I came home, after 2 months they are finally here @dfox

soooooo we are still trying to make the mapping from the classes to hibernate, almost 7 hours and all the time every change we do, we have to close netbeans and open it again to "refresh" the hibernate configuration ._. we have seen the netbeans logo all the f*cking night ._.

Ok the sprint review is tomorrow, there are lots of work to do and qe are half slept, this gonna end well :)

Not again please!

All the night thinking about a possible solution, finally got it, code it, push and went to sleep some time, then I realized it didn't deploy and doesn't actually run ._. almost cry, and then I realized the error was that i was using the wrong variable and forcing an infinite loop .___.

My first new year resolution for this 2017 is learn to do the f****ng unit test before implement the code

just remembering the best lines of the year, my full working cycle :P whichones are yours?

It's almost 2017 and the only thing Im doing is stay laid in bed reading rants it feels wired 😐 but its funny anyway 😝😀😀

Hi everyone.
I wish you all a 2017 full of code, of problems to fix, of oportunities to learn new languages and above all full of bugs to fix because from this, is from wherr we learn the most.