I’ve been spending my recent free time in building an Event-Driven Backtesting Engine from scratch for Options. Backtesting complex option strategies requires processing massive amounts of market data, calculating Greeks, and tracking portfolio metrics simultaneously. To handle this without latency bottlenecks, I decided to architect the entire core engine in C++. for now I have mostly tried to make it very flexible like modular commission and slippage and ability to write custom strategies instead of editing the core engine itself I completely decoupled most of the core things so The entire C++ backend is compiled as a standalone library. I am also trying to Integrate a python bridge using pybind11 exposing this compiled library directly to Python. The goal for this is to make the engine to do all the computation in the background, allowing anyone to write, test, and plug in custom strategies dynamically using simple Python scripts without ever needing to modify the core engine files. Getting the C++ event loop to work good with Python scripting is proving to be a little complicated right now! I'll be pushing a final README and some sample strategies once I get the bindings fully stabilized. You guys can check out the code here : https://lnkd.in/gRSgd4gs #quantfinance #cpp #python #algorithmictrading #options #pybind11 #derivatives

Back to working on a local Python setup and got a quick refresher on something easy to forget My pytest coverage config (in pyproject.toml) wasn’t being picked up in VSCode. CLI? Perfect. VSCode? Different story. Everything looked right… and it was. The catch: VSCode was running pytest from a different working directory and missing the pyproject.toml configuration. Fix: // .vscode/settings.json { "python.testing.cwd": "folder_where_pyproject_is_stored" } Nothing broken — just a good reminder: Same tools, same config… context still matters. #SoftwareTesting #BackendDevelopment #CleanCode #Debugging #Productivity #Python #Pytest #DevEx #DeveloperExperience #Testing

𝐃𝐚𝐲 𝟔/𝟑𝟎: 𝐇𝐨𝐰 𝐝𝐨 𝐏𝐲𝐭𝐡𝐨𝐧 𝐝𝐞𝐯𝐬 𝐡𝐚𝐧𝐝𝐥𝐞 𝐭𝐡𝐢𝐬? 🐍 Coming from C++, I’m used to the compiler being my safety net. If I try to add a string to an int there, the code won’t even run. ➡️ But yesterday I realized Python is... a different world! def add(a, b): return a + b add(10, "5")💣 Boom! Runtime Error In a tiny script, this is a 2-second fix.. But in a massive codebase with thousands of functions? This feels like a 𝐡𝐢𝐝𝐝𝐞𝐧 𝐫𝐢𝐬𝐤 𝐰𝐚𝐢𝐭𝐢𝐧𝐠 𝐭𝐨 𝐡𝐚𝐩𝐩𝐞𝐧. So, the real question for the experts here: How do you guys stop these "sneaky" errors before they hit production? Is it: A) Just remember everything B) Test everything thoroughly (Unit tests for every single edge case) C) Use Python type hints (a: int, b: int) (👀but do they actually stop the crash?) D) Something else(MyPy? Pylint?) I’ve been digging into this 𝐜𝐥𝐚𝐬𝐡 𝐛𝐞𝐭𝐰𝐞𝐞𝐧 𝐟𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐚𝐧𝐝 𝐬𝐚𝐟𝐞𝐭𝐲 𝐭𝐨𝐝𝐚𝐲. I’m hunting for a way to make Python feel just as safe as C++. I'll share what I find tomorrow! Drop your choice below 👇 What’s the standard industry workflow for catching these? #Python #Cpp #LearningInPublic #30DaysOfCode #SoftwareEngineering #Programming

🚀 𝗗𝗮𝘆 𝟭𝟵/𝟯𝟬 – 𝟯𝟬 𝗗𝗮𝘆𝘀 𝗼𝗳 𝗣𝘆𝘁𝗵𝗼𝗻 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 Continuing my journey of building one Python project every day to improve consistency and real-world problem-solving. Today’s focus: **Networking & GUI Applications** 🧠 𝗣𝗿𝗼𝗷𝗲𝗰𝘁: 𝗜𝗻𝘁𝗲𝗿𝗻𝗲𝘁 𝗦𝗽𝗲𝗲𝗱 𝗧𝗲𝘀𝘁𝗲𝗿 Built a Python GUI application that measures internet speed (download & upload) in real-time using an interactive interface. ✨ 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀: • Measures Download Speed in Mbps • Measures Upload Speed in Mbps • Uses best server selection for accurate results • Responsive GUI using threading (no UI freeze) • Simple one-click speed testing 💡 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 𝗨𝘀𝗲𝗱: • GUI development with Tkinter • Multithreading in Python • Working with external libraries (`speedtest-cli`) • Handling network-based operations • Error handling and debugging 🔗 𝗚𝗶𝘁𝗛𝘂𝗯: https://lnkd.in/d5RX2qyT From checking it in on Internet to Building it gave a happy experience Building discipline through code — one project at a time. Follow along as I complete 30 Python projects in 30 days 🚀 #Python #BuildInPublic #DeveloperJourney #30DaysOfCode #PythonProjects #Networking #Tkinter #Automation #Coding #SystemProgramming

💻 Local vs Server: The Real Python Experience Working on Python projects locally feels easy — everything runs perfectly on your machine. But once you deploy the same code on a company server, reality hits: • Hard-coded paths or environment-specific settings break. • Dependencies installed locally may not exist on the server. • A requirements.txt file becomes mandatory to ensure all packages and versions are installed correctly. ✅ Lesson learned: Local testing is just the beginning — making your code robust, portable, and server-ready is the real challenge. #Python #SoftwareDevelopment #Deployment #ProgrammingTips

A client wanted to use LLMs for C# code generation, but LLMs tend to struggle with C# compared to Python or C — producing more syntax errors and language-specific logic mistakes. They asked if we could help close the gap. We combined long-context LLMs with a targeted retrieval system to give the model better grounding in C# conventions. The approach delivered a 5.7% accuracy improvement over zero-shot prompting. For more details, see our full post: https://lnkd.in/e3wrX2pn

VSCode workspace is a game changer! If you're writing Python codes for different versions (2.* and 3.*), then you should try the workspace in VSCode. Basically with workspace, you can define/set which CPython version to use when you click the play/run button in VSCode. This is very useful in cases where you might be trying out a logic in Python 2 and also on Python 3, or when you're migrating either upwards (from 2 to 3) or downwards (from 3 to 2), and since it's on the same IDE, the experience is really enjoyable. This also works on the same major version, so maybe you have Python 2.2 and 2.7, or 3.10 and 3.13; and it's not limited to just 2, you can have more. First time I tried it, had me smiling :) cause I work on different versions and it's not fun going to console and manually typing which python version to run on which folder --- (side note: python launcher is a great tool, but having an IDE that can support multiple versions seamlessly is just another level of ease). I really liked it, try it and see for yourself ;) #vscode #workspace #dcm #python

Day 2/30 – Building with Python Recently, I worked on a Vehicle Feedback System using Python The idea behind this project was to create a simple system where users can: 📝 Submit feedback about vehicles 📊 Store and manage responses efficiently Through this project, I learned: ✨ How to handle user input and data ✨ Basic logic building and structuring a program ✨ The importance of user-friendly systems This is just the beginning — I’m planning to improve it further by adding: OTP-based authentication for better security Database integration for scalability Possibly a simple UI for better user experience Building projects like this is helping me understand how real-world systems evolve step by step Would love your suggestions or ideas to improve this further! #Day2 #PythonProject #LearningInPublic #StudentDeveloper #BuildInPublic #TechJourney

🚨 High Risk Alert! Gramps Web API, a Python REST API for genealogical research software, has a path traversal vulnerability (CVE-2026-40258) 🕸️. An authenticated user with owner-level privileges can craft a malicious ZIP file to write arbitrary files outside the intended directory on the server's local filesystem. This highlights the importance of API security 🔒. Stay safe! #GrampsWebAPI #Python #RESTAPI #OWASP #APIsecurity https://lnkd.in/gsjivDyy

#networking abstractions: In this session we were practicing client-server architecture from different approaches. ⚪ Sockets (Transport Layer) and 🔵Flask (Application Layer). The result, understanding the multiple ways to communicate with a server, leveraging the #OSI model and moreover, creating flask apps for web development using #python. Happy #holyweek