miku86
Workflow:
1. Arrange your windows how you like
2. Save the layout
3. Open the windows
4. Load the layout
Repeat 3 and 4.
Nicely done with rofi/dmenu.
- If you talk about google drive, you can use the file system sync and sync from there
- you can create notebooks and sub-notebooks
If you are still on the search, there is a great list: https://old.reddit.com/r/Evernote/comments/j87fb9/please_hel...
Ignoring: for the maintainer: open loop or maybe hidden closed loop (e.g. afraid of confrontation); for the requester: open loop.
The intention of saying no is a closed loop.
> Nobody should ever have the expectation...
Yes, but that's not a pragmatic solution. People sometimes DO have the expectation.
From a technical perspective: Ignoring leaves the loop open. I don't know: - if you ignore it on purpose - or if you don't want to solve it or - or if you don't have time or - or if you just missed it ...
That's when I would re-send the message or do something else. A Win-Win would be sending a small "won't-fix" or whatever.
This is why you want to have a high compliance, meaning that the sick person does what the doctor recommends. This is mostly caused due technical or behavioral complexity.
You can increase compliance by reducing complexity. At the same time, the accuracy decreases.
Example: High Accuracy / High Complexity: "Do not eat frugugle, fergerio, flululu and fnyvoo." Why low compliance? Because the behavioral complexity is very high, especially for sick people: 1. Find the food ingredients list. 2. Loop over the ingredients list and compare the current item with the "do not eat"-list. 3. Make a decision for every ingredient, if this is in the list ("frugugle" is on the list, but one ingredient is "fruguglelase", what's my decision?)
Lower Accuracy / Lower Complexity: "Do not eat products with more than 3 ingredients." Why higher compliance? Because the behavioral complexity is lower: 1. Find the food ingredients list. 2. Count the amount of ingredients. 3. Make a decision after reading max. 3 ingredients.
IMHO it's easier to start with the second approach, because you make progress faster, and keep the momentum going.
I don't get why the top comments are all about some technical tooling, as if the major part of a developer job would be typing.
So I built an app to create shareable, digital accounts cards I can send to people. It has only links to accounts, no unnecessary information. And it is customizable to the recipient. No signup needed.
The app is built with React and Firebase in one week. I build my stuff in public, you can read how I created it here: https://twitter.com/miku86com/status/1265190217872551942
Let me know if you have any questions and I would love to get your honest, helpful, HN-like feedback.
When you click on signin, there is data to signin with a demo account.
I think I should add a button to signin with a demo account, instead of letting the user to type it in manually.
EDIT: Thanks to your feedback, I just added a button to the navbar, so you can signin with the demo account with 1-click.
Show HN: I built a tool to see quickly when I last contacted my friends
To solve this uncomfortable situation, I've built an app that gives my an overview when I last contacted a specific friend. Because I think other people also struggle with this pain and could benefit from my app, I love to share it.
I would love to hear your feedback: features you would like to see, bugs you experienced, general ideas about it.
I'm more interested in an open source tool, that can run locally with TypeScript.
Anyone knows a tool/package?