Algorithms accountability Pair Programming driver navigator Git GitHub Ruby yoga coaching Debugging Two Truths and a Lie Encoding and Decoding Smartphone Roman Numerals Numbers in Words Revision challenge for Roman Numerals Review: Review others and refactor your own Stretch: Try the following challenges Dictionary Sort Advanced Calculator Engineering Empathy (EE) – Introduction to mindfullness Enumerable’s, nested data, recursion part 1 Nested arrays Enumerable methods Dictionary sort Linear search Binary search Enacting enumerables Engineering Empathy: Deep dive – Sexism Stretch: Try the following challenges Pig latin pseudo code Binary vs. linear search Sort yourself Rubyists Destructive methods Samuel Beckett Recursion challenge EE meditation Intro to classes, stacks and queues Stack and queue Linked list Intro to objects OO basics – orange tree Watch the 20 minute video on Regular Expressions regular expressions challenge Review abstract data structures Stretch: Calculating subsets with recursion Ruby Drill: Prime Factors: Sieve of Eratosthenes EE meditation Intro to Games! Private vs public interfaces Racer Debugging techniques Boggle 1 Boggle 2 Battleship EE meditation Sudoku planning Sudoku part 1 Sudoku breakout Sudoku part 2 Review and Solidify Learning Stretch Forward Reflect Breathe
If, when reading through the above you go “What the …???”, well, that is kind of how the start of this week felt.
It has been a while coming but Week 1 of Enspiral Dev Academy bootcamp has happened. I should rephrase – I have had the pleasure of experiencing, and what an experience it has been!
Time is distorted once you start bootcamp. After only five days it feels like I have been there for at least a month. In the orientation, accelerated learning is talked about. I feel like the pedal has been through the floor this week with what I have learnt both technically and on a personal level. I am experiencing being a student who fully has to take ownership of their own learning.
There have been ongoing conversations around code when pairing with others, which we have done all week. As well as scheduled lectures and focused practices there have been informal conversations around Engineering Empathy:
Engineering Empathy (EE) is our emotional intelligence curriculum partially based off of Google’s program and book titled Search Inside Yourself. EE helps us create an optimal learning mindset and environment for our students by addressing the human side of software development. Through a series of lectures, exercises and routine practice we help students tackle difficult intra-personal and interpersonal issues that keep teams from operating to their full potential.
This has been fundamental in changing my focus on seeing what success is or means for me when working by myself and with others. It is not all about necessarily coming up with a working solution but the process of pairing and working with another human being in an effective and efficient way. And also to optimise the learning for both people.
I think one thing I would like is more time to be able to reflect. Sometimes useful reflection takes time and that is something we definitely do not have a lot of at EDA. With that in mind I am going to try very hard to continue doing these blog posts during bootcamp.
The reflection for us at the end of Week 1 is around guarding our ignorance –
It’s really hard for smart, hard working, passionate people to admit when they don’t get something. Our natural tendency is to guard our ignorance so that everyone thinks we’re competent. Effective developers expose their ignorance. Period. Read the Apprenticeship Pattern on exposing your ignorance and answer the following questions in your own journal.
1. When have you chosen not to expose your ignorance, and what impact did it have on your effectiveness?
I remember the feeling I had when I didn’t expose my ignorance, internal anxiety and stress but at the same time trying to hide it from everyone. I can’t think of a specific example right now but I definitely remember the feeling as it was so strong and overwhelming. It made me become ineffective as I wasn’t focused on what I was doing, rather on how I was feeling and what I was going to do to stop feeling that way
2. What are the 5 things you feel like you understand the least about computer programming?
Finding it hard getting my head properly around nested arrays and hashes. Algorithms. OOP. Recursion. There is heaps I don’t know and don’t understand! But I am just starting out.
3. What is the way you feel most comfortable exposing your ignorance?
Most of the time I am pretty happy just saying what I don’t know. I have learnt over the years that I feel better when I am open about my experience and what I know and don’t know. I hate getting stressed and if I am in a situation where someone thought I knew more than I did, I would be getting pretty stressed. I try very hard to avoid getting stressed, hence I am happy within myself to just say it has it is. Although, it can be quite difficult to do this in a place where there are people that come across as really confident. People who spurt off how good they are make it harder for those that think they don’t know it all or aren’t as confident or just aren’t as outgoing.
How do you deal with your ignorance?
Oh and I am feeling much better at the end of the week then I did at the start. It is going to be a mad, crazy, nuts eight weeks but I think it will be well worth the journey.