Team estimated a huge feature with 60 days. Made a prototype in a day, implemented it in the project the next day. Code looks a lot cleaner than a previous similar solution.

Now it’s 90% done. Should have worked with 2 other people. Oh well, sorry not sorry for that teamwork.

Dear providers of SDKs, when you claim to have a full documentation for your SDK, please at least provide the info about what unit (radians or degrees) the Angle properties are. Especially important when the iOS SDK is taking radians and the Android SDK is taking degrees, as I found out by experimenting. I don't even care so much about float on Android and double on iOS. Just make use of the fucking documentation and provide some actually useful info there. "Sets or gets the angle" is fucking NOT useful.

My company has been looking for a lead app dev for the past three months. I got the news yesterday that they hired one. Which was super unusual because he's leading a team of two people, you'd think myself and the other guy would have been part of the interview process to make sure he matches our personalities and can do what we need him to do since it's a small team we need someone who can perform.

Find out it's the guy who left in January. I'm not sure how I feel about this. He was super fucking disorganized. I had to spend 2 weeks fixing his git issues because he hadn't committed his code for something like 4 months before he left.

He's a nice guy, and usually chasing new trends. But I need someone who I can look up to and who can juggle a bunch of stuff. If you're disorganized I don't think the regular person can handle leading a team of guys.

I've only been at this company for a year and a half, but I keep getting wet feet and nervously looking around. No promotions, a 2% raise. But I also don't want to hop ship because my place before was an ass disaster too and I think I left 2 years in.

I find it interesting to see how scenarios sometimes flip.

30 years ago, the generally accepted "best" thing to do when when interacting with a person of colour was to "not see colour" - to treat them as you would anyone else. Meanwhile the similarly accepted "best" thing to do when interacting with a physically disabled person was to recognise their disability, help them if appropriate, give them a boost, encourage them, etc.

Today it seems very much like the opposite. The correct thing to do when interacting with an ethnic minority is to see their colour, recognise their struggle, help them if appropriate, etc. - whereas with disabilities, that approach generally seems to have been labelled "inspiration porn", and the correct thing to do is simply not to see the disability, treating them like you would anyone else.

Not entirely comparable of course, but there's enough similarity there that I find the situation interesting.

We only recently started and we can really see the benefits of code review.

It motivates you to follow the standards, writing good quality code and using variable/function names that makes sense. Especially that you know someone is going to read through it.

I fucking hate being sick I’d rather be in debugging purgatory

How to sleep for 8 hours in 8 minutes?

So yeah, don't know much about Javascript but a lot of you have recommended to stay away from JQuery and AJAX because they're on the way out. I hope ASP.NET would use a more modern library instead of JQuery

Lack of proper documentation can waste your two days

I makes a React mistake, alright I is fool.

I caused an endless loop, but Chrome won't let me diagnose it, because when you have an endless loop, you can't close the tab, can't open devtools, can't debug to find the source.

Xcode, why do you hate me? You’ll work fine for a few days and then bam, you don’t even wanna open :(
That’s all

Fucking hell, using Android studio and chrome Dev tools at the same time is a pain. You'd think Google would have their shit sorted when it came to sharing adb with their own programs.

Algo at it again

Some light reading...

Well that didn't last long, or did you delete it?