DEV Community: Thalles Augusto(ThesllaDev)

🦆 The Golden Duck: My Experience Building an Educational Web Game with Amazon Q Developer

Thalles Augusto(ThesllaDev) — Mon, 12 May 2025 05:26:02 +0000

This is a submission for the Amazon Q Developer "Quack The Code" Challenge: That's Entertainment!

🎮 What I Built

The Golden Duck: Navigation Chronicles is a text-based educational game with a retro aesthetic inspired by DOS/Windows 95. The player learns to navigate operating systems using only the keyboard through interactive narrative missions. The game encourages memory, logic, and navigation skills, and is accessible to visually impaired users.

Each scene is a standalone JavaScript module and part of a broader modular game engine, created with the help and guidance of Amazon Q Developer. The user interface mimics old terminal UIs with modern accessibility considerations. The game was built entirely from scratch using plain HTML, CSS, and JavaScript — thanks to Q Developer's architectural suggestions and efficient implementations.

Demo

Game Website

💻 Code Repository

Explore the code and check out the additional documents, such as:

Feel free to open suggestions, issues, or pull requests!

GitHub Repository – Golden Duck Game

🤖 How I Used Amazon Q Developer

The entire development process was done with Amazon Q Developer in VSCode, and the experience was fun, productive, and educational. Here's how it went:

1. Initial Setup

Installed the Amazon Q Developer plugin in VSCode.
Registered a Builder ID for authentication.
Created the project context file with game information.

2. Getting Started with Q Developer

I asked Q Developer to help me analyze, plan, and structure the game code. It:

Analyzed the provided context.
Planned the project architecture.
I clicked the "Run" confirmation button, and it created and implemented the necessary files.

After that, it explained how the modular system in JavaScript works for the game, giving an overview of the architecture, chapter flow, how the flow works, main features, architectural benefits, and even taught how to add a new “chapter” with examples of a complete chapter flow.

Note: Right away, I liked the clear description of each file it generated and the terminal integration, offering a practical option to create the folders and directory structure for implementation.

3. Execution and Initial Testing

I ran the project using Live Server.
The retro UI looked as expected, but the game wasn't functioning correctly.
I started inspecting the code and identifying the failure points.

4. Debugging with Q Developer

Debugging went smoothly, thanks to the previous explanations, code quality and comments, and the error message implemented in the console:

    render() {
        if (!this.gameEngine) {
            console.error('Game engine not set for scene:', this.id);
            return;
        }

        // Clear the screen first
        this.gameEngine.renderContent('');

        // Render each component
        this.components.forEach(component => {
            if (typeof component.render === 'function') {
                component.render();
            }
        });
    }

The console displayed the error: Game engine not set for scene: tutorial.
I informed and asked Q Developer to analyze the error.
It identified and fixed the issue in the scene.js file.

After applying the fix, the game worked!

It even added a small debug helper utility to aid development.

Before continuing development, I tested the chat with multiple tabs and disabled the code agent to use one tab only for dialogue, questions, suggestions, etc. I discussed technology choices, the adopted design system, and asked for a more detailed explanation about the "debug helper".

5. Unit Testing

I asked Q Developer to generate unit tests.
It configured package.json, created the test structure, and explained the process.
Some tests failed initially, but with adjustments, we validated most of them.

Note: The process might take some time.

6. Code Review and Improvements

I requested a codebase review focusing on security vulnerabilities and accessibility. Q Developer suggested and implemented improvements, also updating the project documentation. I reran the tests and got one more failure than before, but everything was working fine.

7. Documentation and Workflow

To wrap up, I used Q Developer to generate the documentation and keep the README.md up to date.
It also generated additional files like CONTRIBUTING.md, Chapter Creation Guide, Architecture Document, Educational Design Document, and even a flowchart.

Lastly, I asked it to generate a challenge submission article in Markdown summarizing the whole journey, with an educational tone and clear formatting — which became the basis for this post.

📚 Educational Value

The development process with Amazon Q Developer was highly educational. I learned about:

Structuring modular projects in JavaScript.
Implementing unit tests with Jest.
Best practices for accessibility and security in web apps.
The importance of clear and objective documentation.

🧠 Conclusion

Amazon Q Developer was an essential partner in creating "The Golden Duck." From concept to implementation, debugging, testing, and documentation, its assistance made the process more efficient and educational. I highly recommend using Amazon Q Developer — especially for those who want to learn by doing, with contextual guidance, and gain more confidence while building real-world projects.

The result is a game that not only teaches keyboard navigation but also showcases how AI assistance can enhance the development process, allowing developers to create more robust, accessible, and educational applications.

🦆 The Golden Duck: Minha experiência construindo um web game educativo com Amazon Q Developer

Thalles Augusto(ThesllaDev) — Mon, 12 May 2025 05:10:23 +0000

Esta é uma submissão para o Desafio Amazon Q Developer "Quack The Code": That's Entertainment!

🎮 O que eu construí

The Golden Duck: As Crônicas da Navegação é um jogo educativo baseado em texto, com estética retrô inspirada no DOS/Windows 95. O jogador aprende a navegar em sistemas operacionais utilizando apenas o teclado, através de missões narrativas interativas. O jogo estimula a memória, lógica e habilidades de navegação em sistemas, sendo acessível para usuários com deficiência visual.

Cada cena é um módulo JavaScript independente e parte de um mecanismo de jogo modular mais amplo, criado com o uso e a orientação do Amazon Q Developer. A interface do usuário imita interfaces de terminal antigas, com considerações modernas de acessibilidade. O jogo foi construído inteiramente do zero com HTML, CSS e JavaScript puros — graças às sugestões arquitetônicas do Q Developer e às suas eficientes implementação.

Demonstração

Website do jogo

💻 Repositório do Código

Explore o código e confira os documentos complementares, como:

Sinta-se à vontade para abrir sugestões, issues ou pull requests!

Repositório no GitHub – Golden Duck Game

🤖 Como utilizei o Amazon Q Developer

Todo o processo de desenvolvimento foi feito com Amazon Q Developer no VSCode e a experiência foi divertida, produtiva e educativa. Veja como foi:

1. Configuração Inicial

Instalei o plugin Amazon Q Developer no VSCode.
Registrei um Builder ID para autenticação.
Criei o arquivo de contexto do projeto com as informações do jogo.

2. Primeiros Passos com o Q Developer

Solicitei ao Q Developer que me explicasse e ajudasse a analisar, planejar e estruturar o código do jogo. Ele:

Analisou o contexto fornecido.
Planejou a arquitetura do projeto.
Selecionei o botão de confirmação "Run" e ele criou e implementou os arquivos necessários.

Após isso, ele explicou como funciona o sistema modular em JavaScript para o jogo, passando uma visão geral sobre a arquitetura, o fluxo de cada capítulo, como funciona esse fluxo, as principais funcionalidades, benefícios da arquitetura e até ensina como adicionar um novo “capítulo” e fornece exemplos de um fluxo de capítulo completo

Nota: Logo de começo já gostei da descrição das implementações de cada arquivo que ele gerou e também da integração ao terminal, dando a opção prática para criar as pastas e estrutura do diretório para implementação

3. Execução e Testes Iniciais

Executei o projeto utilizando o Live Server.
A interface retrô estava conforme o esperado, mas o jogo não funcionava corretamente.
Então comecei a inspecionar o código e identificar os pontos de falha.

4. Depuração com o Q Developer

A depuração foi tranquila, considerando a explicação anterior que o Q Developer fez, a qualidade e os comentários no código e a implementação de mensagem de erro no console:

    render() {
        if (!this.gameEngine) {
            console.error('Game engine not set for scene:', this.id);
            return;
        }

        // Clear the screen first
        this.gameEngine.renderContent('');

        // Render each component
        this.components.forEach(component => {
            if (typeof component.render === 'function') {
                component.render();
            }
        });
    }

O console exibiu o erro: Game engine not set for scene: tutorial.
Informei e solicitei ao Q Developer uma análise do erro.
Ele identificou e corrigiu o problema no arquivo scene.js.

Depois de aplicar a correção, o jogo funcionou!

Ele até adicionou um pequeno utilitário auxiliar de depuração para auxiliar no desenvolvimento.

Então antes de seguir com o desenvolvimento, eu testei o bate papo com várias abas e desabilitei o agente de código para utilizar uma das abas apenas para dialogo, perguntas, sugestões, etc. Conversei com ele sobre a escolha das tecnologias, o design system adotado e pedi uma explicação mais detalhada sobre o "debug helper".

5. Testes Unitários

Pedi ao Q Developer para gerar testes unitários
Ele configurou o package.json, criou a estrutura de testes e explicou o processo.
Alguns testes falharam inicialmente, mas com ajustes conseguimos validar a maioria deles.

Nota: O processo pode legar algum tempo

6. Revisão de Código e Melhorias

Solicitei uma revisão da base de código focando em vulnerabilidades de segurança e acessibilidade. O Q Developer sugeriu e eu pedi para que ele implementou melhorias, atualizando também a documentação do projeto. Rodei os testes e teve uma falha a mais comparado a antes, mas estava tudo funcionando ok

7. Documentação e Fluxo de Trabalho

Para finalizar, utilizei o Q Developer para gerar as documentação e manter o README.md atualizado.
Ele também gerou arquivos adicionais como CONTRIBUTING.md, Chapter Creation Guide, Architecture Document, Educational Design Document e até um flowchart.

Por fim, pedi que ele gerasse um artigo de submissão para o desafio em Markdown resumindo toda a jornada, com tom educacional e formatação clara — o que se tornou a base para este post.

📚 Valor Educacional

O processo de desenvolvimento com o Amazon Q Developer foi altamente educativo. Aprendi sobre:

Estruturação de projetos modulares em JavaScript.
Implementação de testes unitários com Jest.
Melhores práticas de acessibilidade e segurança em aplicações web.
Importância da documentação clara e objetiva.

🧠 Conclusão

O Amazon Q Developer foi um parceiro essencial na criação do "The Golden Duck". Desde a concepção até a implementação, depuração, testes e documentação, sua assistência tornou o processo mais eficiente e educativo. Recomendo fortemente o uso do Amazon Q Developer — especialmente para quem deseja aprender na prática, com orientação contextualizada, e ganhar mais confiança ao desenvolver projetos reais.

O resultado é um jogo que não apenas ensina a navegação pelo teclado, mas também demonstra como a assistência de IA pode aprimorar o processo de desenvolvimento, permitindo que os desenvolvedores criem aplicativos mais robustos, acessíveis e educacionais.

We WeCoded Celebration Landing Page

Thalles Augusto(ThesllaDev) — Mon, 07 Apr 2025 06:23:33 +0000

This is a submission for the WeCoded Challenge: Celebrate in Code

We WeCoded Landing Page

The goal of this landing page is to be engaging and interactive, celebrating the evolution from SheCoded to WeCoded, while promoting diversity, inclusion, and empowerment in tech.
The design bridges the past, present, and future of technology, embracing a retrofuturistic and cyberpunk aesthetic. It features pixelated visuals inspired by the official WeCoded logo, vibrant color schemes, and subtle visual effects that connect history with innovation.

Demo

Demo: We WeCoded Landing Page

Code: GitHub repo

How I Built It

Structure

The landing page is made up of key sections that tell a story and invite engagement:
- About We – Showcasing the WeCoded initiative and its evolution from SheCoded
- Community Stories – Featuring inspiring posts from the dev.to community tagged with #wecoded
- Inspiring History – Honoring iconic figures like Ada Lovelace, Grace Hopper, and the women from Hidden Figures
- Organizations That Empower – Spotlighting organizations that support diversity in tech

Tech Stack

React + Next.js
TailwindCSS
ReactBits for animations
dev.to API – to dynamically fetch real community stories using the #wecoded tag

Design Highlights

Fonts:

Fira Code – for code aesthetics
Press Start 2P – for a pixel-perfect retro vibe

Color Palette:

Blue: #4531EA
Green: #CCEA71
Purple: #9D00E5

From Idea to MVP: Building a Shot Tracker with KendoReact

Thalles Augusto(ThesllaDev) — Mon, 24 Mar 2025 06:59:23 +0000

This is a submission for the KendoReact Free Components Challenge.

What I Built

As an amateur basketball player, I always looked for an efficient way to track and analyze my shooting performance during practice. Manual records or generic apps didn’t offer the customization I needed. That’s when I decided to build the Basketball Shot Tracker, an application that allows players to register and analyze their training shots in a simple and interactive way.

The main goal of this project is to provide a clear view of a player's progress, allowing them to log the number of shots taken and made, visualize real-time statistics, and track their improvement over time.

Demo

https://vimeo.com/1068737889/3a633caf68?share=copy

Link to test the app
GitHub code repository

KendoReact Experience

The Basketball Shot Tracker was built using KendoReact Free Components, which were fundamental in speeding up the development process while delivering a rich, interactive, and efficient experience.
Here are some of the components I used and how they helped:

TabStrip: Organizes and enables smooth navigation between the Shot Registration, History, and Analysis sections.
Label: Provides clear field hints in the shot registration form.
DropDownList: Allows users to easily select the type of shot trained (3-Point, Mid-Range, Free Throw).
NumericTextBox: Ensures efficient and validated data input.
DatePicker: Simplifies selecting the training date, keeping records organized.
Button: Used for key interactions within the app.
Notification: Provides visual feedback to users.
Slide: Enhances the app with smooth animations.
Grid: Displays the shot history in a structured and intuitive manner, featuring editing, filtering, paging, and sorting.
ExpansionPanel: Allows users to toggle between detailed and summarized views of their data.

Using KendoReact allowed me to focus on the application logic instead of spending time styling and implementing complex components. The consistent design and seamless integration significantly accelerated development, enabling me to deliver a functional CRUD MVP quickly.

Recommendation

If you’re looking for efficiency and productivity when developing React applications, KendoReact is a great choice!
Before this project, I had never used KendoReact, but I was impressed by how easy it was to implement. Within minutes, I had fully functional and beautifully styled components in my app. This allowed me to focus entirely on the business logic instead of spending hours on UI design and component behavior.
With ready-to-use production components, KendoReact saves time and ensures a refined user experience. Plus, its comprehensive documentation and practical examples make implementation straightforward, even for first-time users.
If you haven’t tried it yet, I highly recommend giving it a shot!

My Hacktoberfest Journey: From First Pull Request to the Hall of Fame

Thalles Augusto(ThesllaDev) — Mon, 04 Nov 2024 05:12:48 +0000

This is a submission for the 2024 Hacktoberfest Writing challenge: Contributor Experience

Overview

This article is about sharing my experience as an open source contributor during Hacktoberfest and is also part of the writing challenge proposed by dev.to: Contributor Experience.

Hacktoberfest is an annual event organized by GitHub, DigitalOcean, and other partners to celebrate open source, aiming to attract and encourage people around the world from various skill levels to collaborate with the open source community, showcasing the potential we have when we join forces. It’s worth noting that it’s not just about code or for developers; writers, translators, testers, and designers can also contribute.

Open source software makes its source code available, providing transparency and the right to study, modify, and use it freely and openly according to the license. The use of open source software has seen significant growth among individuals, organizations, and companies in recent years. Here are some examples of open source software:

Brief Description About Me

I am Brazilian (and my English level is still not very good, but I am constantly trying to improve it; I apologize for any mistakes), a front-end developer fascinated by technology and games, and an enthusiast of gamification and open source. You can find more information on my GitHub.

Why I Decided to Participate and Recommend You Do Too

I have participated in Hacktoberfest since 2020 because I am an enthusiast and want to support the open source community by giving back and collaborating with open source software and content that has helped me throughout my self-taught learning process with free and accessible resources. These resources are often created by the community, for the community.

Through participation and challenges, I have gained a lot of knowledge and evolved in many ways. For these reasons, I recommend that you also participate.

Skill Development

Hard Skills: From technologies such as HTML, CSS/SASS, JavaScript, Git/GitHub, Elixir, and other tools to clean code techniques and understanding other codebases.
Soft Skills: Problem-solving, teamwork, commitment, communication, writing, and practicing English (for non-native speakers).

Participating also opens doors for networking, learning about tools, libraries, and projects. Other advantages include enhancing your resume/portfolio, demonstrating your skills to employers or others, and receiving exclusive rewards from the event, such as: t-shirts, stickers, badges, partner reward kits, and trees planted (in 2023, Hacktoberfest offered a tree in a planting project in partnership with Tree-Nation, which planted a tree in honor of each of the first 50,000 contributors to the event who opted in, and I was one of them; I recently received an email from Tree-Nation saying my tree celebrated its first birthday! 🥳🎋 You can see more information at the tree view and information link). Each year, they offer different types of rewards.
Images of the rewards I've earned over the past few years:

Experience and Evolution from Previous Years

In my first participation in 2020, some of the main challenges and questions I faced were about how to participate and what to do. However, the event provides resources about this, and you can see more at this participation and resources link on the event's website. In 2021, I write my first article, which was a guide and resources for participating in Hacktoberfest 2021 (content in Portuguese).

Guia e recursos open source para participar do Hacktoberfest 2021

Thalles Augusto(ThesllaDev) ・ Oct 19 '21

#beginners #braziliandevs #opensource #hacktoberfest

In the early years, I was learning to use Git and GitHub while making my first contributions to open source projects. I experienced some ups and downs that helped me grow. During this phase, I focused on understanding the concept of open source and version control systems. Since I didn't have much technical knowledge, I made simple contributions such as “solving algorithm exercises and submitting my pull requests,” sharing content, JSON and Markdown changes, correcting typos, and/or broken links. Even though they were simple collaborations, all are welcome, significant, and benefit the community. Remember that there are multiple ways to contribute that do not involve coding skills. To learn more, visit the official Hacktoberfest site that discusses this topic.

In 2023, I completed the Hacktoberfest challenges and had the honor of appearing in the Hacktoberfest 2023: Hall of Fame 🤩✨😎🏆

This year, I did a recap and noticed a good evolution and faced fewer problems, thanks to my participation and challenges from previous years. With a “life-long learning” mindset, this year was no different; I continued to develop my skills and made contributions by sharing my knowledge and accessibility improvements described below in the contributions section.

As the years went by, and with improvements in GitHub/Codespace, it became easier and better to work with open source projects directly on the platform, without needing to download and run the project locally, which is also beneficial for those who do not have much experience or do not like using the terminal.

Contributions

Project 1 - Filosofunk

Description of the Project

It is a Brazilian project aimed at gathering funny, entertaining, philosophical, or creative phrases from funk songs. You simply add a new song lyric by editing the poesias.json file with the necessary information as explained in the README.

My Contribution

This is a project I enjoy contributing to every year since 2020 (my first participation in Hacktoberfest) because it is simple and fun. It’s a great project I recommend for beginners; you don’t need extensive technical knowledge, just read the README for instructions on how to contribute. My contribution was adding a new song lyric.

Add nova frase "Margem Distante" MC Cebezinho e MC Hariel (DJ Boy) #326

ThesllaDev posted on Oct 17, 2024

View on GitHub

Project 2 - Simple Icons

Description of the Project

“Simple Icons” is a collection of SVG icons for popular brands, technology projects, software tools, and online services. It offers a vast library of free, standardized, and simplified icons, ideal for use in web projects, applications, and interfaces. Each icon is carefully designed to follow the brand’s visual identity and maintain a simple, consistent aesthetic. The repository is community-maintained and regularly updated to include new brands and improvements, making it easier to incorporate these icons into projects via SVG or NPM packages.

My Contribution

This repository is not participating in Hacktoberfest, but I decided to spend some time making a contribution because I frequently use it. My contribution was updating the data of a JSON file as described and requested in one of the issues.

Update Aiqfome icon #12063

ThesllaDev posted on Oct 19, 2024

Issue: #10282

Checklist

[x] I updated the JSON data in _data/simple-icons.json

Description

Update the source to match the new source as mentioned in issue #10282

View on GitHub

Project 3 - You Don’t Need JavaScript

Description of the Project

"You-Don’t-Need-JavaScript" is a collection of resources and examples demonstrating how certain functionalities commonly implemented using JavaScript can be achieved exclusively with HTML and CSS. Its goal is to show that in some cases, it is possible to avoid using JavaScript, simplifying development and improving performance and accessibility of web pages. The project provides practical examples for interactions, animations, and features like dropdown menus, sliders, and tabs that can be built using only HTML and CSS.

My Contribution

While browsing the issues in the repository, I found a discussion about the accordion examples not being true accordions. So I added the code for an accordion-type interface component, which is commonly used for developing FAQs (Frequently Asked Questions). In this example, I explain and use the HTML “details” and “summary” elements to construct the component, presenting a simple, semantic, and accessible solution using only HTML and its attributes, and CSS (just for styling), without needing to use JavaScript.

Add modern accordion and FAQs component #660

ThesllaDev posted on Oct 22, 2024

Modern Accordion and FAQs component only using HTML Resolves #16

View on GitHub

Project 4 - Home-Assistant.io

Description of the Project

The "home-assistant.io" repository houses the source code for the website and official documentation for Home Assistant, an open source home automation platform. Home Assistant allows users to monitor and control smart devices centrally, integrating various automation services and devices such as lights, sensors, cameras, and voice assistants.

My Contribution

I proposed accessibility improvements for the website through semantics and SEO, following HTML best practices for semantics to enhance user experience, including for screen reader users.

Semantic Accessibility and SEO Improvements: Correct List Parent Tags and Heading Levels #35339

ThesllaDev posted on Oct 22, 2024

Proposed change

This PR focuses on improving the semantic structure for accessibility and SEO by addressing two key issues:

Added an appropriate <ol> container around <li> elements that were missing a parent <ul>, <ol>, or <menu>. This ensures correct semantic structure and improves screen reader navigation.
Adjusted heading levels by changing <h4> to <h3> to maintain proper descending order in the heading hierarchy, enhancing both accessibility and SEO.

These changes follow best practices for semantic HTML, contributing to a better user experience for all users, including those using assistive technologies.

Type of change

[x] Spelling, grammar or other readability improvements (current branch).
[ ] Adjusted missing or incorrect information in the current documentation (current branch).
[ ] Added documentation for a new integration I'm adding to Home Assistant (next branch).
- [ ] I've opened up a PR to add logos and icons in Brands repository.
[ ] Added documentation for a new feature I'm adding to Home Assistant (next branch).
[ ] Removed stale or deprecated documentation.

Additional information

Link to parent pull request in the codebase:
Link to parent pull request in the Brands repository:
This PR fixes or closes issue: fixes #

Checklist

[ ] This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the current branch.
- I made a change that is related to an upcoming version of Home Assistant and used the next branch.
[ ] The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

New Features
- Enhanced styling for various components, improving visual presentation and responsiveness.
- Updated footer structure with improved semantic hierarchy.
- Recent blog posts now displayed in an ordered list for better semantic HTML.
Bug Fixes
- Adjusted styles for better handling of text and layout across different screen sizes.
Documentation
- Improved clarity in the documentation index with refined styles for list items.

View on GitHub

Project 5 - Tech Guide

Description of the Project

TechGuide is a collaborative platform aimed at mapping the skills and knowledge necessary for technology professionals in various areas, such as front-end, back-end, data science, and other specialties. The project offers guides that help users understand which skills are relevant for each area and which learning paths to follow beyond their chosen specialization. It is inspired by the open source project at roadmap.sh.

My Contribution

I added a new accessibility resource to the cards for three languages (Portuguese, English, and Spanish). The resource is a course from web.dev (Chrome developers) that provides valuable insights and best practices for improving web accessibility development.

Adicionando curso de acessibilidade do web.dev(desenvolvedores do Chrome) #338

ThesllaDev posted on Oct 23, 2024

Adiciona um novo recurso de acessibilidade aos cards para os 3 idiomas (português, inglês e espanhol). O recurso é um curso do web.dev (desenvolvedores do Chrome) que oferece valiosos insights e boas práticas para melhorar o desenvolvimento de acessibilidade na web.

View on GitHub

Project 6 - freeCodeCamp Developer Quiz

Description of the Project

This is a collaborative project to create a quiz platform aimed at developers. The site offers over 1,500 interactive questions across various categories such as programming, security, databases, and other tech areas. The platform helps users test and deepen their knowledge in a practical and engaging way.

My Contribution

I contributed by adding two questions, one about entity representation in an ERD (Entity-Relationship Diagram) in the SQL category and another question about hash definition in the security category.

Add ERD question on entity representation in SQL category #1196

ThesllaDev posted on Oct 24, 2024

Summary of changes

This PR adds a new question to the SQL category, focusing on the representation of entities in an ERD (Entity Relationship Diagram). The question asks about the common shape used to represent entities and tables in an ERD, with an explanation that highlights the use of rectangles to contain the entity name.

Checklist

[x] I have read and followed the contribution guidelines.
[x] I have read through the Code of Conduct and agree to abide by the rules.
[x] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[x] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[x] I have provided a summary of my changes.

View on GitHub

Add question on hash definition to Security category #1207

ThesllaDev posted on Oct 30, 2024

Summary of changes

This pull request adds a new question about the concept of "hash" to the Security category. The question defines a hash as a unique digital fingerprint generated by an algorithm, helping learners understand this fundamental concept in information security.

Checklist

[x] I have read and followed the contribution guidelines.
[x] I have read through the Code of Conduct and agree to abide by the rules.
[x] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[x] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[x] I have provided a summary of my changes.

View on GitHub

Useful Resources for the Event

Official event site with resources
Recommended open source projects to get started:

Tips for Participation

Start with the basics, such as text contributions in documentation or simple code changes; look for “good first issue” labels in repositories, and ensure the repository also has the event label “hacktoberfest” to validate your participation.
Look for projects that align with your profile, interests, and skills.
Always read the README and the contribution guide to ensure alignment with the project’s standards and quality, making it easier for your pull request to be accepted.
When making a pull request, remember to write clear and explanatory titles, commits, and descriptions about the changes. This helps the maintainer understand and can expedite the process of having your contribution accepted.
Observe the project’s activity; for example, if it has been a while since the last commit, pull request merge, updates, etc. This can save you time, frustration, and effort.
Besides pull requests, you can also contribute with issues by suggesting features, reporting bugs, participating in discussions, and code reviews.
As a maintainer of projects, you can:
- Manage issues by creating, organizing, and closing them, setting priorities, and labeling them (for example, “good first issue” for beginners).
- Review pull requests to ensure quality and provide clear, constructive feedback to help and encourage the contributor.
- Communicate, engage, and motivate the community, promoting a welcoming environment. This includes participating in planning and discussions, answering questions, thanking contributors, and explaining the impact of their contributions on the project.

What Not to Do

Pull request spam: Don’t send too many pull requests in an attempt to increase your pull request count, such as removing whitespace; one pull request to fix a typo is fine, but five pull requests to remove whitespace is not good.
Pressuring maintainers for quick acceptance: Avoid sending frequent messages or “pings” to pressure the maintainer to accept or review your contribution quickly. Maintainers have many responsibilities, and Hacktoberfest is a busy time for them.
Fear of asking questions: If you have doubts, ask. Open source communities are generally welcoming and seek to help new contributors.
Neglecting feedback and not respecting maintainers: If the maintainer asks for changes or suggests improvements, do not ignore the feedback. Contributing with quality means being open to revisions and enhancements in your proposal.

For the coming years, I hope that open source continues to grow, that I can meet more people and projects, contribute more and better, and not only as a contributor but also as a maintainer.

Thank you very much, and I hope you enjoyed the content! Explore more about open source, participate in the community, and in upcoming events! If you have any questions, feel free to leave a comment and provide your feedback.

Guia e recursos open source para participar do Hacktoberfest 2021

Thalles Augusto(ThesllaDev) — Tue, 19 Oct 2021 20:25:24 +0000

Olá mundo! Estou fazendo meu primeiro post para divulgar o evento do Hacktoberfest 2021 e compartilhar conteúdos sobre o open source, com o principal objetivo de atrair mais pessoas e ajudar quem está começando.
Com esse guia e recursos você conseguirá dar seus primeiros passos no mundo open source.

O que é Open-Source?

O open source ou “código aberto” significa que o código fonte de um site, sistema ou aplicativo é aberto ao público. É um ótimo movimento para o desenvolvimento de softwares pois ele possibilita o acesso e a modificação ao código fonte desses sistemas.

“O código aberto permite um método de desenvolvimento de software que aproveita o poder da revisão por pares distribuída e a transparência do processo. A promessa do código aberto é de maior qualidade, melhor confiabilidade, maior flexibilidade, menor custo e o fim do aprisionamento predatório de fornecedores.”, Open Source Initiative(OSI).

Isso é muito bom para a participação e colaboração ativa da comunidade de usuários e desenvolvedores para dar seus feedbacks, sugerir mudanças, realizar testes, corrigir erros e fazer com que esses sistemas tenham uma melhora contínua e de qualidade.

Exemplos de projetos open source

Lista com alguns repositórios open source conhecidos :

Sistema Operacional Linux
Navegador Firefox
Editor de sprite Aseprite
Editor de código VSCode
Linguagens e Framework/Libs:
- Vue
- React
- Elixir
- Flutter
- Bootstrap
Kit de ferramentas de ícones FontAwesome
Sistema de Versionamento de código GIT
Gravação de tela e streaming OBS
Aplicativo de voz Discord
Game Engine Godot

Para saber mais sobre como contribuir para o Open Source, veja este guia sobre como fazer contribuições, para novatos e veteranos: Guias de código aberto

Recomendo também esse ótimo curso de Git e Github

O que é Hacktoberfest 2021?

É um Hackathon que está na sua 8° edição, apoiado pela DigitalOcean, Intel, Dev.to, GitHub/GitLab e outros. Esse evento acontece durante todo o mês de outubro celebrando e apoiando os projetos e softwares e de código aberto. Nesse período seu objetivo é fazer contribuições, convidar e incentivar a comunidade a fazer colaborações para o mundo open source. Existe várias formas de se fazer isso:

Prepare e compartilhe seu projeto para receber colaborações
Contribua com feedback, sugestões, traduções, relatando bugs ou melhorias no código para um projeto
Organize um evento sobre open-source e hacktoberfest
Ajude a comunidade com mentoria, criando e compartilhando conteúdos
Doe diretamente para projetos de código aberto
De uma “star” / “estrela” no repositório do projeto
Se voluntarie como mantenedor do repositório para ajudar no que for possível

Vantagens de participar

Ótima forma de aprender
Fazer networking com pessoas do mundo todo
Apoiar o movimento open source
Ao concluir o desafio você tem as opções de escolher uma camisa exclusiva do evento ou plantar árvores em seu nome e ajudar a tornar o Hacktoberfest 2021 mais neutro em carbono.(OBS: apenas os primeiros 50,000 participantes que concluírem o desafio ganharam a camiseta e os adesivos)

Como isso funciona?

Os mantenedores determinam se seus projetos de código aberto participam adicionando o tópico ‘hacktoberfest’ no repositório.
Pull Requests(ou também conhecidos como PR para abreviar) de qualidade enviadas no GitHub e GitLab são recompensadas.
A manutenção envolvida dos repositórios marcados do Hacktoberfest é recompensada.

Regras

As solicitações pull podem ser feitas em qualquer repositório/projetos hospedados no GitHub ou GitLab. Procure o tópico 'hacktoberfest' para saber se um projeto está participando do Hacktoberfest.
A pull request deve conter commits que você mesmo fez.
Se um mantenedor relatar sua solicitação de pull como spam, isso não será contabilizado para sua participação no Hacktoberfest.
Se um mantenedor relatar um comportamento que não esteja de acordo com o código de conduta do projeto, você não poderá participar.
Um pull request é considerado aprovado quando têm uma revisão geral de aprovação dos mantenedores, ou foi merged(mesclada) pelos mantenedores, ou recebeu o rótulo de 'hacktoberfest-accepted.
Para obter a premiação, você deve ter quatro solicitações de pull (PR) aprovadas em projetos aceitos entre 1 e 31 de outubro em qualquer fuso horário.

O que não fazer!

Em linha com o valor do Hacktoberfest “quantidade é divertido, qualidade é a chave”, aqui estão alguns exemplos de PRs que é considerado contribuições de baixa qualidade e que são desencorajadas:

PRs que são automatizados (por exemplo, PRs de abertura com script para remover espaços em branco/otimizar imagens)
PRs que são perturbadores (por exemplo, tomar a branch/commit de outra pessoa e fazer um PR)
PRs que são considerados por um mantenedor do projeto como um obstáculo em vez de ajudar
Algo que é claramente uma tentativa de simplesmente marcar com +1 sua contagem de PR
Por último, mas não menos importante, um PR para corrigir um erro de digitação está bem. 5 PRs para remover espaços em branco perdidos ... não é.

Como participar?

Basta fazer login com sua conta do GitHub ou GitLab no site oficial do hacktoberfest, após ter feito o login você já está participando do evento!

Ainda não conhece o Git e GitHub? De uma olhada nesses recursos de aprendizagem

O próximo passo então é buscar por projetos que contenham o tópico ‘hacktoberfest’ e enviar as pull request.
Atenção! Certifique-se de se inscrever no site oficial do Hacktoberfest para que suas solicitações de pull sejam contabilizadas.

Selecionei alguns projetos com maneiras simples de contribuir:

First Contributions

Repositório feito para ajudar iniciantes a contribuir para projetos de código aberto.

Filosofunk

Projeto feito para juntar frases engraçadas, divertidas, filosóficas ou criativas de músicas de funk. Você pode adicionar uma nova frase apenas editando um arquivo

Canvaz

Use o elemento HTML canvas para fazer uma arte para o desafio de celebração do hacktoberfest

Free IT Courses

Repositório com os melhores cursos de TI de graça

Repositório
Como contribuir: se aprova e conhece algum curso que não esteja na lista adicione o link e o nome do curso na seção correta.

Open Pixel Art

Um projeto colaborativo de pixel art para ensinar as pessoas a contribuir com o código aberto.

Hacktoberfest Animations

Crie uma animação do título no seletor de animações para o Hacktoberfest

Simple Icons

Projeto free com mais de 2000 ícones SVG de marcas populares, você pode requisitar um novo ícone que ainda não tem e adicioná-lo ou escolher um ícone já solicitado e apenas adicionar.

Cloud Haiku

Este projeto com uma simples edição você consegue adicionar um poema em forma de “haiku” e se divertir enquanto o faz.

Sabe inglês ou quer praticar? Ajude contribuindo com esses e outros projetos fazendo correções e traduções:

Elixir School

Elixir School é uma escola para aprender e dominar a linguagem de programação Elixir.

Você pode acompanhar seu progresso no perfil do site oficial do evento e ver mais informações sobre cada uma das solicitações.

Acesse o discord oficial do Hacktoberfest para fazer networking, tirar dúvidas e compartilhar e procurar por projetos

Veja a lista de todos os eventos que estão acontecendo durante o todo o mês de outubro

Caso ainda tenha alguma dúvida você pode perguntar nos comentários abaixo, me mandar uma mensagem no meu linkedin ou consultar as perguntas mais frequentes respondidas aqui.

Muito obrigado e espero que vocês tenham entendido o conteúdo e as vantagens de fazer parte do open source! E não pare por aqui continue buscando mais conhecimento.

O conteúdo foi útil para você de alguma forma? Contribua compartilhando-o com suas conexões, nas redes sociais e/ou dando um “like”, isso ajudaria muito.

Fique a vontade para dar seu feedback e sugestões!

Conhece e indica algum projeto open source ou recurso que não foi citado no post? Compartilha aí nos comentários