Showing posts with label Grit. Show all posts
Showing posts with label Grit. Show all posts

Friday, July 14, 2023

Pushing Through




My uncle was diagnosed with kidney cancer.
I found out an aunt and uncle cannot drive anymore.
I found out my friend with MS has digressed.
I found out another friend was diagnosed with Parkinson's.
My father has declined more than I thought.

Saturday, July 31, 2021

Thinking Time

I have noticed something about myself and the way I solve problems. Not always but, I tend to need a lot of time to think and play with ideas in order to arrive at a solution.

I played around with different ideas before arriving at the final idea, as well as the code, for the initial extensions I made


version 1.0


Today I finally made a Google Sheet that would reveal a part of the picture when you get the right answer. I have been playing around with that one for a week or so, and it just clicked today based on some Googling and some connections to prior knowledge. 

It didn't work initially because I had the code wrong. 
Then it didn't work because the image URLs didn't work.

After a few hours today, I got it to work and have a final product. 

version 2.0


I guess what I need to remember is that sometimes it is good to put projects on the back burner and return to them at a later time.

Here is the post on how I made the Google Sheet and a link to make a copy.

Sunday, April 30, 2017

Creating a Chrome Extension

The MYP Design course is really interesting for me. It is my first time teaching an MYP Course, and it is really fun. The course allows schools to adapt it to the resources available.

The flexibility brings about challenges as well; there is no set curriculum.

At KAS, we try as much as possible to give students assignments that allow them authentic experiences. When they learn about gathering statistics, students are asked to use multiple types of data collection. When they create a poster or a t-shirt for a club, I want them to actually print it. And when they code, I want them to make something they will actually use.

This brings be to last year.

We were coding, and I thought it might be good for students to apply the design cycle to a Chrome Extension. In the event someone had chosen that topic, I wanted to be able to help them if they got into trouble. So I started looking into how to make one myself.





At that time I completed the tutorial I found. In the end, no one chose to make one.

However, this year, more students are interested in learning about coding and there is a student who wanted to take on the challenge I set for him. 

I learned that the URL docs.google.com/create will make a Google Doc. I wanted to have a button to do this, instead of typing it in every time. 

One way to do this is to make a Bookmark. And I tried that. But the bookmark didn't have a favicon (image) and it looked a little dull. It was functional, but I wanted to have an image and I wanted to make a Chrome Extension.

So I did.

          
(Extension Links updated 2021)

I wish I could say that I understood the whole structure and was able to write it myself, but I wasn't. I was able to, however, understand enough to piece together snippets of code I found and realize what from the tutorial I did not need.


Maybe this is how coding should be taught. Maybe after having lessons in the basics, students should be given opportunities to take existing code and modify it how they see fit. 

It was exciting to see my app published where anyone can find it (after I get a few reviews, it might be listed higher). I think most of all, it was a good feeling to complete it after so many failures.