Decent guide/list but it feels as if its for founders who love to build first and leave everything else as an afterthought. Like, the first section is Places To Launch Your Startup.
I understand your concern. The copycat problem is real.
But if you come from a technical background and this is your first time building a product, you'll soon learn that it is so damn hard to get users, especially *paying* ones.
I was there. I built something, shared it, prayed people would notice. The truth is most of the time your product fails. Better explore the problem you are trying to solve first, share your idea if necessary, and collect feedback. You'll have a much clearer picture of what you need to do from there.
I believe OpenAI used Persona during the verification step that you must complete to use their SOTA models in the API. Not sure if it's still the case now.
Anyway, I found that too much of a hassle and switched to other LLM providers.
In fact, many Asian countries use lunisolar calendars, which basically follow the moon for the months but add an extra month every few years so the seasons don't drift.
As these calendars also rely on time zones for date calculation, there are rare occasions where the New Year start date differs by an entire month between 2 countries.
He does though, especially for the early ones like Nomadlist and RemoteOk. If you read his old blog you will see a significant portion of it is about digital nomadism.
A goal tracking app that bridges the gap between a to-do list and a calendar. Todo lists don't track time, while calendar time blocks are too rigid.
I need something that gives me visibility into my pace on recurring goals while still allowing for flexibility, i.e. undone goals roll over to the next period. So Im building an internal app for myself.
TIL Salesforce acquires Heroku in 2011, way before I was even a CS graduate. I remember enjoying using the free tier of Heroku for my school projects but also the pain of dyno cold starts.
Well, depending on the scope of work, they may be still thinking hard, just on a higher level. That is, thinking about the requirements, specification, and design.
I always thought my problem was my notes being scattered and disorganized. But reading this post made me realize something. I don't need better organization for the random links or braindumps I collect over time. Because I rarely actively revisit them. Usually That happens thanks to reminders, or when I need references for something I can't find anywhere else. So I think your action engine idea is sound.
To answer your questions:
1. Retrieval. 90% of my notes never get touched the second time, and I can't remember them at the right time.
When saying 'doing the thing', we often mean getting some progress or a result. I'd say you did the thing if you consider the result created by the AI acceptable.
Agreed. In fact I believe there should be 2 main operations in a data store: retrieve and insert. For this to actually work in practice, you probably need different types of data stores for different phases of data. Unfortunately few people have a good understanding of the Data life cycle.
Hey everyone! I built a site that shows your next age milestones, all on a single page. You can see your next milestone age for each type (like your 10000th day) and save it to Google Calendar.
It looks simple, but I learned a lot building this site:
* To calculate age in planetary years, I had to look up their orbit and rotation info
* The lunisolar calendar took me quite some time to figure out (it is not the same as a lunar calendar and even changes by country)
* Adding the dog and cat age equivalents even led me to cubic splines