Open NASA VS git-sizer

• Empowerment
  Open NASA encourages and empowers women to pursue careers in STEM fields by providing role models and success stories.
• Visibility
  The platform increases visibility of women in NASA, showcasing their contributions and achievements in space exploration.
• Inspiration
  By highlighting the journeys of women at NASA, the site serves as a source of inspiration for young girls and women considering STEM careers.
• Educational Resource
  Offers educational content that can be used by teachers and students to learn more about the role of women in science and technology.

Possible disadvantages

• Limited Audience
  The content might not reach a wide audience beyond those already interested in NASA or gender diversity in STEM.
• Impact Measurement
  The direct impact of the site on increasing women participation in STEM fields can be difficult to measure objectively.
• Content Depth
  Depending on user expectations, some may find the content not deep enough in terms of technical detail or personal stories.
• Resource Intensive
  Maintenance and updating of the platform require continuous resources, which might be challenging for ensuring updated information.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

No analysis of Open NASA yet.

• How can I stay motivated in school if I'm not 100% sure what path I want to take?

  I do think women have a harder row to hoe at NASA. But more women are working there than ever before and some in high-level positions. Here are a few women at NASA: https://women.nasa.gov/. Source: over 4 years ago

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago