nickledave

And the final implementation: https://ratfactor.com/repos/nasmjf/

Here's the Programming from the Ground Up book the author references at the end of the post: https://programminggroundup.blogspot.com/2007/01/programming... https://download.savannah.gnu.org/releases/pgubook/

And the source for asmtutor, which appears to be down: https://github.com/DGivney/assemblytutorials

I'm very interested in this rabbithole, see the similar origin story for uxn: https://100r.co/site/weathering_software_winter.html

I don't know about Frontiers in Psych specifically, but, see also: https://www.reddit.com/r/AskAcademia/comments/1oi5dhy/whats_...

This post is about Zotero. https://www.zotero.org/

If you are not an academic, you might not know Zotero.

It is such a pleasure to use. Every app should be like this.

I read everything in it, including books I'm going through right now from https://teachyourselfcs.com/

It also does an amazing job of taking snapshots of posts. I use it all the time to grab posts from HackerNews so I can mark them up.

And it automagically syncs everywhere across devices and lets me store way too many files on the web like the ADD packrat I am, without breaking a sweat.

In short, this software just works, and it works well. So when somebody behind Zotero talks about how to develop software, I listen.

And it's a fun post with some history. You should save this post to Zotero, and then read it.

I'm not super interested in what the tech industry is calling "agentic" AI, but I am interested in collective intelligence, see David Ha's work in this area: - https://journals.sagepub.com/doi/full/10.1177/26339137221114... - https://neurips.cc/virtual/2024/105817

Would be cool if each ant itself could be an agent

https://en.wikipedia.org/wiki/John_Carmack

oh

Note this is version 4 of the paper and the original post was version 1 (I think?)

OpenReview (for NeurIPS) for the curious: https://openreview.net/forum?id=jiCLUPq5xv

Since you mentioned pySDR: `sdr` is a newer Python library I like https://github.com/mhostetter/sdr

https://x.com/sama/status/2027578652477821175?s=20

Tonight, we reached an agreement with the Department of War to deploy our models in their classified network.

In all of our interactions, the DoW displayed a deep respect for safety and a desire to partner to achieve the best possible outcome.

AI safety and wide distribution of benefits are the core of our mission. Two of > our most important safety principles are prohibitions on domestic mass surveillance and human responsibility for the use of force, including for autonomous weapon systems. The DoW agrees with these principles, reflects them in law and policy, and we put them into our agreement.

We also will build technical safeguards to ensure our models behave as they should, which the DoW also wanted. We will deploy FDEs to help with our models and to ensure their safety, we will deploy on cloud networks only.

We are asking the DoW to offer these same terms to all AI companies, which in our opinion we think everyone should be willing to accept. We have expressed our > strong desire to see things de-escalate away from legal and governmental actions and towards reasonable agreements.

We remain committed to serve all of humanity as best we can. The world is a complicated, messy, and sometimes dangerous place.

Amazing / weird that this sounds like a lot of the stuff Amodei said Anthropic asked for

Here's a similar post with more concrete advice on what to write: https://jamesmckay.net/2017/02/how-to-keep-lab-notes-as-a-so...

1. Choose the most low-friction solution you can get your hands on. 2. Write down everything you do, as you do it. 3. You can not be too detailed. 4. Write down your train of thought when you’re planning and designing your code. 5. Don't worry too much about making your notes look good. 6. Use a searchable text format. 7. Make your notes append-only. 8. Use your notes as a source for documentation, commit summaries and pull request descriptions. 9. Share your notes with your whole team. 10. Don’t make your notes public. 11. Learn from your mistakes.

I used to use HackMD but I have found Obsidian helps me better meet the criteria above (low-friction yet searchable).

I have learned the hard way, repeatedly, that forcing myself to write down a to-do list and notes on what I did actually makes me a better developer, even when I am in software engineering mode, not research mode. I make myself prioritize what to do, I retain better what I've learned, and I converge on solutions faster.