Integrate the DeepSeek API into popular softwares.
github.com/deepseek-ai/...
Integrate the DeepSeek API into popular softwares.
github.com/deepseek-ai/...
Paddle finally approved my application.π
Keep it up!
Changes in learning methods.
Used to be: thank you for the recommendation, I go to learn.
Now: Thanks for the recommendation, I'll let Cursor learn.
I almost bought $TRUMP at $72.π
Fortunately, I hesitated at that time.
Mostly nextjs
I should terminate this #100DaysOfCode plan... π
Returning to work at the company recently and the treatment for my recent illness have taken up too much of my time. π©β³
yes letsconnect
πͺDay 18 of #100daysofcode
1. Fixed styling issues in the portfolio project.
2. Bug fixes for the snippet tool.
#buildinpublic #letsconnect
πͺDay 17 of #100daysofcode
1. Back to work after a 2-month break, still adjusting to the work pace..
2. Optimizing the Landing Page for SaaS Applications.
#buildinpublic #letsconnect
πͺDay 16 of #100daysofcode
Organized my tech stack based on several projects:
π¨ Frontend:
- NextJS
- TailwindCSS
- Shadcn
π Backend:
- NextJS
- Firebase (database + auth)
- one-api (AI api)
π§ Additional tools:
- Vercel Coolify (hosting)
- Paddle (payment)
- Cursor (ide)
πͺDay 15 of #100daysofcode
1. Fixed refund logic bug, pop-up bug.
2. browser-ui failure turns out to be the cause of deepseek: abnormal version
#buildinpublic #letsconnect
πͺDay 14 of #100daysofcode
1. The SAAS application runs the payment process, and now the refund logic is buggy.
2. Experience browser-ui, but try a bug with the deepseek model and don't run.
#buildinpublic #letsconnect
πͺDay 13 of #100daysofcode
1. AI Saas Project Deploys Local Payment Test Environment, Access Third-Party Payment Process.
2. Found a more cost effective vpn and replaced it
#buildinpublic #letsconnect
πͺDay 12 of #100daysofcode
1. cursor use tutorial preparation
2. Improve the ai saas subscription process and logic
#buildinpublic #letsconnect
πͺDay 11 of #100daysofcode
Improve the authentication of AI Saas interface and increase the computing logic of credits
#buildinpublic #letsconnect
πͺDay 10 of #100daysofcode
Migrating Saas services from Vercel to Coolify.
#buildinpublic #letsconnect
πͺDay 9 of #100daysofcode
The medication's effects have worn off, I'm back!
Migrated two self-hosted services to the new server.
If you are interested in tech #letsconnect.
#buildinpublic
I've been feeling under the weather lately and just don't have the energy to code. It's been really tough.
Thanks for the support! Take care of yourself too!
Thanks for looking forward to my work! You can check out the live demo byte.ink , and I'll be open-sourcing it later.
β
πͺDay 8 of #100daysofcode
1. Complete the deployment of coolify.
2. Relearn cursor systematically.
3. Go to the hospital for treatment.
If you are interested in tech #letsconnect.
#buildinpublic
2024 has been tough.
Tired of the corporate grind, dreaming of being an indie dev but can't let go of the high salary.
Good news: a few months off to chase the dream.
Bad news: it's sick leave due to a serious illness.
#buildinpublic #letsconnect
πͺDay 7 of #100daysofcode
Todayβs been a bit rough.
1. The server deployment for Coolify is still throwing some errors.
2. The SaaS app API is using an auth token for authentication, but I havenβt got the process to run smoothly yet.
#buildinpublic #letsconnect
πͺDay 6 of #100daysofcode
Continue developing the SaaS application:
1. Integrate Paddle payment into the SaaS application.
2. Replace the third-party AI interface.
#buildinpublic #letsconnect
Weekends are kinda scattered for me, so I might just check out some marketing stuff.
πͺDay 5 of #100daysofcode
no coding today, checked out the pricing design for AI SaaS solutions, and being a dad.
#buildinpublic #letsconnect
π€
Thanks, the project's almost done.
πͺDay 4 of #100daysofcode
1. Refine the data management logic of AI SaaS applications.
2. Portfolio project addresses mobile compatibility issues.
#buildinpublic #letsconnect