Sprint planning as a new grad is a foreign language. Is it normal to feel so confused? Every time we do sprint planning, I feel completely out of the loop. The senior devs speak entirely in acronyms and base their estimates on decisions made years ago. As a junior, I have zero context and feel like I'm falling behind. Is this standard new-hire confusion, or should I be worried?

My current full-time job is a total dead end and I'm miserable, but it's stable. A recruiter reached out about a contract-to-hire position that's exactly what I want to be doing, but I'm wondering if it's just going to be a glorified temp job. Would it be crazy to leave a permanent position for this?

What’s your take on oversized Pull Requests? Knowing that it’s the norm of AI assisted development, automation hasn’t still caught up with humans reviewing the changes.. I would and still reject overly large PRs for reasons outside of testing and fixtures.

Final-year Software Engineering student based in Perth, WA, actively applying for internships. Would love any advice from engineers on what companies look for in junior/intern candidates — especially for AI or software dev roles. Also curious what the Perth tech scene is like for new grads!

Ageism sucks. And I see older folks constantly subjected to it. But let's be clear, ageism isn't *just* towards older people. A common occurance is older people trying to pull rank on younger developers, even when the younger devs are clearly more qualified. It seems the more meaningful distinction is not age or years of experience - but whether or not you care about your work, and have continued to refine your taste and explore new ideas. Maybe we need a new metric: "Years of new experience".