cross-posted from: https://lemm.ee/post/36326370
Hey Everyone,
I'm very happy to see the engagement in my last post... Hoping to improve my communication skills and reduce my verbosity in the next couple of discussions.
I feel like it is due time to follow-up on what I posted on this board last year. That is, to follow through with "full-stack" hardware-software-application study groups.
If any of you still are interested, I'd like to open up this form for discussion of how that group should be run.
On the subject of HDLs (Hardware Description Languages), VHDL (Verilog HDL) could be fun for some of us to try together. Architecture is also a large concept frequently glossed-over, enciphered with too much jargon, or taught in a very "academic" fashion with very little discussion between students... The traditional classroom model, from what I experienced, is not too conducive to neurodivergent learning styles.
On that note, the RISC-V processor architecture could provide an amazing opportunity to gain a low-to-high understanding. Starting from the Silicon, where we delve into unit operations for chip manufacturing, fundamental solid state / condensed matter physics, and some mathematical models to describe the underlying phenomena. Then we will proceed to what can actually be configured in the ensemble of devices that constitute your "computer". What is a "piece of logic"? How do transistors actually operate? Why do certain design topologies make more sense than others...? And so forth.
We would conclude with some software projects like writing an I/O driver for a keyboard, or pool a fund together for some type of chip we design in EDA together. Overall, it sounds like a great idea for us all to increase our technology literacy, have a fun hobby group to hang out with, and to feel like you own every part of your computer.
On top of this, I feel that we should discuss FOSS tools with each other, as well as how they are best implemented to accomplish common tasks. I've punted the majority of my "Big Tech" stack to the curb the last 5-ish years.
TUI tools as well as CLI interaction is a paradigm of computer operation that I feel many of us have been sleeping on. It also has helped me understand how GUI applications can be better suited for the task at hand, versus when I should be using a terminal emulator to navigate the directory hierarchy instead. Many of you are more versed in programming than I am, so I would love to hear your thoughts.
We could even come up with a project for mobile, who knows? Not sure about the format, whether or not this would be synchronous, and the time commitment and sustainment of motivation throughout a probably 8 week period. However, I feel like a realistic solution for us all to get something meaningful out of an experience like this exists.
Any thoughts on how to get this up and going? What would we need to do on our first meeting together? What things would you want to learn in this course? It seems to me that many of us are already quite literate in sub-domains of what we are interested in. Maybe a teacher carousel routine could be adopted? Where we adopt a general "roadmap" curriculum, and, in an ad hoc fashion, assign people to be the instructor for the desired lesson? Then that person could go and create a slide deck in Beamer, or prepare a presentation with an overhead camera or digital drawing device to use as a teaching medium.
Those are just some ideas. Really looking forward to hearing what all of you think about this.
Someone is going to need to pull a lot of weight in planning, organizing, and leading these meetings, presentations, and projects.
I find that unless you communicate the time and financial cost expectations to participate in groups like this, you'll get a lot of people who are marginally interested and attached to the group and it's purpose. Which may or may not be important in a successful endeavor.
Discuss the questiona you've raised here.
This is a what I mean by someone pulling a lot of weight, a teacher carousel has a slim to none chance of working out. One person is going to need to define and implement the vast majority of the curriculum. They'll need to do a lot of research and work in advance.
I've never managed a project before, but assume we should gather everyone who is interested by sending out some sort of survey. It would be good to have knowledge about what people are interested in learning, send out my ideas of how this should be structured, and ask for general comments. These could be about the final project, individual time commitment, references, philosophy of learning, etc. I'm thinking 8 weeks could be a good place to start. How should this survey be sent out to others? I want to choose a service that doesn't encroach on user privacy since we are on Lemmy. The same is to be asked of a communal repository. I don't want to use Google Drive.
Saturday mornings or Monday evenings (Pacific US Time) are some thoughts. The sessions could be between 1 and 2 hours depending on the engagement.
I'd like to ascertain this information in the survey if anyone with expertise in particular programming domains would like to lend their expertise and put together a short slide deck. Otherwise, I'm okay to deep-dive on topics we agree on, find a healthy amount of literature as resources, and brainstorm a way that each subtopic could be useful in the grander scheme of the project. So that there is some type of cohesive narrative to this endeavor.
Hope that's a good starting point.