user should be able to add e.g. smalltrack to the link

• add project field to LinkForm
• add project field to Links

• connect to vercel

• data model
• links
• delete /server

elon make API too expensive

until it become economical, track plox

• server route
• client UI/UX

e.g. are you sure

• install react query
• install RQ devtools
• Providers component
• add P to layout
• refresh/refetch on submit

• show date on LinkForm, let user pick date
• show date on Links
• user can edit date on Links
• date object should be same day [1]

too small

• facebook login
  https://developers.facebook.com/docs/facebook-login/

• move components into atoms, molecules, organisms

one day behind

dashboard

https://github.com/themesberg/flowbite-admin-dashboard

problem:

field type is currently String - might be too unusual

need to add ?timezone offset when type of date is DateTime so that the date is what's in date picker and not e.g. 1 day behind due to time zone

possilbe solution:

revert back to DateTime and find client + server side handling

too small

can't see boundaries

• date added to todo
• add related company field

🐇

• data model
• get route
• upsert route

frontend

• show
• create

backend

• add Project data model
• update migration
• update local
• update railway

frontend

• update TodoForm
• update Todos

newest to oldest

show human readable in read mode then e.g. 2024-03-16 for edit mode

https://www.reddit.com/r/node/comments/wulc2w/what_is_prisma_bad_at/

Essentially, prisma is like any other ORM. It works great until you need to do something that it doesn't support, and then it breaks down fast. It's for this reason I tend to avoid ORMs in general and stick to query builders that are 1:1 wrappers to Sql (check out kysely for an interesting query builder in the works). What pains me most about Prisma, is that their model breaks down quicker than other ORMs I've used.

pros

• fix timezone issue

cons

• change architecture

I want to know if I made two posts in one day that they're sorted reverse chronologically

e.g. the engagement one came later in the day IRL so it should be first in this list

• rails api
• configure postgres locally
• add-platform x86_64-linux
• secret key base [1]
• add postgres resource on railway
• deploy

1 - https://community.render.com/t/missing-secret-key-base-for-production-with-rails/5183

options

• devise
• doorkeeper 1

cons - not good UX as user logs in and out all the time :/

https://sdrmike.medium.com/rails-7-api-only-app-with-devise-and-jwt-for-authentication-1397211fb97c

save on duplicate calls

s3

upload e.g. screenshot

https://obsproject.com/forum/resources/background-removal-virtual-green-screen-low-light-enhance.1260/

https://www.youtube.com/watch?v=veqNEsMqEE0&ab_channel=RoyShilkrot

help user track social media engagement

https://www.kevinqi.com/react-calendar-heatmap/
https://cal-heatmap.com/
https://github.com/haripo/react-github-contribution-calendar

• upgrade to prod