I recently started building VR apps for VR headsets with Kotlin/Android after five years as a front-end/full-stack engineer. It has been humbling and scary, but I'm learning and loving it. The switch was motivated by several reasons typical to FAANG companies.
My mac mini is heavily constrained due to only having 2 proper cores and not much RAM. So the smallest models run best. The quantized tiny runs better than the regular tiny simply due to memory pressure.
So, in my testing on my mac mini it tends to take about 30% more time to process than the audio clip that was recorded. I added a specific warning that lets the user know to reduce their thread count if the processing time takes longer than a specific threshold.
Some of my stream viewers report it being pretty fast though. (much faster than what they see on my mac mini).
They sound increasingly self-aware. Adverse childhood experiences are important to crawl out from under, and it takes a lot of work. If you're confused about what they're saying, why not ask for clarification?
I see this a lot, but I will go out on a limb to tell you ADHD is not the reason for your failures. You probably already know this, but it feels better to blame it on something you think is beyond your control.
No, Leetcode interviews are very much alive. I have interviewed at all three companies you mentioned for frontend roles & they all ask Leetcode questions, but to varying degrees.
FB: I currently work here.
LC style questions but with a frontend twist. Best believe if you don’t have a strong handle on algorithms, data structures and Javascript, you won’t stand a chance.
Google:
Phone screen is leetcode, during onsite they ask two leetcode questions & 1 frontend focused one.
Apple:
Phone screen is Leetcode, onsite is a combination of leetcode & frontend.
I actually find frontend interviewers to be harder because you have to have a strong handle on frontend technology + data structures and algorithms, as opposed to non-frontend roles where just doing leetcode is all you need.
Also, there is the very wrong notion among people ignorant about the frontend engineering world like yourself that assume all it entails is simply knowing how to use React & CSS. It is more complex than that, you’d have to know about the DOM tree, know how to manipulate it, think about accessibility & performance. It can become complex very fast. Most of these interviews create Leetcode style questions from DOM tree manipulation & they are harder to reason about.
I applied for a frontend position 1-2 years ago at FB. I thought I was going the Leetcode route so I prepared for that but somehow my application went through as a frontend position (because my CV and OSS is mostly frontend React and then some node.js), I was just asked some JavaScript basic algorithm (nothing you need to prepare for, implement a stack and something else similarly simple) && CSS (which I bombed completely, I certainly haven't used CSS without some sort of abstraction for the past 10 years, I certainly won't get it right at the first shot).
I didn't pass eventually.
I have a friend who joined FB for a year (left purely for the stock decline, he was doing fine performance wise) and had a similar experience with zero LC asked.
My wife went through the normal engineer route a few months prior that and got asked only Leetcode.
My friend got hired at Apple as a frontend engineer and got asked zero LC.
I disagree on the perceived hardness, I feel like LC interviews are way harder than frontend engineer ones but I might be biased as I've been doing frontend for almost 20 years.
My point is, the reasoning ability you need to have to solve LC (unless you memorise most of them) is way higher than getting the logic right for a frontend exercise. I would not call them "LC style with a frontend twist".
Really sucks man. Most times companies are looking for people with experience, most self-taught programmers like myself built up that experience over the year(regardless of what language)s through side projects in college and stupid stuff for fun. It pays to build up your portfolio while doing your 9-5. One can't just take tutorials within a year, build a test app and get a job, am not sure if the tech industry works that way.
Sorry but I have to take offense to this. Whatever side projects and stupid stuff (your words) you did in college for fun 100% pale in comparison to the full fledged Rails app I built over 3 months 90 hours/week for work, and the other 2 iOS apps I built and released on the App Store, which took an order of magnitude more time than the Rails app.
Not fair on your part to downplay these efforts by condescendingly calling apps I built "test apps" (what just because I read a tutorial? How did you learn????). You maybe don't realize it, but the only reason you're able to get a job as a self-taught developer is because you're in the US and you have a Bachelor's. That is the way the tech industry works.
I'm really sorry if you took my words the wrong way, I guess it came out wrong. I'm not downplaying your efforts, on the contrary I think they are great, most people give up after 3days of debugging. IMHO I'm just saying that sometimes companies look for experience not just from apps, but also from years of programming.
For the record, I'm not in the U.S (never been there before), but I've worked for U.S(New York) based companies as a remote developer. I currently work as a remote developer for another startup in Germany. I've never left Africa before. I taught myself to code, learnt the hard way(I mean epileptic power supply, no/poor internet service) and I don't really value my degree, I'm not sure if it has helped in any way, ironically I don't have it(have not gone back to get it) and have never applied for a job with it. I admire your efforts and wish you good luck in all your future endeavours.
