<h1>building my own cli tool</h1>
<p>i've used a lot of developer tools in my time. linters, formatters, analyzers, you name it. they're all useful, but they all share one thing in common: they're too nice. they tell you "this could be improved" when what they really mean is "this code is a disaster and you should feel bad."</p>
<p>i wanted something different. something honest.</p>
<h2>the spark</h2>
<p>it started when i was dealing with a legacy codebase. you know the type, thousands of lines, no comments, variables named <code>data</code>, <code>data2</code>, <code>result</code>, <code>final_final.js</code>. i ran every analyzer we had and they all gave me the same polite suggestions.</p>
<p>i wanted something to look me in the eye and say "this file has strong 'we'll refactor later' energy."</p>
<p>so i built it.</p>
<h2>building wtf-code</h2>
<h3>the stack</h3>
<p>i went with typescript because i wanted type safety. cli tools can get messy fast. for parsing, i used acorn, a javascript ast parser. no ai, no apis, just raw ast analysis.</p>
<p>the core modules:</p>
<ul>
<li><code>analyzer.ts</code> - file and directory analysis</li>
<li><code>metrics.ts</code> - ast-based code metrics</li>
<li><code>complexity.ts</code> - nesting and complexity analysis</li>
<li><code>rating.ts</code> - code scoring from 0 to 10</li>
<li><code>blame.ts</code> - git blame parser</li>
<li><code>diff.ts</code> - git diff reader</li>
<li><code>humor.ts</code> - commentary and phrase pools</li>
<li><code>formatter.ts</code> - chalk-based terminal output</li>
</ul>
<p>each module does one thing and does it well. i tried to keep the architecture clean because i knew if i didn't, the tool would roast its own code, and i couldn't have that.</p>
<h3>the hard parts</h3>
<p><strong>variable name detection</strong> - this was trickier than i expected. extracting variable names from the ast is easy, but determining if they're "vague" required building a whole heuristics system. i ended up creating a list of offender names like <code>data</code>, <code>temp</code>, <code>stuff</code>, <code>thing</code>, <code>result</code>, and variations of <code>final</code>.</p>
<p><strong>the humor</strong> - generating funny commentary without ai was a challenge. i built phrase pools and templates that get selected based on code metrics. if a file has no comments and 400 lines, it gets the "pain" greentext. if it has 5 classes and 2 imports, it gets the "doing too much" joke.</p>
<p><strong>git integration</strong> - parsing git blame and diffs required understanding the output formats. turns out git output is... not great to parse. had to handle a lot of edge cases.</p>
<h3>what i learned</h3>
<p>building a cli tool is different from building web apps. you have to think about:</p>
<ul>
<li>exit codes - what does your tool return when things go wrong?</li>
<li>stdout vs stderr - where does output go?</li>
<li>argument parsing - commander saved me here</li>
<li>cross-platform compatibility - windows paths are fun</li>
</ul>
<h2>the result</h2>
<pre><code>$ wtf project

  Project analysis
──────────────────────────────────────────────────

  Files analyzed: 42

  Largest file:
    server.js (910 lines)

  Code smells detected:
    • large files
    • vague variable names

  Developer commentary:

    this project has strong "we'll refactor later" energy.

──────────────────────────────────────────────────
</code></pre>
<p>exactly what i wanted.</p>
<h2>it's a meme project (but actually useful)</h2>
<p>let's be clear: this started as a joke. i wanted to laugh at bad code instead of cry about it. the greentext format, the roasting, the brutally honest commentary, it's all meant to be funny first.</p>
<p>but here's the thing: behind the memes, it's still a real code analyzer. it counts lines, functions, classes. it detects complexity, nesting depth, code smells. it parses git blame and diffs. the <code>--explain</code> flag gives you a clean technical breakdown without the sarcasm.</p>
<p>so yeah, it's a meme project. but if you strip away the humor, you still get useful metrics. the comedy is just a wrapper around actual analysis.</p>
<p>and honestly? sometimes that's what you need. a tool that makes you laugh while also telling you that your 400-line file has "variable naming confidence level: zero."</p>
<h2>why no ai</h2>
<p>a lot of tools are rushing to add "ai-powered" features. i get it, it's trendy. but i think there's value in deterministic, offline analysis. you don't need an api key. you don't need to send your code to some server. it's just you and the ast.</p>
<p>plus, real developer humor comes from pattern recognition, not language models. the phrase "this function works but nobody knows why" hits different when it's generated from actual code metrics.</p>
<h2>what's next</h2>
<p>typescript better support is planned. right now it only analyzes javascript files, but the ast parsing foundation is there, just need to handle the type annotations.</p>
<p>i also want to add more humor pools. the community has been suggesting phrases and i love it.</p>
<h2>try it out</h2>
<pre><code class="language-bash">npm install -g wtf-code
</code></pre>
<p>then roast your worst file with <code>wtf &#x3C;file> --roast</code>.</p>
<p>sometimes you just need brutal honesty. and that's exactly what this tool delivers.</p>


building my own cli tool

<h1>building kry</h1>
<p>every discord server needs its own personality, and for our community, that personality comes from kry. what started as a simple bot project evolved into a comprehensive moderation and engagement system that keeps our server safe and welcoming.</p>
<h2>the origin story: the nekotina incident</h2>
<p>it all began with a frustrating experience. a user asked nekotina - a popular discord bot - how they could make friends to play roblox. nekotina's response? spamming other discord server invitations. this wasn't just annoying; it was actively pulling members away from communities they were trying to build.</p>
<p>that's when i realized we needed better control over our server's bot ecosystem. instead of relying on third-party bots that might not align with our community values, i decided to build kry from scratch.</p>
<h2>kry's core responsibilities</h2>
<p>kry serves as the digital backbone of our server, handling several critical functions:</p>
<h3>custom embed system</h3>
<p>kry creates beautiful, consistent embeds for all major server sections. whether it's welcome messages, announcements, or channel descriptions, kry ensures everything looks professional and on-brand. these aren't just text messages - they're rich, interactive embeds that enhance the user experience.</p>
<h3>intelligent greetings</h3>
<p>when new users join, kry is there to welcome them. but this isn't just a generic "welcome to the server!" message. kry's greeting system:</p>
<ul>
<li>provides essential server information</li>
<li>highlights important channels</li>
<li>encourages new members to introduce themselves</li>
<li>sets the tone for our community culture</li>
</ul>
<h3>autoroles system</h3>
<p>kry manages a comprehensive autoroles system that lets users customize their server experience. members can self-assign roles for:</p>
<ul>
<li><strong>age groups</strong> (helping users find peers in similar life stages)</li>
<li><strong>gaming preferences</strong> (connecting players with similar favorite games)</li>
<li><strong>interests and hobbies</strong> (facilitating conversations around shared passions)</li>
<li><strong>availability</strong> (letting others know when they're typically online)</li>
</ul>
<p>this isn't just about role assignment - it's about community building. the autoroles system helps members find like-minded people and fosters genuine connections based on shared interests.</p>
<h3>advanced antispam protection</h3>
<p>this is where kry really shines. after the nekotina incident, i implemented a sophisticated antispam system specifically designed to prevent discord invite spam.</p>
<h4>the bot whitelist system</h4>
<p>here's the clever part: kry's antispam filter only applies to other bots in the server. this means:</p>
<ul>
<li>human users can still share invites (when appropriate)</li>
<li>bots are restricted from sending discord links</li>
<li>trusted bots can be whitelisted for specific purposes</li>
</ul>
<h4>the security exception</h4>
<p>we have a security bot that needs to send appeal server links when users get banned. kry's whitelist system allows this specific bot to share discord invites while blocking all others. it's the perfect balance between security and functionality.</p>
<h2>technical implementation</h2>
<p>building kry taught me a lot about discord bot development and community management:</p>
<h3>event-driven architecture</h3>
<p>kry responds to various discord events:</p>
<ul>
<li><code>GUILD_MEMBER_ADD</code> for new user greetings</li>
<li><code>MESSAGE_CREATE</code> for spam filtering</li>
<li>interaction events for custom commands</li>
</ul>
<h3>smart content filtering</h3>
<p>the antispam system uses pattern matching to detect:</p>
<ul>
<li>discord invite links (discord.gg, discord.com/invite)</li>
<li>variations and obfuscated attempts</li>
<li>context-aware filtering based on user type</li>
</ul>
<h3>modular design</h3>
<p>each feature is built as an independent module:</p>
<ul>
<li>greeting system</li>
<li>embed generator</li>
<li>spam filter</li>
<li>whitelist management</li>
</ul>
<p>this makes kry easy to maintain and extend with new features.</p>
<h2>the impact on our server</h2>
<p>since deploying kry, we've seen significant improvements:</p>
<ul>
<li><strong>zero spam incidents</strong> from discord invite bots</li>
<li><strong>consistent branding</strong> across all server communications</li>
<li><strong>faster new user integration</strong> with intelligent greetings</li>
<li><strong>reduced moderation workload</strong> through automated filtering</li>
</ul>
<h2>lessons learned</h2>
<p>building kry taught me several valuable lessons:</p>
<ol>
<li>
<p><strong>community-specific solutions beat generic tools</strong> - a custom bot built for your community's needs will always outperform off-the-shelf solutions</p>
</li>
<li>
<p><strong>automation enhances human moderation</strong> - kry doesn't replace our moderation team; it empowers them to focus on meaningful interactions</p>
</li>
<li>
<p><strong>flexibility is key</strong> - the whitelist system shows how important it is to build exceptions into automated systems</p>
</li>
<li>
<p><strong>user experience matters</strong> - beautiful embeds and thoughtful greetings make a real difference in how users perceive your community</p>
</li>
</ol>
<h2>what's next for kry?</h2>
<p>kry is constantly evolving. future plans include:</p>
<ul>
<li>ai-powered content moderation</li>
<li>custom games and activities</li>
<li>integration with other community tools</li>
<li>advanced analytics for server insights</li>
</ul>
<h2>the bigger picture</h2>
<p>kry isn't just a discord bot - it's a case study in solving real community problems with custom technology. by building kry, i not only solved our spam issues but also created a more engaging, professional, and welcoming environment for our community.</p>
<p>sometimes the best solutions come from frustration with existing tools. nekotina's spam might have been annoying, but it ultimately led to something much better: a bot that truly serves our community's needs.</p>
<p>if you're running a discord server and finding that existing bots don't quite meet your needs, maybe it's time to consider building your own. the learning experience alone makes it worthwhile, and the end result could be exactly what your community has been missing.</p>


building kry

<h1>homelab</h1>
<p>sometimes the best projects start with a problem you didn't expect to solve. for me, it was getting suspended from a discord bot hosting service for "multi-account shenanigans." what began as a necessity quickly turned into an exciting weekend homelab experiment.</p>
<h2>the hardware: a 2015 macbook's second life</h2>
<p>digging through my old tech, i found my 2015 macbook pro - not exactly cutting edge, but surprisingly capable for server duties:</p>
<ul>
<li><strong>processor</strong>: intel core i7-4770hq</li>
<li><strong>memory</strong>: 16gb ddr3 ram</li>
<li><strong>storage</strong>: 240gb ssd</li>
</ul>
<p>these specs, while dated for daily computing, are actually perfect for a home server. the quad-core i7 handles multiple services well, 16gb of ram provides plenty of headroom, and the ssd ensures fast i/o operations.</p>
<h2>the setup: ubuntu server and docker</h2>
<p>the first step was wiping macos and installing ubuntu server. this wasn't just about getting linux running - it was about transforming the laptop into a true server. one crucial setting: <strong>disabling suspend mode</strong> so i could close the lid and keep everything running 24/7 while plugged into power.</p>
<p>with ubuntu up and running, i chose docker as my containerization platform. docker makes it incredibly easy to:</p>
<ul>
<li>isolate different services</li>
<li>manage dependencies cleanly</li>
<li>deploy and update applications with minimal downtime</li>
<li>keep my homelab organized and scalable</li>
</ul>
<h2>the discord bots: kry and xora</h2>
<p>my primary motivation was hosting discord bots, and i now have two running successfully:</p>
<h3>kry - the heavy hitter</h3>
<p>kry is my flagship project, serving a discord community. this bot handles:</p>
<ul>
<li>moderation and admin commands</li>
<li>user engagement features</li>
<li>custom integrations and apis</li>
<li>high-volume message processing</li>
</ul>
<p>running kry on my own hardware gives me complete control over performance and uptime - no more worrying about third-party service limitations!</p>
<h3>xora - the personal assistant</h3>
<p>xora serves my personal discord server, handling:</p>
<ul>
<li>custom server management</li>
<li>fun commands and games</li>
<li>integration with other homelab services</li>
<li>experimental features i'm testing</li>
</ul>
<h2>the minecraft challenge: better minecraft 5</h2>
<p>with the bots running smoothly, i got ambitious - why not host a modded minecraft server? i chose <strong>better minecraft 5</strong>, a popular modpack that offers incredible gameplay enhancements.</p>
<h3>first attempt: crafty control panel</h3>
<p>i initially tried using crafty, a web-based minecraft server management tool. the setup looked promising with its clean interface and automated server management features. however, i ran into frustrating network connectivity issues that prevented me from uploading the server files properly.</p>
<h3>the direct approach: manual docker setup</h3>
<p>after struggling with crafty's web portal, i pivoted to a more hands-on approach. by creating a custom docker container and manually configuring the server files, i gained:</p>
<ul>
<li>complete control over java settings and memory allocation</li>
<li>direct access to logs and configuration files</li>
<li>the ability to fine-tune performance for the modpack</li>
<li>a deeper understanding of how minecraft servers actually work</li>
</ul>
<p>the result? a stable better minecraft 5 server ready for my friends to join!</p>
<h2>network magic: playit and custom subdomain</h2>
<p>here's where it gets really cool. i needed to expose my minecraft server to the internet without dealing with complex port forwarding and router configuration.</p>
<h3>playit.gg tunneling</h3>
<p>playit.gg provides secure tunneling services that create public endpoints for your local services. with playit:</p>
<ul>
<li>no router configuration needed</li>
<li>automatic ddns updates</li>
<li>secure tunneling through their infrastructure</li>
<li>easy setup with just a few commands</li>
</ul>
<h3>custom subdomain integration</h3>
<p>the cherry on top: i pointed a subdomain from my company website directly to the playit tunnel ip. now instead of sharing some random ip and port, my friends can connect to something clean and professional like <code>minecraft.mycompany.com</code>.</p>
<h2>lessons learned</h2>
<p>this weekend taught me several valuable lessons about homelabbing:</p>
<ol>
<li><strong>old hardware has value</strong> - that 2015 macbook i almost forgot about is now a workhorse server</li>
<li><strong>docker is essential</strong> - containerization makes managing multiple services incredibly clean</li>
<li><strong>problem-solving beats convenience</strong> - when crafty didn't work, manual setup gave me better understanding</li>
<li><strong>network services are powerful</strong> - tools like playit make self-hosting accessible without complex networking</li>
<li><strong>start with a real need</strong> - having actual discord bots to host gave me motivation to see this through</li>
</ol>
<h2>what's next?</h2>
<p>now that the foundation is solid, i'm already thinking about expanding the homelab:</p>
<ul>
<li>adding monitoring with prometheus/grafana</li>
<li>setting up automated backups</li>
<li>exploring self-hosted alternatives to other cloud services</li>
<li>maybe even hosting a small website or two</li>
</ul>
<h2>the takeaway</h2>
<p>what started as a workaround for a discord bot suspension became a full-blown homelab project that taught me more about linux, docker, networking, and server administration than months of reading tutorials ever could.</p>
<p>the best part? i now have complete control over my digital services, save money on hosting, and gained valuable skills along the way. plus, there's something incredibly satisfying about turning "obsolete" hardware into something useful and powerful.</p>
<p>if you have old hardware lying around and a problem to solve, maybe it's time to start your own homelab adventure. you might be surprised what you can accomplish in a single weekend!</p>


homelab

<h1>my journey</h1>
<p>since i was very very young i fell in love with technology, phones and computers. back then i didn't know what programming was, so i was more into customizing everything, making android look like ios, creating youtube tutorials about how to install x program, that kind of stuff.</p>
<p>like the majority, i got interested in programming because of the idea of creating videogames. but i have to be honest, i gave up on that idea a long time ago haha.</p>
<h2>the beginning</h2>
<p>at 16, i went to a vocational highschool to study software development. that's where everything changed. we started with c++ in the first year, which was rough but it taught me the fundamentals. second year we moved to c# mvc .net, and that's when i started to see how things actually work in the real world.</p>
<p>the final year was web dev, js and php. that's when i decided i wanted to be a web developer. something about building things that people could actually use and see immediately clicked with me.</p>
<h2>where i am now</h2>
<p>fast forward to now, i'm 21, studying computer science (systems engineering), and i've shifted from web dev to backend and automation. i'm currently doing ccna to learn about networks, which has been eye-opening. understanding how data moves through networks is fascinating.</p>
<p>i cofounded tridnio studios and founded euxorasoft. i still do voice acting for minecraft events, which is fun and keeps me connected to the gaming community even though i'm not making games myself.</p>
<h2>what's next</h2>
<p>i'm interested in low-level stuff, reverse engineering, cybersecurity, ai, and rust. there's so much to learn and explore. i primarily use windows on my desktop (college programs and gaming), but i'm running linux on two laptops, currently trying arch (omarchy) and ubuntu with omakube.</p>
<p>i normally use typescript for my web projects and java because of college. but i'm always experimenting, always learning.</p>
<p>the journey from customizing android phones to where i am now has been wild. and honestly, i'm just getting started.</p>


my journey

<p>hello world</p>
<p>this is the beginning of my blog. here i'll write about low-level programming, backend development, automation, cybersecurity, reverse engineering, and whatever else catches my interest.</p>
<p>expect random notes, technical deep-dives, and thoughts on the things i'm learning and building.</p>
<p>let's see where this goes.</p>
