Hello World #introductions
I'm Brad, 31, he/him, in the US Midwest, and an engineer working on cool space hardware.
Stuff I like and am good at:
- Embedded Programming
- Tabletop Games
Stuff I like and am getting better at:
- RATS RATS RATS
- Web Programming
Stuff I want to do:
- Start a commune with all my friendos
- Fully Automated Luxury Gay Space Communism
Future Proof Your Community:
There a basic things every community needs. Doesn't matter if your displaced, homeless, or somewhere new.
You need to get the following done asap...
- hygiene (showers, restrooms, sanitation, recycling, cleanup)
- security/stability (daycare, good lighting as deterents at night etc., Community watch)
- knowledge networks ( language classes, diy unschools, news shares, missing persons board, job boards, volunteer opportunities, groups etc.)
- Food ( community kitchen, gardens, pantry, canning etc.)
- water and power
- cooling station, a way to keep people warm (heating zones, free clothes etc.)
- first aid
A new member of one of the labs I'm working with is a Hitchensonian atheist, and insufferable. In an attempt to get him to quit arguing with me, I let him know that I considered myself an atheist too, and that was a mistake.
One choice quote: "Don't tell me as an atheist that you seriously believe in free will?"
I'm trying to figure out how I can help folks (including myself) to do better at documenting the hardware/firmware/software we make.
I think my ideal documentation system sits somewhere at the intersection of code autodoc system, wiki, and bug tracker.
We should be able to document and understand caveats, remove them when they get fixed (and maybe document the removal!), and put weirdness on the to do list automatically.
I'm not aware of anything that's close to that right now.
This is a really cool string formatting library for C++: https://fmt.dev/latest/index.html
Borrows the Python 3 string formatting rules, much safer, but not a lot more inefficient than printf.
Might mess around later and see if I can get it working efficiently on embedded with some fixed-allocation string templates.
Organising, Being Local
Don't be disparaged by national and international politics. People are organising in your local area. Check out how to volunteer and help with schools, libraries, local food banks. The people there may not have the same politics as us, but think of yourself as a seed. Your actions can be used to help grow a radical, verdant garden in your community.
The Fascists infiltrated politics by playing a long con. We can play the long game too. Go and play the civic game. When you run into a wall or resistance, organise with your fellows about getting around it. If the organisation you are working with doesn't do something you want, talk to the folk working there. Someone will want to help. There are always people looking to help.
Speak your heart. Listen to others. Take care of yourself. We will get through this. We are the Ones we are waiting for.
It's in the repository directory. And it contains the different ASF versions as tagged commits in that repo.
And (almost) every directory contains an asf.xml file with information about what files are needed how and when and why.
Dunno what I'm gonna do with this info. Probably waste a bunch of time. But, huh.
Obviously they have this data, because Atmel Studio can do it, through the Atmel Studio ASF extension. So, what's up?
Well, you see, the ASF in the extension is organized differently.
You can download the extension from Microchip's site. VSIX files are zips, so just open it with whatever. All the metadata is in extensions/[version number]/content.xml.cache
But where's the data?
They ship a GIT REPO with the extension.
Today I'm tearing into the Atmel ASF to try and liberate it from Atmel Studio for reasons that I still don't really understand myself. And sheesh, this is some weird/clever/weird corporate obfuscation.
The ASF they distribute as a zip is basically useless. It has all the source, sure. But all the example project and doxygen files are mixed right in, making it /basically/ impossible to include in your project. Plus, there's no dependency data! No data on what goes with what!
I think for me that means licensing things separately for "personal, non-commercial, and small business" use and "commercial" use.
We should also think seriously about licensing that excludes parties with malicious intent. I wrote this a while ago as a joke: https://github.com/Zuph/ACAB-License/blob/master/LICENSE.md/LICENSE.md
But maybe we should take it more seriously. What do I want my work to manifest in this world? It sure as hell isn't Palantir.
been thinking a lot about open source culture and tradition since reading this (https://blog.licensezero.com/2019/08/26/but-you-said.html) especially wrt to hardware.
Hardware is different in that the cost of replication is non-trivial, yet to be considered Open Source Hardware you have to let people make money from your work.
So: How to license hardware in a way that is fair to folks, but doesn't exploit the labor of the person that designed it?
This is an adapter to help me take a Dell MD1200 that I got criminally cheap and hook it up to some quieter fans, so I can stand to run it in my house.
The quiet fans don't move as much air, but this thing will never see anything resembling worst-case conditions storing my filez.
Really, all this does is translate the RPM values coming from the slower, quiet fans into a range the server expects to see.