Michael Ojiakor’s Post

Imagine the following situation: you created a superb app suiting your use cases perfectly, loads of unit tests, and even a pile of well-designed integration tests. Seemingly nothing to worry about. And then the database gets involved. Gert Driljeux and Alain Van Hout encountered the same issue and used Testcontainers to solve it. Read how in their blog post: Testcontainers to the rescue! https://loom.ly/CBcd0Ec #testcontainers #integrationtests

How to find Blind XSS? (it's super easy) 🔴 What Is It? ↳ XSS that's stored on the web app but reflected on another part of the application, at a different time, etc. 🟡 Where To Find? ↳ Contact/Support Forms ↳ Referrer Header ↳ User Agents 🟢 Payloads? Use these payloads: ↳ https://lnkd.in/dX-sC3BW Do you want to crush bug bounties in 2024? ↳ Follow Eman Ćatić for more tips!

Hey connections, here is a Simple "Arcade" style snake game developed by me. This project is taught by Mitch Koko on YouTube, i really enjoyed the process of making this project. Here is a web app link where you can play and score... if you are play good enough, you name might get displayed on the screen too..... Try it... https://lnkd.in/gnTgCFwu The player scores are being stored on Firestore database. The data is being sorted wrt the scores in descending order, thus if a player scores a value greater than the current highscore, their name will be displayed first(on top) on the app. PC controls :- up arrow =>upward snake movement down arrow =>downward snake movement left arrow =>left snake movement right arrow =>right snake movement

Have you ever experienced nasty experiences online involving multiple calls to the server, thus causing you to see the progress bars / spinners all the time? 🤷♀️ These experiences can be a lot irritating to the users as  they may not be interested in your product. 🏃♂️   Well, Don't worry! ✨ There's an excellent solution to combat this problem - which is either using Debouncing / Throttling as their magical purpose is to optimize the performance of the web app. How? 🤔 By limiting the rate of function calls for eg. API calls.😍   Debouncing : It suggests only making an API / function call when the time difference b/w 2 input events is greater than a time value. 😉 Throttling: Suppose there are lots of events happening , it suggests only making a function call after a certain limit of time. 😉   So which one should you go for? 🤔 👉🏻The answer would be either, as both have different use cases & serve their purposes very well when used correctly. 👉🏻To give y'all more clarity, I've documented a blog which talks about what they're, how they can be used, in which strategies they can be utilised along with the code-snippets, so do check that out on  my hashnode link -  https://lnkd.in/gcr_yTda    Git : https://lnkd.in/g-WqNdUM

Had a productive morning working on the reseller app. The main goal was to restructure the Supabase database to allow individual items to relate to a bundle (a lot of stuff the user picks up). The second step was straightforward: create the number of items based on the quantity of items in the bundle. After that, I created another dynamic route in Next.js and pushed to that page when selecting an item. Finally, I wanted to allow the user to update fields in that item by reusing the “quick add” button. Next steps are to fix the data loading issue I’m experiencing now 😂 Check out my YouTube livestreams if you want to see the full process. https://lnkd.in/evjBTDt4

Another new Insight 😮 Caches and Queues – so you can finally figure out if your app is using caching correctly, why those cache misses are killing your latency, and see how queues are impacting your app's performance (while ensuring your background jobs aren’t being sent to /dev/null). As usual, here’s the post with everything you need to get started in the comments.

You can easily find out the bugs on your expessjs app using this code ‘’’ function bugFinderMiddleware(req, res, next) { debug(`Incoming Request - Method: ${req.method}, URL: ${req.originalUrl}`); debug('Headers:', req.headers); debug('Body:', req.body); res.on('finish', () => { debug(`Outgoing Response - Status: ${res.statusCode}`); }); next(); }

Route Handlers in Nextjs : Route Handlers allow you to create custom request handlers for a given route using the Web request and response APIs. Good to know: Route Handlers are only available inside the app directory. They are the equivalent of Api Routes inside the pages directory meaning you do not need to use API Routes and Route Handlers together. The following http methods are supported: GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS. If an unsupported method is called, Next.js will return a 405 method not allowed response.

How to find Blind XSS? (it's super easy) 🔴 What Is It? ↳ XSS that's stored on the web app but reflected on another part of the application, at a different time, etc. 🟡 Where To Find? ↳ Contact/Support Forms ↳ Referrer Header ↳ User Agents 🟢 Payloads? Use these payloads: ↳ https://lnkd.in/dX-sC3BW Do you want to crush bug bounties in 2024? ↳ https://patreon.com/omnibb

Polaris is the game-changer in web app reliability! 🌟 Say goodbye to complex and costly observability tools. With Polaris, you won't need to install any agents on your servers! 🌐 We put the user first and measure your web app's reliability from their perspective, providing real-time incident detection. 📊 But that's not all – we're rewriting the observability equation. 🎯 Sign up for our free tier and receive 100k measurements per month at no cost. Ready to experience the future of web app reliability? Sign up for a demo now! 👉 https://ow.ly/Xxi450Q5AcE #Polaris #WebAppReliability #Observability #ai #SRE