Worked on organising tasks for all my responsibilities decided to follow a very simple model of backlog -> tomorrow -> today planning. Which is guided by a quarterly plan and notice calendar.
Started documenting a plan for an MVP of a product I'm working on.
Broke down tasks that need to be done in the next few days
Got back to reading a book about making an interpreter in Go. Realised whilst building the lexer tests that I'm fuzzy on idiomatic Go so I decided to pickup some books on learning Go more in depth.
Contacted an open-source maintainer to see if a feature flag solution had been created or finalised yet so I could start coding up a potential feature to add.
What I learned
Tokens are a combination of "types" and "literals" and these are used by a lexer to produce tokens from each input to the lexer ie the input "=" is read and a token with type "ASSIGN" and literal "=" is created.
Go syntax and use is vastly different to object orientated languages that I am used to however overall it seems more concise and straightforward with lesser amounts of abstraction.
Simplistic planning always works out the best, every time I use more complicated planning besides a long-term guide that feeds into a calendar that feeds into a backlog that feeds into today and tomorrow planning its never used. Even a week is too much, the plan doesn't even survive Monday. Perhaps that is the nature of university though, could be different outside university in a more stable environment.
Reflections & Mood
Go feels vastly more rewarding than most languages that I have wrote in so far. Though there is a learning curve the language gives a nice insight and understanding into what each line or block of code is actually doing without burying too much of it under packages etc.
Feeling okay, should be the last full day of admin stuff before I can get back to learning, working, studying and building things for the majority of the day.
How it feels spending most of the day doing life admin
