Abishek
1.1K posts

Abishek
@glaucusec
Software Dev trying to keep up with current tech. Building https://t.co/K21E80dB9e
Lost In Space Katılım Nisan 2018
1.5K Takip Edilen145 Takipçiler

my second customer almost asked for a refund within hours, here's how i saved it in 30 minutes:
he subscribed, tried using the app, every single action failed. mailed me saying refund me or i'm charging back.
i panicked. first instinct was to just refund him.
instead i checked my vercel logs, found the real issue phones shoot 15-20MB photos now, my serverless function limit was 4.5MB.
every upload was dying before my code even ran, this was silently broken for every mobile user since launch.
fixed it in 30 minutes, added client-side image compression before upload, resized everything, converted to JPEG, went from 20MB to 500KB.
pushed the fix, told him to try again, worked perfectly.
the scary part? he was the first person angry enough to email me. everyone else just left forever.
your angriest customer is your best QA tester.
Prasenjit@Star_Knight12
just woke up to this, second sale on my SaaS
English


@mansistwt Yes. @hoppscotch_io is the one you are looking for. If i remember correctly, they first named this product postwomen and changed it later.
English

#KiteReader Updates
✅ Completed RSS Parser Package.
✅ Fetcher Worker Completed.
✅ Dispatcher Worker Completed.

English
Abishek retweetledi

Vibe Coding lessons I learnt the HARD WAY ( Extended Edition )
Bookmark this to 10X your workflow
DO's (What Actually Saves You Time)
> Use ready-made auth (Clerk / Supabase Auth)
> Use Tailwind + shadcn/ui for UI
> Use Zustand / Server Components for state
> Use tRPC / Server Actions for APIs
> Deploy with Vercel one-click
> Use Prisma + managed Postgres
> Validate with Zod + React Hook Form
> Use Stripe for payments
> Add Sentry / error tracking early
> Set up analytics (PostHog / Plausible)
> Store secrets in env files
> Use UploadThing / Cloudinary for files
> Set up preview deployments
> Use component libraries (Radix / shadcn)
> Write a README from Day 1
> Keep folders clean and modular
> Add onboarding + empty states
> Use Lighthouse / performance tools
> Use a monorepo or clear app structure from the start
> Document your env vars in .env.example
DON'Ts (What Burns Your Time & Energy)
> Don't build auth from scratch
> Don't write raw CSS for everything
> Don't over-engineer state management
> Don't build custom APIs too early
> Don't deploy manually
> Don't write raw SQL everywhere
> Don't build your own payment system
> Don't roll your own search engine
> Don't skip logging & monitoring
> Don't hardcode API keys
> Don't DIY file uploads
> Don't push straight to main
> Don't build realtime systems alone
> Don't ignore performance
> Don't assume users "will figure it out"
> Don't postpone refactoring forever
> Don't rely on memory for decisions
> Don't chase "perfect" before shipping
> Don't skip error boundaries and fallbacks
> Don't forget a health check endpoint

English

#KiteReader Updates
✅Configured better auth with backend
✅Created Auth Pages for login and signup.
✅Shadcn for components.
Base is now ready. will start working on the The Engine from tomorrow.

English

#KiteReader Updates
✅Setup Drizzle ORM and
✅Basics of cloudflare workers and using wrangler.
With that we completed Setup and Database Checklists.

English

Locking in for 2 hours.
Plan
1. Create a detailed plan for kitereader.com.
2. Understand cloudflare workers, queue, D1.
3. Get started with the project.
English

Alright !
Let's break the ice. Its a rss reader that i am planning to build in a serverless platform .
It's my first time building a complete end to end saas application.
The product is named as KiteReader.
Abishek@glaucusec
Just purchased a domain for building my app 🥳. Its time i build something that is mine. Its a simple app idea (which is absolutely not fresh). Goal is to prove myself that i can build something that I care about. Will share my journey here with you folks. Genuinely excited...
English

@HxrshitYadav Thanks for reminding me of this.
Will use a structured sheet to plan practicing DSA
English

Here's something nobody told me about learning DSA that would have saved me months.
> You don't need to solve 500 problems.
> You need to recognize 15 to 20 patterns.
Two pointers, Sliding window, Binary search, BFS/DFS, backtracking, merge intervals, fast and slow pointer, monotonic stack, top K with heap, prefix sum.
That's it.
That's most of it.
Every NEW problem is just one of these patterns wearing a different costume.
Once you see that it stops feeling like you're starting from zero every single time.
I spent months solving random problems jumping from arrays to trees to graphs to dynamic programming with no structure. Felt like I was getting nowhere because I literally was getting nowhere.
> The moment I stopped solving randomly and started grouping problems by pattern everything clicked.
> Not instantly, but it started making sense for the first time.
You don't need to grind harder. you need to grind smarter. Solve 5 problems of one pattern back to back instead of 5 random problems from 5 different topics.
What pattern finally made DSA click for you?
For me it was sliding window. the first time I recognized it in a problem without being told felt like a cheat code.

English

Meet BugSkills.
I built a tool to convert the knowledge and methodology used in your HackerOne reports into AI skills you can use to automate vulnerability discovery.
Thank you @rez0__ for the idea.
github.com/BehiSecc/bugSk…
English

Stop Google from limiting APK file usage - Sign the Petition! c.org/tK9vFqBqPW via @ChangeOrg_India
English

Google is set to restrict sideloading unverified apps on certified Android devices starting in September 2026 in select countries, with global expansion to follow.
Unverified apps can still be installed normally for now.
Following backlash over limiting Android's openness, Google added an "advanced flow" for experienced users to bypass the restrictions, with additional warnings and steps.


English


