This week, delving deeper into Java with Coding Bat challenges has been quite a journey. It's been about revisiting the basics and exploring new ways to tackle problems using Java's tools. Each challenge felt like solving a puzzle—I started by carefully reading through the problem, considering different strategies, and jotting down ideas before writing any code. Planning things out helped a lot; it clarified my thoughts and made the coding part smoother. What worked best was breaking down the tasks into smaller steps and testing as I went along. However, there were times when I got stuck in overthinking or missed simpler solutions, which required going back and refining my approach. On average, I needed a couple of tries per challenge to get it right, but each attempt taught me something new about Java. Overall, these challenges have been a great way to warm up to Java again, boosting my confidence and skills bit by bit.
Posts
Part 1: Review Other Teams' final video projects JRS Consulting The video on predictive modeling has a lot of potential, but a few tweaks could make it much more engaging. Right now, there's a lot of text on the screen, which can be overwhelming for viewers. Summarizing the smaller topics and using more visuals or bullet points might help keep the audience's attention. Also, I noticed the volume levels varied between different presenters, which can be a bit jarring. Keeping the audio consistent would make the video flow better. On the plus side, the variety of predictive models covered is great, but presenting this information in a more dynamic and visually appealing way could really capture and hold the audience's interest. Bridge The video on robotics in the industry is pretty engaging overall. I liked how they designed the slides—it made everything easy to follow and visually appealing. They covered some really cool stuff, like NASA's robots and the innovations t...
Part One Looking back on our team's final research video project planning, collaboration was key to our success. We met several times to map out our tasks and responsibilities, making sure everyone had a role to play. We mostly communicated through Zoom and Slack, keeping each other updated and sharing ideas effortlessly. For the actual work, we used tools like Google Slides for presentations. While things went pretty smoothly overall, we did hit some roadblocks, mainly in scheduling and agreeing on creative details. Next time, I think setting clearer deadlines and expectations from the start would help us work even better together. Part Two As we near the end of the course, I've been happy with our lectures and videos, taking up invaluable insights along the way. Understanding the rubric for our video presentation was crucial. It gave me a clear roadmap of what's expected in terms of content, engagement, and collaboration. The Ted Talk videos were good, especially the one ...
Part 1: Help Your Teammates to Develop Capstone Ideas In our recent team discussion about possible capstone ideas, I proposed several concepts, including a smart waste management system, augmented reality navigation for the visually impaired, and biometric vehicle authentication. Adan, on the other hand, suggested using a Raspberry Pi for a parking garage management system, a home improvement application, and a self-refilling pet water bowl. Each idea presents unique challenges and opportunities for innovation. Personally, I find the augmented reality navigation system particularly intriguing due to its potential impact on improving accessibility and mobility for the visually impaired. I plan to further explore its feasibility and scope for our capstone project. Part 2: Keep Up With Your Learning Journal This week was a dynamic blend of academic and professional development activities. We ventured into website creation, setting the stage for documenting our academic journey and sh...