> I find the most frustrating part of using CI to be to wait for a CI run to finish on a server and then try to deduce from the run log what went wrong. I’ve alleviated this by writing an extension to rad to run CI locally: rad-ci.
I moved from VSCode to Emacs with the help of Doom Emacs. You can check it out online. It’s a distribution and configuration management solution.
Generally people like to recommend writing your config from scratch but that didn’t work for me.
It comes with pretty much all you requested out of the box.
One thing I liked more than with the default Emacs setup is that I could “activate” support for a Language just by un-commenting a line in the well organized config.
> and on some days, i feel there is nothing to write
This is what I was trying to fix for myself.
And I found that creating a new text document is just an additional friction.
> i'd be tempted to answer with a multi page essay
This is what I visually restricted the input field for as I also feel like some questions would otherwise suggest a long answer. Trying to answer them in a brief way is a feature for myself.
There is not yet an open feature as you suggested but I feel like this could be nice. Not only for journaling but also for todo lists or similar, just starting every day with a blank sheet.
I saw that “1 Day” as suggested in another comment seems to be basically that.
I guess an about page is a great idea, I'll create one that answers the questions here later.
My setup for the questions is the following - I have a questions file with one question per line and a cron job that takes the top one, builds the static page by including it in the template and then appends the question in the end.
That way I can always add more questions but if I run out of questions it would just start from the beginning.
Do you have an idea on how to save to a git repo from a static page? I don't want to make it any more complicated than it needs to be.
Do you have an idea why you could not maintain it?
I think another component why I open the page every day is that I only have the chance to fill this question that day - something that you wouldn't have in the paper one.
I can just open it in other tools and for example merge two sources. E.g. I do this on my laptop and on my phone.
Download both, open with Excel and sort by date.
I also considered more questions in the future or tracking numerical values.
There is a great community driven list [0] of 1 on 1 questions that I like to pick a couple questions as conversation starters or as backup when the conversation goes stale.
It is also available as JSON so you can script the random selection.
If you delete and retype the word it is technically the same attempt and you are not being fast enough, so it is in deed a feature to practice the words you have made a mistake in in the first place.
But I can see how that can be less than obvious.
I fixed that now.
That is actually the way it works. If you turn on logs (bottom right) you will see the time measured in ms for each attempt.
The measuring starts on the keydown of the fist key and stops on the keydown of the space to complete the word.
The time er only continues in case you start typing the word delete it and retype it. That counts as one attempt.
I've added a lookahead to the next word now, feel free to check it out.
For more I wouldn't know how to add it design wise and I don't think it is the goal of the application.
I usually go to https://10ff.net/ when I am looking to practice the whole typing flow.
Do you have any ideas for the feedback when your speed is to low?
I am not a designer and struggle to find ideas that keep the UI as minimal as it is right now while improving the user experience.
I've created this small project to fix my own typing and thought you might benefit from it as well.
To calculate the WPM words with 5 letters are taken. To reach e.g. 80 WPM you'd have 150ms per character.
The application uses ~1000 most common english words and only gives you the next word once you've cleared the word in the calculated time.
The time is measured only as soon as you press the first key.
Give it a try.
Controls: [Space] or [Enter] to complete a word. [Esc] to move on to a next word
Click [wpm] to set your target speed. The default is quite low but you might still find words that you can't type within the time limit. Click [log] to see a log of your individual attempts.
How it was build:
No dependencies, single html file
Respects system preferences for dark them
Keyboard friendly (autofocus, tab & enter for settings, etc.)
locally running CI should be more common