Hi guys I have created a hero section for my personal portfolio (still under development) Is it good or I need to improove it more any suggestions, thoughts are most welcome

Hey Papafam Community, If you're looking to take your productivity and skill mastery to the next level, I’ve got two must-reads for you. These books have profoundly shaped the way I approach work and learning, and I believe they’ll do the same for you: 1. So Good They Can't Ignore You by Cal Newport In this game-changing book, Cal Newport debunks the “follow your passion” myth and instead advocates for the power of developing rare and valuable skills. Newport’s insights will help you understand why becoming exceptional in your craft can lead to greater job satisfaction and success. 2. The Programmer’s Brain by Felienne Hermans This book is a treasure for developers at any level. Felienne Hermans delves deep into how our brains process and understand code, offering practical techniques to improve learning and problem-solving. It’s an essential read for anyone who wants to code more effectively and gain a deeper understanding of programming concepts. Both books provide actionable takeaways that will transform the way you develop your skills and approach your projects. Trust me, these reads are worth every minute! Happy reading and keep pushing boundaries! Remember Learn - Do - Teach Is one of the best approach to keep you coding skill leveling up and their is lot of science backing it up. Keep doing you Peace 👊

Why Showing Your Work Matters in Programming As developers, we often focus on perfecting our code in isolation, waiting for the day it’s “good enough” to share. But in today’s collaborative world, your growth, opportunities, and reputation can flourish when you let others in on your journey. Show Your Work! by Austin Kleon offers powerful insights that resonate deeply with programmers: sharing your process, challenges, and successes can not only improve your skills but also build a supportive network within the dev community. Here’s how you can tailor the book’s lessons to amplify your impact as a programmer. The 10 Rules for Programmers to Show Their Work 1. You Don’t Have to Be a Genius – Just Be a Contributor Forget trying to be the smartest person in the room. Instead, share what you’re learning as you go. Whether it’s a bug fix, a small script, or a feature update, your contributions matter to someone out there. 2. Think Process, Not Product Codebases evolve, and so should your sharing. Don’t wait until you’ve completed the “perfect” app or tool. Instead, show how you’re iterating and the thought process behind your decisions. > Example: Share your GitHub repository early, document your progress, and explain your challenges in the README. 3. Ship Small Wins Every Day Consistency beats perfection. Push daily commits, tweet about an interesting code snippet, or write LinkedIn posts about lessons learned. 4. Share Your Tools and Inspirations Openly share the libraries, frameworks, and resources that inspire your work. Other developers will appreciate your transparency. 5. Tell the Story Behind Your Code Every app, feature, or line of code has a story. Share why you built it, the problem it solves, and how you approached it. 6. Teach What You Learn Teaching is one of the best ways to solidify your knowledge and connect with others. Share tutorials, snippets, or explainers. > Example: Write a Medium post or do a video explaining the difference between server-side rendering (SSR) and static site generation (SSG) in Next.js.

Hey Papafam! 🚀 Let’s talk about a game-changing mindset shift: transitioning from being just a consumer to becoming a producer in the world of software development. Most of us start our journey consuming tons of tutorials, articles, and courses. That’s normal—it’s how we build a foundation. But here’s the truth: real growth happens when you start producing. Here’s why you should make the leap: 1. Producing Solidifies Your Knowledge You think you understand something until you try to teach it, build it, or explain it. By creating projects, writing articles, or sharing your learnings, you deepen your understanding and retain knowledge longer. 2. Producers Build Portfolios, Consumers Don’t Employers and clients don’t care how many tutorials you’ve watched—they care about what you’ve built. As a producer, every project, blog post, or GitHub repo becomes part of your personal brand and proof of your skills. 3. Producers Create Value Consumers take value, but producers give it back. Whether it’s an open-source contribution, a tutorial you publish, or a product you ship, you’re leaving a mark and helping others grow while growing yourself. 4. Producers Get Paid Let’s be honest—consuming content doesn’t pay the bills. Producing code, selling digital products, or sharing your expertise can. The more you create, the more opportunities you unlock for income and career growth. 5. It’s About Confidence, Not Perfection You might think, “I’m not good enough to produce.” That’s a myth. No one’s perfect, and sharing your journey—even the messy parts—makes you relatable and valuable. Start small, and grow from there. How to Start Producing Today: 1) Build: Take on side projects, join open-source, or freelance. 2). Teach: Write blog posts, record tutorials, or mentor someone. >Just like how @Digitl-Alchemyst Steven-Watkins create time despite his tight schedule to mentor his brother 3) Share: Post your journey on LinkedIn, GitHub, or in communities like Papafam!

Hi Papafam how are things going on for you everyone? Well, I've followed Sonny's latest tutorial for a personal project which shares a few of the functionalities Sonny showed us with a few add-on features. Well, I'm having an issue though and I need your help. Even though I've managed to create records in Sanity for my different schemas, I'm having issues when I'm trying to upload an image from the frontend. I'm seeing error related to permissions and the create. Anyone faced and/or solved it somehow? I know that I should upload an image as a server action since the token isn't exposed to the client but once again I can't do it.