this is more like what i really needed. since i spend most of my time indoors, i read lots of material, so I needed a place to store the metadata of what I read. plus, i was learning a couple of new technologies, and this will wrap it up

phew

https://www.devatrophy.com/

been literally almost 3yrs since i was deep in trenches with vanilla js. completely forgot how to write a debouncer 🥲 lodash was my go-to even back then

good ol' days when i still had the obsession with js

feels like you achieved the highest level of manhood after treating your mom

once again

sup y'all

wish him all the best for this wholesome human being too

been a super busy week. hopefully i'll get to finish it this weekend

i mean, she got a point 👀
will be writing a custom bootloader today to experiment with claude opus 4 and test if the claims are really realistic

have a beautiful day y'all

my initial point to not be completely alienated

https://interrupt.memfault.com/blog/how-to-write-a-bootloader-from-scratch

so, was playing around with low-level application of agents, specifically claude opus 4. i'm working on this custom bootloader called Initia. just gave claude a really detailed prompt and with my very limited knowledge of C (and ofc the usual nattering with the AI), i got some pretty impressive results. my current implementation includes: the startup initialization starts by initializing the hardware and clearing out the BSS section so everything starts clean. it then detects available memory using BIOS/UEFI/multiboot services (so that memory is mapped correctly) and gets the file system ready. after that, it loads the kernel image and proceeds. there's an abstraction layer for read operations and there’s basic FAT32 support to read the kernel file without a hitch or error. plus, serial port logging is fully supported so that it will be easier to debug later. and full support for FAT32, exFAT, and ext2 filesystems and simple boot manager UI for picking kernels is on its way.