full image - Repost: 27M Stuck in my own little bubble, Join me? (
from Reddit.com, 27M Stuck in my own little bubble, Join me?)
Hey, I’m Jonathan. My Husky said you should send me a chat!I’ve realized life’s gotten quiet, going through the same routines, Feeling a bit stuck in my own little bubble, join me? I’d really like to change that by meeting some new people. Whether it turns into a long-term friendship or just good conversations here and there.What are you up to tonight? I’m just trying to relax a bit, Looking for something to watch but absolutely no idea what to put on, any suggestions? What’s your favorite movie or show?A bit about me:I’ve got a seven-year-old Siberian Husky named Zeus, so if we talk long enough, you’ll probably get dog pictures.• Male, 27 years old• 6’1, curly brown hair, brown eyes, glasses, dimples• Mullet• From Northern Minnesota• Full-time student majoring in Computer Information Technology with a minor in CybersecurityI enjoy problem solving whether that’s in school, working on boats and outboard motors, or just figuring things out in everyday life. I plan to keep working with motors on the side because it’s something I genuinely enjoy although I want to go into Computer Networking.I’m big on the outdoors, fishing, boating, hunting. Being out on the water or in the woods clears my head. At the same time, I’m also a homebody and perfectly happy staying in with movies, TV shows, gaming, or watching sports.If you’ve made it this far, Tell me what color eyes you have, they’re my favorite feature!
full image - Repost: Did something change in the plat-diamond ranking? (
from Reddit.com, Did something change in the plat-diamond ranking?)
https://ift.tt/lT3oOeN
full image - Repost: Your app works, but your code is messy. Now what? My Kiro checklist before scaling (
from Reddit.com, Your app works, but your code is messy. Now what? My Kiro checklist before scaling)
As a senior software engineer, I've audited 120+ vibe coded projects so far.One thing that kept coming up in those conversations was founders saying "I think my app is ready to scale, but I honestly don't know what's broken under the hood."So I figured I'd share the actual checklist I run when I first look at a Kiro app (as an example) that has users or is about to start spending on growth. This isn't about rewriting your app. It's about finding the 5 or 6 things that are most likely to hurt you and fixing them before they become expensive problems.The health check1. Is your app talking to the database efficiently?This is the number one performance killer I see in AI-generated code. The AI tends to make separate database calls inside loops instead of batching them. Your app might feel fast with 10 users. At 100 users it slows down. At 500 it starts timing out.What to look for: if your app loads a page and you can see it making dozens of small database requests instead of a few larger ones, that's the problem. This is sometimes called the "N+1 query problem" if you want to Google it.The fix is usually straightforward. Batch your queries. Load related data together instead of one at a time. This alone can make your app 5 to 10 times faster without changing anything else.2. Are your API keys and secrets actually secure?I still see apps where API keys are hardcoded directly in the frontend code. That means anyone who opens their browser's developer tools can see your Stripe key, your OpenAI key, whatever you've got in there. That's not a minor issue. Someone could run up thousands of dollars on your OpenAI account or worse.What to check: open your app in a browser, right-click, hit "View Page Source" or check the Network tab. If you can see any API keys in there, they need to move to your backend immediately. Your frontend should never talk directly to third-party APIs. It should go through your own backend which keeps the keys hidden.If you're on Kiro, use .env file for your environment variables. If you've migrated to Railway or another host, use their environment variable settings. Never commit keys to your code.3. What happens when something fails?Try this: turn off your Wifi and use your app. Or open it in an incognito window and try to access a page that requires login. What happens?In most AI-generated apps, the answer is nothing good. You get a blank screen, a cryptic error, or the app just hangs. Your users are seeing this too. They just aren't telling you about it. They're leaving.Good error handling means: if a payment fails, the user sees a clear message and can retry. If the server is slow, there's a loading state instead of a frozen screen. If someone's session expires, they get redirected to login instead of seeing broken data.This doesn't need to be perfect. But the critical flows, signup, login, payment, and whatever your core feature is, should fail gracefully.4. Do you have any test coverage on your payment flow?If your app charges money, this is non-negotiable. I've worked with founders who didn't realize their Stripe integration was silently failing for days. Revenue was leaking and they had no idea.At minimum you want: a test that confirms a user can complete a purchase end to end, a test that confirms failed payments are handled properly, and a test that confirms webhooks from Stripe are being received and processed.If you're not sure how to write these, even a manual checklist that you run through before every deployment helps. Go to your staging environment (you have one, right?), make a test purchase with Stripe's test card, and confirm everything works. Every single time before you push to production.5. Is there any separation between your staging and production environments?If you're pushing code changes directly to the app your customers are using, you're one bad commit away from breaking everything. It's worth repeating because it's still the most common gap I see.Staging doesn't need to be complicated. It's just a second copy of your app that runs your new code before real users see it. Railway makes this easy. Vercel makes this easy. Even a second Kiro deployment can work in a pinch.The point is: never let your customers be the first people to test your changes.6. Can your app handle 10x your current users?You don't need to over-engineer for millions of users. But you should know what breaks first when traffic increases. Usually it's the database queries (see point 1), large file uploads with no size limits, or API rate limits you haven't accounted for.A simple way to think about it: if your app has 50 users right now and someone shares it on Twitter tomorrow and 500 people sign up, what breaks? If you don't know the answer, that's the problem.What I'd actually prioritizeIf you're looking at this list and feeling overwhelmed, don't try to fix everything at once. Here's the order I'd tackle it in:First, secure your API keys. This is a safety issue, not a performance issue. Do it today.Second, set up staging if you don't have one. This protects you from yourself going forward.Third, add error handling to your payment flow and test it manually before every deploy.Fourth, fix your database queries if your app is starting to feel slow.Fifth and sixth can wait until you're actively scaling.Most of these fixes only take a few hours each, not weeks. And they're the difference between an app that can grow and an app that falls apart the moment it starts getting attention. If you don't have any CS background, you can hire someone on Vibe Coach to do it for you. They provide all sorts of services about vibe coded projects. First Technical Consultation session is free.No matter your app is on Kiro or other IDEs, most of this still applies. The principles are the same.Let me know if you need any help. If you've already gone through some of this, I'd genuinely be curious to hear what you found in your own codebase.
full image - Repost: 🚨🇮🇱 ISRAELI REPORTER 'FLIPS OUT' ON LIVE TV: AIR DEFENCE SYSTEM COLLAPSED IN THE FACE OF IRANIAN MISSILES! (
from Reddit.com, 🚨🇮🇱 ISRAELI REPORTER 'FLIPS OUT' ON LIVE TV: AIR DEFENCE SYSTEM COLLAPSED IN THE FACE OF IRANIAN MISSILES!)
https://ift.tt/OGZrVq5
full image - Repost: RL agents go from face-planting to parkour when researchers keep adding network layers (
from Reddit.com, RL agents go from face-planting to parkour when researchers keep adding network layers)
Tired of clunky AI? PROBLEM: Current AI struggles with real-world agility. PROMISE: New research shows adding network layers makes AI agents WAY more adaptable, like going from face-planting to parkour! PROOF: Continuously increasing layers dramatically improves performance. PROPOSITION: Unlock AI's full potential with layered networks. PRODUCT: Smarter, more responsive AI. What do you think? #AI #LLM #ArtificialIntelligenceRead more here : https://ift.tt/f2BxLzd
full image - Repost: Cant connect online to FC26 (
from Reddit.com, Cant connect online to FC26)
I keep getting The “in order to access the online feature for this title. You must be signed into PlayStation network and you must be signed into the EA servers. “ ERRORi am signed in on everything and I did restart my router
full image - Repost: struggling to even get interviews anywhere (
from Reddit.com, struggling to even get interviews anywhere)
everyone keeps preaching about how big 4 experience opens doors and accelerates your career trajectory but man i'm starting to wonder if i'm missing something major hereapplied to probably 15+ positions across all the major firms and haven't landed a single interview yet. my undergrad gpa was 3.8 and just finished my masters with a 3.95. already cpa eligible too so it's not like i'm lacking the credentials on paperstarting to think there's some secret handshake or networking component i'm completely oblivious to. anyone else struggle this hard just to get your foot in the door? feeling pretty defeated since even the smaller regional firms aren't biting eitherupdate: yeah it's not just big 4, applied broadly and crickets everywhere
Social Media Icons