_
>projects_shipped:13
>time_frame:3 months
>avg_build_time:3 days - 2 weeks
>hackathon_misses:6
>reason:"already building next one"
>status:OBSESSED
// process
Speed isn't about rushing. It's about eliminating wasted cycles through upfront research and clear scope.
Before writing a single line of code
- ›Social media listening for user pain points
- ›Market validation and competitor analysis
- ›Understanding what users actually need vs what they say
- ›8-12 hours of research before implementation
Avoiding roadblocks before they happen
- ›Tech stack decisions based on project needs
- ›Scope definition - what ships, what doesn't
- ›Identifying potential blockers early
- ›Design system reuse to save 10+ hours per project
Heads-down shipping
- ›No notifications, no meetings, just code
- ›48-72 hour sprints for core architecture
- ›Ship when it works, not when perfect
- ›Ruthless prioritization of features
// contact
profile.png
status:open for collabs
looking_for:co-founders, collaborators, interesting problems
response:<24 hours
$ echo "ship fast, ship often"