nucamp week 3 workshop assignment

a better way to camp

Reserve a campsite.

Breadcrumb Trail Campground

Let Nucamp be your guide to this off-the-beaten-path, hike-in-only campground.

Nestled in the foothills of the Chrome Mountains, this campground on the shores of the pristine React Lake is a favorite for fly fishers.

Spend a few sunny days and starry nights beneath a canopy of old-growth firs at this enchanting spot by the Chrome River.

Discover & Review

Our Campsites

Explore our growing database of curated campsites and leave your own reviews!

Featured Campsites

React lake campground.

Our Community Partners

Bootstrap Outfitters

Bootstrap Outfitters supplies you with gear you need at prices you can't beat.

Instantly share code, notes, and snippets.

ProbonoBonobo / test_pyfun_workshop_2.py

• Download ZIP
• Star ( 1 ) 1 You must be signed in to star a gist
• Fork ( 1 ) 1 You must be signed in to fork a gist
• Embed Embed this gist in your website.
• Share Copy sharable link for this gist.
• Clone via HTTPS Clone using the web URL.
• Learn more about clone URLs
• Save ProbonoBonobo/a424fc5e7733cec5865c17918b976a6a to your computer and use it in GitHub Desktop.

NuCamp BootCamp – Notes: Table of Contents – Bootstrap

NuCamp Full Stack (Class Notes) – Bootstrap

Note to readers from CS: These notes are very detailed, but also contain stuff that is missing from NuCamps Videos. They are not a substitute for the class. Tests have been left. Other things have been added to make things easier to understand. If you want to really learn take the class. It is worth it! Beware, what you put into the class is what you get out.  Be sure to use my referral code ( WWJSU4 ) if you sign up for a class!

Week 1: Intro to Bootstrap 

• Bootcamp Notes – Day 1 (Mon) – Bootstrap: NuCamp Bootstrap Begins!
• Bootcamp Notes – Day 1 (Mon) – Bootstrap: Using Git
• Bootcamp Notes – Day 2 (Tues) – Bootstrap: Node and NPM
• Bootcamp Notes – Day 2 (Tues) – Bootstrap: The Web Development Stack and Git
• Bootcamp Notes – Day 3 (Wed) – Bootstrap: Responsive Web Design
• Bootcamp Notes – Day 3 (Wed) – Bootstrap: The Bootstrap Grid
• Bootcamp Notes – Day 3 (Wed) – Bootstrap: Adding Custom Styles & Bootstrap Alignment Classes
• Bootcamp Notes – Day 3 (Wed) – Bootstrap: Glossary Week 1

Week 2: Bootstrap CSS Components

• Bootcamp Notes – Day 4 (Mon) – Bootstrap: CSS Components
• Bootcamp Notes – Day 5 (Tues) – Bootstrap: Display Content
• Bootcamp Notes – Day 5 (Tue) – Bootstrap: Glossary Week 2

Week 3: Bootstrap JavaScript Components & More JavaScript 1

• Bootcamp Notes – Day 6 (Mon) – Bootstrap: JavaScript Components
• Bootcamp Notes – Day 7 (Tues) – Bootstrap: Week 3 Glossary
• Bootcamp Notes – Day 8 (Wed) – Bootstrap: JavaScript Fundamentals
• Bootcamp Notes – Day 9 (Thur) – Bootstrap: JavaScript Fundamentals – Making Decisions

Week 4: Web Development Tools & More JavaScript 2

• Bootcamp Notes – Day 10 (Mon) – Bootstrap: Bootstrap and jQuery | CSS Preprocessors & Sass
• Bootcamp Notes – Day 11 (Tues) – Bootstrap: Building and Deployment: NPM Scripts
• Bootcamp Notes – Day 11 (Tues) – Bootstrap – Week 4 Glossary
• Bootcamp Notes – Day 11 (Tues) – Bootstrap: JavaScript – While and For Loops and also Arrays

Week 5: JavaScript Advanced

• Bootcamp Notes – Day 12 (Mon) – Bootstrap: JavaScript Advanced
• Bootcamp Notes – Day 13 (Tues) – JavaScript Variables: Var, Let, Const
• Bootcamp Notes – Day 14 (Wed) – Week 5 Glossary
• Bootcamp Notes – Portfolio Project – 2021

To see the Nucamp campsite working live on a web server go here to see it!

To see my nucamp portfolio project go here to see, project code examples here at codepen (look at only if you get stuck on project. also note codepen does not display the work properly as you will see. you still need to build everything in vs code):, contactus.html, aboutus.html, bootcamp notes – day 3 (wed) – bootstrap: glossary week 1, orlando east region outdoor service, related posts.

CNET Top 5 – Tech turkeys of 2013

Hands on with CES 2014’s craziest human interfaces

MailtoPro | Advanced Mailto Links for WordPress

You may have missed.

BEYOND THE RESET – Animated Short Film – That Exposes Great Reset! 1 Million Views!

Project Veritas’ James O’Keefe Discusses State Of Journalism, Details Defamation Lawsuit Against NYT

China’s Real Estate Crisis Spreads To The US!

Orlando Church of Christ Sunday Service

DFW Church Service 01/23/20222

Jon Favreau Reveals Horrible Story Of Kathleen Kennedy! NEW Details Arrive (Star Wars Explained)

AngularJS is Dead

Love Perseveres | Story of the Week

Goldman Sachs Just Collapsed!

STACKr News Weekly: Web Dev 2022, JS One-Liners, 3d JS

Privacy overview.

Get the Reddit app

Welcome to the original programming bootcamp subreddit! We're back in 2023 and ready to grow the community again! This community supports thoughtful and authentic discussions about programming bootcamps, immersives, apprenticeships, and online education. Please read the rules before posting and commenting. Feedback about the community is always appreciated and cherished so please share with the moderators.

NuCamp Full Stack Web Dev Bootcamp Review

Updated April 2020 at end of post

I'm currently taking the Full Stack bootcamp with NuCamp (November 2019 - April 2020) I'm not living in a big city, so I'm taking the online version where we use daily.co for the Saturday workshops instead of meeting at a co-working space. My fellow students are scattered across the states, and I appreciate the diversity. The online version of the Saturday meetings suffices, but honestly I'd rather meet with other students and my instructor in person if I had the choice. That said, I'm learning quickly and can reach out to my instructor and the NuCamp community by Slack whenever I have a question or find something useful to share with the group.

Right now I'm on week 4 of the Bootstrap course, and am redesigning a website for a past employer. I'm motivated to apply what I learn in the coursework to my own portfolio project. The coursework only takes me an hour or two a day to complete, but I've already spent much more time this week building my website. Real experience writing code and reading documentation to troubleshoot/understand how each component works takes a lot of time, but my results are proof that I'm learning!

If you're unmotivated or busy, it could be easy to sneak through the curriculum at NuCamp just to get a passing grade. If you're starting from zero, expect a steep learning curve. I feel like a kid with a new set of legos, and have too many ideas for what to build with my new toy. Each project I add to my portfolio gets me closer to my goal of obtaining freelance work in some area of web development.

My instructor keeps recommending that we learn as much javascript as we can ourselves on the side during this BootStrap course. He says once we get to React, we'll thank him. NuCamp also recommends setting aside more time each day (5 hours!) during this segment of the bootcamp, a sign that the material will be more difficult.

Anyone free to message me if you have any questions about my experience at NuCamp, I'm happy to chat.

If you decide to sign up, my referral code is: GW9PKP

EDIT: The backend course was a complete letdown. I've watched free videos on youtube that were made with more care. I started keeping track of all the times the video was "patched" sloppily to update the material. They'd overlap and repeat sentences and the volume would get louder or quieter. Beyond this, my instructor ditched all review for weeks 3 and 4. The backend course is only 4 weeks long, so effectively half the course was skipped over. After a week or two of non-response from Nucamp, and emailing at least 3 different points of contact, I was offered a partial refund or the opportunity to retake the course in late May.

To top off my bad experience, they just sent out an email to me with a list of 87 other students. You'd think a school teaching web development might now how to respect their student's privacy.

It's pretty clear that after you make your last payment, they stop caring.

By continuing, you agree to our User Agreement and acknowledge that you understand the Privacy Policy .

Enter the 6-digit code from your authenticator app

You’ve set up two-factor authentication for this account.

Enter a 6-digit backup code

Create your username and password.

Reddit is anonymous, so your username is what you’ll go by here. Choose wisely—because once you get a name, you can’t change it.

Reset your password

Enter your email address or username and we’ll send you a link to reset your password

Check your inbox

An email with a link to reset your password was sent to the email address associated with your account

Choose a Reddit account to continue

Layla Rowen

#acodingjourney.

Not every webpage needs to be built from a fancy framework.

Just like we don’t use a hammer to place a tack, not every website needs to be built with React/Angular/Vue/Ember, or what have you. Sometimes a simple html file with <style> tags holding css is enough.

Why build with more fluff than you absolutely need, anyway? Isn’t there also a need to keep websites lean and fast?

Well, it’s still early as of this blog post, but here’s the result of some serious simplification of my sister’s website: https://www.joyofquiltingart.com

It will likely change, and maybe by the time you click that link even, but that’s how the internet is, isn’t it? Things just keep changing.

I do find myself missing the re-usability and organization of React Components, so I’ll definitely come back to those but this is a good reminder that just because you can use a tool doesn’t mean you should .

Tools are for using when they’re the right thing for the task.

Custom Remarkable Templates

Following this tutorial video , I’ve created and added some of my own custom templates to my Remarkable tablet!

I used Mac OS Paint S to create the PNG file and CyberDuck to SFTP in. It was surprisingly simple to follow along:

• start up the SFTP connection using the username, password, and ip address found on the Remarkable
• save a backup copy of the whole /templates folder just in case!
• copy the .png file into the templates folder (usr/share/remarkable/templates)
• update the .json file with the template’s name, filename, and categories in the same format as all the others

I just need to remember that the dimensions of the file had to be 1404x1872px.

Looking forward to making my Remarkable tablet even more useful.

This is the template I made, based on the 54321 planning method of thinking backwards through what I want to accomplish and what I can do, starting now, to get there.

That’s one of the tools that helped me make my decision in January to start attending Nucamp Coding Bootcamp in March.

CascadiaJS 2020

First, an opening speech by Claudius Mbemba openly acknowledging race and the Black Lives Matter movement. Even some book recommendations: So you Want to Talk About Race , and How to Be Anti-Racist . This fit so perfectly with the rest of the welcoming atmosphere at CascadiaJS. It wasn’t in-person, but the sense of togetherness and humanity was definitely still very present.

Another significant theme I noticed was an emphasis on accessibility. There were 3 talks each day that talked explicitly about how to make tech accessible. In particular, Jemima Abu (Understanding Accessibility as a Concept ) insisted that accessibility is usability, and that it is everyone’s job to ensure accessibility. Even the first version of a product should have accessibility in mind because otherwise, it will be unusable to a significant number of people!

The talk that intrigued me the most dipped into the “DWeb”, or Decentralized Web, by Kelsey Breseman . The idea of no longer being dependent of large companies hosting massive servers, and that profit from our data that we freely (or pay to) provide, strikes a chord with me. I’ll admit I didn’t fully understand a lot of the content of her talk, but I have been digging into it since.

Joel Hooks also suggested the idea of building a “digital garden”, a space to learn in public and to keep a collection of notes for yourself about what you’re learning. He mentioned a few ways to make it easier to document your learning:

• Piccalilli has a tutorial for 11ty here.
• dabble.me to privately journal via email prompts
• typoria.io to easily write markdown for journaling via gists on github or on your new 11ty site

Even now, as I pull up those links I’m getting side tracked with fascinating rabbit holes…

I also enjoyed Shaw Wang’s (or @swyx on Twitter) talk about The Operating System of You . He compared our body maintenance to the maintenance of our electronics, and also preached learning in public.

On day 2, I especially enjoyed Pantelis Kalogiros’ talk on Constrained Creativity , described as “a way to achieve a novel effect or goal that is not otherwise possible using conventional, readily accessible methods.”

Then there was Rahat Chowdhury’s Building Better Communities with Mental Health Support . He pointed out that there’s a tendency to romanticize scarcity, burnout, and hustle culture; that there’s never enough, and that you’re not good enough unless you’re putting everything into your work. “We don’t suffer alone. We suffer in silence.”

The last speaker, Fred K Schott wondered aloud what’s next with “Snow Pack, Webpack, and the Third Age of JavaScript”. He argued that we’re already in the “third age” with ESM (or ECMAscript ) and that Svelte might be the next evolution after React. Of course, now I’m intrigued by Svelte, too.

You can find the list of all the events with links about the speakers here. They are still adding more content, such as the recording and the slides from the speakers: https://2020.cascadiajs.com/#schedule

.then(…)

Now that I’ve officially graduated, my next steps are on me.

The last few days were a whirlwind and a rush, and then graduation happened… and now what?

Well, I’ve got Souvien live as a very basic demo page with a json file of lorem impsum entries. Here’s Souvien as a demo page !

There’s still a long way to go, and I’m realizing that the user data storage issue is bigger than I realized at first. So I’m going to work on a few other, simpler projects for a while before coming back to this.

Most importantly, proof of it is live.

Next is building more projects, putting them on a portfolio page, and attending virtual networking events, like CascadiaJS !

Reacting to Node.

It’s been about a month since I’ve finished the React Native course, which completed the Front End section. We even had a Zoom-based graduation ceremony. During the React Native course I felt drawn to the idea of building apps… but I kept remembering my React instructor’s commentary that React Native is somewhat exclusive in nature. It is for app stores. Whereas, React can be accessible on all devices, and is designed with accessibility in mind. So my dreams of becoming an app rock star faded when I finished the course. But I did build out that cool Nucampsite app alongside the course material.

I found the emulator to be a be heavy on my computer, so usually just used the Expo app on my phone instead. The magic of having an app in development and running on my phone was mesmerizing.

In React, I built out the same Nucampsite content into a very cellphone oriented app. It wasn’t quite the same magic, but it held the same content and functionality.

Which brings me back to my dream of this journal app. I’ve started it back up in React, and now that I’m learning “the back end” (aka Node, Express, Mongo, Mongoose, Passport…) I’m developing a server and database to go with it. They’re living together in a Github Project .

Right now, my app looks far from finished…

It’ll get better. Promise.

Now, this server-interacting-with-a-database stuff… I’m starting to get stuck less often. And when I do get stuck, I feel less stuck. Patterns are popping out, intuition around where to look next and why a thing is breaking is starting to develop. So cool.

Sure, I still get those “What the heck am I suppose to do here?” moments, too. However, when I typed up and exported a verifyAdmin function in my authenticate.js file , while screen sharing with my classmates I was sure I couldn’t have it right, and I embraced making the mistake while they watched. But it worked.

It keeps the privilege of deleting all campsites in the database to users with admin status only.

One week left of this course and the bootcamp. My final graduation ceremony is on August 3rd. Coursework due July 25th, and portfolio project due July 29th.

Gotta get my app up and running, pulling data from the server. I’ll post again when it’s done.

When something doesn’t work right, you need to ask, “why?”. When you can’t figure out “why”, you need to ask yourself how you can find out. When you can’t figure out where to look… ask what haven’t you tried? Where haven’t you looked? What did you do before it broke? What have you tried before that worked? What parts make sense? What patterns can you see?

It’s a skill to ask the right questions. And you’ll need it, frankly, for whatever challenge you’re facing, code-related or not.

There will be times when you don’t even know what to ask next. That’s when you ask for help. The general guideline is to give yourself 20 minutes to try to figure it out first. Then definitely ask for help. There are so many folks out there that want to be the person to help you figure out your problem. Not only is it satisfying to help someone, it seems a lot of us are in it (at least partly) for the satisfaction of figuring things out.

I’m just about to start week 3 of my React Native course (how is it already week 3 of 4??) and it’s getting trickier. The workshop assignments (what we work on every Saturday are leaving more challenging tasks for me to figure out. I cranked out the first 2 tasks of the latest assignment, then spent a lot of time struggling, trying new things, just to get that third and last part of the assignment to work. I kept thinking, “I’ll ask a classmate” but then I’d come up with another question, something else to try.

I commented out the code I thought was causing the error, and that proved the failure was in that section – it turned out I’d imported components from the wrong library. Oops!

Then there were more errors — every new error is cause for celebration because it means the old error is probably solved, and there’s a new puzzle!

Eventually, I didn’t get any more errors. It just wasn’t doing what I needed it to do.

I used console.log() (sometimes I call it “console.clog”) and alert() to test the values that I’d been passing and returning, changed where I put my variables, changed how I referred to variables, checked code where I’d built similar functionality, scrolled through Slack and Stack Overflow looking for someone struggling with the same thing, re-checked the assignment wording, traced the relevant functions and variables through the application (maybe there was a typo?!), restarted Expo, pushed myself to really try to understand what each part was expecting from the other parts…

Eventually I did ask for help from a classmate, but didn’t get a response – it was already late into the evening. So I went to bed annoyed that I still hadn’t figured it out.

The next morning, determined to figure it out, I continued asking where the code and I didn’t line up. I wasn’t understanding something. I’d narrowed it down to which file the failure was in, and even which function it was probably in. Continued using alert until I got the right values returned, then I knew how to assign them where they needed to go.

But wait, one of the values wasn’t quite right – I still hadn’t properly assigned the new comment’s id the value of the length of the array of already stored comments. It was still returning 0. I’d forgotten to refer to the comments array with state.comments.length. I’d been trying to call comments.length in the reducer(? still fuzzy on specifics of which parts are called what).

And wow. It felt so good I spend a little extra time to look around for custom alerts, which, naturally, React Native has one ready for import.

If you’re just starting out on your coding journey, know that you will learn a lot about how to ask the right questions. Also, it’s good to ask. Please feel free to ask me if you’re here and you’ve been stuck for over 20 minutes with no more questions coming to mind — I’m one of those that enjoy the solving as well as the helping!

In the weeds with bugs.

Coding is like gardening.

Sometimes it’s hard to get started because you know you’ve got so much work ahead of you. But after a few minutes of picking weeds it’s hard not to grab the next one. I mean, it’s right there .

30 minutes later you’re elbows deep, brow sweating, and “just one more” with a list of 3 more things you want to check on or maintain, one more segment of morning glory root to dig out.

An hour later you’ve forgotten to take a water break.

4 hours later you’ve pulled out two buckets full of morning glory roots in favor of strawberry plants…

Ok. That’s not always how coding or gardening goes. But sometimes it does. All it takes is opening up the file, opening up the door, pulling one weed, trying to fix one bug or add one tiny feature. If I’m struggling to warm up to coding (or gardening!) and haven’t touched it yet that day, sometimes all it takes is committing to change one little thing (even if it’s just aesthetic or maintenance). Since it’s all so intertwined, one thing usually leads to another.

Nearing the end of Nucamp’s React course (this is week 5 of 5! Next is a week “break” and 5 weeks of React Native), I’m still not sure about what each part of a React app depends on from other parts. I don’t understand it all. I’m following along and trying to build things out and research or ask questions.

I understand it like I understand Latin — some of it is familiar, and I can read and parse some of it, but generating whole useful chunks of it is tricky without referring to a working model… I feel like I’m just keeping up.

But I keep opening up the coursework, my portfolio project, and articles. Chewing on a little bit at a time. Every time I get stuck, I figure something out. Sometimes I pull a little of my hair out before I get there, but so far I keep getting there. My confidence is slowly thickening. My neurons are getting more and more familiar with the intricate parts involved.

Reaching out to help people earlier on in their coding journey, I’m finding that I now know some JavaScript bits like the back of my hand. What’s the basic template of a for loop? An object? A while loop? How to create a new class? These things are familiar now because I’ve kept coming back to them.

You can’t get strawberries from your backyard if there aren’t any planted.

I’ve sat with this blog post open and empty for days now. I started with the first sentence, sure I was just jotting down a note for later. The rest came out shortly after.

Alright, enough procrastination. Gotta start Week 5. First up: “Welcome to Week 5” video. Baby steps!

DOMing and Reacting

Got a head start on my React course, prepared for class yesterday, but somehow I forgot that I have another week until our first workshop. (Whew!) So now I’m working on getting even further ahead.

Since I’ve finished my Nucamp curriculum up to the workshop project that is intended for the Saturday workshop, I have dipped back into my freeCodeCamp lessons. There are a lot of parallels in tools, but I’ve found the resources to be very complimentary — the SCSS lessons are completely different between Nucamp and freeCodeCamp, for example, so it’s not just repeating the same.

The way the fCC React lessons describe JSX, the markup language in React, reminds me of SCSS, in that it is a way to more dynamically write to html through JavaScript code. Like this:

JSX => html

SCSS => CSS

Of course, I stumbled upon another reference to the DOM , too. Which reminded me that I still didn’t fully grasp what that really meant. Sure, it stands for Document Object Model, but that doesn’t actually clear much up. Another search lead me to Chris Coyier’s article on CSS Tricks . Finally. I can sum it up like this: The DOM is basically the html that renders after everything else compiles.

There have been some people in the Slack chat offering Nucamp feedback that the last two weeks of the React course, when Redux is thrown in, is far more intense than previous weeks. Sounds like it gets clearer in the next course, React Native, but feels like a lot at first.

So I’m doubling down on getting ahead where I can. Why not?

Ultimately, I feel like I’ll always be behind in that there is always so much more to learn (which is really exciting, too!). But every little gem I stumble upon feels like a beautiful addition to the tangled puzzle of languages that make up coding.

The End of Bootstrap…

Until I open my code up again, that is!

Well, I’ve officially finished the Bootstrap class in my Nucamp bootcamp. It’s the first of 4 classes in a 5 month program. In case you’re looking to support me, my reference code is L0ZUC5. It gets me $50 for sending you their way if you sign up, too.

My review of the Bootstrap class, the first of 4 in the Full Stack program, on Course Report .

In short, at this point, I would recommend this set of courses for folks that are interested in having structure and are willing to fill in the gaps with their own passion. There are a lot of things left optional, perhaps more so that the program can be adaptable to different students’ needs, but if you disregard something because it’s optional, (like partner work, or using Github) you risk missing out.

While working my way through the coursework, I definitely appreciated the structure. So much of the content felt familiar, though from a while back. It was good to review and pull it all together. Some of my classmates were picking it up for the first time, though, so if you aren’t familiar with it, don’t despair!

While working with a partner was optional, I chose to because it can be the hardest skill to build, especially remotely. Everything else can be figured out with a web search, but partner work takes lots of practice, communication, and relationship building. Bonus: I need all the allies I can get in this work. I imagine REACT will be an even trickier set of knowledge to attain than Bootstrap has been, so I’m even more grateful that I now have a working relationship with my partner, and we’re continuing on in the same cohort together.

My partner and I built a basic website to display and possibly allow the sale of quilt art. It still needs work, and every time I pull it up, I feel a bit of excitement about the next part I want to build. That and having a partner that I’d be happy to pair with again, is the best outcome I could have asked for.

Both incredibly challenging for us as beginners, but also full of so much potential and natural documentation, we used github to collaborate on issues and slack to chat regularly. I learned how to use my README.md file for leaving breadcrumbs for how to install all the necessary dependencies for future users (aka my partner and instructor) — though that was something I did independently from class, and I think I’ll do it prettier, with markdown, next time.

Still on our todo list (issues in our Github repo!):

• Include actual blog posts from Jamie herself, whether via RSS feed or by having a back-end for her to upload her blog content
• Add ability to email Jamie to request a commission
• Add price estimator functionality to commissions page (where the radio buttons are, and result displayed when modal pops up)
• Update with various pictures, more informative text
• Update format of display to be a bit more creative

I’m sure I’ll come up with more…

Always Forward

Alright, it’s been a while. Almost 3 years, even. I’ve been spending my time and energy digging into and enjoying my dream job in the field I have on and off enjoyed, but which I would necessarily need to leave in order to become a full-time coder.

While I haven’t been coding, I have been working on other relevant skills:

• problem solving
• listening to (and looking for) others’ perspectives
• self-reflection
• pushing through challenging situations
• community building
• networking between colleagues
• explaining my understanding in a way that others less familiar with the subject can understand
• acknowledging and working through my own mistakes

All of this is crucial to being an educator of 2 year olds (and the k-3rd graders I’m working with this year). These skills are crucial to any successful team.

On top of these skills, I’ve also developed greater understanding of what a quality work environment should be and higher expectations from any future employers. In the past, I’ve accepted many things in an employment situation that I would not tolerate now.

The employee/employer relationship is a partnership.

So, armed with these strengths, I take my next step into the realm of code: I’ve joined a bootcamp.

My current job is still wonderful. I love the people, and I have found many creative ways to use my non-educator skills, too. Along with the soft skills, I’ve initiated and progressed these cool things:

• increased colleague cohesion
• staff collaboration on time of day cross-classroom activities
• increased staff self-advocacy
• Wrote a published piece about workplace conflict
• Facilitated discussions at our full-day professional development events
• Set up an emergency spare clothing stash for adults -’cause we get kids’ body fluids on us, too, sometimes
• increased ridership significantly!
• after building momentum and training a team how to use Libib, our library has become organized and has a fully functional patron check-out system
• Practiced good documentation habits (of the children’s learning!)
• How to take over the Step Up Coordinator role (aka community project manager)
• How to find our school-wide calendar in Microsoft Outlook
• How to set files to display in tiles in both Microsoft Sharepoint and then in Teams, too
• ordered weekly supplies while managing food budget
• added mini fridges
• added cutting boards and knives for easier snack prep
• developed an interactive spreadsheet for generating quarterly menus based on cycling weekly meals
• trained the kitchen manager in new recipes
• generated and incorporated feedback from many surveys of staff and families regarding food quality and preferences
• Managed materials library contents and budget
• Managed classroom budget
• marker recycling program
• field trips guide
• developing a natural materials and loose parts library
• social coordinators
• provocation binder
• Learned enough basic skills/tools to cover the bookkeeper’s week-long vacations

As you can see, I haven’t been doing nothing.

This school has offered me so much opportunity.

This partnership has been mutually beneficial.

I’ve loved this partnership. I chose to run with Nucamp , a part-time 5 month-long program to regain traction, so that I can maintain my current, wonderful job for as long as it takes to transition to a different career that I still know that I want to be in.

We’ve just finished the second week of Nucamp’s Bootstrap course, and while it started out familiar and easy enough, I’m already feeling the increase in challenge. We meet every Saturday to review the week’s tasks and to work through another piece of an ongoing website building project. Though, right now, that’s online, too. Thanks, #coronavirus.

So here I am, with more coding story to blog about again.

Ever onward.

• Already have a WordPress.com account? Log in now.
• Subscribe Subscribed
• Report this content
• View site in Reader
• Manage subscriptions
• Collapse this bar