3 ms·
Such is the current goal-tool environment that, if you tried any tool for more than a year, and are over it, and you are also into tech, it's probably a very go
by themodelplumber 4y ago
Such is the current goal-tool environment that, if you tried any tool for more than a year, and are over it, and you are also into tech, it's probably a very good idea to pick your favorite code/no-code tools and start on your own system.
You will naturally and immediately integrate both subjective emotional and logical energy into such a tool, and you probably already have some objective methodologies in mind from past experience. So it's a huge advantage. Just IMO.
Personally I wrote a bunch of my own tools and I found that they taught me a lot about what I really wanted. The tools came and went and new tools were built, but the general lesson-integration flow remains intact and that's the important part.
Prior to that I was too worried about systems maintenance and contingency planning to bother with putting my own tools together, but it turns out that this was easily worked around.
Good luck in achieving your goals.
- hrorq 4y agoThis is true. Existing systems really solve an extreme user's issues or are too limited in their ability to be flexible to a user's (in this case, my) requirements. Yeah, going ahead with the no-code/low-code solution seems most plausible. The challenge is to not over-engineer it and make it an ambit for my own fallacies or lapses in behaviour. Keeping it light, balanced, and focused should be the priority. I think the emotional side of things can come in a bit later as what I am looking for is that core, objective follow-up and motivation for task completion as well as a progress update on every weekend, month-end, and year-end.