Drilldown: CapGrads
CapGrads > Capshortdescrip
:
Automatic irrigation system
or
Computer design and assembly
or
Learning various new artistic skills 
:
Automatic irrigation system
or
Computer design and assembly
or
Learning various new artistic skills 
Use the filters below to narrow your results.
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) ·
Pick something you love doing, but maybe something you don't know much about. Then you'll be able to have your school project and also have fun while doing it. There were many times I forgot I was working for a grade and I just enjoyed what I was doing, so it still turned out great. (1)
My capstone is based on the concept of seeing something you like, thinking "I can make/do that, too," and learning how to do it without spending much money. For this project I focused on resin, sewing, and propmaking (for cosplay). (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)
I originally described it as a furthering of talents I already had — learning composition for drawings and paintings, making my own molds and designing my own resin pieces, and learning how to sew better (I had basic knowledge before). (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 took away the composition stuff because I found the resin aspect to be way more fun. I also added propmaking because cosplay is something I love doing, and I love designing different aspects of characters that I can make myself. A lot of the projects I had planned had to be cut simply because I di (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 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) ·
Resin is way more finicky than I ever imagined. It's also not safe to touch without gloves. That was a good scare. Also, fur fabrics are the bane of my existence, but they're worth using because they cover up seam mistakes (also if you use the right ones, they're such a nice texture!).
I also lear (1)
Showing below up to 3 results in range #1 to #3.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

