Skip to content
View codeby-arsb's full-sized avatar
🔆
IDK
🔆
IDK

Block or report codeby-arsb

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
codeby-arsb/README.md




Akash Ram S B







I don't actually enjoy programming.

I use it when it helps me create more.







Most of the repositories here didn't start as software engineering projects.


They started because something in my creative workflow became frustrating enough that I had to build a solution.







Some days I'm leading a media team.

Some days I'm documenting an event.

Some days I'm editing until 3 AM.

Some days I'm automating something that should never have been manual in the first place.







— THE WORKSPACE —


Sorting 10,000 photos by hand.

What annoyed me: Sorting thousands of photos manually after a long event. It drained the energy out of the entire editing room.

Why I cared: The time we spent sorting was time we weren't spending actually being creative.

What changed: I built an AI-assisted workflow to cull the bad photos automatically. It gave our team days of our lives back.


Context switching while editing.

What annoyed me: Having to break my editing flow state to open a browser, search for an asset, download it, and format it.

Why I cared: A good edit requires momentum. Context switching kills it.

What changed: I wrote a CLI utility that fetches and formats video or audio instantly. The flow stays unbroken.

[View the Utility]


Losing files in the chaos of an event.

What annoyed me: Photographers shooting amazing moments, but the media team losing track of assets across massive file transfers.

Why I cared: A lost asset is a lost story.

What changed: I automated the synchronization scripts. Now photographers shoot, editors edit, and the pipeline quietly handles the rest.

[View the Scripts]







Open the desk drawer

Things you'll currently find scattered here:


· A notebook full of ideas for event campaigns.

· Three half-finished automation scripts that I'll probably never complete.

· A massive Premiere Pro timeline that crashed twice today.

· A failed machine learning project. (I built it because it sounded complex. I abandoned it because nobody needed it.)

· Thoughts on how to make event promotions feel magnetic instead of forced.







Technology should make life easier and connect people.

Automation exists to make time for humans.

Success means peace of mind.







LinkedIn        Portfolio        Email




Popular repositories Loading

  1. local-ai-culling local-ai-culling Public

    A privacy-first, purely local AI image culling pipeline for professional photographers. Features intelligent burst detection, duplicate removal, and a web-based photographer feedback dashboard.

    Python 1

  2. VeriUnlearn VeriUnlearn Public

    JavaScript

  3. codeby-arsb codeby-arsb Public