this post was submitted on 07 Jul 2024
0 points (NaN% liked)

Autism

6720 readers
26 users here now

A community for respectful discussion and memes related to autism acceptance. All neurotypes are welcome.

We have created our own instance! Visit Autism Place the following community for more info.

Community:

Values

  • Acceptance
  • Openness
  • Understanding
  • Equality
  • Reciprocity
  • Mutuality
  • Love

Rules

  1. No abusive, derogatory, or offensive post/comments e.g: racism, sexism, religious hatred, homophobia, gatekeeping, trolling.
  2. Posts must be related to autism, off-topic discussions happen in the matrix chat.
  3. Your posts must include a text body. It doesn't have to be long, it just needs to be descriptive.
  4. Do not request donations.
  5. Be respectful in discussions.
  6. Do not post misinformation.
  7. Mark NSFW content accordingly.
  8. Do not promote Autism Speaks.
  9. General Lemmy World rules.

Encouraged

  1. Open acceptance of all autism levels as a respectable neurotype.
  2. Funny memes.
  3. Respectful venting.
  4. Describe posts of pictures/memes using text in the body for our visually impaired users.
  5. Welcoming and accepting attitudes.
  6. Questions regarding autism.
  7. Questions on confusing situations.
  8. Seeking and sharing support.
  9. Engagement in our community's values.
  10. Expressing a difference of opinion without directly insulting another user.
  11. Please report questionable posts and let the mods deal with it. Chat Room
  • We have a chat room! Want to engage in dialogue? Come join us at the community's Matrix Chat.

.

Helpful Resources

founded 1 year ago
MODERATORS
 

cross-posted from: https://lemm.ee/post/36499694

Hope everyone is having a relaxing Sunday morning/evening.

I wanted to follow up from my previous post, as some of you have indicated interest.

About logistic considerations, I believe 8 weeks is a good time commitment for a hardware project. The goal is to learn more about silicon manufacturing, lower-level computer hardware details such as architecture, circuit design, fundamental condensed matter physics, and digital logic design. Other goals involve understanding firmware systems such as BIOS and the cascade of events that occur from power-on to user operation as well as conceptualizing the small timescales that these events occur on. My intention is not to dictate the philosophy of learning, but bring awareness to details that otherwise would have never been known or to draw a larger picture using the constellation of components that is a modern computing device. We then will delve into HDLs (Hardware description languages) and look specifically at the VHDL (Verilog HDL) for how to design a chip. This is where my understanding of what is out there becomes fuzzy.

We will need a repository to store documents. It is not my intention to use Google Drive. Is there a trusted platform that offers this functionality? I am also curious as to learning a VCS (Version Control System). Git seems to be the choice for this. Maintaining our codebase, resources/references, questions/comments, presentations, notes, and miscellaneous documents in some platform that does not infringe on user privacy. Any ideas in this domain?

Individual development environments are also crucial to a productive hobby/working session. I think it'd be fun to discuss IDEs, TUI environments, barebones software to accomplish simple tasks, CLI navigation, file system implementation, and drive partitioning. Some of you are adept TUI text editor users, which your expertise would be greatly appreciated.

Because this is Lemmy, I assume most of us are interested in FOSS software/hardware. Perhaps there are open source architectures for GPUs, RAM devices, and other fundamental computing units.

Is there a such thing as open source RAM architectures? Is that even the correct question to pose? I see that "OpenRAM" exists for ASIC design. Maybe we can have an ultra-specific computing task that we could optimize all the constituent hardware pieces to perform. Maybe a game engine for a programming project, but where we patchwork the pieces, or at least examine the guts of Godot together. I've found that discussing how one actually READS documentation, can be helpful in becoming more independent during information searching.

Apologies if some parts are still unclear. I'm just happy to see some of you are interested! As per the survey and what you'd like to get out of something like this, or if the idea needs other parts glued together, feel free to suggest them here. Looking forward to your feedback.

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here