Just had an interview with our new potential product manager. I companioned our CEO, if technical questions arise...

First, he came to our office, to the interview, and never..never looked at our application. Neither he saw some screenshots, review's or anything related to the product. As a potential product manager...gasp

And he really tried to impress me, by mentioning what a great full stack developer he also is (LOL), with years of experience in frontend and backend.
But, since I am an android software developer, he mentioned he don't like java. But he loves java script...

Me: ehhh what? So you compare apples to oranges. Why do you don't like java? (And I could image a lot things ...)

Him: because unlike JavaScript, java is a mess when writing code.

Me: ok Iam done.

There are 3 incorrectly labeled fruit baskets (all 3 are incorrectly labeled). One basket has only ORANGES, another one has only APPLES, and the other has mixed ORANGES-APPLES. You can't see anything. You can only pull out 1 fruit from 1 of those baskets. With that, move each label to it's corresponding basket.

Legit Apple Interview
There are three boxes, one contains only apples, one contains only oranges, and one contains both apples and oranges. The boxes have been incorrectly labeled such that no label identifies the actual contents of the box it labels. Opening just one box, and without looking in the box, you take out one piece of fruit. By looking at the fruit, how can you immediately label all of the boxes correctly?
Those who got it answer it directly on Saturday/Sunday until then good luck

Ok I'm going to jump in on the new iPhone shit, yes they are expensive, yes they are pale in comparison to flagship android devices (no I'm not an apple fan at all but I like Mac) but you don't buy an iPhone for the hardware, you buy it for the software and custom silicon.

iPhones will probably out perform android in synthetic tests for ever, they are working with custom designed hardware, custom software where as android will run on a multitude. Can't have 1 size fits all without compromise.

I will still say that iPhones are 110% to the power of 100 not worth the money in any way, but I'm sick and tired of seeing people compare iPhone to android when it's like comparing apples to oranges -,-

A tech as well as a life question (actually more of a useless sleepless thought) : What do you think is more important? Exposing yourself to multiple technologies, career paths and life experiences or diving deep into a single technology, career path and life experience?

I feel like being an expert in 1 tech might pay off in terms of job life , and it would be bad for a person who is constantly switching between career paths, but sometimes i feel like i should have tried other paths too. Not just the life of a techie, like people who are deep into media and journalism, accountancy or those film industry jobs ; politics or finances , etc.

Its like, we found an apple to be a tasty fruit and now we have to be the apple guy forever. The better i am in being the apple guy, the more i will have to eat apples and the more i will earn. Why can't i try pears or oranges?

Didn't see any rant about Apple's new declarative UI framework: SwiftUI. Looks a lot like Flutter, but I'm still new in flutter so I'm not sure that way of creating UI, why is it better that way? Or it is just like Oranges and Apples, choose what fits your needs?

I get so tired of people hating on PHP, Javascript and promoting Python or C#/Java.

Python is basically Perl with slightly different syntax plus has py2/py3 issues. And suffers from pip like js does from npm.

Java/C# started as application languages, while PHP started in web servers (again from Perl but at least it now has full object support). So comparing apples and oranges is one thing.

Another one is that people don't seem to know much about PHP / js (and tbh not even about the languages they are promoting) when they try to hate. That just comes off as lazy and borderline idiotic. Don't be that guy.

If you have had a bad experience, maybe you need to open the documentation instead of copying code from stack overflow.
Again, lazy and unprofessional.

Devs are supposed to be able to find the most efficient solution, that takes as little code as possible, not as little time from them when they arent familiar with the subject.

Damn Im angry right now, this rant really worked me up! :D

Telling the customer it's not a system problem but their end users network problem over and over with proof and still making a fuss over it. What the hell do I do next?