Amani Kanu

Day 1 - Memo, roadmap R19, RSC in Expo Router etc https://lnkd.in/d9gxYsD2 Day 2 - React server components, accessibility, pigment css, forms, errors etc https://lnkd.in/dPnK8bU5 #react #reactconf #meta #frontend

12

1 Comment

When I began learning frontend development, I started with HTML5, CSS, and JavaScript. I then progressed to learning the CSS framework Bootstrap and the JavaScript framework React.js. I built several projects and then started looking for a job. After a few months, I landed a role, but the company used Material UI as the design framework. I turned to YouTube to learn about it. In my next role, the company used Next.js, which was new to me, so I used online resources to learn it. Then another role introduced me to Nuxt.js. The point I'm trying to make is that being a frontend developer requires continuous learning. The knowledge you gain from a six-month bootcamp won't be enough in the long run.

6

I just completed a web development project using React.js and Three.js and Emailjs, creating an interactive and dynamic portfolio that showcases my skills. 🌐✨ A huge shoutout to JavaScript Mastery for their incredible YouTube content that guided me throughout the process. Your tutorials made the journey so much smoother! 🙌 This is just the beginning, and I can’t wait to explore even more with these powerful tools. 🔥 #webdevelopment #reactjs #threejs #javascript #learningjourney #portfolio #javascriptmastery #Projects #LearningEnthusiast JavaScript Mastery

89

28 Comments

New book recomendation, great one for anyone looking to learn React and React Native! It covers the foundation of React and JavaScript and then it moves to TypeScript. Once you become confident with React in section two it starts with React Native which goes hand in hand with React. Great book for beginners to start building their first applications with the React ecosystem. Link here: https://lnkd.in/dGXsMgWn #react #reactnative #reactdeveloper

267

16 Comments

Learning something new can be quite demanding - I am teaching some student Flutter but they had this JavaScript mindset or I should say they were all coming from Web development so it was quite confusing. I, like my nickname, Hephzisoft, I told them to go and master functions and constructors, so that it can be SOFT to some extent because that is what I did which worked for me. I always tell my students that Rome was not built in a day, but most of them were not born then 🤣🤣🤣 Share any of your experience while learning something new. #development #flutter

1

Dear Backend Developers, As a frontend engineer, I have nothing but respect for the work you do. But let's be honest, there are a few things that have been driving us on the frontend side crazy. And it's about time we had an open conversation about it. First of all, we get that data structures, databases, and servers are your playground. But when it comes to APIs, can we please prioritize usability and efficiency? If I have to pass through another inconsistent, under-documented, or overly nested JSON response, I might lose it. Let not even forget the fact that the UI flow we work on sometimes doesn’t correspond with your backend logic, I mean it won’t kill for you guys to check the UI flow before writing any logic right? And nothing is more frustrating than a 500 error with zero clues about what went wrong. A little transparency goes a long way, I mean a detailed error messages and meaningful status codes aren't just "nice to haves", they're essential. We all know that speed matters. But when it comes to user experience, latency can kill. Frontend developers often get blamed for slow load times, but sometimes the culprit is an unoptimized backend. The silos between frontend and backend teams need to come down. Regular sync-ups, better documentation, and mutual understanding of each other's challenges can only lead to us building a better product and let's make communication the norm. Looking forward to some spirited discussions and, most importantly, meaningful improvements. Best, A “Frustrated” Frontend Engineer #webdevelopment #frontend #backend #techcollaboration #softwareengineering #developercommunity #techtalk #productivityboost #devlife

1,057

156 Comments

Update on my backend journey Recently I learnt how to restrict a user to a particular route based on their role. I created a function called `restrictTo` in `authController`, which is exported to the `userRoute`. The function is used before calling the function for the route that you want to restrict users to. The `restrictTo` function takes an array of parameters containing roles that any user must have to access that particular route. Let's say, for instance, you want to restrict ordinary users from deleting a user route, then you use: router.delete("/users/:id", restrictTo("Admin", "Moderator"), deleteAUser); In this case, only users with the role of Admin or Moderator can access that route. Inside the `restrictTo` function in the `authController`, the roles parameter was destructured since it's an array. Then, I wrote a conditional statement that checks if the logged-in user's role is included in the destructured roles parameter using req.user.role. If not, it returns an error message telling the user that he/she is restricted from accessing that route. That's all for today. Thank you all for the feedback and support—it's helping me improve every day. I’ll keep sharing updates as I continue my journey. Thank you for your support! #Nodejs #Expressjs #JavaScript #BackendDevelopment #programming #LearningJourney #coding #tech

63

13 Comments

The Work of Fullstack Developers: Bridging the Gap Between Frontend and Backend Introduction In the dynamic world of software development, the role of a fullstack developer has become increasingly vital. These versatile professionals possess a deep understanding of both frontend and backend technologies, enabling them to build complete, end-to-end solutions. As businesses continue to demand more seamless, responsive, and scalable applications, fullstack developers are at the forefront, turning ideas into functional, user-friendly products. The Role of a Fullstack Developer A fullstack developer is a software engineer who is proficient in both frontend and backend development. This dual capability allows them to handle every aspect of web and mobile application development, from designing the user interface (UI) to managing databases and servers. Their work is crucial in ensuring that the various components of an application function together smoothly. Frontend Development Frontend development focuses on the user experience and interface of an application. This involves creating the layout, design, and interactivity that users interact with directly. Fullstack developers use a variety of technologies to achieve this, including: HTML/CSS, JavaScript, React etc. Backend Development While the frontend is what users see, the backend is where the application’s logic and database interactions occur. Backend development involves creating and maintaining the server, database, and application logic that powers the frontend. Key technologies and concepts include: Server-Side Languages: Fullstack developers often work with languages like Node.js, Python, Ruby, PHP, and Java to build the server-side logic, Databases like MySQL, PostgreSQL, MongoDB, etc The Fullstack Workflow A typical fullstack development workflow involves several stages, each requiring different skill sets and tools. Requirement Gathering and Planning Designing the Architecture Development Testing and Debugging Deployment Maintenance and Scaling The role of a fullstack developer is one of the most dynamic and rewarding in the tech industry. By bridging the gap between frontend and backend development, these professionals are able to build comprehensive solutions that meet the needs of users and businesses alike. For those motivated by curiosity, creativity, and the desire to build, a career as a fullstack developer offers endless opportunities for growth and achievement. My name is Ahiakwo John also known as King johney in the social media space and I'm a fullstack developer with a lot of experience with working on different projects, products and teams. Do well to reach out to me if you have a project or product idea and I'm open to taking a new role in the software development space. Have a wonderful and productive week 😊. #tech #fullstackdeveloper #coding #programming #softwaredevelopment #kingjohney

126

15 Comments

How would you explain what you do to your grandma? Follow me for more related content🤗 . . . #FlutterTips #DevLife #MobileAppDev #CodeNinja #ReactNative #TechTrends #ProgrammingPro #SoftwareDev #AppDevelopment #HassanZaheer #TechInnovation #CodeMastery #DevCommunity #FlutterDev #MobileTech #SoftwareEngineering #Flutter

5

Day 9 of 100 Today, I tackled user authentication using Firebase, a crucial aspect of building a secure and personalized user experience. *Creating a bridge between authentication and Firestore* I wrote an async function, `createUserDocumentFromAuth`, to fetch user authentication data from Firebase and link it to my Firestore database. This function plays a vital role in connecting the authentication process to my application's backend. *Fetching user data with Firebase's Authentication.uid* Using the `createUserDocumentFromAuth` function, I successfully retrieved the user's unique ID (Authentication.uid) from Firebase. This ID serves as a unique identifier for each user, enabling me to create a personalized document in my Firestore database. *Utilizing the doc() method to fetch user IDs* I employed the `doc()` method to access the user ID of individuals who sign in or sign up through my application's forms. This method allows me to target specific documents in my Firestore collection, ensuring efficient data management. *Unlocking personalized experiences* By linking user authentication to my Firestore database, I can now create personalized experiences for my users. This integration enables me to store and retrieve user data seamlessly, paving the way for features like user profiles, preferences, and more. With user authentication and Firestore integration in place, I'm eager to continue building and exploring new features that will elevate application's user experience in the future. #React #CodingChallenge #100Days #LearnWithMe #CodeWithMe

1

We are cooking!!! But before we finish what’s cooking, 🧑‍🍳 💻 I want to briefly share what I learnt from a highly experienced software engineer. So we were having a random conversation after a code review session and we were both talking about YEARS OF EXPERIENCE in software engineering. He said something that struck me. “Yes, years of experience matters a lot, but this depends on the QUALITY of projects you have worked on, the number of active users on the project’s platform and how you are able to LEAD/IMPACT your team members including the junior ones.” I think I agree with this because you can’t compare someone with 3 active years of experience and has worked on complex projects, legacy codebases and a massive engineering team to another software engineer that claims to have about 6 inactive years of experience, have only built basic e-commerce projects, dashboards and does more of repetitive projects/tasks. I mean, the results are gonna speak for themselves. So this is to recruiters as well, that junior or mid-level software engineer might know a lot more than you think he or she does. Learn to give them a chance. To each and everyone of us out there, let’s keep putting in the work. Try to solve more complex problems, stay active, seek help when you hit a brick wall, read other developer’s codebase, constantly evolve and PLEASE stay grounded in one or two programming languages first before moving to another. Wow 😮 it was really a long read. Welldone! You got this far and I am sure you either found so many typos or you found this post insightful. 😀✌️

15

4 Comments

The Backend Evolution: Developer to Engineer Hey there, fellow tech enthusiasts! I posted this to share a crucial lesson I've learned in my journey as a software engineer: the difference between being a backend developer and a backend engineer. When I first started out, I was focused on writing code, testing, and debugging. I was a skilled carpenter, building a house one nail at a time. But as I grew in my career, I realized that there was more to building a scalable and efficient system than just writing code. That's when I discovered the role of a backend engineer. It was like a light bulb went off in my head! I realized that I wasn't just building a house, I was designing a skyscraper that would stand the test of time. A backend developer is focused on writing code, testing, and debugging. They're like a skilled carpenter, building a house one nail at a time. On the other hand, a backend engineer is responsible for designing, architecting, and implementing the backend infrastructure. They're like a visionary architect, designing a skyscraper that will stand the test of time. Let me illustrate the difference with real-world project scenarios. For example, when building an e-commerce website, a backend developer might focus on writing code to connect the payment gateway, while a backend engineer would design the entire e-commerce platform, architecting the backend infrastructure to handle millions of users and transactions. Similarly, when building a mobile app, a backend developer might focus on writing code to implement the login feature, while a backend engineer would design the entire mobile app architecture, ensuring scalability and security for millions of users. By developing your skills as a backend engineer, you can increase your earning potential, broaden your skill set, and have a greater impact on the overall system design and architecture. Ready to take your career to the next level? Let's connect and explore opportunities! You can contact me by sending a DM or by sending a message to [email protected] Thanks for reading, and happy coding! Till next time, cAPTain. #BackendDevelopment #BackendEngineering #SoftwareDevelopment #CareerGrowth #CareerAdvancement #TechCareers #Programming #Coding #SoftwareEngineering

6

Facebook started with this UI. You whose first 10 users not even sure to get onboarded wants a crazy design. Maybe we all need to tell ourselves that software development lifecycle revolves around expected functionality and not solely about crazy design patterns. #Softwaredevelopment #UIUX #Frontenddev #Fullstack

7

5 Comments

"🎨 Day forty-two of my 100 CSS challenge was all about bringing animations to life! 🚀 Today, I focused on creating beautiful animations using React, GSAP, and Tailwind CSS. As I began my learning journey with GSAP, I explored its powerful features to enhance my project with smooth, engaging animations. And used Tailwind CSS provided a clean and efficient way to style my components. Excited to continue mastering GSAP and incorporating stunning animations into my projects. Stay tuned for more updates! 💻✨ #100DaysOfCSS #GSAP #ReactJS #TailwindCSS #WebDevelopment #CSSAnimations"

18

🚀 My Journey into the Software Dev Space: The Real Story. Transitioning into the software space has been nothing short of daunting. The road to becoming proficient in software development is often painted as a smooth, glamorous path. But let’s be real , it’s far from that. 🔧 The Hurdles: Learning Curves: From mastering new programming languages to understanding complex algorithms, the learning never stops. Each day presents a new challenge, and sometimes, it feels like you’re running a marathon with no finish line in sight. Imposter Syndrome: There are days when you feel like you don’t belong, like you’re not good enough. The constant comparison to others can be overwhelming. Burnout: Long hours, debugging sessions that last through the night, and the pressure to keep up with rapidly evolving technologies can take a toll on your mental and physical health. 💪 The Persistence: Consistency is Key: Despite the hurdles, the one thing that keeps me going is consistency. Showing up every day, putting in the work, and pushing through the tough times is what truly matters. Support Systems: Leaning on fellow tech enthusiasts, mentors, and online communities has been invaluable. We share knowledge, provide encouragement, and celebrate each other's successes. Small Wins: Celebrating the small victories – solving a tough bug, completing a project, or even understanding a new concept – keeps the motivation alive. 🛠️ The Reality Check: We often glamorize the tech world, showcasing the perks and successes. But the truth is, behind every successful project, there are countless hours of hard work, failures, and lessons learned. It’s not an easy path, and it’s okay to feel overwhelmed. What’s important is to keep pushing forward, one step at a time. 🌟 Why I Keep Going: The passion for creating, solving problems, and the thrill of seeing my code come to life is what drives me. Knowing that each hurdle crossed brings me one step closer to my goals is what fuels my journey. To everyone out there facing similar challenges, know that you’re not alone. Keep pushing, stay consistent, and remember that every great developer has faced these struggles too. 💪👩‍💻👨‍💻

4

🚀 Exciting times for JavaScript developers! Introducing Bun—a groundbreaking all-in-one tool designed to transform the way we develop, test, run, and bundle our JavaScript and TypeScript projects. 🔍 What is Bun? Bun is not just another JavaScript runtime; it's a robust toolkit crafted for unmatched speed and efficiency. With an integrated bundler, test runner, and a Node.js-compatible package manager, Bun streamlines your development process from start to finish. 📈 Why Bun for Backend Development? Speed: Bun is built with performance at its core, offering lightning-fast execution times that can significantly reduce your project's turnaround time. Efficiency: Manage all aspects of your development cycle with one tool—no need for multiple plugins or configurations. Compatibility: Designed to be fully compatible with Node.js ecosystems, easing the transition and integration into existing projects. 🛠️ Personal Experience: I recently transitioned a mid-sized project to Bun and was impressed by the seamless integration and the time savings in both testing and deployment phases. The ability to handle everything from a single platform has not only optimized our workflow but also enhanced our team's productivity. 🤔 Thinking of giving Bun a try? Whether you're developing a small personal project or working on large-scale enterprise applications, Bun offers a comprehensive suite of tools that can cater to your needs. Explore how Bun can elevate your backend development and share your experiences with this powerful toolkit. 🔗 https://bun.sh/ #JavaScript #TypeScript #BackendDevelopment #WebDevelopment #TechTools #Innovation

4

**Is the MERN Stack Dead?** You’ve probably seen a lot of videos on YouTube with every YouTuber making this claim. I got a bit confused too 😕, wondering if the MERN stack is really dead because I recently completed my backend and was working on a fullstack project 😔. So, I asked my senior, "Is the MERN stack dead?" I was curious to hear his response. He said: "Adnan bro, nothing is ever truly dead. These things are just trending." Then he showed me the Stack Overflow 2024 survey and said, "Look at this." For the next two days, I noticed every YouTuber making videos about the same topic, "Is the MERN stack dead?" 😅 Then it hit me – these YouTubers are just following the trend. If one makes a video, everyone else starts making the same content. Some YouTubers are saying the field is getting saturated, Everyone learning the same thing, while others have different opinions. 🤔 So, what do you guys think? Let me know in the comments!👇

14

2 Comments