i think what you're missing is how good removing a layer of abstraction /feels/ when putting things together. it didn't quite click for me until i built something with it. it ends up being a question of "where the work is done" i think, and the work being done within a string in your component just melts away layers of friction
I think you can still succeed at development if you want. Interviews are stressful-- don't take that trip up as a gospel reflection of your knowledge. And there's a chance that your "not very good" is better than a lot of people.
But it depends on what you want. There are plenty of tech paths from where you are that don't require hard cs knowledge. You can lean into the people side, building teams. You can focus on wiring up big systems with flowcharts. Or you can imagine this a speedbump and keep going in the direction you know.
You're conflating issues, and that's fine because you're frustrated. But we are over-represented in tech, and not anywhere else. There are obvious systems-level hiring problems that this company has and they're trying to fix that. It's so strange and selfish to hear "they should not try and fix this".
Well, that's not quite what he's saying. Remember, nobody is even claiming that underrepresented groups are actually applying and getting turned away - the statistics just suggest that they never even show up in the first place. Yet the suggested fixes are always like the ones in the linked article: turn away the people who _do_ show up until some underrepresented people come in to take their place.
I was hoping the article would at least mention Pleistocene Park, an effort to mitigate climate change that depends on the recently extinct wooly mammoth. If it had, the question in the title would be better stated: "Can We Afford To Not?"
When thinking about the API only, any one of your line implementations seems just as good as the other.
But if you also ask "which of these makes sense for the client application" that will likely narrow your options down.
Indeed, the parent PDF says that before even writing any code, write use cases. "The implementation should adapt to the user, not the other way around."
Anyways, a university experiment video that went viral [0] is the first I recall seeing a quadcopter in action. Maybe the tipping point if you care to investigate further.
Yep, same here. May have seen another article or video that same year but that was the one that stuck in my head. Kind of sad that I didn't even get a "toy" quad until this year but I ought to be building my own sometime this summer.
I feel old. This video is a late addition to the quadcopter world. But then again, while multicopters were popular within DIY scene for some time, they only recently went mainstream and started being sold to "normals".
Would be interested in hearing more about your project. Couldn't find any contact info for you, my email is in my profile. I do a lot of streaming work, and enjoy talking shop.
