🥔 True story: two of my hackathon teammates spent 2 days building the exact same feature.
Neither knew the other was doing it. We found out when they both opened PRs for basically identical code.
So I built something to fix that 🧵
Started as a hackathon fix, but it works just as well for any small team shipping fast. Side projects, startups, whatever. Anywhere coordination is the thing that quietly breaks first.
Felt like a fitting way to represent where I actually am right now: 4+ years frontend, currently going deep on Go and backend systems on the side.
Check it from https://t.co/Vbsql1quiF
Built my portfolio this weekend with one rule: no boring grid layout.
Flip the toggle in the nav and the entire site switches from a clean, polished frontend view to a raw "backend" view. Same content, rendered as JSON and logs instead. Same data, different layer of the stack.
Last 12th June, I participated in the Infinity AI BuildFest at BRAC University.
While my team didn't make it to the winners' list, the experience was absolutely worth it. 🧵
The biggest takeaway wasn't a prize.
It was:
• New technical learnings
• Valuable feedback from mentors and participants
• Meeting talented builders
• Gaining more experience shipping products quickly
It looks like the Golang port of the transcoder is working now. However, it still lacks dynamic input handling. My next steps are:
1. Accept the source file path, desired resolutions, and output directory name as dynamic inputs.
The HLS Transcoder I was working on seems to be done (mostly). It now has a REST API wrapper. You can now access the `/transcode` endpoint to initiate transcoding of your uploaded video file. You can also check the progress status in `/transcode/status/<task-id>` endpoint