Urgent.News

What's breaking now, across thousands of outlets.

Tech

Tell us your story, and we might read it on the CodeNewbie Podcast ๐ŸŽ™๏ธ

Hi! Iโ€™m Lauren ๐Ÿ‘ฉ๐Ÿผ๐Ÿ’ป, the new host of the CodeNewbie Podcast , and Iโ€™d love to hear your story. This season, Iโ€™m asking for your help. I want to read your stories on the show and talk through them with our expert guests. Weโ€™ll dig into what happened, what was going on under the hood, and what theyโ€™d do next in your shoes. Your story becomes the starting point for the whole conversation, soโ€ฆ

Hi there! Welcome to the CodeNewbie Podcast, where we love hearing your unique coding stories. My name is Lauren, and I'm thrilled to announce that I'll be hosting this season of the show. I'm eager to read and discuss your tales of triumphs, challenges, and lessons learned while building with technology.

Your story becomes the foundation for our conversation, offering valuable insights and advice to our listeners facing similar situations. So, grab a cup of coffee and get ready to share your experience with us. We're all ears!

To share your story, leave a concise version of it in the comments below or submit it as a post by tagging it #codenewbiestory. If you'd prefer to remain anonymous, feel free to email your story to lauren@codenewbie.org, and let us know if you'd like us to modify any names, companies, or details.

Please note that by sharing your story, you grant us permission to read and discuss it on the CodeNewbie Podcast. We're especially interested in hearing about your encounters with AI, both the successes and the unexpected challenges. Some of the topics we'd love to explore include:

- AI agents deleting your data or causing deploy issues

- Unexpected bills or double charges from your app

- Accidentally publishing API keys or secrets to public GitHub repositories

- Discovering security vulnerabilities in your own app

- Launching an app with no takers despite your hard work

- Navigating job hunting or landing your first developer role with AI in the mix

No matter the subject, the more detail you provide, the better. Start from the beginning and walk us through what you were building, your expectations, the moment you realized something was wrong, every attempt you made (successful or not), the people you reached out to for help, and the current state of affairs. Don't worry if your story doesn't have a happy ending yet; we're all about real-life experiences and learning from them.

Please avoid including any sensitive information like passwords or API keys to protect privacy. Focus on crafting a narrative you'd comfortably share over coffee with a friend. Just keep your story to at least 500 words, but feel free to expand it as much as you'd like.

Thank you for entrusting us with your story. We truly appreciate your willingness to share and help others learn from your journey. We can't wait to read your account and discuss it on the podcast!

Written by urgent.news from Dev.to's reporting โ€” not their text. Machine-written โ€” may contain errors; check the original before relying on it.

Read the original at dev.to โ†’

More in Tech

SCIM Provisioning & Deprovisioning That Actually Removes Access

Here is a scenario I now test on every enterprise SSO integration. An employee leaves a customer company. Their IT team disables the account in the identity provider.

  • IdP sends deprovisioning request with user's unique identifier
  • Application blocks login, revokes live sessions, disables tokens
  • Transaction-safe step ensures single-step deprovisioning

Untangling Dependency Cycles in a Modular Laravel Monolith

Once the strangler fig from Part 1 is working, the new Laravel app grows fast. Each migrated route brings a feature with it: dealers, orders, invoices, stock.

  • Laravel modular app grows rapidly with new features in separate modules
  • Dependency cycles emerge as modules import functions from each other
  • deptrac tool identifies dependency violations in codebase

More from Friday 20 November โ†’