Samuel Tosin

Node.js is a server-side programming language. Lol, that is a costly joke. Node.js is not a programming language; it's a JavaScript framework. That is a lie again before my agba tech bros and sis come for me 😂😂 . Node.js is not a JavaScript framework either. I am so sorry for telling two lies consecutively please forgive and forget 😂. Now, if Node.js is not a JavaScript framework nor a server-side language, then what is it? Well, Node.js is a JavaScript runtime environment. I know you must be wondering what a runtime environment is. Let me give you a brief history of JavaScript and Node.js. JavaScript was originally designed to run in web browsers, making web pages interactive. Think of fun stuff like clicking buttons, playing games, and moving things around on a page. But JavaScript was limited to just the browser. Node.js was created by Ryan Dahl in 2009. Ryan had a brilliant idea: "Why not use JavaScript outside the browser?" So, he built Node.js as a runtime environment that allows JavaScript to run on servers. This means JavaScript can now be used to build things like websites, apps, and even robots, outside of your browser! A runtime environment is like a playground where JavaScript can run and play, but instead of just in the browser, it can now run on your computer or on servers anywhere in the world. It provides all the tools JavaScript needs to do cool stuff like reading files, handling network requests, and talking to databases. Why is Node.js So Awesome? 1. Fast and Efficient: Node.js is built on Chrome's V8 JavaScript engine, which makes it super fast. 2. Single Programming Language: Developers can use JavaScript for both frontend and backend, simplifying the development process. 3.Large Ecosystem: With npm (Node Package Manager), you have access to thousands of libraries and tools. 4. Real-time Capabilities: Great for building real-time applications like chat apps and online games. 5. Scalable: Perfect for building scalable network applications, able to handle multiple connections at the same time. Node.js has become highly sought after in the tech world for these reasons and more. It's a game-changer, allowing developers to create powerful, dynamic applications with ease. What do you think about Node.js? Have you used it in your projects, or are you curious to try it out? Share your thoughts and experiences in the comment section below! 👇 #NodeJS #JavaScript #WebDevelopment #TechTalk #Programming #LearnAndGrow

4

Hey everyone 🤗  Still on #Day52 on my #100daysofcodechallenge. I had to break it because the last post was getting too long 😁 - I also had a discussion with my friend and Senior Android Engineer Segun Francis about Process deaths in Jetpack Compose. I knew about deaths coming from configuration change and theme change but I had not really studied about Process deaths. So Process Death is what happens when your app is killed abruptly without going through the motions of onPause, onStop and then onDestroy. These are the lifecycle methods called when your app is minimised to the background and then closed. Sometimes it doesn't have the chance to undergo these lifecycle stages before it is killed. This is called Process death. There are two kinds of Process death - System initiated process death and User initiated process death. The reason why we are concerned about this death in the first place is because the state of the app (the data displayed or accessed on your application) is cleared once it goes through death (configuration change or process death) if it is not properly stored. To store your data, the following options are given: - Viewmodel object (for configuration changes) - onSaveInstanceState() - If you're using Android Views - rememberSaveable - If you're using Compose onSaveInstanceState and rememberSaveable are for storing UI related data in the case of process death. And you can also persist user data to disk or cache to save in the instance of process death. To read more about this, check out this link: https://lnkd.in/dgvEw2i4 #Day53- I fixed the issue I had with Hilt (from the previous post) - I worked on updating the Readme.md on one of my GitHub projects. I realised to: Create a bold header, all you need to do is - # Bold Header in the edit box and it works fine. To insert a link in a text, you do this - [Text](link to insert in text) To arrange things in a list, you use * as the bullet and it automatically lists it for you. It was nice playing around with this. I hope to share more as I keep learning. See you tomorrow 😉 . #100daysofcode #processdeath #github #readme #lifecycle #activity #androidos #application

19

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

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

64

13 Comments

Dear Backend Engineer, I regret to inform you, that merely knowing CRUD operations and basic backend tasks was never enough. Not many people will tell you this, but to truly stand out and excel in your career as a backend engineer, it's essential to delve deeper into core principles like systems architecture, system design, and more. Here's why and how mastering these areas can elevate your engineering prowess: 1. Understanding Systems Architecture: Systems architecture is the blueprint of scalable, efficient, and maintainable software. By grasping concepts like microservices, monolithic architectures, and serverless computing, you can design systems that are robust and adaptable to change. 2. Mastering System Design: System design goes beyond coding. It involves creating high-level structures that solve complex problems. This includes knowledge of design patterns, scalability, fault tolerance, and distributed systems. Being proficient in system design can help you foresee potential issues and innovate better solutions. 3. Implementing Load Balancing: Load balancing ensures your application can handle high traffic efficiently. Understanding various strategies (round-robin, least connections, IP hash, etc.) and tools (NGINX, HAProxy, AWS Elastic Load Balancing) will make your systems more resilient and performant. 4. Leveraging Caching: Caching significantly boosts application performance by reducing database load and latency. Familiarize yourself with different caching mechanisms (in-memory caches like Redis and Memcached, distributed caches, etc.) to deliver faster and more efficient applications. 5. Optimizing Data Logging and Monitoring: Effective logging and monitoring are critical for diagnosing issues, understanding user behaviour, and ensuring system health. Tools like ELK Stack, Prometheus, and Grafana can help you maintain robust monitoring and alerting systems. 6. Ensuring Security: Security should be a priority from the start. Learn about common vulnerabilities (SQL injection, XSS, CSRF) and how to mitigate them. Implementing secure authentication, authorization, and encryption practices can protect your users and data. 7. Exploring CI/CD and DevOps Practices: Continuous Integration and Continuous Deployment (CI/CD) pipelines streamline the development process, reduce bugs, and accelerate feature delivery. Embrace DevOps tools (Jenkins, GitLab CI, Docker, Kubernetes) to automate and enhance your development workflow. 8. Enhancing Communication Skills: Technical prowess is important, but so are communication skills. Being able to explain your designs, collaborate with cross-functional teams, and document your work effectively can set you apart as a well-rounded engineer. Go far and beyond, this will make you stand out, even during interviews. You’ve got this, cheers 🥂

4,187

198 Comments

Recently , I've been working on a project that's a bit old , it uses Next.js13 pages directory , but I've decided to convert it to app directory, so come with me the on journey of migrating from pages to app . You'll need to focus on these points: 1. package update "next - react - react-dom .... etc" you'll need to update react , react-dom and next packages 2. linter update "Eslint" just run ` npm install -D eslint-config-next@latest ` 3. Folder structure Folder structure has been changed a lot between those versions so , migrate _app and _document -> app/layout.tsx migrate <Head></Head> -> export const metadata: Metadata = {...} migrate pages inside pages -> app/page.tsx 4. update Router hooks useRouter is now imported from "next/navigation" instead of "next/router" The new useRouter does not return the pathname string. Use the separate usePathname hook instead. The new useRouter does not return the query object. Use the separate useSearchParams hook instead. You can use useSearchParams and usePathname together to listen to page changes. 5. change data fetching methods now , there's no getServerSideProps() or getStaticProps() , use fetch directly inside page or component , you still can determine it to be SSR ,SSG or ISR using fetch options object and determining {cache : "no-store" | "force-cache"} or determine { next: { revalidate: 10 }, }) and that's it ! happy Hacking ^^ learn more : https://lnkd.in/dE-62hz5 (Vercel) https://lnkd.in/d69M5HpT (Clerk.com)

7

🚀 Just launched a Java-based Electronic Cash Register (ECR) system that's now live in production! This is a major personal achievement, marking my second Java application and a significant step in my transition from PHP to Java development. In just three months of learning Java, I've built a system that seamlessly integrates with Paymob and National Bank of Egypt POS terminals, streamlining transactions and enhancing security. This project involved diving into network programming with WebSockets, ensuring secure communication with SSL, and applying design patterns like Observer and Factory for a flexible and maintainable codebase. The system is packaged as a JAR file, seamlessly embedded within our Flutter-based Windows POS application at Codelytical as a part of our Product Improvement Mission, running efficiently on the main thread of each cashier's machine. The video attached shows a demo Flutter app with the integration, demonstrating basic sale and void operations. The learning curve was steep, but incredibly rewarding. I gained hands-on experience with Java's threading model, serial communication protocols, and the nuances of integrating with external hardware. Seeing this project come to life and make a real impact in a production environment is a testament to the power of continuous learning and dedication. I'm excited to continue my Java journey and tackle even more complex challenges in the future! #Java #ECR #POS #softwaredevelopment #careergrowth #PayMob #NBE #Flutter

23

4 Comments

Coding requires thinking and above all is the ability to remain persistent as you deal with bugs and compilation errors. There was a particular bug I was dealing with when working with React native using android studio 2 days ago. I was stuck for some time before I found a solution 😂😂. For people facing similar issues, Stack overflow and chatgpt is helpful along the way but is not enough as a developer. You need to first find out what could have caused the error before looking for solution. Then sometimes you need to reference the documentation to ensure you are using the package or tool properly.

2

This is where I think most frontend/full stack developers get it wrong They don't realise the need for a mindset shift when transitioning into the Backend domain especially when coming from a front end domain. Front end developers usually when building user interfaces, all they care about is the user experience and accessibility ( just building an intuitive GUI ). In the domain of server infrastructure that's not the case, when building for servers every little decision or implementation made matters, you don't just want to solve a business problem but also looking to prevent awful unforseen events. The mindset shift here is that you are now thinking in terms of security, performance and scalability. Before you make a critical step or the design of an API careful considerations must be taken so you won't leave your systems vulnerable to attacks and performance bottlenecks And I have come to realise that it's easier to build a backend system not a resilient one. Therefore it's mandatory to adopt the mindset of a defensive developer when building for servers, consider every tiny decision and first do due diligence by questioning what could be the negative impact if not done right. #infrastructure #frontend #servers

5

1 Comment

Whether one is a designer or a developer, tools play a crucial role in our productivity. I am a backend engineer. Let me walk you through my three game-changing tools. ### 1. 𝐢3 A tiling window manager that allows us to arrange windows into mutually non-overlapping frames. 𝘞𝘩𝘺 𝘥𝘰 𝘐 𝘶𝘴𝘦 𝘵𝘩𝘪𝘴 𝘵𝘰𝘰𝘭? - Workspaces — Workspaces are a true game-changer for me. I can easily switch contexts by changing a workspace. It's like having different rooms for different tasks: one for browsing and instant messaging, another for development, and so on. - Less use of mouse — Switching between windows can be done easily using the keyboard, reducing the need for a mouse. - Status bar — Provides a quick overview of disk usage, VPN connection status, and other critical information without needing to run commands. ### 2. 𝐃𝐁𝐞𝐚𝐯𝐞𝐫 DBeaver is a client for most popular databases. 𝘞𝘩𝘺 𝘥𝘰 𝘐 𝘶𝘴𝘦 𝘵𝘩𝘪𝘴 𝘵𝘰𝘰𝘭? - Color scheme — Helps distinguish between development and production environments through different color settings. - Extra prompts in production — Prompts when executing sensitive queries on the production system, such as when analyzing a query execution plan for a PostgreSQL query on a production database. ### 3. 𝐟𝐢𝐬𝐡 Fish is a user-friendly command-line shell. 𝘞𝘩𝘺 𝘥𝘰 𝘐 𝘶𝘴𝘦 𝘵𝘩𝘪𝘴 𝘵𝘰𝘰𝘭? - Auto-completion — Offers intelligent auto-completion for commands. - Syntax highlighting — Provides syntax highlighting for better readability. - User-friendly prompt — Enhances the command-line experience with a customizable and informative prompt. Photo credit: https://lnkd.in/dBZgH9ay

8

2 Comments

🚀 How to Be an Effective Software Engineer in Everyday Life 🚀 As a software engineer, your skills go beyond the office. In fact, the principles you apply at work can also help you achieve success in your personal life. Here are some practical tips to level up your everyday life as a software engineer: 1️⃣ Think like an Algorithm: Just like you break down complex problems into smaller, manageable tasks at work, you can do the same in your personal life. Apply a systematic approach to solve everyday challenges, whether it's planning your schedule, managing finances, or organizing your home. 2️⃣ Optimize Your Routine: Efficiency is key! Embrace automation tools and time-saving apps to streamline your daily tasks. From setting reminders, tracking expenses, to scheduling workouts, there's a plethora of software available to help you optimize your routine and make the most of your time. 3️⃣ Continuous Learning: The tech industry is constantly evolving, and so should you. Cultivate a growth mindset and stay up-to-date with the latest trends and technologies. Attend conferences, join online communities, and engage in continuous learning to enhance your skills and stay ahead of the curve. 4️⃣ Collaboration is Key: Software engineering is often a team effort, and the same principle applies to your personal life. Collaborate with friends, family, and peers to tackle challenges together. From planning events, organizing trips, to brainstorming ideas, teamwork brings fresh perspectives and ensures success. 5️⃣ Work-Life Balance: While your passion for coding may drive you, it's crucial to maintain a healthy work-life balance. Take breaks, pursue hobbies, and prioritize self-care. Remember, a refreshed mind is a creative mind! By implementing these strategies in your everyday life, you'll not only excel as a software engineer but also enhance your personal well-being. So, go ahead and unleash your software engineering skills beyond the realm of coding! 🤝 Let's connect and share more insights about being an effective software engineer! Feel free to comment below or send me a message. Together, we can keep growing and achieving greater success! 🚀 #SoftwareEngineerLife #PersonalGrowth #ContinuousLearning #Efficiency #Collaboration #WorkLifeBalance

6

Yes, web development is saturated, but if you are considering tech, why should you worry about that? It's a necessity, and here are my reasons: === If your goal is any other field, such as data, DevOps, or cybersecurity, consider web development as a prerequisite. Note: don't go for mastery in the prerequisite; just learn enough to understand how the system works—front-end, back-end, app, ops, how they communicate. Understand the system, and then go for any field you love. Don't restrict yourself to just one genre. Even I'm exploring everything from surface web, DevOps, cybersecurity, data and whichever resonates with me more, I'll go niche in it. Trust me, web development knowledge has always been an added bonus. Web development is like an iceberg—way deeper than you think. Beyond websites, it involves complex systems for a reason: >> Distributed asynchronous programming, queues, and distributed databases. >> Microservices, containers, and Kubernetes. >> Creating complex systems like the Google Maps system. etc. etc. There is a lot to it. Web development is a skill that will always be valuable because it helps you connect everything together. It will help you understand internet better. Also you should not consider job options while learning it. If you are in college, just go with it; it will consume about 4-5 months. Then, you will be in a much better position, to answer your own doubts and choose a path in future. You will understand technology, different APIs, databases, proxies, different approaches to problems, and creating solutions. So yes, I feel understanding web development is very important even if you are aiming for other career path like data or devops. It helps us understand how the internet works. Best thing to invest time on. My Languages, path for web dev was: >> JavaScript—yes, it's everywhere. It's the language of the browser. It holds the meme: "hate it or love it, but you can't ignore it." >> Python with Django—if you're moving to data science, Python will help you in future. >> A low-level language like Golang—let's understand things a little more closely now. After that, you can dive into cloud computing, hacking, front-end, back-end, and data. The concepts will enrich your understanding; for example, in data engineering, there is a lot of use of queues like Kafka, and knowledge of web development will help there. PS: I doubt anyone is using LinkedIn during the World Cup final, but this is a question one of my colleagues asked in a DM, and I felt like giving a detailed reply. :) #day21

41

2 Comments

🚀 How to Stand Out in the Competitive Frontend Development Market? Many people aspire to build their careers in frontend development and it making the market highly competitive. Most beginners often jump into learning tools like React and start building projects without properly understanding the basics of JavaScript, HTML, and CSS. This can be incredibly frustrating, as they struggle to crack the interviews and secure jobs. To stand out and do well, it’s important to have a strong foundation. Here is my honest advice to beginner: 𝗗𝗼𝗻’𝘁𝘀 ❌ 1. Avoid Copying Popular Websites: Don't just make clones of sites like YouTube, Zamato or Swiggy because lots of people already doing it. 2. Don’t Rush into Projects: Learn the basics first. If you start building projects without understanding HTML, CSS, and JavaScript, it can be very frustrating. 3. Focus on Quality, Not Quantity: It's better to have a few high-quality projects than many low-quality ones. Do’s ✅ 1. Build a Strong Foundation: Learn HTML, CSS, and JavaScript well before moving on to more complex projects. 2. Create Unique Projects: Work on unique projects that show your creativity and skills. 3. Ensure High Quality: Make sure your projects are high-quality, user-friendly, and well-coded. 4. Open to feedback: Share your code github link over social media like:LinkedIn and take the feedback from seniors in positive way. 5. Challenge yourself: Try to add as much as functionality in your project. By following these tips and focusing on unique, high-quality projects, you’ll build a strong foundation and stand out in the competitive field of frontend development. 👉 Here are some unique project Ideas 1. Make an online interactive resume builder with interactive elements to showcase your skills dynamically. 2. Movie or Web series recommendation system based on user choice. 3. Meditation and Mindfulness App: Develop an app with guided meditation sessions and mindfulness exercises. 4. Design an app that helps users plan their trips, including itineraries, accommodation, and sightseeing. 5. Make an app that helps users learn new languages with vocabulary lists, quizzes, and practice exercises. 💡Follow 👉 Salman Ahmad for more amazing tips. #FrontendDevelopment #WebDevelopment #JavaScript #HTML #CSS #CodingTips #CareerAdvice #TechCareers #Programming #LearnToCode #DeveloperLife #WebDesign #SoftwareEngineering #CodingCommunity #TechTips

9

1 Comment

My Backend Bias! I'm glad I left my frontend path back in October to pursue backend development and never looked back. I remember looking at roadmap.sh and thinking, "I still need to cover this 'XYZ CSS library' --oh god, no!" Any tech enthusiast reading this: pick backend. For frontend, just know JavaScript, its paradigm (event loop), and how to deal with APIs, and you're done. If full stack is your goal, go with React and Redux—that's it. Don't spend time on CSS or animations; it's a waste of time. If you have an interest in "tech," you will regret spending too much time on frontend. And why so? Here are my 3 points: >> Backend doesn't restrict you: Its learning helps you understand the overall system and communication better. You can explore new domains, and backend knowledge will indeed support you. For example: * Networking and authentication concepts are useful in cybersecurity. * Database and SQL knowledge are valuable in data science and engineering. * Even in the cloud, understanding how to host or allocate right resources to container is crucial. >> Makes you Responsible: Failures in the backend can impact data integrity. Frontend issues, while frustrating, are often less critical. >> Pay the bills: Backend deployment and hosting require careful consideration of infrastructure, scaling, and monitoring strategies; it affects both cost and performance. Frontend deployment is generally less complex than backend. And if you are thinking, "I will just write my frontend and go for no-code on the backend," well, even serverless requires servers, and to understand them better, you must have knowledge of the backend. Frontend alone, just can't unlock that potential. P.S.: Genuinely, no hate for frontend developers. SEO is crucial, and a better user experience is always in demand, but you should definitely try backend development at least once as its skills are transferable to different domains too. What are your thoughts on this? Correct me if I am wrong. #LinkedIn

88

17 Comments

I have been busy working at CoinCircle recently. Now that the project is wrapping up, I'll soon rejoin the community. Stay tuned as the list continues to grow. Kindly tell in comment that which library do you like most. 1. LokaleNow An android cradle plugin to generate localised xml string files automatically  https://lnkd.in/dT4Gn8DR 2. Internet Speed Test A Complete native android open-source project https://lnkd.in/dEYZtxv6 3. ANR Spy An android library to detect ANRs https://lnkd.in/duXmphut 4. Word Connect (JetPack Compose) A Complete open-source word connect game written in compose + Kotlin https://lnkd.in/d7qD33y5 5. Word Tracing An SDK to make alphabet tracing game for kids Note: Needs improvement. Your contribution is most welcome. https://lnkd.in/dppsxe3a 6. PandaSpector An android studio grade plugin to detect ANRs Note: Needs improvement. Your contribution is most welcome. https://lnkd.in/dJp8VHaM 7. PermissionMate An android library to simplify and manage permissions in just two simple steps. https://lnkd.in/dJp8VHaM 8. Admob Native An android SDK to implement native ads in compose. https://lnkd.in/d3RPV4_x 9. ZeroCrash An android library to handle crash globally. It will prevent crash report to google play console but will still record as non-fatal in firebase. https://lnkd.in/d3RPV4_x 10. Profile Image Maker An android SDK to create avatar using tensor flow https://lnkd.in/d3RPV4_x 11. Document Scanner An android SDK to make an app in just a week like CamScanner https://lnkd.in/d3RPV4_x 12. MaxGuard An android library to protect your app against reverse engineering. https://lnkd.in/dsynN6G2 13. Super Caller Id An android SDK to create app like TrueCaller. https://lnkd.in/da6vnuyq 14. PrimeUtil An android library to handle scoped storage https://lnkd.in/dcECS3KH 15. SpeedMeter Compose An android SDK to create speed meter (animated) https://lnkd.in/d3_7fcjq 16. GuageView An android library to create xml based gauge view https://lnkd.in/dNe5BPdB 17. WifiMaster An android SDK to make app for wifi. It will scan wifi along with its passwords around the world. https://lnkd.in/dCJ9VjHb 18. PagePilot (a compose pdf viewer) A compse based android library for viewing pdf files. https://lnkd.in/dCJ9VjHb 19. SuperStar An android library to create an app like StartMaker in just few days. https://lnkd.in/dC6awZf2 20. InfiniteRunner A unity based open-source project. Note: Your contribution is most welcome. https://lnkd.in/dJwqqwJy

96

2 Comments

💡 As a Junior or Senior developer, remember that A framework should not define what type of developer you are. You will define yourself as a React, ReactNative, Vue, Angular, Springboot, or Laravel developer until you deal with some in-depth bugs. Being an engineer can take you where being a “frameworker” can’t.

10

1 Comment

Day 16 #100DaysOfCode I did more exercises on function, I was stuck at a spot for a long time and wondering why the code isn't working 😂 I think I need to read up more on functions, kindly recommend some sources. On to the next day 😎 #bulildinpublic #javascript #html5 #CSS

2

4 Comments