The idea is stolen from beeple and coding garden's try Fridays except the timescale is a week, not a day. It will go something like this:
- Monday: learn and ideate
- Tuesday: learn and ideate
- Wednesday: build
- Thursday: build
- Friday: build
- Saturday: share
- Sunday: rest and choose the next topic
Basically I will try something for a week, document my learning, judge its success then move on to the next thing. There are 52 weeks in a year, I already missed the first few in 2024, so starting today, which is week 8. Status codes will signal how well I think it went:
- 102: processing
- 200: successful
- 206: partially successful
- 303: see next week
- 403: failure was my fault
- 503: failure was not my fault
| week | topic | status | comments |
|---|---|---|---|
| 8 | Rust command line game: guess the pinyin | 403 | Had to learn the language basics first |
| 9 | Rust CLI: guess the pinyin | 200 | It runs |
| 10 | Rust in JavaScript | 403 | Learned more about wasm, but didn't finish in time |
| 11 | Rust in JavaScript | 200 | Too much wasm and not enough Rust programming |
| 12 | Guess-the-pinyin (feat Rustlings) | 206 | Made some refactorings based on new knowledge of Rust, but didn't not get as far as I wanted |
| 13 | Wasm game of life | 206 | A setback |
| 14 | Magic cookies | 200 | A 🍪 break from Rust |
| 15 | Web performance & the CWVs | 200 | |
| 16 | Service workers | 501 | too busy on vacation |
| 17 | Service workers | 400 | too busy with back-to-work, and learned just enough about this topic to probably be dangerous |
| 18 | OpenAI Assistant | 102 | |
| 19 | OpenAI Assistant | 102 | |
| 20 | OpenAI Assistant | 206 | Completed but unpublished |
| 21 | File handling on the Web | 403 | Too focussed on the AI project |
| 22 | - | 503 | Conference and travelling |
| 23 | - | 503 | Travelling |
| 24 | AWS | 303 | Taking an AWS Cloud Practioner course with a colleague |
| 25 | AWS | 303 | AWS Cloud Practioner course ongoing |
| 26 | Iterators, Generators, and their async versions oh my | 200 | Learned and solved a problem I was having |
| 27 | - | 403 | Read up on promises but did not write about it. |
| 28 | File input security | 200 | Considers various file upload security risks. |
| 29 | - | 503 | Shipping AI notes @ Studocu |
| 30 | - | 503 | Shipping AI notes @ Studocu |
| 31 | - | 503 | Shipping AI notes @ Studocu |
| 32 | - | 503 | Shipping AI notes @ Studocu |
| 33 | - | 503 | Shipping AI notes @ Studocu |
| 34 | - | 503 | Shipping AI notes @ Studocu |
| 35 | - | 503 | Shipping AI notes @ Studocu |
| 36 | - | 503 | Shipping AI notes @ Studocu |
| 37 | Game design patterns | 102 | Implementing game design patterns in JS |
| 38 | Game design patterns | 102 | Implementing game design patterns in JS |
| 39 | Game design patterns | 102 | Implementing game design patterns in JS |
| 40 | Game design patterns | 102 | Implementing game design patterns in JS |
| 41 | Game design patterns | 102 | Implementing game design patterns in JS |
| 42 | Game design patterns | 102 | Implementing game design patterns in JS |
| 43 | Try Godot | 403 | Got bored by the tutorial and petered out |
| 44 | Beginner's guide to IndexedDB | 200 | A small website with a vanilla JS IBD usage example |
| 45 | Padel | ||
| 46 | Padel | ||
| 47 | Try anything in Godot | ||
| 48 | |||
| 49 | |||
| 50 | |||
| 51 | |||
| 52 |
- How to profile memory usage in Next.js
- What happens when a file is uploaded?
- CORS
- Create a website with Leptos
- Deploying a wasm app
- SQLite/SQLX and wasm
- Godot
- Build a game in Rust, e.g. a maze explorer
- Any FE systems topics (polling, workers, caching)
- SpacetimeDB https://spacetimedb.com/
- Debugging wasm
- How does the modern VCS work, e.g. Jujutsu https://github.com/martinvonz/jj
- Git, mercurial, graphite
- Create a book from my notes with https://rust-lang.github.io/mdBook/
- Write myself a git in Rust https://wyag.thb.lt/#intro
- System retrosynthetic analysis methodology
- Any open system design topic
- VPN - how does it work, how is it detected?
- Using WASI in Node, https://nodejs.org/api/wasi.html
- A Chrome extension
- A Chrome side panel feature
- Wasm by example: https://wasmbyexample.dev/home.en-us.html#
- Record audio content with web assembly: https://wasmbyexample.dev/examples/reading-and-writing-audio/reading-and-writing-audio.rust.en-us.html
- Content renderer in Rust
- Does streaming HTML make critical CSS generation unnecessary?
- Error handling design
- https://www.youtube.com/watch?v=xyxrB2Aa7KE
- Toyoto Full Send was an error handling bug