i just spent 3 hours on a problem that could have been solved in 12 lines.

i really hate myself sometimes

Spent a whole day sorting out catastrophic issues writing loads then finding the root cause is else where so remove my fix and fix the root then find out its even deeper and repeat to then end up at the end of the day with just 1 line of code that has resolved it all.

It's a good thought that you found the 12 line fix :) good job!

There was an engineer who had an exceptional gift for fixing all things mechanical. After serving his company loyally for over 30 years, he happily retired.Many years later the company contacted him regarding a seemingly impossible problem they were having with one of their multimillion dollar machines.
They had tried everything and everyone else to get the machine to work but to no avail. In desperation, they called on the retired engineer who had solved so many of their problems in the past.
The engineer reluctantly took the challenge. He spent a day studying the huge machine. At the end of the day, he marked a small "x" in chalk on a particular component of the machine and stated, "This is where your problem is." The part was replaced and the machine worked perfectly again.
The company received a bill for $50,000 from the engineer for his service.
They demanded an itemized accounting of his charges. The engineer responded briefly:
"One chalk mark $1. Knowing where to put it $49,999"

Don't worry. I've spent 11 hours just to find out that ONE line containing
getFragmentManager()
had to be
getChildFragmentManaget()
.

Divide your time spent by the character count to really make yourself feel like trash!

And that's how you learn.

@redundandundant Are you sure it's not getChildFragmentManager() ?