Skip to content
View iankiku's full-sized avatar
πŸ—οΈ
#BuildInPublic
πŸ—οΈ
#BuildInPublic

Block or report iankiku

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.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

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

Report abuse
iankiku/README.md

Hi there πŸ‘‹

LinkedIn

About Me

Product engineer by day, code explorer by night. I turn coffee into solutions and dreams into deployments. Whether I'm crafting AI agents or building the next big thing, I'm always in my element when turning complex problems into elegant code.

What I'm up to:

  • πŸš€ Building AI Agents that make life easier
  • 🧠 Deep diving into AI possibilities
  • πŸ’‘ Crafting full-stack solutions with Python, TypeScript & friends
  • 🌐 Connect with me on Twitter | LinkedIn

Tech Stack


Profile views

Made with πŸ’š using components from Readme components

Pinned Loading

  1. iankiku iankiku Public

    Personal blog

  2. vibe-cli vibe-cli Public

    Vibe CLI: Speak Plain English, Run Dev Commands

    Python

  3. Grokking the coding interview equiva... Grokking the coding interview equivalent leetcode problems
    1
    # GROKKING NOTES
    2
    
                  
    3
    I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
    4
    
                  
    5
    So below I made a list of leetcode problems that are as close to grokking problems as possible.