Kristin's Blog

During my OWASP Juice Shop project, I spent a lot of time testing for vulnerabilities, and Postman became one of the most useful tools I worked with. As I’m building my skills in web application security, Postman helped me understand how client-server communication works and how I could use that to identify and exploit potential weaknesses.

What is Postman?

Postman is a platform for testing APIs. It lets me send requests and inspect responses in a clean, easy-to-use interface. Instead of working through a browser or command line, I was able to customize HTTP requests, set headers, cookies, and payloads, and then view the exact response coming back from the server. This was especially helpful when working on vulnerable applications like Juice Shop.

How I Used Postman for OWASP Juice Shop

In Juice Shop, I was testing several types of vulnerabilities, including SQL Injection, Cross-Site Scripting (XSS), and Authentication Failures. One of the most effective ways I used Postman was to test how the application handled user authentication and authorization.

For example, I used Postman to capture the login request and observed how JWT tokens were generated. After logging in as a standard user, I tried modifying the token and using it to access administrator-only endpoints. I also experimented with sending unauthorized PUT requests to change user profile data, and Postman made it easy to repeat these tests with small changes in payload or headers.

By adjusting parameters manually and observing how the server responded, I could better understand where the app was vulnerable and what could be done to patch it.

Why I Found Postman Useful in Security Testing

Postman gave me more control than browser-based testing. I could clearly see how the backend was responding to my inputs, and I didn’t have to rely on guessing. It also helped me document my process. I saved collections of requests and labeled them by vulnerability type, which helped me keep track of what I was testing and how.

It also allowed me to move at my own pace. If something failed, I could tweak one part at a time and figure out why. That kind of learning experience would have been harder to get using only automated scanners or browser tools.

Final Thoughts

Using Postman with Juice Shop helped me build confidence in both API testing and manual vulnerability analysis. It showed me how important it is to understand what’s happening behind the scenes and gave me hands-on practice with real-world concepts. As I continue working on web security projects, I know Postman will continue to be part of my toolkit.

As I wrap up my Website Security Research Project, I’ve been reflecting on my personal journey—what I’ve learned, the challenges I faced, and how I overcame them. Working on this project solo meant I had to take full ownership of the research, testing, and implementation, which was both a challenge and an opportunity to grow.

Biggest Challenge & How I Solved It

The most difficult challenge I encountered was bypassing payment validation for the Deluxe Membership. Initially, I struggled to understand how the web application processed transactions, and I wasn’t sure where the vulnerability existed. By analyzing HTTP requests, modifying parameters using Burp Suite, and researching real-world payment bypass attacks, I eventually found that the system relied too heavily on client-side validation. The fix? Implementing strict server-side validation to ensure that transactions couldn’t be manipulated through direct API requests.

Did I Have Doubts About Completing the Project?

At first, yes. Security research can be overwhelming, and I questioned whether I would be able to identify and exploit vulnerabilities effectively. However, as I started breaking the project into smaller steps—learning how to conduct XSS attacks, test for SQL injection, and simulate CSRF attacks—I became more confident in my ability to analyze and secure a web application. Now, I feel much more capable of approaching security challenges systematically.

What Would I Do Differently?

If I could start over, I would have planned a structured testing process earlier. Initially, I explored vulnerabilities in an unorganized way, which made it harder to track findings and document fixes. A more methodical penetration testing framework—perhaps using OWASP’s testing guide—would have made my workflow more efficient.

Key Takeaways from the Project

1. Security is a continuous process—fixing one vulnerability doesn’t mean the system is secure.
2. Client-side validation is not enough—attackers can easily modify requests.
3. Burp Suite is an invaluable tool for web security testing.
4. Understanding how attackers think is crucial for building secure applications.
5. Documenting findings from the start saves time later when implementing fixes.

Final Thoughts

This project has been challenging but rewarding. I’ve gained hands-on experience in ethical hacking, penetration testing, and secure coding, which has strengthened my technical skills. Going forward, I plan to continue learning about advanced security threats and defense mechanisms to further enhance my understanding of cybersecurity.

As I dive deeper into the development process of this project, I’ve had the opportunity to explore several technologies that have been both exciting and challenging. Here’s a reflection on the tools and platforms I’ve been using, what I’ve learned, and what I would do differently if I could start over.

Favorite Technology: Developer Tools (DevTools)

One of my favorite tools throughout this project has been Chrome DevTools. It’s such a powerful utility for inspecting, debugging, and even exploiting web vulnerabilities during testing. For example, I used the Network tab to analyze API calls and inject payloads to test for XSS vulnerabilities. Watching the changes I made in real-time gave me a sense of control and instant feedback, which is immensely satisfying as a developer. The intuitive interface and immediate results make DevTools a clear winner for me.

Least Favorite Technology: Validator Library

While the validator library is essential for sanitizing inputs and enhancing security, it wasn’t my favorite to work with. Initially, I found it frustrating to understand its API and implement it correctly across multiple input fields. However, as I used it more, I appreciated how it became a cornerstone for securing the application against injection attacks. It’s a “love-hate” relationship, to say the least.

Technology with the Most Difficulty to Learn: Input Sanitization

Learning how to sanitize and validate input correctly was a steep learning curve. Initially, I underestimated how intricate this process would be. The idea of escaping harmful characters seemed simple, but implementing it consistently throughout the application—from database interactions to API endpoints—was a challenge. Now that I understand its importance, I can confidently say it’s a skill I’m proud to have gained.

Technology I Would Change: OWASP Juice Shop Configuration

The Juice Shop is an incredible platform for learning security concepts, but I found its configuration process to be unnecessarily complicated. From npm dependencies throwing vulnerabilities to the lack of a proper build script, getting the app up and running took longer than expected. If I could change anything, I’d streamline the setup process and ensure all dependencies are secure by default.

Easiest Technology: npm and Node.js

npm and Node.js were surprisingly easy to learn and use. I appreciated how straightforward it was to install dependencies, run scripts, and manage the application lifecycle. The modularity of Node.js’s ecosystem made debugging and customizing the Juice Shop environment far less intimidating.

A Technology I Wish I Had Included: Docker

Looking back, I wish I had included Docker in the tech stack. Using Docker could have standardized the environment across machines and minimized configuration issues. Setting up the Juice Shop would have been as simple as running a container, saving time and avoiding dependency mismatches.

How My Favorite Technology Works

Chrome DevTools is essentially a suite of web development tools built into the Chrome browser. I primarily use the Network tab to monitor HTTP requests and responses. For example, during one test, I intercepted a POST request to the /api/Users endpoint, modified the payload to include a malicious script, and observed how the server handled it. This allowed me to uncover vulnerabilities and then fix them in the codebase by sanitizing inputs with the validator library. DevTools also features the Console tab, which I used to execute JavaScript and inspect DOM elements directly.

Reflections

If I could start this project over, I’d prioritize understanding security practices earlier. My initial approach was focused on functionality, but now I see that security is just as critical. The journey so far has taught me to think like both a developer and an attacker, ensuring that every feature I implement is both useful and secure.

Conclusion

This project has been a hands-on crash course in web application security, teaching me to use tools like Chrome DevTools and validator libraries effectively. While some technologies challenged me, overcoming those hurdles has been the most rewarding part of this experience. Moving forward, I’m excited to continue learning and refining my approach to building secure, user-friendly applications.

When I revisited some code I wrote during my first year of college, I struggled to understand my own logic. It felt like deciphering a foreign language, even though I had written it myself. This experience highlighted the importance of clean code. Inspired by Robert Martin’s Clean Code: A Handbook of Aigle Software Craftsmanship and Martin Fowler’s Refactoring: Improving the Design of Existing Code, I explored the principles of clean code and the warning signs of bad practices known as code smells. Here, I’ll share one thing I plan to start doing more often and one thing I’ll strive to avoid, supported by examples and insights.

One Thing to Start Doing: Meaningful Names

One key takeaway from my reading is the importance of using meaningful names. Robert Martin emphasizes that names should revival intent. Variables, functions, and classes should communicate their purpose without requiring additional context or comments.

Why?

Meaningful names make code easier to read and maintain. They reduce cognitive load for both the original developer and others working on the code later. This practice fosters better collaboration and faster debugging.

Example of improvement

Bad Practice:

Improved Practice:

By adopting meaningful names, I’ll reduce ambiguity and make my code self-explanatory. This change ensures that I, or anyone else, can quickly understand the purpose of each variable without extensive documentation.

One Thing to Avoid: Long Methods

From Martin Fowler’s discussion on code smells, I learned that long methods are a common sign of bad code. A function that tries to do too much becomes difficult to understand, test, and modify.

Why?

Long methods often violate the Single Responsibility Principle (SRP). They are harder to debug because a bug can be hidden anywhere in the lengthy code. They also discourage code reuse because the functionality is tightly coupled.

Example of Refactoring:

Best Practice:

Improved Practice:

By breaking the method into smaller, more focused functions, I’ll make my code easier to read, test, and modify.

Applying Clean Code Principles to Advanced Projects

To deepen this discussion, let’s analyze a practical implementation: a Bloom Filter. This structure efficiently checks membership in a set and illustrates how clean code principles can enhance complex logic.

Code Implementation

Here’s an example of a Bloom Filter:

Clean Code Practices Illustrated

1. Meaningful Names: Functions like load_bloom_filter and check_bit_array_saturation clearly describe their purpose, improving readability.
2. Short Methods: Complex operations like password loading and testing are encapsulated in modular functions, adhering to the SRP.
3. Comments and Documentation: Each method includes a brief docstring, ensuring clarity for future developers.

Conclusion

Clean code is not just about aesthetics; it’s about writing code that is easy to understand, maintain, and improve. By starting these practices and avoiding common pitfalls, I hope to make my code more professional and sustainable.

References

• Martin, Robert C. Clean Code: A Handbook of Agile Software Craftsmanship. 1st edition, Pearson, 2008.
• Fowler, Martin. Refactoring: Improving the Design of Existing Code. 2nd edition, Addison-Wesley Professional, 2018.
• Clean Code Concepts Adapted from Robert C. Martin
• Code Smells – Martin Fowler’s Blog

When I first stumbled into the world of IT Project Management, I had no idea it would become such a fulfilling career path. At the time, I was exploring ways to blend my love for technology with my knack for organization and problem-solving. Over time, I realized that IT Project Management is not just about managing tasks and timelines—it’s about bringing people together to create meaningful technology solutions.

Why I Chose IT Project Management

For me, IT Project Management felt like the perfect blend of structure and creativity. I enjoy diving into the technical details of a project, understanding the “how” behind the systems, and then stepping back to see the bigger picture. It’s incredibly rewarding to take a project from concept to completion, knowing that my efforts helped a team build something impactful.

What My Day Looks Like

My daily routine as an IT Project Manager is a whirlwind of activities, but that’s part of what keeps it exciting. Here’s a glimpse into my typical day:

• Morning Stand-Up Meetings: I start the day with a quick stand-up meeting to sync with the team. It’s my chance to ensure everyone is aligned and address any blockers they might be facing.
• Planning and Prioritizing: I spend a lot of time reviewing project timelines and reprioritizing tasks to adapt to changes.
• Problem-Solving: Whether it’s a resource shortage or an unexpected technical challenge, I’m constantly finding creative ways to keep the project moving forward.
• Communicating with Stakeholders: Keeping everyone informed is key, so I make time to update stakeholders and make sure their expectations are clear.

---

Lessons I’ve Learned Along the Way

Like anyone new to a field, I’ve made my fair share of mistakes. But each one has been a learning opportunity that’s made me a stronger project manager.

• Early Mistakes: I remember the first project I led where I underestimated the importance of clear communication. My team misunderstood the project requirements, which led to a lot of rework. That experience taught me to over-communicate rather than assume everyone is on the same page.
• Biggest Success: One of my proudest moments was modernizing a clinical placement system. I led a team of developers, designers, and testers to deliver a user-friendly platform on time and within budget. The feedback we received from users was overwhelmingly positive, and that sense of accomplishment was worth every challenge we faced.
• Ongoing Struggles: Managing competing priorities is always a challenge. I’ve learned to rely on tools like Smartsheet and ClickUp to stay organized and help my team focus on what matters most.

My Favorite Tools

As I’ve grown in my role, I’ve discovered some incredible tools that make my life easier. Here are a few I can’t live without:

• Smartsheet: For automating workflows and keeping everything in one place.
• Microsoft Project: Perfect for creating detailed schedules and tracking progress.
• ClickUp: A lifesaver for task management and collaboration.

These tools not only help me stay organized but also give my team the clarity they need to succeed.

How I Manage the Chaos

IT Project Management can get overwhelming, especially when multiple deadlines are looming. Here are a few strategies that help me stay grounded:

1. Time Blocking: I schedule dedicated time for focused work, like creating project plans or analyzing risks.
2. Celebrate Wins: I make it a point to celebrate small milestones with my team—it boosts morale and keeps everyone motivated.
3. Continuous Learning: I’m always on the lookout for new techniques and tools that can improve how I manage projects.

Advice for Aspiring IT Project Managers

If you’re considering a career in IT Project Management, here’s what I’ve learned:

• Embrace Challenges: Every project is unique, and you’ll constantly be learning and growing.
• Build Relationships: Success comes from collaboration. Building trust with your team and stakeholders is essential.
• Stay Curious: Technology evolves quickly, so make it a habit to stay updated and curious about new trends.

What’s Next for Me

I’m excited to continue growing in this field. My next goal is to lead larger, more complex projects that challenge me to step out of my comfort zone.

IT Project Management has been an incredible journey for me, and I can’t wait to see where it takes me next. If you’re curious about this career or want to share your own experiences, feel free to reach out—I’d love to connect!

Toxic Inequality: The Flint Water Crisis as a Case of Environmental Racism 

Understanding Environmental Injustice 

The water crisis in Flint, Michigan represents one of the most devastating examples of environmental racism in recent American history. In 2014, state-appointed emergency managers decided to switch Flint’s water supply from Detroit’s system to the Flint River to save money. What followed was a public health disaster that exposed deep systemic inequalities and governmental neglect.

The Flint crisis embodies what environmental justice scholar Robert Figueroa identifies as the intersecting dimensions of environmental injustice. As Figueroa explains, “Environmental justice encompasses a variety of notions of justice: distributive, participatory, political, and cultural” (Figueroa, 2009). These dimensions help us understand the deeper implications of what happened in Flint. 

Distributive Injustice: Unequal Burdens

With a population that is nearly 57% Black and a poverty rate exceeding 40%, Flint exemplifies what Figueroa terms the question of “how environmental benefits and burdens are distributed across populations.” The decision to use corrosive river water without proper treatment – which causes lead to leach from aging pipes into thousands of homes – reflects a broader pattern of systemic disregard for marginalized communities. 

The Human Cost 

Through extensive reporting and documented accounts, we know that residents immediately noticed something was wrong. Their taps ran brown, smelling foul and metallic. Children developed rashes. People got sick. Yet for months, officials insisted the water was safe to drink. 

The impacts have been devastating. According to Hanna-Attisha et al. (2016), over 9,000 children under age 6 were potentially exposed to lead, and the crisis resulted in 12 deaths from Legionnaires’ disease. Campbell et al. (2016) documented the economic toll, estimating $450 million in property damage and projecting over $600 million in long-term healthcare costs.

Community Response and Recognition Justice

But amid this tragedy, Flint residents have shown remarkable resilience. Community organizations have emerged to distribute water and filters, while residents have become citizen scientists, learning about water testing and environmental justice. This grassroots response represents what Figueroa calls “recognition justice” – communities demanding acknowledgment of their experiences and rights. 

As Figueroa notes, the environmental justice movement are “united in the larger struggle for ecological democracy,” combining social justice concerns with environmentalism. Local activists have forced the nation to confront uncomfortable truths about race, class, and access to basic resources. 

Moving Forward: A framework of change 

Moving Forward requires a comprehensive approach that addresses all dimensions of environmental justice that Figueroa outlines: 

Distributive Justice 

• Strong environmental regulations 
• Equitable infrastructure investment 
• Fair distribution of resources 

Participatory Justice 

• Community involvement in decision-making 
• Transparent governance 
• Local control over environmental decisions 

Recognition Justice 

• Acknowledgment of community experiences 
• Respect for cultural perspectives 
• Equal representation in environmental policy

The Long Road Ahead 

Today, despite claims that the water meets federal standards, many Flint residents still don’t trust what comes from their taps – and who can blame them? Their experiences show how trust, once broken by institutional betrayal, isn’t easily rebuilt – the psychological scars of the crisis run as deep as the physical ones. 

The Flint water crisis isn’t over. While pipes can be replaced, rebuilding trust and addressing the long-term health impacts will take generations. As a nation, we must ask ourselves: how many more communities will face similar crises before we decide that every American deserves clean, safe water? The answer lies in embracing Figueroa’s comprehensive vision of environmental justice – one that addresses not just the physical infrastructure of our communities, but the social, political, and cultural dimensions of environmental equity as well. 

Work Cited 

Figueroa, R. M. (2009). Environmental Justice. In J. Baird Callicott & Robert Frodeman (Eds.), Encyclopedia of Environmental Ethics and Philosophy (Vol. 1). Macmillan Reference USA.

Hanna-Attisha, M., LaChance, J., Sadler, R. C., & Champney Schnepp, A. (2016). Elevated blood lead levels in children associated with the Flint drinking water crisis: A spatial analysis of risk and public health response. American Journal of Public Health, 106(2), 283-290.

Campbell, C., Greenberg, R., Mankikar, D., & Ross, R. D. (2016). A case study of environmental injustice: The failure in Flint. International Journal of Environmental Research and Public Health, 13(10), 951.

Butler, L. J., Scammell, M. K., & Benson, E. B. (2016). The Flint, Michigan, water crisis: A case study in regulatory failure and environmental injustice. Environmental Justice, 9(4), 93-97.

Kennedy, C., Yard, E., Dignam, T., Buchanan, S., Condon, S., Brown, M. J., … & Breysse, P. (2016). Blood lead levels among children aged <6 years—Flint, Michigan, 2013–2016. MMWR. Morbidity and Mortality Weekly Report, 65(25), 650-654.

Introduction: Discovering the World of GovTech

As I’ve been progressing through my studies at Oregon State University (OSU), I’ve recently found myself drawn into the fascinating world of government technology or “GovTech”. This sector focuses on using technology to modernize and improve public services, making them more efficient, accessible, and citizen-friendly. While much of my coursework has revolved around core computer science principles and software engineering, diving into GovTech has broadened my understanding of how technology can create real-world impact on a large scale.

This blog post is an exploration of what I’ve learned so far about GovTech, particularly around the role of program and project management in this field. It’s been an eye-opening experience researching how government projects are managed and how technology can drive positive change within public institutions.

Understanding GovTech: What is it All About?

GovTech is all about leveraging technology to solve the unique challenges faced by government agencies. Unlike the private sector, where the focus is often on profit and speed, the public sector prioritizes transparency, accessibility, and inclusivity. Whether it’s modernizing legacy IT systems, improving digital services, or securing data, GovTech projects aim to enhance how governments serve their citizens.

Through my research, I’ve come to appreciate that GovTech is more than just applying technology to government processes. It’s about transforming the way public services are delivered, ensuring they are accessible to all segments of the population, and using data-driven approaches to make informed policy decisions.

The Role of Program and Project Management in GovTech

One of the most intriguing aspects of GovTech is the critical role that program and project management play in bringing these projects to life. Here are some of the insights I’ve gathered through my research on this topic:

1. Complex Stakeholder Dynamics: Government projects typically involve multiple stakeholders, from policymakers to citizens. Manging these relationships is crucial to ensure that the project meets the diverse needs of everyone involved. I’ve learned that effective project manager needs to be skilled in communication, negotiation, and stakeholder management.
2. Regulatory Compliance and Security: Unlike private sector projects, public sector initiatives have to adhere to strict regulations and standards, particularly around data privacy and security. Project managers in GovTech must ensure that solutions comply with these requirements, which adds layers of complexity to project planning and execution.
3. Budget Constraints: Governments operates within fixed budgets, so projects need to be executed with a high level of financial accountability. This has helped me appropriate the importance of resource allocation, budget forecasting, and cost management skills that are vital for project success.
4. Long-Term Impact: One of the key differences between private sector projects and government initiatives is the focus on long-term outcomes. GovTech projects often aim to achieve social good rather than immediate financial returns. This has deepened my understanding of how project managers must align their short-term actions with broader, long-term goals.

Challenges and Opportunities in GovTech Project Management

As I’ve been studying project management principles, I found it fascinating to see how these theories apply to GovTech projects. Some challenges are unique to the public sector, such as dealing with bureaucratic hurdles, political changes, and the slow pace of decision-making. However, there are also tremendous opportunities to innovate and drive digital transformation.

One thing I’ve found particularly interesting is how adopting agile methodologies, even in government settings, can help streamline processes and foster a more iterative approach to project delivery. Research suggests that while traditional waterfall methodologies are still prevalent, there is growing trend toward embracing agile practices to improve efficiency and adaptability in GovTech projects.

My Personal Reflections on Learning About GovTech

As I dive deeper into GovTech through my coresework and independent research, I’ve realized that it aligns closely with my passion for using technology to solve meaningful problems. The idea that technology can help governments better serve their citizen is inspiring to me, especially as someone who is considering a career in technology project management.

What’s been particularly enlightening is discovering just how critical project management is in the successful execution of GovTech projects. I’ve been able to connect many of the concepts I’ve learned in class-such as risk management, stakeholder engagement, and agile practices-to real-world scenarios in the public sector.

Looking Forward: Potential Career Paths in GovTech

As I continue my journey, I’m excited about the possibility of exploring roles that blend my technical skills with project management expertise in the GovTech sector. Whether it’s modernizing outdated systems, improving digital services for citizens, or helping secure sensitive public data, there are numerous ways to make a tangible impact.

My research into GovTech has opened up new avenues for me to consider post-graduation. I am particularly interested in exploring roles where I can help bridge the gap between technology and public service, ensuring that government projects are delivered on time, within budget, and aligned with the needs of the community.

Final Thoughts: The Journey Continues

Learning about GovTech has been a rewarding experience that has expanded my perspective on how technology can be applied beyond the traditional corporate environment. I’m excited to continue exploring this field, bot academically and professionally, as I move forward in my career journey.

For those interested in making a difference through technology, I highly recommend looking into GovTech. It’s a field where you can use your skills to create a positive social impact, improve public services, and drive meaningful change.

Hi everyone! I’m Kristin, and I’m thrilled to start this blog to share my journey in my computer science capstone course. I currently live in Corvallis, Oregon in the Pacific Time Zone. When I’m not studying, you’ll probably find me either exploring new shows, working on my fitness routine, or at bible study.

What Got Me Started with Computers

My passion for computers and software started when I was young, tinkering with whatever technology I could get my hands on. I vividly remember the first time I built a website as a hobby project, and that sparked my curiosity about programming. That interest grew when I realized the potential of software to solve complex problems and real-world applications.

My Journey with OSU

I’m currently pursuing a degree in Computer Science at Oregon State University. It’s been an exciting, challenging, and rewarding journey so far. OSU has offered me a solid foundation in software deployment, algorithms, and systems. From introductory coding classes to advanced topics, OSU has shaped my technical and problem-solving skills immensely. OSU has also encouraged me to continue learning using outside resources like codeacademy and Tryhackme to explore my curiosity.

Current Job

Currently, I work full-time as an IT Project Manager, where I get to blend my technical knowledge with project management skills. This role has given me insight into how technology projects come together through the planning and execution phases to deliver real results for stakeholders. It’s a balancing act managing a team while also diving into coding on my own time, but I love every moment of it.

Favorite Technologies

My favorite technologies include Python for its versatility and simplicity and MySQL for database management. I’m also fascinated by web development frameworks like Flask and React, which allow me to build both the frontend and back end of web applications. Lately, I’ve been diving deeper into machine learning, and experimenting with frameworks.

Capstone Project Interests

I’m particularly excited about working on projects that combine my passion for software development and my experience in project management. A few areas that interest me include:

• Building a Full-Stack Web Application: I’d love to create a comprehensive full-stack application with a focus on user experience, backend efficiency, and scalability. This project would allow me to use technologies like Flask, React, and AWS to build something impactful.
• Machine Learning Integration: Another project I’m excited about is integrating machine learning into a real-world application. Whether it’s predictive analytics, recommendation systems, or automating processes with AI, I’m eager to explore the possibilities that ML offers
• Cloud-Based Application Development: I want to delve deeper into cloud technologies like AWS to develop applications that take advantage of cloud computing. Working on deploying and scaling apps in a cloud environment would be an excellent way to bridge my technical skills with current industry trends.

Two projects stand out for their real-world impact and technical challenges: Creating Portland’s Open Data Digital Commons and Predictive Modeling of 911 Calls for Fire Department Planning. Both align with my interests in full-stack development, data systems, and public service.

1. Creating Portland’s Open Data Digital Commons

This project is about building a shared data library for the City of Portland, focusing on equity datasets. The goal is to make data available to the community through a digital commons. I’m excited about this project because:

• It promotes equity and transparency by making data accessible for public use.
• I’d work with open-source tools to build a cloud-based data catalog.
• It allows me to handle data pipelines and API integration, while also learning about cloud architecture.
• The project explores continuous development/integration (CI/CD) practices, which is great for improving my engineering skills.

2. Predictive Modeling of 911 Calls for Fire Departments Planning

This project involves building a predictive model for forecasting 911 calls, helping fire departments improve their response times, and resource planning. I’m drawn to this project because:

• It has a direct impact on public safety, potentially saving lives by predicting future emergencies.
• I’d gain experience building a web application, from the UI/UX to the backend and database integration.
• It uses machine learning and data visualization to predict emergency scenarios, which is something I’m excited to learn more about.
• Collaborating with industry experts makes it a valuable real-world experience.