Yes...How can i get one ?

I like your shirt. Where I can get it?

Xaxaxaxaxaxaxa

I don't know where you can get one. My wife got it for me and she can't remember where.

I've got a Firemonkey Shirt (Delphi)

PS the pineapple shirt is always a winner 👌

Arrogant people are the worst to work with

👋

Good ideas. I'll maybe make some videos on that

British Columbia

👅

Ya I'm a fan of the take home project

Take home android project

If you're applying to a company that does DS and algo questions then sadly grinding leet code is probably what you have to do. Some companies do take home projects instead - like square. So apply to square 😉

My tip for take home projects would be to take the time to make sure every single thing in the project is as good as you can make it to be. If you are not sure about something or you don't have time to implement something well and it is not mandatory, then it's better to skip that feature. Chances are your code will be nitpicked to oblivion. If they don't like your code, then chances are that you won't even get an interview where you could explain your reasons. It happened to me where I wanted to add lots of things to the project to show that I know and use them because they will be good conversation starters (naive me) but they were not 100% perfect (due to time constraints), so they declined me without a chance to explain them.

@@BapeRuLLZ ya that's a good point. Don't add things you aren't 100% confident in. They're going to tear it apart.

@@codingwithmitch Thanks! Another thing I learned is to try to specify the scope of the take home project with them if it is too broad initially. Something you deem unnecessary for a project like this could be a must-have for them. For example one time all they said was "show the content of a dummy api in a list" and all the recommended dummy apis and the one I used only sent a few items (8-20) with a simple call so I didn't implement paging which they heavily criticized.

I feel like there's not much more to it other than solving the actual problem if we're talking about DS and algos

Ya sounds like not a great place to work lol

I was thinking that lol but he prob wouldn't know

@@codingwithmitch eh, even if he does, lesson learned for him I guess. You didn't name the person so it's totally okay.

Are you talking about navigation drawer? Did they ask you to make one in your interview?

@@s-w No, sliding window is a technique to reduce time complexity in DS&A tests

@@s-w that right there is sarcasm 🙂

You can choose to do a take home project or a classic leet code style

@@codingwithmitch after the take home is there a follow up interview, or that's it?

@@isaac48 ya follow up on site where you build onto the project

@@codingwithmitch Nice! Also recently I heard you say in another video I think. That you won't hire someone who doesn't write unit tests. Do you mean UI or viewmodel/repo tests. I still find it hard writing tests on Android, there's never any clear guidance, there are so many variants and things are constantly changing. And the tests I do write sometimes I feel are obvious and not doing anything important. Any tips/resources you can suggest for this?

@@isaac48 unit tests specifically. Ya watch my courses 😏

Super duper

Other advices are legit 👍. Really agree. But still: any mind games during interview is a huge red flag. Why? Because they want to know, how you behave in a conflict, but a single case is not reliable source. You could be nervous (you probably are), frustrated and so on. Technical interview should be technical.

Well I was more thinking something like: "hey, why didn't you choose path B?" Not really trying to confuse you necessarily. More like just trying to get more info about your thought process.

@@codingwithmitch of course how you ask makes difference, agree

This weekend when I launch the new course I'll do a discount code