Back
Similar todos
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
Got the GoLand debugger working with my web app backend, it was super easy, I just had to switch the configuration "Run kind" from Package to Directory and point it at /cmd/api/
Started looking into how to debug Go code: blog.jetbrains.com/go/2019/02… 
#govuetifytemplate
Continue reading the IntelliJ tutorial on debugging Go; was told I needed to install the ARM version of Go so I did that; trying to resolve other errors when I try to run the debugger.
Kept exploring AI-assisted code tools and switched from Cursor back to VS Code and subscribed to GitHub Copilot Chat 
#chores
Spent time learning about using Go for a web app back-end to see if it would be better than using Python.
Go: Switched my existing 'hello world' route/handler to use huma as a way of familiarizing myself with huma; checked out the huma-auto-generated /docs endpoint; spent ~90 minutes debugging an issue w/ how I defined a handler b/c the error message was not at all helpful; got POST /api/users (new user registration endpoint) working with the new setup (chi/huma).
Spent an hour reading some of [the backend code][1] for a Go / Vue chat app I saw posted to Reddit, as a way of trying to build familiarity with how my Go / Vue projects should be structured / work.
[1]: github.com/wizzldev/backend/
Go: Bought "Let's Go Further" b/c it has a section on authentication for API backends; read that section; notice he has the code in his project set up differently than mine; rearrange my project directory structure to match the book's recommendation; spent some time looking at how he does authentication in the book; decided that I should maybe instead try to follow the Huma guide to doing OAuth 2.0: huma.rocks/how-to/oauth2-jwt/
got my personal website (nathanwailes.com/, just an index.html) working on a new $4/mo DO droplet that I intend to move everything over to while switching backends from Python to Go, nginx is way easier than Apache so far. Switched my personal site to use GitHub version control.
Gradually learning to use the git UI in Jetbrains
#life Buy JetBrains all Products Pack because I get it at 40% discount now
cross post dev.to/golangch/what-i-develo… 
#altafino
Started going through the "Let's Go" ebook, started my first Go web app.
upgrade to heroku hobby dev 
#tba
Struggled to incorporate the Line "echo bot" code into my existing Huma Go backend framework code, so I just YOLO'd it and copied the example code into my `main.go` for the purpose of seeing if I can get it working...ran into an error when pushing to Dokku, it seems to be because I didn't set the Line-related env variables before pushing...set those vars on my Dokku server...clicked the Line 'Verify' button for the callback URL and got a 404, so I now need to look into what happened...I think the issue is that the echo bot code assumes I'll use the DefaultServeMux, but I'm actually using a chi Mux. The key line difference is `log.Fatal(http.ListenAndServe(":"+port, r))`, where the example has `nil` instead of `r`...YOLO'd it again by just disabling the router I had gotten working, just to see if the webhook will work, and got a Success when I clicked the Verify button...next up is to either clean up this mess I've made in my code or keep pushing forwards and try to get the ChatGPT part working.
