| Category | Specialization |
|---|---|
| Systems | Rust, Lisp |
| Scripting | Lua, Fennel, Lisp |
| Data | R, Lisp |
| Development Philosophy | DRY, testing&benchmarks > boilerplate |
My main languages would be lisp and lua, and I can really do anything and everything with just those two, but R I've been learning more of, it's just tedious with every library being its own DSL.
AUR: autodock4 - Automated docking of flexible ligands to proteins(for arch linux)
Lisp: cl-freelock - lock free queue data structures library for common lisp
Lean4: ln_messagepack - the lean4 messagepack serialization library (beta)
PDB-library - personal PDB molecule library
- GitHub: ItsMeForLua
- Email: andrewforlua@gmail.com
(03/27/26) Note: I'm depricating my use of perl, despite previously listing it as one of my known languages. Perl just generally goes against my code philosophies, and its testing enviroments are very impractical. I love perl, because I think it's cool, but, since the code that made if fast for parsing and regex is open source, and made in C, many other programming languages have adopted that code, and can be just as fast(if not faster).
This section displays what I plan to do currently regarding my projects. Most of my projects have a TODO.md, but it's still necessary for me to split time between projects.
- cl-freelock needs to have its system definition symbols updated from
#:to: - cl-freelock needs its API-usage wiki-pages updated: I've already written multiple pages-worth for all 23 symbols; I'm just refining.
- I will add a github actions yml to Rust2d (and a dockerfile at the same time if my time constraints are reasonable).
Meaning I have not abandoned
- Helping update the clasp install scripts for Roswell.
- Helping cl-messagepack with benchmarks.
- I will create google forms for all my projects, and integrate them into automatic github issue reports.
- I wll use github actions to automatically create issue reports for
cl-win32-typesandcl-win32-errorswhen the upstream API has changes. - I will fix the one non-critical warning from RCBOR's rust build-system for CRAN submission, as per CRAN's sys-admin recommendations.
This can wait since it's non-critical