thesunny

This is a really cool idea. I especially like the math blocks where you can add blocks of information that actually do things. I could see this potentially even growing beyond math, but other types of functionality as well.

One optimization that might be interesting is to simply use Markdown as your main document all the time and then when you want to add special functionality like the math block to simply have that as a code block in Markdown. For example, using the triple back tick followed by the word math. Then anything inside of that math block works just like you already have.

This also makes it easy to add other types of blocks incrementally.

One challenge for me in reading the sample document was that it wasn’t clear that a math block was a math block without the comments that you wrote. Using the triple back tick with the block type would solve that problem

I really like the idea behind this. And the first impressions for me were that I loved it.

It has a few issues but should be fixable:

- Lofi needs to keep playing more than one song. I've read elsewhere, and I agree, that when the music becomes recognizable, it doesn't have the same effect in terms of helping to maintain focus.

- Loop of playlist for background noises shouldn't fade out/in before replaying

- The To Do list when entering, it doesn't wrap at all. And once it's entered, it doesn't wrap based on words so a word is split in two which is awkward.

These feel like they should be easy to fix though.

I'm keeping it bookmarked and will look for the updates. Good luck!

Yes, I have plans to log user provided inputs and the responses from GPT. You can monitor these inputs/responses to see if the responses that are coming back are of high quality. If it feels like you can improve the prompt, you will be able to use a prompt engineering tool which will let you experiment with different prompts and run them against a bunch of user inputs. You can then compare the new responses to the old ones and see if it's an improvement.

If you're thinking of integrating into another app, one of the next steps is to be able to take the AI web app you built and turn it into a component that you can put into your own websites/web apps. Also, at this point, you will be able to have inputs that are not just user provided, but can also come from your website/web app (e.g. data from your database).

I'm the creator and I'll be hanging out in the comments all day. If you have any feedback, I'd love to hear your thoughts. Thanks!

I'll be checking into the comments throughout the day. Please let me know if you have any suggestions, especially if you had some experience with open source fundraising.

While I've contributed to multiple open source projects, this is quite a different undertaking to raise funds. Thank you for any ideas or advice you have.

Switching context from, for example, focusing on a specific programming problem to taking a macro view about what you should be doing next in business can be challenging.

Over about ten years, I've come to a solution that works for me. My context is that I'm working on a startup. It's my third and I've had success previous ones (millions of dollars in annual revenue though not billions).

- Every morning, I spend 25 minutes outside my office to plan my day which includes asking questions about what I should be working on that brings value. Because it's the first thing I'm doing, I start with a clear mind. Once I know why and what I should be doing, it's pretty easy to get into focusing. The reverse is harder to do.

- Once a month, I take a day off outside the office to focus on strategy. I stay in a hotel though I recognize not everybody has the budget for it. Took a while to figure out this worked. I originally started with the idea of doing it when I think I needed it. Problem is that when you feel under pressure to complete something, is when you don't want to take the day to clear your mind and strategize but is precisely the thing that helps the most.

- Still trying to figure out the best for this, but 2-4 times a year I'll spend 3-5 days on big picture strategy.

It took a long while to have the discipline to take the time to clear my mind and strategize. The idea of I'll take it when I need it didn't work well but scheduling it did.

Eventually, I realized that not wanting to spend time to clear my mind and strategize is a signal that I should be doing precisely that. It's helped to force me to take the time.

That said, I don't think it's necessary to force oneself to do this as a hard rule. I do break the guidelines under situations, but when it becomes extended, it's a sign to take the time.

In the article, they mention the refresh token needs to be revokable which I assume means that it is stored in a table in a database or other data store. When the user logs out, the refresh token is removed from the table (i.e. it is revoked).

The JWT server would check to see that the refresh token probably stored in the browser with a cookie or localStorage is valid before sending the new JWT.

This is a biased article.

I do like that the article does some analysis to deduce that the NHTSA-FARS data is incorrect for Tesla and they make several well reasoned arguments why. Then using other data sources, they try to extrapolate what the correct data might be.

The problem is that the Tesla data in the NHTSA-FARS database is lower than expected. Yet they are comparing the "fixed" Tesla data with the rest of the data in the database that they take at face value.

It goes to reason if the NHTSA-FARS data for Tesla is easily proven to be underestimated (i.e. there are actually more fatal accidents than shown) that the data for other car manufacturers and models are also underestimated.

I implemented Android support on Slate. It is currently the first release and I will be committing time to fixing the remaining bugs starting within this month most likely.

Timely for me as well. Another reason for adding an additional version number component is this: I use an open source library that I need to fork. Since the library uses the `patch` number component, it's hard to release forked versions to NPM without having conflicting patch numbers.

For example, if the library is at `0.15.4` I don't want to release my updates as `0.15.5`, `0.15.6` etc. because when the main library updates to `0.15.5` we have conflict/confusion. Instead, I'd like to `0.15.4.1` to indicate my `.1` update to `0.15.4`. When they update to `0.15.5` I can merge and release a version at `0.15.5.1`