Day 11 of #100DaysOfCode
After logging in, notebook's data is now saved in the cloud, so you can access your data from any device. Plus, a perk of logging in is now you can reorder your tasks.
#builtinpublic
Day 10 of #100DayOfCode
I tried to ask AI how to configure a custom auth domain and it made me migrate my project, do some refactoring and go through so many loops. Lesson learned: follow YT videos like I used to before AI and it'll save me 4 hours.
@Nightmux@nextjs You say learning SEO is procrastination, what would you recommend to do when away from my workstation? I dont really have a lot of content on my page, so im just checking CTR. Once i add more content, i'll track how users interact with that content
Day 8 of #100DaysOfCode
One thing that I've absolutely being obsessing over are my app's metrics. Since I'm building with @nextjs, I've started reading their guide on SEO optimisation whilst idling as I'm travelling. I hope to implement what I'm learning as soon as I get back
Day 9 of #100DaysOfCode
Well not really coding, more planning. I spent some time at the airport with my stylus and S24 Ultra designing the dashboard, new features and APIs. Hopefully, I will commit some code tomorrow and soft launch user auth here
Day 7 of #100DaysOfCode
For the next few days, I'm on holiday so I'm updating and still keep the momentum going. The main goal of this project is to learn more about Software Engineering (also coz i cant get a job in this market), so I'm reading Software Engineering at @Google
@mitansh_j07 I've read that the most optimal way of implementing auth persistance is using cookies which i've never used before. Ive stored data in local cache, but that is client side rendering and would be an even lazier solution. But yes, at the end of the swe is all about iteration
Day 6 of #100DaysOfCode
I've spent more time today integrating auth persistance than the actual auth itself. I've implemented "sloppy" solution, I'll improve this process in a future iteration.
Day 5 of #100DaysOfCode
User auth✅
It wasn't as dreading as I thought it would be. @Firebase also makes it stupid simple with their API and their doc to implement auth. I'm most likely going to use it again for DB, I just need to do some research on how to design a NoSQL.
Day 4 of #100DaysOfCode
User auth. The feature I dread the most when starting projects as it's the same everytime, it's long and I don't learn anything new. Fortunately, I get faster each time I implement it. Just designed the UI for now, implementation will start from tomorrow.
@anupamrjp My own productivity tool, boffin. Still in very early stage. It's still a passion project and I'm only able to spend 3 hours a day on avg after work developing it. I've working on it for only a week. I've also been documenting my journey on my profile.
https://t.co/b8He11rdrM
@anupamrjp My own productivity tool, boffin. Still in very early stage. It's still a passion project and I'm only able to spend 3 hours a day on avg after work developing it. I've working on it for only a week. I've also been documenting my journey on my profile.
https://t.co/LueZPIISIR
Day 3 of #100DaysOfCode
Today I added a proper header and footer. I'm not sure if it is SEO friendly enough, but I will come to later after implementing user auth. This UI isn't live, it currently lives on diff branch from main. I also got a new feature request from a real user
Day 2 of #100DaysOfCode
Today I got some of the boring part of my project out of the way. Documentation. I need to implement user authentication and build a database. I wanna use firebase, since most of my project is connected to GCP anyways, but I still gotta do some research