Donald Raab’s Post

📚 Excited to share my latest project! 🚀 🔍 Are you tired of struggling with keeping track of your extensive book collection? Say no more! 📖 With our new Book Record Management system built using JavaSwing, you can effortlessly organize, catalog, and manage your books with ease. 🖥️ Our user-friendly interface offers intuitive navigation and robust functionalities, allowing you to: 📌 Add new books to your collection with just a few clicks. 📝 Edit book details such as title, author, genre, and more. 💾 Save and export your library for safekeeping or sharing. 💡 Whether you're a bookworm with a vast collection or a librarian looking to streamline operations, our Book Record Management system is the perfect solution for you! 👨💻 Built with JavaSwing, it combines the power of Java with the flexibility of Swing to deliver a seamless user experience across different platforms. 🚀 Ready to take control of your book collection? Get started today! 💼 #BookManagement #Java #JavaSwing #LibraryOrganization #Efficiency #Productivity #TechSolutions GitHub link - https://lnkd.in/g3j86Kvt

source code of NativePayload_Call4.cs published. Emit(Opcodes.Call)" instead "Emit(Opcodes.Jmp)" in C# you can use Emit(Opcodes.jmp,TargetMethod) in your codes without writing any asm bytes in code to jump to pointer of TargetMethod or (MethodInfo) to run in-memory via Emit(Opcodes.jmp, method) in system.reflection namespace ;D yeah you can use this technique to create your own Jump code without write any assembly code in source code ;p lol , "so in this case Csharp Method name [ExecuteInMemory] indirectly called in-memory via jump method without calling c# Method in source code" , i talked about this in my ebook "Bypassing Anti-viruses by C# Programming v2.0" in chapter 3.4 and now you can see source code ;) now you can do this method via "Emit(Opcodes.Call)" instead "Emit(Opcodes.Jmp)" , this is new for me maybe is new for you too ;P #pentest #csharp #sourcecode #emitcall #ebook https://lnkd.in/d36-SdN7

🚀 #ProjectCompleted: Python Phonebook Application 📞 I'm excited to share that I've successfully built a Python-based Phonebook application that handles basic CRUD (Create, Read, Update, Delete) operations. Here's a quick overview of what the app can do: ✨ Features: 1 .Add a New Contact: Prompt the user for the name and phone number of a new contact and add it to the phonebook. If the contact already exists, it shows a message. 2. Search for a Contact: Allow the user to search for a contact by name and display the phone number. 3. Delete a Contact: Easily delete a contact by name if it exists. 4. List All Contacts: Show all contacts with their phone numbers. 5. Exit: Terminate the program with an option. 🛠️ Steps I Followed: Initialized a Python file called phonebook.py. Created an empty dictionary to store contact names as keys and phone numbers as values. Used a simple CLI with a while-loop that shows options like adding, searching, deleting, and listing contacts. Ensured seamless user interaction with condition checks for errors, such as duplicate contacts or searches for non-existent entries. Implementation Steps:- #Step 1: Setup Your Project ● Create a new Python file named phonebook.py. ● Open this file in your chosen text editor. #Step 2: Initialize the Phonebook ● At the beginning of your program, create an empty dictionary to store your contacts. Each contact name will be a key, and the associated phone number will be the value. #Step 3: User Interface ● Implement a loop that continuously displays a menu of options to the user until they choose to exit. Use input() to read the user's choice and if-else statements to handle different actions based on the choice. #Step 4: Implementing CRUD Operations ● Add a New Contact: Check if the name already exists in the dictionary. If it does, display a message; otherwise, add the new entry. ● Search for a Contact: Check if the contact exists in the dictionary. If so, display the contact's phone number; otherwise, inform the user that the contact was not found. ● Delete a Contact: Similar to search, but remove the contact from the dictionary if it exists. ● List All Contacts: Use a loop to iterate through the dictionary and display each contact's name and phone number. #Step 5: Testing ● Thoroughly test your application to ensure it handles different scenarios gracefully, such as searching for a non-existent contact or adding a contact that already exists 🔍 #SourceCode https://lnkd.in/g6ZDC6SZ 🌟 #Python #CodingJourney #ProjectComplete #PhonebookApp #Programming

Spring users, we have updated our handy cheat sheet! Download your copy for a guide to Spring annotations here > https://bit.ly/3ynao9S

🚀 I've just published Part 4 - 'Formatting' of my series, where I share my notes from the book 'Clean Code' by Robert C. Martin. This part highlights importance of code formatting and its impact on readability and maintainability. Discover best practices for structuring your code to make it cleaner and more understandable. Read it here: https://lnkd.in/dD9yGMcG #CleanCode

Spring users, we have updated our handy cheat sheet! Download your copy for a guide to Spring annotations here > https://bit.ly/3ynao9S

Spring users, we have updated our handy cheat sheet! Download your copy for a guide to Spring annotations here > https://bit.ly/3ynao9S

📕 Book Recommendation A significant portion of the performance issues I've encountered in web applications have been related to databases. It is really important to know how to identify bottlenecks and implement solutions for each type of problem. A few days ago, I finished reading this awesome book written by Andrew Brookins. The book creatively explains how to identify and solve these issues within the context of Django applications. It's definitely worth the read. Link: https://lnkd.in/e6BZKekd

Finally managed to finish this classic and wanted to share my thoughts on it: If i had this book wheh i was first starting out my career, i would've considered it a must read. Its like going back in time a bit, seeing first hand how the author disembowels legacy monster code - providing both C++ /Java code snippets examples (the monster+ the solution). I really enjoyed the chapters on slaying sticky singletons, blocking I/O static calls to databases and untested concrete hierarchies of classes. The lesson of this book for me was: as soon as you get into a brown project, start writing tests, start putting your classes into test harnesses and see how deep you have to dive into the guts of the underlying system. Once you do that you'll get a fairly good idea of the difficulty of your task On the negatives: I found the examples in this book too focused on C++ (i got an iffy feeling when a book is too focused on a single programming languge). I totally recommend this book for people that have to deal with legacy code or are not yet accustomed with the "modern approaches" (DRY, SOLID - which aren't that modern anymore anyway) or juniors just starting out. #programming #books #review

Refactoring by Martin Fowler is one of my favourite technical books. There's so much wisdom in there. I own the first edition, and it was only last week that I learnt about the second edition, published in 2019 😅 A free chapter with an example that showcases several Refactorings can be downloaded here 👇 https://lnkd.in/dY_cMHCZ Emily Bache created a repository with the code for this example, together with some tests. The code it's available in several languages: https://lnkd.in/dEBV9tzg And, since I thought it was a great idea and the example wasn't available in Ruby, I decided to contribute with a PR: https://lnkd.in/dB_zgyT3