may 27

code, design, and documentation: a trifecta of productivity (with time miscalculations)

today's checklist

  • im swissgambit on linkedin projects

  • im swissgambit on notion project portfolio

  • bookbot on linkedin projects

  • bookbot on notion project portfolio

  • compclub hub on linkedin projects

  • compclub hub on notion project portfolio

  • blog home page design

don't leave the most important tasks for the end of the day

plan and design along implementation

is what i would've been told off for if this was my computer mathematics and declarative programming coursework. thankfully, it isn't and i don't have to guiltily live through that talk again (this is why we don't procrastinate - says someone who has a phd in procrastination).

but seriously, make sure to finish your entire plan and design before even thinking about implementing your project. today, i didn't listen to my own advice, and luckily, there were no consequences.

after spending most of the day designing and gathering code materials for the blog, i tried updating my linkedin projects section and notion portfolio, but of course ran out of time.

i ended up updating linkedin and the notion portfolio slightly. my goal was to finish documenting the im swissgambit, bookbot, and compclub hub projects today but underestimated how much time it'd take to gather all the materials (code, and uploading this code to github, documentation like reports, and writing descriptions to the projects and what skills i used and developed during them).

tailwindcss and alpine.js research

when thinking about what i wanted my blog to look like, i wanted the homepage to seem like your typical social media page, but what would i put in the so-called 'profile banner'?

a countdown!

i wanted a countdown to my final year of university. why? knowing time is running out tends to activiate the 'productivity' module within me (perks of being a procrastinator, no?).

how is the figma file for the blog going?

very well!