I took assembly as well before switching over to linguistics (though I did quite well in assembly). I don't remember cache locality ever coming up. I also don't know Objective-C that well but it looks like you tried to do a one-to-one translation between a language with an isolating morphology (English) and another with an agglutinative morphology (Japanese). I imagine that might bring out derisive chuckles from people who share your mindset though I'm not one of them.
This is like saying that "is" and "are" (one of the few areas where English is still inflectional) are the same thing. Grammar is integral to vocabulary. I could snicker and sneer at you not knowing this but I'm not going to because I recognize that working with others shouldn't be an endless gotcha game. Consider treating others with the same respect.
Say that to the Japanese politician who gave me the idea. He was a language teacher.
This alone does not give him enough discernment to draw up plans for a translation program between two vastly different languages. In the case of Japanese you might be able to make things work in the specific instance of grammatical case because case is cleanly marked with a suffix that doesn't alter the noun before it (AFAIK).
However, your ambitions appeared to be broader than translation between English and Japanese or vice versa and I can guarantee that your approach would bomb with a language like Latin, or Finnish, or Quechua.
I don't stick my nose in what I don't know.
I'm afraid that hasn't been adequately demonstrated, sir. Acknowledge this and treat others around you with the same respect that you should receive yourself in making forays into unfamiliar territory.
It looks like you took a completely wrong message away from this: because you unreasonably demand specific formal qualifications for hiring a software engineer, you have also unreasonably and irrevocably wiped out your text translation application instead of learning the linguistic fundamentals on your own and improving it accordingly.
People in the field of software are constantly thrust into areas where they have no formal qualifications. No less a person than Geoffrey Hinton unwisely proclaimed that deep learning means that training as a radiologist is now pointless. Flesh-and-blood radiologists have rightly pointed out that he's in the wrong about this. That doesn't mean that Hinton should walk back his efforts in deep learning in general, or that he or anyone else applying deep learning to radiology should just shitcan their entire efforts.
What they should really do is recognize that they don't know everything and update their work instead of just wiping it out and sneering at everyone who doesn't have their very specific knowledge base. The moral of the story is, again, that you should treat honest mistakes made by others as your own honest mistakes and be willing to forgive others as you forgive yourself. And don't forget that "bootcamp people" may know a lot of things that you don't know.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I took assembly as well before switching over to linguistics (though I did quite well in assembly). I don't remember cache locality ever coming up. I also don't know Objective-C that well but it looks like you tried to do a one-to-one translation between a language with an isolating morphology (English) and another with an agglutinative morphology (Japanese). I imagine that might bring out derisive chuckles from people who share your mindset though I'm not one of them.
This is like saying that "is" and "are" (one of the few areas where English is still inflectional) are the same thing. Grammar is integral to vocabulary. I could snicker and sneer at you not knowing this but I'm not going to because I recognize that working with others shouldn't be an endless gotcha game. Consider treating others with the same respect.
This alone does not give him enough discernment to draw up plans for a translation program between two vastly different languages. In the case of Japanese you might be able to make things work in the specific instance of grammatical case because case is cleanly marked with a suffix that doesn't alter the noun before it (AFAIK).
However, your ambitions appeared to be broader than translation between English and Japanese or vice versa and I can guarantee that your approach would bomb with a language like Latin, or Finnish, or Quechua.
I'm afraid that hasn't been adequately demonstrated, sir. Acknowledge this and treat others around you with the same respect that you should receive yourself in making forays into unfamiliar territory.
It looks like you took a completely wrong message away from this: because you unreasonably demand specific formal qualifications for hiring a software engineer, you have also unreasonably and irrevocably wiped out your text translation application instead of learning the linguistic fundamentals on your own and improving it accordingly.
People in the field of software are constantly thrust into areas where they have no formal qualifications. No less a person than Geoffrey Hinton unwisely proclaimed that deep learning means that training as a radiologist is now pointless. Flesh-and-blood radiologists have rightly pointed out that he's in the wrong about this. That doesn't mean that Hinton should walk back his efforts in deep learning in general, or that he or anyone else applying deep learning to radiology should just shitcan their entire efforts.
What they should really do is recognize that they don't know everything and update their work instead of just wiping it out and sneering at everyone who doesn't have their very specific knowledge base. The moral of the story is, again, that you should treat honest mistakes made by others as your own honest mistakes and be willing to forgive others as you forgive yourself. And don't forget that "bootcamp people" may know a lot of things that you don't know.