Kept going on the code to send Gmail emails from my Go backend, this is a good way to get comfortable with Go...successfully ran the `quickstart.go` file example from developers.google.com/gmail/a… more time reading advice on Reddit about how to apply for jobs.

Fixed a bug where the resume status-checker wasn't returning the right value b/c the auth middleware that loads the user wasn't selecting all user fields...fixed misc other issues with the PDF uploader / Delete buttons...successfully sent myself an email with my resume attached (Cursor sped that WAY up)...got it working where the original resume filename will be saved to the db and then used as the attachment filename...got it working where I can customize the email title and body in the frontend UI...fully replicated the last email that got me a full-time job offer, including images...have my email title and body saved to the db and populate the fields when I load the frontend view...

Worked on a first draft of a 1-page "how to hire and manage remote workers" PDF that I want to start sending along with my resume and possibly also use as a marketing thing for my Wailes & Company remote work management consultancy idea...drank a double espresso ~4-5hrs before my expected bedtime, I hope I don't regret this...emailed another YouTuber but w/ a slightly different email approach...continuing to learn how to use Cursor, resolved a deploy.yml error by signing into GitHub after some Googling to understand what was going on...spent a while breaking up my backend code into sub-app directories as a way of setting the stage to work on multiple app ideas at the same time, and also to continue to build familiarity with Go since I'm still very new to it...spending the time after the caffeine high has kind of worn off (3hrs post-double-espresso) just thinking about what I should work on next...decide on some next small steps for tomorrow: 1) be able to query the Algolia HN API and get back the list of HN jobs, 2) set up a new db schema for the jobs app, 3) figure out how to best use ChatGPT to analyze the different job posts (individual queries vs. some kind of batch request).

Only got ~5hrs of sleep after two double espressos yesterday, so I took a Lycopene capsule...signed up for a LinkedIn Premium free trial so I could send a message to a Kasikorn backend engineer to ask why users can't export their transaction history in CSV format...removed the 'Blog' link on nw.com b/c I don't have the WordPress blog up and I never really used the blog that much, added a link to my email address instead so people can contact me...started going through the Kasikorn API "Slip Verification" challenges...got the first one done...the second one requires I have SSL set up on my domain and not through Cloudflare...discovered while doing that that my whatdo site is returning a 404 if I try to sign in...got GoLand's db tool connecting to the digital ocean postgres db b/c I noticed that wasn't set up yet...install postgres on my macbook b/c something got messed up and somehow it seemed to not be installed...got all the db problems fixed, don't know how that happened...now having a CORS issue when running locally, all this stuff was working, IDK how it all broke...ok I remember now, I YOLO'd the backend code and disabled the existing router to get the Line echo bot working...sent an email to another local YouTuber to ask if I can be in a video with him...installed cursor and tried using it for a simple refactor task to get a sense of how it works...figured out a way (thanks to ChatGPT) to get the Line callback handler working while also not breaking the existing routes...went for a massage to give my brain cells some time to recover...used cursor some more and I get the hype, this is really cool, I'm surprised Jetbrains hasn't copied it yet...after a long while I finally got my whatdo backend working properly again (auth + user middleware working), it was a good learning experience with cursor and Go...got a GitHub Action set up so my DO dokku VPS will update when I push to main, so now both frontend and backend will update automatically when I push to GitHub...ending the day on this banger set: www.youtube.com/watch?v=d2340… Tomorrow: I need to bill hours to my client to make $, I want to try to finish the KBank API challenge to see if I can do the Slip Verification, I want to email another YouTuber, if I have any time left over I want to keep going with that Line/ChatGPT bot and try to make a frontend interface for it.

Only got ~6hrs of sleep, so try taking 120mg of lycopene...emailed back the WorkTime rep b/c their software isn't tracking any activity, it's crazy for it to be so broken in such a basic way...ask on Upwork forums if identity verification ever needs to happen again...created a Jira board for managing studying system design...started a pastebin system for rehearsing basic system design patterns daily b/c that's been working well for studying DSAs...feeling anxiety today, presumably from all the caffeine yesterday, so I'm going to take some Caffeine+ capsules to see if the extra vitamins in it makes the anxiety go away...run the Algolia HN API request that I found in the hnjobs repo in Postman as a first step towards grabbing those jobs myself...spent 30 minutes feeling anxious about what the next step should be, thinking I should set up the backend pulling jobs, before changing my mind and deciding I want to be able to use a frontend UI to connect my email address and then press a button to have the backend send an Gmail email for me...

Spend hours and hours pouring through the raw output gmail processes of my emails as nobody seems to be able to fix it, and find plenty of issues that are possible to fix so fix them - of course with tabs and spacing a lot of errors, because why process things nicely when you can do them horribly! My detest of google will outlive me (or hopefully them). Manage to figure out how to get it to respond to responsive fonts, of course it doesn't respect the actually set size and instead increases the baseline which makes it impossible to manage, so ultimately find a compromise whereby it's not too large on gmail, not too small on other phone clients - nobody will have it perfect. Email clients. The best. #creativity

today was my first day actually doing Go development instead of just tutorials: took a magnesium tablet b/c I felt anxious last night, I think from the caffeine in the cocoa I had been drinking; copied my frontend code from my flask/vuetify template repo to my go/vuetify template repo; confirmed I can serve the frontend code locally; installed Go; drank an iced cocoa; successfully started my 'Hello World' main.go backend file as a web app server; asked ChatGPT for help converting my "POST /users/" request to use Go; created a Go module; installed Postman macOS; took a 15min break after an hour; got my frontend app "talking to" my Go backend (successfully returned "Hello World" and had it on-screen in my frontend app); added Go middleware to log every request to the console so I can see what is happening; renamed my (default) branch from 'master' to 'main'; got live reloading for my Go backend (it automatically reloads the backend when I make changes to the code); confirmed my "POST /users/" returns 201 when I use the frontend registration form; came up with a task for tomorrow: get "POST /api/session" working; set up PyCharm to be able to explore my SQLite db from within the DB toolbar; confirmed that my user registration created a new user record in the db

Send email 2 #work