 For the circuit python part today, what I wanted to do is show how we can account for different microcontroller boards inside of one piece of code. So as you can see here, I have a whole bunch of different microcontrollers. They're all running the same code. But the code is aware of which board it's running on and therefore can accommodate four differences where we have dot stars versus neopixels, one neopixel versus many. And so the way we do this is we're importing time and board and we're importing OS. Using os.uname.machine command, I'm able to set this variable called board type, which just asks the board, hey, what type of board are you, which returns a string, then we can do things like if the word trinket was in the board name, set it up as a dot star. If QDPiM0HackPress was in the board name, set it up as a single neopixel. If it's a macro pad, we're going to use the actual macro pad library to talk to the whole set of 12 neopixels. This is what happens at the top of the code. We figure out which board we're using and then we set things up and port libraries, do what's necessary for that board. Then inside of the main loop of the code, I'm checking a variable I created called LEDStyle. So some of these actually are pretty similar once they've been set up. If it's LEDStyle 1, it's going to use a dot star. If it's style 2, it's going to use however many neopixels are on there. If it's the style 4, we know it's the macro pad and we're going to use some different code for that. Now you can see this in action. I'm going to change this to be just pure green. I'm going to save that file. Now you can see over here in the finder, just copy the code one at a time. So we'll go to the circle playground, blue fruit. I'll hit save. Now you can see that blue fruit board is a green set of neopixels. If we drop that onto the macro pad, replace, and you can see here I'm not having to save eight different code.py files. I can use them all on any of these boards because we have accommodated for their differences. This is really useful for display based boards such as the FunHouse and the macro pad and PyBadge, PyGamer, anything that has a display on it. There's going to be some differences in how you set those up. So that's one use case for this. And so that is how you can accommodate for different boards inside of your code.py, inside of CircuitPython. And that is your CircuitPython Parsec.