Isaac Oresanya’s Post

A simple counter of notifications with the blue color to no-read notifies, an option to mark every notify as read. https://lnkd.in/eWDmrWRn

Sometimes, requests fail because there are simply too many of them 👨👩👧👦. When this happens, we can retry the failed requests—if they are idempotent, of course. But retrying all the requests simultaneously leads to the same problem: more failed requests 🔁. That’s where an important concept comes in—jitter 🪇. A jitter is a random delay added to the retry back-off to randomize or desynchronize the requests. 💡So, instead of retrying 500 failed requests all at once with a linear back-off, which only repeats the issue, we add a jitter to each retry. This way, the retries are spread out and happen at different times. This concept, though simple, is highly effective in addressing failures caused by an overload of simultaneous retries. Have a nice weekend and happy coding! 💻✨ #retries

You know you are onto something when all the class behaviors are implemented in 2 or 3 lines of code. The image is all the code needed to handle templates, coding, and having workflows inside a workflow. It just falls out of the design. This week I am working on a step agent that can step forwards or backwards a specific number of steps based on a specific condition. And all that is configurable. I also want to look at packaging results up when there is more than one, like there would be if you stepped back and reran steps. But I want things to be as simple as the other three classes.

On today's episode of Jade does dumb things. I couldn't get poetry to work on my VSCode. I installed it and added the correct path locations to the environment variables but I still couldn't get it to work unless I referenced the folder directly. I restarted VSCode, still no hope. WELL, WELL, WELL, IT TURNS OUT... Because I had another VSCode opened, it didn't update the environment variables. So when I was printing the environment variables in the terminal I was like 'WHY CAN'T I SEE THE UPDATED VARIABLES?' So, let this be a lesson to you all. Close all VSCode instances down to update your environment variables. And if that fails... Turn it off and on again.

In the realm of software development, the technique of "rubber duck debugging" has gained traction among programmers seeking to enhance their problem-solving skills. This method involves explaining code line by line to an imaginary companion, often represented by a rubber duck. Research suggests that verbalizing thoughts can significantly boost cognitive functioning, leading to clearer understanding and the identification of errors, such as overlooked syntax issues. Historically, this concept resonates with the wisdom of Seneca, who observed that "while we teach, we learn," underscoring the dual benefits of teaching and learning through explanation. Moreover, rubber duck debugging not only enhances productivity but also serves as an effective preparatory strategy for technical interviews, providing programmers with a structured approach to articulate their thought processes. As software developers continue to navigate complex challenges, this technique stands out as a valuable tool for improving clarity and efficiency in coding. #SoftwareDevelopment #Debugging #ProblemSolving #CognitiveScience #Productivity ---------------------- Learn more here: https://lnkd.in/ecNEcQNm

The Rule of Holes: Recognizing and Escaping Blind Alleys "Blind alleys are a fact of life for all software craftsmen. Sometimes you will make a decision and wander down a technical pathway that leads to nowhere. The more vested you are in your decision, the longer you will wander in the wilderness. If you’ve staked your professional reputation, you’ll wander forever. Prudence and experience will help you avoid certain blind alleys, but you’ll never avoid them all. So the real skill you need is to quickly realize when you are in one, and have the courage to back out. This is sometimes called The Rule of Holes: When you are in one, stop digging. Professionals avoid getting so vested in an idea that they can’t abandon it and turn around. They keep an open mind about other ideas so that when they hit a dead end they still have other options." ― Robert Martin, The Clean Coder: A Code of Conduct for Professional Programmers  https://lnkd.in/dfAGSx-e #cleancode #experimentation #decisionmaking #extremeprogramming

I struggle sometimes with the push to "don't repeat yourself"/DRY in programming. I understand the value in not having copies of the same bit of code throughout your program. However, in practice, I've seen this principle result in a single Ur-library on which all of your other software depends, and you cannot make a change in any dependency without making a change in the Ur-library that could affect *all* of your other dependencies. This feels like an anti-pattern to me. To be clear, I've been working in software engineering for several years. I'm not looking for answers to this. I'm pushing gently against folks blindly accepting and applying principles like DRY without any consideration for what that means in practice. I will, though, gladly take examples of this principle going wrongly like this or if someone does have a really nicely architected example.

Inline Constraints I have defined some constraints in my class. However, I have a requirement to add some more constraints to existing class constraints depending on my test scenario. What do I do? - Use Inline Constraints Let us learn: 1. What is the need of Inline Constraints 2. Usage 3. Coding examples Link in COMMENT

🧦 Just tackled a fun problem: matching socks! From code challenges to real-world tasks, finding the right pair is always satisfying. Here's to solving one challenge at a time and keeping the code clean and organized. #PairingUp #CodeProblems . . . . . . . . . #CodingChallenge #PythonProgramming #ProblemSolving #DeveloperLife #CodeNewbie #TechSkills #ProgrammingLife #ContinuousLearning #WomenInTech #TechCommunity #SoftwareEngineering #Algorithm #LinkedInLearning #LearningJourney

𝐕𝐒 𝐂𝐨𝐝𝐞 𝐟𝐞𝐞𝐥𝐢𝐧𝐠 𝐜𝐥𝐮𝐧𝐤𝐲? ⌨️Keyboard shortcuts are the secret sauce to coding like a pro. But who has time to memorize them all? How To: Master these top 5 time savers : ⌚ 1️⃣ Ctrl+P: Find & open any file faster than you can say "autocomplete." 2️⃣ Ctrl+D: Select multiple occurrences of a word & edit them all at once. Boom! 3️⃣ Ctrl+Shift+K: Delete entire lines like they never existed. Poof! 4️⃣ Ctrl+/: Toggle line comments on & off – your code's on/off switch. 5️⃣ Ctrl+F: Find & replace text like a pro. No more manual hunting. 📍𝐁𝐨𝐧𝐮𝐬: 𝐖𝐚𝐧𝐭 𝐦𝐨𝐫𝐞? Hit up the official shortcut guide and become a coding legend. #vscode #codelife #productivityhacks