DONT LAUNCH YET!!!

@jordankodes

7.1K followers · usually 11.6K views a post

Views

34.8K

Likes

2.4K

Comments

17

Shares

254

Selling · SaaS › Developer Tool

—

Why it worked

The video provides actionable security advice for developers, presented in a concise and easily digestible format. The use of on-screen text and clear explanations makes complex topics accessible, while the call to action encourages further engagement.

Summary

A software engineer advises against launching an app without addressing three critical security vulnerabilities: unauthenticated endpoints, lack of data pagination, and overly verbose error messages. He suggests these issues can expose sensitive data and provide attackers with valuable system information.

Structure

1Don't launch your app yet
2Three backend security mistakes
3Open endpoints are dangerous
4Pagination is crucial
5Avoid excessive error messages
6Check the bio link for more

Call to action

click the link in my bio

On-screen text

DONT LAUNCH YET!!! LAUNCH FROM ENGINEER, THINGS NEVER ONE ENDPOINTS. REQUESTS, CAN REQUEST HAVING YOU'RE ONCE, SINGLE PAGINATE OVER NO. ERROR APP ERRORS, TELLING SYSTEM GO TOGETHER, BIO.

Original caption

api security, backend security checklist, secure your api, web app security tips, software engineering best practices, api endpoint security, pagination api, prevent data leaks, backend development tips, protect your database, secure api routes, web development security, coding best practices, full stack security, developer tips backend

More from @jordankodes

Their other posts in the index, biggest breakout first.

Transcript

Don't launch your app if I. From an engineer, these are the three things your backend should never expose. One, open endpoints. If your code doesn't check who is making the requests, anyone can hit your data and request it. Two, not having pagination. If you're returning everything at once, someone can dump your entire database in a single request. You should paginate over the data over multiple pages. No. Three, excessive error messages. If your app is returning raw errors, you're literally telling the attacker how your system works. If you want to go over your app together, click the link in my bio.