Chameleon
Kara Peoples
Self-Starter in Remote Customer Service | Empathetic & Tech-Savvy | Passionate DEI Advocate
Characters in Life
So many journeys can intertwine in life. I have people I consider friends all over the world. Some I have even found are part of the tech world too. You can travel the world from the keyboard with games if you have the time. I also saw people come and go in Team Awesome to reign in this story some and weave it back to my thoughts for this newsletter. So, I am not na?ve and know that Tech is not going to be the answer to everyone's journey. I just want to encourage you to find your path and will try not to forget that my readership is going to or at least wanting to include other professionals.
By the time I reached Unit 3 Team Awesome had seen 3 people move on from Lambda. To those 3 I do wish you well on your journeys and I know you will all Keep Moving Forward!
REACTJS (Unit 2)
React is hard! React is easy! I never really fell into the argument, myself, but I guess to me React is easy. On the surface level anyway, you go into the real things like hooks and things. I do need a deeper dive. Although, I am can make REACT work for me. I just recently helped another up and coming developer tackle the basics of REACT. It was great being in that teaching seat again. We had a rather at length discussion on the argument of easy/hard subject. I believe we came to an agreement that it was easy once you understand props better. This brings us to:
**TECH BREAK**
Down with Props!! This is the chant we made in Team Awesome quite often. So the first thing I did was show my new mentee how I de-structure props. Upon building a card component and having an API pulled up in the console. I name my props de-structured there before passing the props to the card component form API call List Component.
领英推荐
As you can see I decided on my prop name and instead of props.name et. al I de-structured them so I knew exactly what I was wanting to display and if I revisit this component later to change anything I can. This may just be a simple overview but it really helped me to see how information was being passed around and I think it helped most everyone else that has added the DOWN WITH PROPS!! adage to their chants.
I am absolutely comfortable being a leader and teaching what I know to others but I thirst to be a follower as well. In REACT Level 1 we started learning about form validation and testing with the JEST Framework, which I later found out was built on Selenium and can now build my own testing framework from Selenium with Java, not fluently I still need to rinse and repeat and I am trying to do this daily now as this is what I have learned to do with GenSpark and where my current career and purview lies until I get back to my Front-End love.
Chameleon
I used to consider this a bad thing to call myself, but I love the term and have now turned that negative self-talk into a positive pep-talk. So I say it again loudly, I AM A CHAMELEON! I am comfortable being a leader or follower in the workforce. I am comfortable teaching or learning in the tech field. I am comfortable being my own worst enemy as a QA and Software Engineer. I; jest, of course, but I am a mediator who can bridge the gap in a SCRUM master type role. I also have a way of saying what is a developing bug or an eye for it to make it easier for testers once I am in a developing role. I like having my shoe be able to fit in many roles in the tech world and I am a kid with wonder at what companies and roles will fill my next few years.
We all know by now Disney is and will remain my aim, whether first as a tester or not remains to be seen. Also, we know I want to be a Front End Developer and that day will arrive too. However, eye on the prize for two years is somewhere in the testing realm. Yet, I am ready to take on many hats with any project roles I assume while journeying with GenSpark just another great reason to be a chameleon.
Next Time
Unit 3 Redux and Context API. Why I understand React so well. Dealing with Tech Updates. The next may take a bit to roll out as I want to include some thoughts and with the new Redux Update I don't want stale ideas to populate my next article. However, if something comes up I will publish my thoughts on that beforehand.
Thank you all so far that have subscribed and to my future subscribers. If you are thinking about starting plan properly but don't get stuck planning. Keep moving forward!
Self-Starter in Remote Customer Service | Empathetic & Tech-Savvy | Passionate DEI Advocate
3 年Yes with this particular API call I realize that should probably be a forEach and not a map on displayData function as this returned one Object not an array of Objects like most API Calls but the de-structuring works the same regardless so I won't bother updating that as that is a Code Sand Box I made just to check if I could pull info from an API before use. ??