Day 11/100 of trying to be consistent
>continued book reading (the idiomatic approach)
key takeaway
"In many languages, a nonzero number or a nonempty string can be interpreted as a boolean true. This can be confusing. Unsurprisingly, Go doesn’t allow truthiness."
Day 10/100 of trying to be consistent
>Made a BGV crew in python using crewai for my college project
> Created Design Docs for other features after brainstorming with GPT
> Day 8/100 of trying to be consistent
--> Implemented a terminal based chat sever to which multiple clients can connect and chat in a group .
-->This drove me to dig deeper in the area of interfaces in go and explore the net.Conn interface
Day 6/100 of trying to be consistent
>Revised GET from Scratch and appropriate StatusCodes
>Answered the compiler viva
Will share somethings related to a hackathon project we built soon!
Day 4/100 of trying to be consistent
> Explored the concepts around Makefile and its importance
> Came to know about some linters in go and language servers (anyway most modern IDEs handle that to a decent extent)
Couldn't cover up much tho
@christoph_wertz@Grady_Booch True. I have seen it writing the most sophisticated piece of code which would take days for humans to write but yet fumbles on maintaining the broader context and sometimes the most simplest of things.