Toy Project Week 3: From Initial Setup to Deployment
Here's the Week 3 development log for the toy project I'm building with a team of acquaintances. I'm a bit worried that things are going slowly overall, but if we keep taking it step by step, it'll eventually be done.
This week, I spent a lot of time on backend API design and authentication/authorization. At first I tried to build everything from scratch, but due to time constraints, I ended up replacing it with well-known libraries.
What I completed:
- Finished login and sign-up APIs
- Established the Refresh Token policy
- Drafted the DB schema
- Set up basic CI scripts
Next week's goals:
- Complete four CRUD APIs
- Finalize communication structure with the frontend
- Document error handling
The biggest lesson I learned while developing is that no one knows everything from the start. After struggling through searches, I managed to solve the problems I was stuck on. Although I'm a bit embarrassed to admit it, I also paid for video courses when the official docs weren't enough.
Since this is just a personal log, feel free to read it when you're bored, and feedback is always welcome.
3 answers
Agreed, the initial setup seems like the hardest part lol
I've been through something similar—using a library for authentication/authorization is much better for your sanity. However, refresh token policies are hard to change later, so I'd recommend designing them carefully now. Also, settling the communication structure with your team in advance will save you a lot of headaches down the road.
Well, I'm not sure I agree with that. If you start off custom and then switch to a library midway, the design might end up awkwardly half-done. It would've been better to do your research up front and decide from the beginning. Of course, it's not too late now, so it'd be good to weigh the pros and cons again.