I just did the equivalent of (it's actually a lot longer, this is psuedocode):
Color bg = Color.argb(
mColor.getAlpha(),
mColor.getRed(),
mColor.getGreen(),
mColor.getBlue()
);

god im tired…

After 5 hours of coding u be like...

To confuse everyone, someone should make a programming language called Psuedocode

-See vaguely interesting feature in language (currently C#)
-Look at the docs and psuedocode to get a feel for what the feature is intended for
-Design small project around the feature
-Learn the feature by using it

I’m really liking the Algorithm Design Manual so far, except for the fact that there’s not a glossary somewhere for “random mathematical symbols you have probably never had to deal with but we will use in psuedocode examples”

Sometimes when other devs ask me to explain something in the specs I cannot make into smaller words (example: javadoc says throws <error name> when x <= y. I was asked to explain 'what all this psuedocode means'), or their code horrifies me, I ask my mother if she knows what it is doing.... just as a 'wtf am I missing' check.

She still finds it amazing when we text her a gif and asks for help when she 'loses' her icons on her phone, but she will still ask what is wrong with some of these people.