Reading traceback messages to resolve invalid syntax in Python requires diligent investigating
Creating a unit test in Python and executing it with a test runner like unittest differs from creating one in Ruby with RSpec
Feeling a sense of belonging is dependent on the quality of experiences within any given context
Connecting across differences starts small
Cross-cultural learning is continuous
Starting points for learning are often helpful
Mapping learning is necessary
Conversations can help map learning or exploration
Immersion and experiential learning require adaptability
Python code follows conventions outlined in PEP 8 (Python Enhancement Proposal 8)
Using a YAML validator brings up informative error messages
Creating a template document in markdown to add it to a process is never a bore to me
Tools can support or hinder you if you do not have enough context. You need just enough context to be able to use them
Writing integration tests in Rails is a fantastic way to try out different use cases for applications
Solving a technical challenge in fewer lines of code makes a difference
Running a test suite and working through error messages before tests pass is fascinating
There isn’t an equivalent to the Ruby switch statement in Python. From version 3.10.0, the Match Statement in Python is all I could find
This is where you will find some of my coding experiments.
Familiarising myself with C#
