Drilldown: CapGrads
Use the filters below to narrow your results.
Be your own best friend. (1) ·
HAVE A BACKUP PLAN!! And a backup plan for that. But remember there is a such thing as too safe. Let loose but be prepared for failures and lessons. (1) ·
Make sure you plan out your capstone well, and set your goals reasonably accounting for personal work ethic. (1) ·
Start early and gradually work on it. (1)
It’s a journal comprised of multiple wild plant species. In this journal I explain the identifying features, the edibility of the plant, where to find the plant, and it’s various niche utilities. (1) ·
My original capstone project was to create an irrigation system for the plants in the Commons on top of the bookshelf. I designed the dropper, the base, end caps, the hose splitter, and connectors. I have my irrigation system put together on a metal shelf that I bought to finish the project. My irri (1) ·
We use computers every day of our lives, but have you ever stopped to ask what all the parts inside your computer do? I decided to tackle that question head on by having my friend and computer expert Maxwell Mahabir walk me through the process of building myself a new computer from the ground up. Be (1) ·
Well essentially its my photography portfolio. All images are black and white film dark room prints that have been scanned in; other than one color film negative scan. The portfolio had two goals for me: the capstone and submissions for OSAI Quartz Mountain. I can now proudly say both goals have bee (1)
A portfolio of my photography work. (1) ·
Essentially this journal was going to be the back up to a video of me camping in the wilderness actually eating these plants. (1) ·
My capstone project was an indoor irrigation system for the plants on top of the book shelves in the Commons. The irrigation system was to be automated and would only need for the reservoir to be filled every so often; everything else would be taken care of by the system. The system would run off of (1) ·
My original project was going to be a video game coded in C# with a team of two other people aiding in code, assets, and sound design. (1)
I expanded the journal with drawings and utility. (1) ·
It felt like I had to completely change my project. I had to downsize everything and almost start over. I lost the capability to set up the system how I had originally designed it. In order for the new system to work I had to completely change the way that the water was going to flow to the plants. (1) ·
The core of it went well and I'm pleased with my portfolio. However, as an extra thing I had wanted to include a video to play alongside my portfolio at the capstone booth that would've been essentially a sped up slideshow of all my negatives. They would be in order from freshman year to my senior y (1) ·
The game project would have needed more time for us to fully learn Unity and C#, so we were forced to switch to building a computer. This project was still at least in the field of computer science so it still applied to what I will go on to study in college. (1)
I did the best that I could with the time that I had. I made a system that worked and that watered my plants. It is not nearly as fancy or sophisticated as I had originally planned on it being, but I still made it happen and I am proud of it. It was a struggle and a half to completely spin and start (1) ·
I now know with great detail how all the parts in a computer fit together and can build a computer from the ground up without the assistance of my friend and mentor. (1) ·
I really love what I’ve made, even if it doesn’t blow you away on the surface, this journal could really morph into something amazing. Sic parvis magna. (1) ·
I wouldn't say I have any takeaways from the capstone itself, but I do think it served as a catalyst to hone in on my photography. (1)
Showing below up to 4 results in range #1 to #4.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)


