!rant
print("Hello World!")

Erm..... Here goes nothing.
Hello everyone, I'm [REDACTED] from [REDACTED] in the SEA region. I'm a highschool student, 17, with a hobby of programming in Python 3 as a self-taught trial-and-error script kiddy, mostly small scripts from random "Yea I should do that, how long will it take?! ¯\_(ツ)_/¯"-moments. I found DevRant while talking with people in a few programming Discord servers. Hope this is enough for a "Hello World!" post....and yea, welcome me to DevRant *pop confetti and hope not forced to clean up later*

Guy's Discord bot "crashes"
we asked him what error.
"no error" he replies
we ask for a screenshot.
bot immediately exists

We ask: have you added this and this (`client.login(token)`)?
He replies: "yes"
We ask for sauce-code, he provides
what do we see? he forgot to add `client.login(token)`

I started learning Golang today and really like it.

The error handling is *excellent*. It always works the same way and is standardized, unlike the hell that NodeJS error handling is (.catch(), try).

Modules confused the fuck out of me. I eventually figured out how they worked, but Go really doesn't try to make it easy to have multiple source folders...

I'll probably be re-writing my Discord Bot in Golang soon. Being able to have just one binary output will make things infinitely easier. Compile-time variables are another feature that's nice and easy to implement.

The goal is only having to upload a single binary to deploy on production from my CI script that has all keys and stuff inside. Feels good to finally throw all that old bad JS code out and starting completely fresh.

Obligatory this happened last night, roughly 1-2 hr before my first rant. And obligatory this is rookie and human error

After some encouragement from a few folks from a programming Discord server, I decided to give git a try. And it feels good! After an hour struggling, scouring the web and reading, I finally got the hang of git 101 and made my first working repo on GitHub!

.......except for one thing. My Picross generator (doesn't generate the image, just clues) was lost while I was struggling to get rid of the SCM from my generator in VSCode (turned out it was as simple as deleting ".git" folder), I accidentally deleted the generator. 4hr of work, down the drain. At least I kept the papers on the generator's logic so rewriting isn't gonna be a pain in the ass but...ughh.....

I did not think that making a serverless Discord bot would be such a learning experience. The code itself was easy. The hard part was the infrastructure, because I decided to automate it all with Terraform and deploy it on AWS.

Before this project, I had no idea how API Gateways worked. Now I still have very little idea how they work but I managed to build one anyway. Eventually. And then I had to figure out how to automate the deployment of a lambda layer and function that would both still be managed in the Terraform state, with any code changes triggering a rebuild and update for the resource.

And then I had to untangle a dependency mess because API Gateways have some weird issues where two resources that have no explicit dependencies on each other will throw an error if they don't deploy in the right order.

And then I went the wrong way with Github actions trying to conditionally chain multiple workflows together before I realized I could just put multiple jobs with conditions in a single workflow.

And now after all that work over the course of 2 days, I have a bot that does this:

5 fucking days of Google search after Google search. Error after fucking error. Deadline getting closer by the fucking minute. teammates interrupting me every 10 minutes over discord asking for help on their fucking part of the project

and it turns out the solution was just one damn line

One fucking line in a forEach to iterate over the model data sending the necessary aspects to the Javascript function to create map pins for the database locations

5 fucking horrible days all amounts to 1 line

Really shows how much I still have to learn. And the yelling at my screen reveals my need to take an anger management class

Me and a friend are making a discord bot, and added a warning command to warn users.

All was going well, and when we tested the deleting a warning it seemed fine. I then tried to delete all the warnings one by one, when we came across a problem. It wont delete the last warning in the array, the 1st, 2nd, 3rd etc? Thats fine, just the last index that isnt working.

Our code is like this:

list = data.warns//a list of JSON format warnings
console.log(list)//shows the value is in the list
console.log(list[index])//shows the value
delete list[index]
console.log(list)//shows its gone
data.warns = list;
console.log(data.warns)//shows the value is still no longer present
data.save().catch(blah blah)//no error is caught, and nothing crashes, it proceeds to send a message to the channel after this

but then the value at index is still there in the database as if it didn't save it, but only if the index is the last item in the array.

We have been stuck on this for over an hour and I now remember why I hate programming.

Me and my friend were doing a discord bot using an extensions that allow us to collaborate.

We were making the bot with Node JS and. Something so horrible happened.

While making a purge function wich should remove the last messages of the discord we met a problem. When you do !purge 1
It were removing 11 messages.

The problem were that in my code i were adding 1 (int) to a string (my amount of message to remove) so it result 11 as string....

This is JAVASCRIPT

I don't know if this were a bug but being able to add 1 (int) to 1 (string) it's fucking dumb. It should result an error not making it as string!

Random error that was occurring in prod discord authentication for new users (only in prod):

It wasn't returning the discord ID of the user logging in (only in prod). This should not even be possible if the user authenticates. So the null value from the ID was used and returned the first user in the DB (I know, weird mongodb edge cases). It should have returned null for the user searched not the first user in the DB wtfff.

Anyways, new users logging in would be logged in as me. Bahahah

Pushed the fix. All is good in the hood.