Ship
I created an APOD (Astronomy Picture of the Day) website. It has four pages: the "Home" page, which features a feed of API data (displaying photos from newest to oldest); a "Search" tab, where you can look up a photo by a specific date; a "Favorites" tab, where you can view photos saved while browsing the feed or the daily view (to favorite a photo, simply click the heart icon below the image—the icon changes color! ;D); and finally, a "Daily" page, where you can view the current day's photo. Things might take a little while to load, especially on the feed and search pages.
19m 51s logged
DevLog #6
I wrote the project README in a simple format (I’m obsessed with using tables, hahaha) and also took the opportunity to add a favicon to the site.
To my own stress—lol—when I went to commit to the APOD repository, I messed up and pushed over 14 files to the wrong repo; when I realized it, I just wanted to give up.
2h 5m 8s logged
1h 59m 15s logged
DevLog #4
I’ve finished the Daily APOD section. I think it turned out really well and closely matches the vision I had for the project.
The page now automatically fetches the Astronomy Picture of the Day using the NASA API and displays the featured image, title, date, and the full description.
I also added a favorites system using LocalStorage, so you can save the APODs you like best and access them later. The heart icon also changes state when an image is favorited.
24m 54s logged
15m 36s logged
SOMETHING
This wasn’t supposed to be a devlog lol.
I just found out the error wasn’t on my end; GitHub had simply gone down.
I spent ages trying to figure out why GitHub Actions kept returning a “Startup failure.” I checked the workflow, permissions, and secrets; I tried pushing via Git and the browser; I even considered starting the project over from scratch.
In the end, I checked the GitHub status page and discovered a global outage affecting GitHub Actions. New workflows were failing to start—exactly the error I was getting.
I am now officially annoyed with GitHub. I’ll wait for the service to return to normal and try again… but first, I think I need five minutes just staring at the wall.
16m 35s logged
DevLog #2
Nothing but pain. AAAAAAAAAAAAAAAAAAAAAA
I spent a good while trying to set up the project deployment using GitHub Actions, but so far, I’ve only managed to get a “Startup failure.” The worst part is that the workflow doesn’t even start, so there are no useful logs to figure out what’s wrong.
Honestly, right now I have no idea what to do. I’ve checked the settings, reviewed the workflow, and tried again, but the error remains exactly the same.
I might have to start the project over from scratch. =(
49m 5s logged
DevLog #1
I’ve started the APOD project. Right now, I’m running some tests with the API. My idea is to create something like a vertical feed with “infinite” scrolling, displaying images and information from different dates.
The API isn’t too difficult to use, especially since I’ve already worked with it on other projects and tests. For the time being, I’m just checking out some basic features, such as fetching the APOD for different dates.
37m 8s logged
Ship
I created a personal website using HTML and CSS. Right now it has three sections: Home, with some basic information about me. Projects, where I showcase my projects with images and links to their GitHub repositories. Blog, where I post devlogs and other things I think are interesting. The website doesn't use JavaScript yet, but I may add it in the future as I continue improving it.
1h 0m 39s logged
1h 29m 10s logged
4h 13m 23s logged
DevLog #2
Today I worked on my website’s interface. Honestly, I really liked the result! I designed the icons and the logo myself (which is why they look so ugly and funny, hahaha).
I spent a good chunk of time trying to get the sidebar right. It took a bit of effort, but in the end, I was happy with the result.
Ship
@AdaChan
on
My first slack bot!
I created a Slack bot using JavaScript. My bot features nine commands, including /koi-ping, which replies with "Pong!" to check if the bot is online; /koi-apod, which uses the NASA API to send the Astronomy Picture of the Day; commands like /koi-cat, /koi-dog, /koi-fox, and /koi-duck, which use APIs to send random animal images; /koi-sound, which sends MP3 animal sounds; /koi-say, which repeats the user's message; and /koi-tts, which converts text to speech using Microsoft Edge TTS.
To develop the project, I used various APIs, primarily to fetch images from NASA and of animals. I also worked with audio files to implement the commands related to sounds and text-to-speech conversion.
The biggest challenge during development was dealing with file paths. Honestly... who decided it had to work that way? 😭 I spent a long time trying to figure out why the files weren't being found before I managed to organize everything correctly.
@AdaChan
on
My first slack bot!
15m 44s logged
.png)
@AdaChan
on
My first slack bot!
40m 28s logged
DevLog #6
Okay… I finally finished the project’s README! 🎉
I think it turned out pretty cool; it’s not super professional yet, but I think it does a good job of showing what the bot can do. I might improve it in the future whenever I can shake off the laziness, haha.
I also realized I used Axios quite a bit in this project. Most of the new commands rely on external APIs.
There isn’t much else to add to this devlog; at least I’m happy it’s not just a bot that replies “pong” 😆
@AdaChan
on
My first slack bot!
36m 3s logged
DevLog #5
New command, wow!! 🎉🎉🎉🎉
Person: “Wait… isn’t that just /koi-say?”
Well… sort of. It’s basically an improved /koi-say.
Meet the new command: /koi-tts.
As the name suggests, TTS stands for Text to Speech. The bot takes the text you send, uses Microsoft Edge’s TTS voices to turn it into an MP3, and then sends the audio back to you. Pretty cool. =)
(I hate path😭)
@AdaChan
on
My first slack bot!
15m 44s logged
DevLog #4
Today I added a very simple command: /koi-say.
It does exactly what the name suggests: the bot repeats the message you type. Nothing spectacular, but it’s a classic, useful command for testing interactions.
If you don’t type anything, the bot replies by letting you know that text is required. The message might seem a bit blunt… but remember: it’s just a koizinho. 😭
By the way, I was thinking about how to explain the bot’s name in English. I think the closest equivalent would be something like “little koi”. In Portuguese, we use the suffix -zinho to form a diminutive that often conveys affection or cuteness. So, koizinho would be something like a “little koi” or an affectionate way to refer to the bot.
@AdaChan
on
My first slack bot!
40m 24s logged
DevLog #3
So… continuing the animal saga, I present to you: /koi-sound. 🐾
This command makes the bot send a humble animal selection menu. Then, you just pick one (there are still only a few, hahaha), and the bot replies with an .mp3 file containing the chosen animal’s sound.
The list of animals is still small, but I plan to add many more in future devlogs.
And a quick rant: I hate path. 😭 Who decided that handling file paths had to be done this way?
Loading more…