Fadamiro Catherine @_KatFad

The most eye opening book I’ve read in a long time. This puts things in perspective and hit me like a ton of bricks.

Amazon Web Services (AWS) AI & ML Scholarship Program 2024 opportunitydesk.org/2024/09/17/aws…

please let's follow @TheAyoBankole

Edward Israel-Ayide @wildeyeq

2 years ago

If you're wondering what happened to @AyoBankole, he lost access to his Twitter account and has now opened another handle, @TheAyoBankole Please follow his journey to support millions of African SMEs and Startups with strategy.

1 15 8 2K 0

@ProgressiveCod2 Retrieving only the required set of data from the database also helps.

My 9-year-old son asked me: “What is Dependency Injection?” He understood the concept from my very first explanation. This is how I did it: Imagine a Home Service company frequently having this situation: A client has a Plumbing appointment, and they send a Plumber to his house, but then the Plumber detects an extra issue with electricity. There are two options: 1- Make the plumber learn electricity to do both works. 2- Contract an Electrician to fix those issues When proceeding with option 2, the company will add a new specialty/service to its portfolio. It will be like injecting skills on demand. Doing that: - They can serve more clients in parallel. - Each employee needs to carry fewer tools every day. - Every work can be finished faster, in parallel. - Employees will need to learn less content/knowledge, so they will learn faster. It is the same as Dependency Injection where: You inject services into your classes and methods and delegate particular tasks or skills to them. In that way, your class stays clean, simple, and focused only on its single responsibility (SOLID principles). When the same happens with another type of work like Roofing, the procedure should be the same: adding/injecting a new technician. ** Every week I post trying to explain the Software Development concepts as simply as possible; and sometimes, as explaining concepts to my little son.

John the Baptist was one of the major influencer in the Bible

𝗪𝗵𝗮𝘁 𝗜 𝗟𝗲𝗮𝗿𝗻𝗲𝗱 𝗙𝗿𝗼𝗺 𝗧𝗵𝗲 𝗕𝗼𝗼𝗸 "𝗣𝗿𝗮𝗴𝗺𝗮𝘁𝗶𝗰 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗲𝗿" One book I always recommend to developers is "Pragmatic Programmer" by David Thomas and Andrew Hunt. Although it is not new, it builds on a foundation that is important today and will continue to be. Here are the main learnings from the book: 𝟭. 𝗪𝗿𝗶𝘁𝗲 𝗴𝗼𝗼𝗱 𝗲𝗻𝗼𝘂𝗴𝗵 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 Striving for perfection can lead to never-ending projects. Instead, aim for "good enough" and iterate. Deliver value early and often. Write code that works, prove it by writing tests, and ensure they are executed automatically. Record every change in your software using version control software. If you mess up, you can always revert to the previous code version. 𝟮. 𝗧𝗿𝗮𝗰𝗲𝗿 𝗯𝘂𝗹𝗹𝗲𝘁𝘀 You can use tracer code or prototypes to validate your understanding of the problem. This helps in clarifying requirements before fully implementing a feature. 𝟯. 𝗗𝗼𝗻'𝘁 𝗯𝗹𝗮𝗺𝗲, 𝗳𝗶𝘅! Sometimes, you will find lousy code that someone else wrote. Sometimes, you will find bad code that you wrote some time ago. Pragmatic programmers don't say, "I didn't write this, so I will not fix it," but do something about it and open a debate in a team about why. 𝟰. 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝘁𝗿𝗼𝗽𝘆 In the book, you will learn about the "Broken Window Theory," which states that if something is broken, others will break it even more in the future. As a pragmatic programmer, you should fix all significant problems you find in the system while working on it. 𝟱. 𝗞𝗲𝗲𝗽 𝘆𝗼𝘂𝗿 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝘂𝗽 𝘁𝗼 𝗱𝗮𝘁𝗲 Continuous learning is essential. Stay updated with new tools, technologies, and best practices. Learn at least one programming language or tech stack every year. Read technical and non-technical books every once in a while. This investment in your skills pays off in your career growth. 𝟲. 𝗗𝗥𝗬 (𝗗𝘂𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝘁𝗵𝗲 𝗥𝗼𝗼𝘁 𝗼𝗳 𝗔𝗹𝗹 𝗘𝘃𝗶𝗹) Redundant code is more complex to maintain. When you notice duplication, refactor it into a shared function or module. This will promote consistency and reduce errors. 𝟳. 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗯𝘆 𝗰𝗼𝗶𝗻𝗰𝗶𝗱𝗲𝗻𝗰𝗲 Understand your code deeply; don't rely on coincidental successes. Make sure you know why your code works, not just that it works. 𝟴. 𝗕𝗲 𝗮 𝗴𝗼𝗼𝗱 𝗹𝗶𝘀𝘁𝗲𝗻𝗲𝗿 To help your users, you'll need to understand them first. Be careful when others speak (Product managers, developers, business analysts). And ask good questions. Check my complete list of the most recommended books for software developers in the comments. #programming

You probably knew about JavaScript's new .at() method for accessing array items. Did you know it works for strings too? Easily grab the first/last/nth character of a string. Handy👌

@olubukolasthots @yinkanubi @gtbank I did the exact thing 🥲. They did us dirty

@chichiofficiall @gtbank This upgrade wasn't properly tested because how will thousands of your users be unable to access the application with the same issue and no backup app to revert to.

@toyosioyesile I posted something like this on my whatsapp status yesterday😂😂.. pure cruise

LAPTOP CALL 2 - If you know any tech newbie currently learning UX/UI WITHOUT A PC, kindly tag them to this. Pick a number beneath & apply for a laptop via [email protected] with subject “LAPTOP CALL TWO” Retweets are highly appreciated❤️

@BimYonce 😒😒

@BimYonce No, i want soft life for him.. don’t stress him

@sesigl Free

I interviewed over 50 front-end engineers in the last 2 years. I created a new Notion "Learn Frontend Development Pack" that contains a learning path & projects to become a frontend dev with only free resources. RT and reply with "free" and I'll DM it to you. (need to follow)

@BimYonce 😀😀

Today I'm launching my Beginner JavaScript text guide! These notes are totally free and have been modeled after the content in my Beginner JavaScript course. This is a huge resource I've been working on for over a year and I'm so excied to share it! wesbos.com/javascript

Yawning doesn't always necessarily mean you're tired, it also means your body needs more oxygen.