tcoff91

14 ms·

181.
by tcoff91 1y ago
Storyteller can sync your progress between devices, although there’s occasionally a bit of a bug with it (will be fixed soon). I sync between my iPhone and boox. Once you get all the e-ink settings dialed in to make black text more readable
182.
by tcoff91 1y ago
It's a little less user friendly but I really like my Boox tablet because it's a full android device. I run Storyteller app on it and have my ebooks & audiobooks synced up perfectly like whispersync but better.
183.
by tcoff91 1y ago
Have you ever tried Excalidraw? It doesn’t have as many features but with the keyboard shortcuts you can whip up diagrams so fast. It’s just so nice to draw in.
184.
by tcoff91 1y ago
If you just want to draw a simple diagram, Excalidraw is amazing.
185.
by tcoff91 1y ago
I think it does but rerere is not nearly as good as first class conflicts in jj
186.
by tcoff91 1y ago
I wholeheartedly agree with you. What makes jj a killer app to me is that it allows me to work with source control in a whole new way that just feels so much more powerful to me. I haven't felt like this since I first discovered git af
187.
by tcoff91 1y ago
Heres a great article about a powerful workflow that jj makes practical https://ofcr.se/jujutsu-merge-workflow/ Where jj shines is advanced workflows that aren’t practical with git. If you aren’t interested in those th
188.
by tcoff91 1y ago
I am a git expert and I very much prefer jj. It enables workflows that are impractical with git. It’s hard to even imagine these workflows if you only use git because your thinking is constrained by the limitations of your tools. Git rebase
189.
by tcoff91 1y ago
I understand git at a pretty deep level. I still very much prefer jujutsu. Its rebase is just so much more powerful than git. I regularly work on top of octopus merges in jj of all my in-review parallel PRs and when I want to rebase them al
190.
by tcoff91 1y ago
That's absolutely wild.
191.
by tcoff91 1y ago
The sanitizers and static analysis tools are not as good as the borrow checker for preventing data races.
192.
by tcoff91 1y ago
I self review but I don’t add comments I just fix the problems that I find. I should add clarifying comments.
193.
by tcoff91 1y ago
I self review but I don’t write comments. I simply fix the code as I see the problems that I find self reviewing.
194.
by tcoff91 1y ago
By self review, you mean that the developer adds comments in the code review tool? that is a great idea, I want to try this.
195.
by tcoff91 1y ago
It all depends on the lines. It can take a long time to review a 1 line change to a critical function that is used everywhere in the app and it can take minutes to review 1000 lines of declarative UI code.
196.
by tcoff91 1y ago
What I find helps with stacked PRs is it helps with getting code review incrementally as the various changes for a larger effort come together.
197.
by tcoff91 1y ago
Just use jj instead of git and cut your rebasing time by 95%. Suddenly rebasing a stack of branches becomes 1 command.
198.
by tcoff91 1y ago
A stack of PRs is much better for reviewers than a single massive PR. Use jujutsu and then stacking branches is a breeze
199.
by tcoff91 1y ago
#!ruby if ARGV.size < 1 puts "Usage: wz path" exit end # Get current working directory current_dir = "#{Dir.pwd}/" # puts "Current directory: #{current_dir}" # Run git
200.
by tcoff91 1y ago
I actually made a git worktree aware function called w that wraps zoxide and will basically switch to the main worktree, execute z, and then switch back to the worktree you came from. That way you don’t run into zoxide switching from one wo
201.
by tcoff91 1y ago
It’s just so good. fzf and zoxide are probably my two most game changing cli tools. They make the terminal feel so good.
202.
by tcoff91 1y ago
CRDTs are a pretty good experience for many data types when it comes to collaborative editing.
203.
by tcoff91 1y ago
Most are full time iOS developers.
204.
by tcoff91 1y ago
Great question. It does seem like you would not want to use it for raw chicken.
205.
by tcoff91 1y ago
The web is not an application platform, it’s a document rendering platform that has been hacked together to be an application platform. Without libraries it’s incredibly hard to be productive building applications. It’s only with dependenci
206.
by tcoff91 1y ago
npm should require it for all packages.
207.
by tcoff91 1y ago
Wait, the Mac Studio has worse single core perf than an iPad Pro? that's absurd.
208.
by tcoff91 1y ago
Publishing a package involves 2 phases: uploading the package to npmjs, and making it availble to users. Right now these 2 phases are bundled together into 1 operation. I think the right way to approach this is to unbundle uploading the pac
209.
by tcoff91 1y ago
Many packages have only 1 author.
210.
by tcoff91 1y ago
I think that ultimately it’s the fault of the web platform. With just a bit of retraining those engineers that could not be productive without a ton of npm packages could ship an iPhone app written in Swift. JS’ standard library is abysmal.

More ›