5h 21m 48s logged
Devlog #3 - Making the app more open and dynamic: I am working on making the app feel less claustrophobic, adding/updating engines like the research engine, and making the UI more professional and multipage. Not commited and running yet, but almost there.
I made my own personal site, telling almost everything about me. The trickiest part was mastering the UI, but at the end I love the result. Want to know me better? This is basically it.
4h 41m 55s logged
Update complete, different modes, options, buttons, descriptions, and UI overall.
9h 16m 45s logged
Large UI refresh, still in progress. Not deployed just yet, but large backend refresh, as well as smoother layout and multiple pages.
1h 2m 49s logged
Made some fixes for the bugs. UI remains the same
@Ishaan_Jha
on
My first slack bot!
1h 13m 37s logged
Updated the project after review by hosting the bot on Nest, creating a dedicated Slack channel for testing, adding the requested demo link, and improving the bot with an additional /speedybot-advice command. I also cleaned up the README and verified all commands were working before resubmitting.
I made my personal site about me! I made it notebook style, as i love it that way and I like the whole engineering layout. It is pretty basic, and I didn't have much difficulty making it. There are 3 main buttons, that use a cool scroll feature to scroll to the section (i learned how to do that when i was pretty young, but it wasn't that easy back then).
15m 44s logged
Devlog 1: Starting My Personal WebsiteStarted building my personal website as part of Stardance. I created the initial structure with HTML and CSS, set up the GitHub repository, and deployed it using GitHub Pages. The first version focused on getting the foundation working so I could iterate on the design and make it feel more personal.
@Ishaan_Jha
on
My first slack bot!
I made my own slackbot! I called it speedybot. It was not too hard of a process, just running in and out of vs code and terminal :D. The commands it supports are /speedybot-ping, /speedybot-help, /speedybot-catfact, /speedybot-joke.
@Ishaan_Jha
on
My first slack bot!
17m 22s logged
Built SpeedyBot, a Slack bot created with Node.js and Slack Bot. I added slash commands for checking latency, getting help, and fetching API-powered responses like cat facts and jokes. After testing locally, I deployed the bot to Nest and configured it to run continuously with systemd so it can stay online 24/7.
I made my first webOS, called NebulaOS! It is a space themed webOS, with light and dark mode, showing a cosmos themed background. It includes draggable windows/panels of mission control, file bay, astro notes, star explorer, and comms radio. While the data is obviously random, parts like star names are all true. It is also interactive, with occasional messages of detection of satellites, or telemetry data. Some challenges was the UI, as it was difficult to add highlights to some buttons on the panels, as well as the transition from light and dark mode. The backend was not too hard, as it contained basic draggability, random data, simple animations, and maybe a little easter egg :)
15m 44s logged
Devlog #3 - Final Polish and Release PreparationFor the final stage of NebulaOS, I focused on preparing the project for release. I improved the documentation, reviewed the overall user experience, and tested the different applications and window interactions to make sure everything worked smoothly. This milestone was about refining the details and making sure NebulaOS was ready to be shared with others.
26m 43s logged
Devlog #2 - Expanding NebulaOS Features after completing the core operating system, I focused on improving existing applications and making NebulaOS feel more complete. I added more depth to the Star Explorer experience, improved the way information is displayed, and tested how the new additions worked with the rest of the system. This stage was mainly about building on the foundation and making the OS more interactive while keeping the original design consistent.
31m 57s logged
Today I focused on polishing (and building :) NebulaOS and making it feel more like a complete operating system. I improved the overall user experience, tested every app and window interaction, fixed small issues I found during testing, and made sure everything worked smoothly together. I also cleaned up the project, updated the documentation, and verified it was ready to be shared through GitHub and GitHub Pages.
2h 35m 4s logged
Ellery Devlog #2 - This time wasn’t about adding new features. Instead, I spent the time refining Ellery from the ground up. I removed over 600 lines of UI code, simplified the interface, rewrote much of the copy, and cut away anything that distracted from the actual purpose of the product. The biggest lesson I’ve learned so far is that good software isn’t just about what you build, but it’s also about what you’re willing to remove. Every animation, button, label, and panel has to earn its place. Ellery feels much calmer now. The interface gets out of the way, and the focus stays where it should: understanding your data. Next up is a new demo video, and after that I’ll be taking on the first Stardance software challenge by building my own web operating system.
8h 17m 28s logged
Ellery AI - Devlog #1 I kept watching people open a spreadsheet, stare at it, and just… give up. The story was in there. They just couldn’t see it. So I started building Ellery to fix that. Honestly, I started where everyone starts: AI that summarizes your data. But I never trusted it. The summary sounded confident, changed every time I asked, and I could never tell if it was actually true. That’s useless if you’re about to put it in front of your boss.So I went visual instead - timelines, rank boards, an insight map. They looked great. But a pretty chart still makes you do the thinking. I’d basically built a nicer haystack.The thing that actually clicked was the Discovery Engine. Before anything gets drawn, Ellery reads your data and pulls out what matters - top items, outliers, what’s out of stock - as plain findings, each one traceable back to the exact rows it came from. No model, no guessing. Same data, same answers, every time.That changed everything downstream. Now the visualizations explain themselves, and you can export the whole thing to a slide in one click.Next up: turning those findings into recommendations, then a real narrative - and pointing it at NASA telemetry to see if it holds up beyond retail.It’s early, and I’m building it in the open. Follow along if that sounds like your kind of thing.
