The Weekly Edition
banner
theweeklyedition.xyz
The Weekly Edition
@theweeklyedition.xyz
130 followers 97 following 790 posts
https://theweeklyedition.xyz/
Posts Media Videos Starter Packs
(ancient times)
Hey I invented it! AND CHEESE!
Thank God nobody had invented the milk jug, or we wouldn't have cheese.
Lastly, I should mention that I'm quite addicted to the new VCS jj. The simplicity by which I can take a bunch of MRs creating a single integration branch, and without thought randomly tweak some of them has me converted. I couldn't go back to the mess that is git.
Next in the Weekly Edition, head into Settings > Appearance, and upload the font and select it. Your existing books and any newly generated books should all switch over to the new font.
To begin search for "amazon typography complete font set" with your preferred search engine, and, assuming it's a good one you'll gets to the Typography page from Amazon.

Inside the downloaded zip file, you will find the Bookly font. Copy it to the device that you're running the Weekly Edition on.
My recommendation for the The Weekly Edition font would be the Bookerly font from Amazon. Unfortunately, I can't directly embed it in the application, the best that you can do is to provide you with instructions for doing so yourself.
When putting together my collection of feature descriptions for the day, I'll strive to avoid merge conflicts. I generally do this by attacking different parts of the code / UI in waves. Sometimes this requires quite some attention.
If I do run into issues that can't be trivially resolved via a quick follow-up question to Codex, I will either go back to the drawing board or try a new prompt feasibly updating my AGENTS.md. Mostly, this happens because the feature was ill-specified. With experience, it'll occur less.
Whenever I do work on something with visual elements, I do so within a mini style guide contained within the project. This allows me to quickly preview the components. This lets me build/run iterate far faster on device than the main project. I'll generally ask Codex for four different variants.
Here are some follow-up tips and tricks for my Codex / Expo workflow thread from earlier:
True, she missed out "add the milk".
I find that Codex doesn't work extremely well for UI. So for anything that requires finesse, I instead get it to produce an architecturally sound component, which I then iterate upon locally using Cursor.
My personal workflow is to make recordings of ramblings while walking my dog. Finally, once my ramblings have come to a cohesive idea, I write the feature specification up using Wispr Flow and pass it directly to Codex.
If the implementation requires some architectural juggling, you should make it clear rather than expecting the model to implement it in the way you hope.
This mostly requires two to three paragraphs of detailed text. Everything you can imagine a junior developer coming back to ask you should be specified in that text.
Each time I sit and begin an iteration, I'll make notes on the key objectives I aim to accomplish during the session. I'll mostly begin with single sentence ideas and I will iterate the definition until they are complete and valid feature requests.
You'll need to ensure that all of the steps that Codex will need to create a valid and useful merge request can be executed in the Cloud environment you set up for it. This will require some iteration on your local development environment.
Next up, my overall flow is as follows:

I begin with a template of an application. The application has the rough architecture that I am aiming for, and really requires its iteration. For Codex Cloud, the key is to have something that can be iterated by the model in isolation.
2. A set of rules that should be applied during development. This can be everything from ensuring that actual linters that should be ran in the container, to specific rules that the model itself should check its reasoning against (as in, previously seen stupidity during code generation).
The first thing to mention should probably be my use of AGENTS.md, my file focuses on two primary sections:

1. An overview of the architecture of the application focusing on critical areas which have previously caused misunderstanding when implementing feature requests.
My development workflow using Codex Cloud and Expo EAS:
From time to time, I like to set Dead Cells to cheese mode and run around eating brie. It makes me feel a lot better about my dairy allergy.