---
title: "Arun Tyagi (@aruntyagi) | Hashnode"
description: "Freelance Laravel & SaaS developer, Noida. Building products for startups in India and the UAE. Read the latest articles by Arun Tyagi on Hashnode."
url: "https://hashnode.com/@aruntyagi"
---

@aruntyagi

# Arun Tyagi

@aruntyagi · Noida, India · Joined November 2026

Freelance Laravel & SaaS developer, Noida. Building products for startups in India and the UAE.

### [Securing a Laravel API before launch: a 10-point checklist](https://aruntyagi-laravel.hashnode.dev/securing-a-laravel-api-before-launch-a-10-point-checklist?utm_source=hashnode&utm_medium=feed)

Most Laravel APIs I review aren't hacked through anything clever. They leak because of defaults nobody changed. Here's the checklist I run before an API goes live for a client's mobile app or SPA. 1.

2 min read · [aruntyagi-laravel.hashnode.dev](https://aruntyagi-laravel.hashnode.dev/securing-a-laravel-api-before-launch-a-10-point-checklist?utm_source=hashnode&utm_medium=feed)

[5h ago](https://hashnode.com/posts/securing-a-laravel-api-before-launch-a-10-point-checklist/6b00735e3fd093e16c3774b4)

### [Your developer disappeared? A checklist for taking over an existing Laravel project](https://aruntyagi-laravel.hashnode.dev/your-developer-disappeared-a-checklist-for-taking-over-an-existing-laravel-project?utm_source=hashnode&utm_medium=feed)

A surprising number of my projects start with: "Our previous developer stopped replying, and the app is live." Taking over someone else's Laravel codebase is very doable, but only if you do it in the

2 min read · [aruntyagi-laravel.hashnode.dev](https://aruntyagi-laravel.hashnode.dev/your-developer-disappeared-a-checklist-for-taking-over-an-existing-laravel-project?utm_source=hashnode&utm_medium=feed)

[3d ago](https://hashnode.com/posts/your-developer-disappeared-a-checklist-for-taking-over-an-existing-laravel-project/6afc8a28a5aba7ea87892084)

### [The N+1 query problem in Laravel: how to spot it in 5 minutes on a client app](https://aruntyagi-laravel.hashnode.dev/the-n-1-query-problem-in-laravel-how-to-spot-it-in-5-minutes-on-a-client-app?utm_source=hashnode&utm_medium=feed)

When a client says "the dashboard got slow after we added more customers", the cause is usually not the server. Nine times out of ten it's an N+1 query hiding in a Blade loop. Here's the quick routine

2 min read · [aruntyagi-laravel.hashnode.dev](https://aruntyagi-laravel.hashnode.dev/the-n-1-query-problem-in-laravel-how-to-spot-it-in-5-minutes-on-a-client-app?utm_source=hashnode&utm_medium=feed)

[Nov 13](https://hashnode.com/posts/the-n-1-query-problem-in-laravel-how-to-spot-it-in-5-minutes-on-a-client-app/6af683c91e6a5a078610b9d7)
