SimplGy

Daily Obsidian user here. I often need to do a bit of math or adding numbers in a column, and could be the target market for this, but I'm not sure yet.

I am confused about using Excel as a metaphor, and calling things "cells" -- Excel is all about cells and tables, but actually this is just "assigning variables and doing a bit of math inside of :: these blocks :: like a templating language.

Suggestion: just explain it like that to people?

As a feature request, I often have a list of values (in a column) and want to sum them. It'd be nice if I could write it and have it print the sum in the view/wysiwym mode. Eg:

:: 10,000 20,000 5,000 = total_expenses ::

(maybe it could ignore commas too :) )

Cool work, love seeing things in the markdown space!

Reminds me of "The Duke", a great board game that exposed the piece movements by necessity.

https://www.nonsensicalgamers.com/the-duke-review/

Very happy to be with hubitat. It’s OSS and not user friendly, but it mostly works with most devices and once it’s running I don’t have to maintain it except to restart (twice in about 3 years)

I also like that if I did want functionality enough (Eg: graph of temperature) I could probably figure out how to write a plugin.

Testing User Interface code sucks. I hate it. It's difficult and fragile. You probably agree so far. Controversially; I also think UI testing is low value and the answer is to be pretty decisive about cutting it.

Probably happens to all of us, especially the kind of folks that read Hacker News, I just wanted to think about it, and thank them.

I find I keep coming back to this as a framework for thinking about product decisions.

I wrote a post about this, because I think it surprises my engineering colleagues.

But I think objectively, it's a better quality of life per dollar than anything else available in the area.

The distraction free workflow with timer motivation is a really killer feature. I wonder if you could handle the longer term PKM / organize / retrieve kinds of use cases by integrating really nicely with tools that focus on that, like Obsidian?

Respectfully, might need to rename it if you’re going for broad adoption.

Just imagine speaking the name of your product to a family member who asks what you’re working on, or the cashier at the grocery store asks what your startup is.

I know you don’t know me and it’s none of my business. I just thought better to rebrand sooner than later. Maybe ask someone you trust wrt marketing kinds of questions?

I came here to say this. The similarity was so striking it was jarring. Both really great articles. Might both be explaining the ~same thing in different terms.

So you actually mentioned web3, but not the technology from it that is most interesting to me for this problem.

I’m hopeful that “decentralized identity” is a solution here.

In theory this would let people cryptographically prove whatever small fact about themselves they would like to share with a service provider like marginalia, without paying you, or sharing their identity, or anything else.

Eg: “I am a human”, or “I have written less that 100k words on the Internet” or “my comments have an upvote average above zero”

I am convinced that corned beef hash and pumpkin pie will still exist, but the pill lunch will roll by their side.

Searched for “chocolate chip cookie recipe”

First result had a recipe I could see both recipe and directions in a single page, no ads, no scrolling, no fake seo anecdotes about kids and grandmas.

(Pls make the search query box fit small mobile devices)

Great project idea!

This is a beautiful app, thank you for making it.

I can't find how to use a fixed-width font: are community themes the right way to accomplish that?

Markdown is a whitespace sensitive format, it might be that fixed pitch is a candidate to be a first class setting, even the default.

+1 for A local only version of this that stores plain text somewhere on my hard drive. Optionally as an encrypted zip archive.

I love markdown. It’s been my primary way of taking notes for many years.

A key benefit of the format to me is that text files will never be deprecated and are infinitely portable.

I saw mentioned a local cache. Would you add a pitch or squeeze page on this topic to help convince users like me? I want to love your product. The scrolling alone; beautiful.

Example user stories:

* can always see all notes as simple, well named, plainly organized, easy to read text files.

* Can output/sync certain folders of notes to plain text files. (To, for example, a Dropbox folder target)

I want to start using this, but I'm concerned what happens when a service changes their domain.

When the domain changes, even subtly like from api.foo.com to www.foo.com, it will break my ability to access the site. If I do not remember the previous URL, I will not be able to recover it.

More details in this github issue comment: https://github.com/lesspass/lesspass/issues/45#issuecomment-...

Has this been a real-life concern for you while you've used the tool?

http://i.giphy.com/4IuDIJDlV1HBS.gif

There are lots of existing readers, and I didn't think there was much to displaying that content.

What could be better about them?

Ah, great. That phrase "speedcoding" is exactly what I was looking for; hadn't heard of it before. Thanks!

I thought of a very concise way to say this. Tutorial videos teach me known unknowns.

I want to learn some things I don't even know are unknown.

Quiver looks really interesting, thanks for sharing. I love that you can export as plain text or markdown. The idea that this would count as "no vendor lock in" to me hinges on exactly how the text export works -- when exported, can I go back to a text-only experience pretty easily, or will I have 1000s of separate text files for each "cell". Sort of a tangent, but hey.

A big text file, with a heading for each day.

In go tasks, troubleshooting attempts, outcomes, links, etc. Then I copy+paste into github issues, commit messages, and wiki articles as needed (part of my deliverables, as @LeifCarrotson puts it).

* No vendor lock-in, no lag, no migration issues.

* Never have duplicate typing because of copy+paste.

* Get a daily history of your work going back into time in a light, portable, ubiquitous format.

* Recover from accidentally hitting the back button while writing a Jira ticket.

* Be able to precisely answer "What did you work on last week" (or last Monday when you logged out of VPN, or anything else)

I have to move the text from my file into the tracking tool(s), and that could be a downside. But I like having a layer of translation there. It lets me select and rephrase snippets that will communicate best in each environment.

Example: https://gist.github.com/SimplGy/a516c54a81fb24f807f9512fed82...

I've read both of these comments, and I really struggle to see how both of the following can be true:

1. As a hiring manager, knowing your previous salary will not impact my decision on your value. 2. As a hiring manager, I insist on knowing your previous salary. If you do not want to discuss it, you must not trust us.