Sasuke

8:30 AM, pulling another 10 hour session again Sadly, can't post what I'm working on but it's majorly Internet and my personal project

Building Terraform is really challenging, but I have learned that the best way to solve a big problem is to break it into smaller sets of problems. So if we go for the arch, the first thing that points to its behaviour is something like an AC that sees 3 states at a time and takes action: - what's the user’s desired temp - what’s the room current temp - what temp I have been set to in the prev attempt (if it exists) In Terraform, this is called: - Desired State (The Code) - Actual State (The Real World or AWS) - Known State (The State File) The Code is written in HCL normally, but building a parser from HCL to Go will be a completely separate project, so I will be using just the JSON to Go. For AWS state, initially I am thinking of doing it with a mock env once the arch is built nicely, then I will try to implement real AWS there. And for the state file, as it needs to store a persistent state, I can choose a db, but I know that's making it unnecessarily complex. I think I can just work with a local file. This part is easy: making the correct state level or classification of machines and their necessary data. The next part is making a direct acyclic graph of them and making that apply phase cmd, which involves making various concurent gRPC calls based on independent services and building services! But whatever, I did gain the understanding of the complete problem now and know what I have to do about it.

Started Working on a new project habit tracker to practice React + Typescript Later, maybe over time I will turn this into mini full-stack project by adding Supabase/Appwrite. Suggestions are welcome:/

- woke up at 5.30 am - saw payout money received in the bank - hit gym - had a protein rich breakfast - all set for the day (btw ignore my hair, ik i need a haircut now)