Imran Shaikh

Do you remember when you joined X? I do! #MyXAnniversary

@s_chiriac PDF Generation API typcraft.com

Sell me your startup in 3 words! add link! 👇

@Robert_Watkin_ imrandev.com

Let me roast your landing page 🔥🔥🔥

@jaxnode @gitconnected At this point its kinda gamble.

Stop ‘Vibe Coding’. You Are Destroying Your Career. by Prem Chandak in @gitconnected levelup.gitconnected.com/stop-vibe-codi…

@buildinpublic Building typcraft.com

What are you working on this week?

@just_siddardh14 Here is my one imrandev.com

Devs, drop your portfolio website here... I'll rate it out of 10

@JorgeMenaDev Absolutely 💯

built product after product thinking the code would speak for itself. it doesn't. nobody cares how clean ur architecture is if they never see it. shipping is easy now. getting attention is the real skill. time to cook differently

@aher_vet google calendar sync sounds like a nightmare honestly. and yeah puppeteer in docker - you don't really understand the pain until you've babysat those containers at 2am

@imrandev Google Calendar API. The docs make it look simple until you actually try to sync events both ways reliably. Puppeteer in Docker is a special kind of pain though, been there.

What's the worst developer tooling pain you've just... accepted? For me it was Puppeteer for PDF generation. 800ms per document. Memory leaks. Chrome in Docker. I accepted it for years before finally building something better. What's yours? #buildinpublic

@JorgeMenaDev docker + puppeteer is a whole different level of pain. the memory just keeps climbing until everything crashes

@imrandev i had to deal with docker memory leaks too

My portfolio had a game slot that said "coming soon." For two years. Finally built it. Tetris in Rust + Bevy, compiled to WebAssembly, running inside my React portfolio. Two years of "I'll do it next weekend." Shipped it today. imrandev.com #buildinpublic

@SeaCatWiz Too accurate. I'd add: 5% time writing the feature 15% time making it work 80% time figuring out why it broke in a way you didn't think was possible

Pareto's law in action for developers: 20% time, you create very complex, back-end logic 80% time, you fix bugs that prevent it from being shown 🙄 #buildinpublic

@guilatrova Racing to $10k MRR in public takes guts. Rooting for you! I'm doing something similar - building a document generation engine in Rust and sharing the whole journey. The transparency keeps you accountable. What's been your biggest growth channel so far, YouTube or Twitter?

Officially rebooting as an AI Indie Maker 👨‍💻🚀 Already at $1k/mo from YouTube growth Launching & scaling Gemlet (Gemini for Mac) Racing to $10k MRR – transparent updates weekly If you're into AI tools, SaaS & build in public, follow along! #indiehacker #buildinpublic

@mark_is_here Love this. Simple problem, clean solution. The drag-and-drop UX looks smooth. I'm building something similar in spirit - a tool for document generation because existing solutions felt overcomplicated. Sometimes the best products come from personal frustration.

Always struggled to resize images, so I built a tool to turn any image into the perfect size for any platform. Upload --> Pick Platform --> Download Free to try → easyresize.io Made it playful, colorful, and fun ✨🫶🍌 #BuildInPublic

@saimacreates That makes sense.

@imrandev As a video editor laptop isn’t a viable option for me.

Introvert dev confession: I've been a desktop guy my whole life. Powerful setup, zero complaints. Then recently I hit a blocker - iOS development. Can't build or test without Apple hardware. I don't buy out of FOMO. I wait until it's actually required. So I got a MacBook Air M2. Desktop or laptop for coding? #buildinpublic

@giladvdn I mostly get messages from elonmusk 😇

Being a bit more on twitter in the past couple of day, is this normal for a chat requests screen?

@giladvdn Fair point, laptop portability is huge. But desktops still give you way more power per dollar. Portability wasn't a factor for me until iOS development forced the switch. Now I get both worlds.

@imrandev Using a laptop for years and years now. I find desktops big, ugly, inelegant and dusty. That's just me though.

Valid point - browsers solved a lot of hard problems. But for API-based PDF generation at scale, spinning up headless Chrome per request isn't ideal. Memory, cold starts, container limits. Different tool for a different job. Not trying to replace browsers - just avoid them where they're overkill.

@imrandev This ignores that Puppeteer's "overhead" is actually feature completeness-your Rust engine will spend the next two years reimplementing CSS edge cases and font rendering quirks that browsers already solved. You've traded known costs for unknown maintenance debt.

Hot take: Puppeteer for PDF generation is a terrible pattern. Browser overhead for every document. Memory-hungry processes. Inconsistent rendering. I built a Rust engine that's 10x faster. No browser. No headaches. Puppeteer had its time. #buildinpublic #rust

@Maulik_055 I'm using Typst as the rendering engine - handles fonts and layouts natively without CSS pain. The visual editor handles the design side, so no code needed. Give it a shot at typcraft.com if you're curious!

@imrandev curious what you're using for complex CSS layouts and web fonts tho, that's usually where the pure code solutions fall apart in my experience