41 lines
1.8 KiB
Markdown
41 lines
1.8 KiB
Markdown
**ideas**
|
|
|
|
**1. book recommendations**
|
|
- train a model on all books
|
|
- recommend books based on user inputs (keywords) (like dall-e image generation)
|
|
|
|
**2. sqlite as a service (done on java and rust)**
|
|
- on the server: automatic sqlite data file generation based on (queried) data
|
|
- in the browser: run sqlite in wasm,
|
|
- download the datafile,
|
|
- FAST queries on local data
|
|
|
|
**3. use LLJVM as a starting point to compile rust to java bytecode**
|
|
|
|
**4. compile rust using truffle (graalvm)**
|
|
|
|
pixelate camera
|
|
|
|
fodmap app
|
|
|
|
use sunflower and or pumpkin seeds as a 'coagulating base' with other proteins like nuts when creating a curd and ferment it?
|
|
becos pumpkin seeds coagulate easily (says yt)
|
|
|
|
* 200g plain white raw almonds
|
|
* 500g water
|
|
* 10g seasalt
|
|
* 10g plain sugar
|
|
* 5tbsp juice from fermented beetroot
|
|
* 1tsp guar
|
|
|
|
**7. a circular list in rust (as an excercise)**
|
|
|
|
**8. a java bytecode interpreter (not necessarily written in java) that estimates runtime complexity (static analysis)**
|
|
|
|
**9. [blog] code as human communication. inspired by knuth I p. 195 zero based encoding of nr of chars. since zero repetitions would be meaningless, zero encodes one so n+1 in general, which makes total sense for efficiency and maybe mathematicians but it increases cognitive load for the human decoder. So is readability at odds with efficiency? also YouTube video about clean code (actually polymorphism) not being performant.
|
|
|
|
**10. [blog] give back my monolith. daily life in microservice 'hell'. ie. dependency hell**
|
|
|
|
**11. create a realtime (java) gc viewer in rust :)**
|
|
**12. visualize a datastructure from the actual code: ie HashMap, create images of internal storage using instrumented <?> code
|
|
**13. >graphiz editor<, images from code and back (ie draing tool actions translate back into the textual representation)
|