Read on Twitter
Yesterday, I was knee deep in Polymorphic Json deserialization, custom converters and branched state machine paths.
If you came to me, before yesterday, uttering any of these terms: I would have tuned out, run away or decided never to ask you a question again.
If you came to me, before yesterday, uttering any of these terms: I would have tuned out, run away or decided never to ask you a question again.
But when you're thrown at the problem and have no choice but to figure it out, you'll realize it isn't that complex at all.
Harkens back to the Rx days. Yes it was complex; my "functional reactive programing" skills were minimal/non existant; But we figured it out! (mostly)
Harkens back to the Rx days. Yes it was complex; my "functional reactive programing" skills were minimal/non existant; But we figured it out! (mostly)
Personal learnings:
1. Don't be afraid of highfalutin fancy pants tech terms. They're not always as complex as they sound.
2. I'm going to consciously try to not use fancy terms when attempting to explain these concepts to others.
1. Don't be afraid of highfalutin fancy pants tech terms. They're not always as complex as they sound.
2. I'm going to consciously try to not use fancy terms when attempting to explain these concepts to others.
If I do use these terms... I'll make sure that the listener also shares the lexicon for these terms.
Otherwise I'm doing everybody in that conversation a disservice.
Otherwise I'm doing everybody in that conversation a disservice.
