Reddit Programming
208 subscribers
1.22K photos
123K links
I will send you newest post from subreddit /r/programming
Download Telegram
How to Classify images using Efficientnet B0
https://www.reddit.com/r/programming/comments/1m9a8m8/how_to_classify_images_using_efficientnet_b0/

<!-- SC_OFF -->Classify any image in seconds using Python and the pre-trained EfficientNetB0 model from TensorFlow. This beginner-friendly tutorial shows how to load an image, preprocess it, run predictions, and display the result using OpenCV. Great for anyone exploring image classification without building or training a custom model — no dataset needed! You can find link for the code in the blog : https://eranfeit.net/how-to-classify-images-using-efficientnet-b0/ You can find more tutorials, and join my newsletter here : https://eranfeit.net/ Full code for Medium users : https://medium.com/@feitgemel/how-to-classify-images-using-efficientnet-b0-738f48665583 Watch the full tutorial here: https://youtu.be/lomMTiG9UZ4 Enjoy Eran <!-- SC_ON --> submitted by /u/Feitgemel (https://www.reddit.com/user/Feitgemel)
[link] (https://eranfeit.net/how-to-classify-images-using-efficientnet-b0/) [comments] (https://www.reddit.com/r/programming/comments/1m9a8m8/how_to_classify_images_using_efficientnet_b0/)
Testivus on Test Coverage
https://www.reddit.com/r/programming/comments/1m9kxaa/testivus_on_test_coverage/

<!-- SC_OFF -->Came across this today and thought it was worth sharing. <!-- SC_ON --> submitted by /u/Original-Character57 (https://www.reddit.com/user/Original-Character57)
[link] (https://stackoverflow.com/a/90021) [comments] (https://www.reddit.com/r/programming/comments/1m9kxaa/testivus_on_test_coverage/)
The Case for Being Lazy
https://www.reddit.com/r/programming/comments/1m9log0/the_case_for_being_lazy/

<!-- SC_OFF -->I have always thought that being lazy enough to work hard was a completely unervalued skill <!-- SC_ON --> submitted by /u/WifeEyedFascination (https://www.reddit.com/user/WifeEyedFascination)
[link] (https://osada.blog/posts/the-case-for-being-lazy/) [comments] (https://www.reddit.com/r/programming/comments/1m9log0/the_case_for_being_lazy/)
"Individual programmers do not own the software they write"
https://www.reddit.com/r/programming/comments/1m9qy4w/individual_programmers_do_not_own_the_software/

<!-- SC_OFF -->On "Embedded C Coding Standard" by Michael Barr the first Guiding principle is: Individual programmers do not own the software they write. All software development is work for hire for an employer or a client and, thus, the end product should be constructed in a workmanlike manner. Could you comment why this was added as a guiding principle and what that could mean? I was trying to look back on my past work context and try find a situation that this principle was missed by anyone. Is this one of those cases where a developer can just do whatever they want with the company's code?
Has anything like that actually happened at your workplace where someone ignored this principle (and whatever may be in the work contract)? <!-- SC_ON --> submitted by /u/CancelProof6072 (https://www.reddit.com/user/CancelProof6072)
[link] (https://barrgroup.com/sites/default/files/barr_c_coding_standard_2018.pdf) [comments] (https://www.reddit.com/r/programming/comments/1m9qy4w/individual_programmers_do_not_own_the_software/)
Opening Chrome: A High Level View of CS Concepts
https://www.reddit.com/r/programming/comments/1ma0y80/opening_chrome_a_high_level_view_of_cs_concepts/

<!-- SC_OFF -->One click is all it takes, falling in love with computer systems. <!-- SC_ON --> submitted by /u/Competitive-Hunt-276 (https://www.reddit.com/user/Competitive-Hunt-276)
[link] (https://harsh-doshii.github.io/posts/127-post/) [comments] (https://www.reddit.com/r/programming/comments/1ma0y80/opening_chrome_a_high_level_view_of_cs_concepts/)
I’m a front end developer and I think AI will take my job(if it hasn’t already).
https://www.reddit.com/r/programming/comments/1mahsch/im_a_front_end_developer_and_i_think_ai_will_take/

<!-- SC_OFF -->So recently I have been using ai tools like Claude for my coding work and oh my gods.. It’s crazy good. I don’t know where to start. I have always been a front end girl, even though I have a little backend knowledge but after seeing how good it is I think it’s probably going to happen. What do guys? Yo and why the hell does this sub require a link for ever my post? <!-- SC_ON --> submitted by /u/blvckgirl (https://www.reddit.com/user/blvckgirl)
[link] (https://claude.ai/login?returnTo=%2F%3F) [comments] (https://www.reddit.com/r/programming/comments/1mahsch/im_a_front_end_developer_and_i_think_ai_will_take/)
findpath - give it just the filename and it’ll hand you the absolute path
https://www.reddit.com/r/programming/comments/1mahtup/findpath_give_it_just_the_filename_and_itll_hand/

<!-- SC_OFF -->Hey r/programming 👋 I hacked together a tiny helper called findpath whose entire pitch is: you only need to remember the name of the file. Point it at a logical “root”, tell it the filename, and it’ll walk everything under that root and return the single absolute path that matches—otherwise it raises clear, typed exceptions (file not found / more than one match / root not set, etc.). PyPI: https://pypi.org/project/findpath/ GitHub: https://github.com/joshikarthikey/findpath Why bother? 🔎 Zero mental overhead – stop remembering long nested directories; remember just settings.yaml. 🧯 Clear failure modes – you’ll know if the file doesn’t exist or exists more than once. 🧰 No third‑party deps – pure stdlib (os). 🧪 Easy to unit test – deterministic, small surface area. 🧱 Works anywhere – POSIX/Windows (relies on os, not shell tricks). Attributes (all exposed as properties with sanity checks) root: (required) folder name that marks the boundary you’ll search under (e.g., "my_project"). root_path: absolute path of that root folder once discovered. all_paths: list of every file path under root_path found during the scan. file: the file name you’re currently searching for. your_path: the final resolved absolute path to the single matching file. current_dir: the working directory when the object is created (captured via os.getcwd()). Methods find(desired_file: str) -> str Main entrypoint. Walks up from current_dir until it hits root, then recursively scans down. Returns the absolute path if there’s exactly one match, else raises. find_all_paths(root_path: str) -> list[str] Recursively collects all file paths below root_path. Used internally by find, but you can call it yourself if you want the raw list. Looking for collaborators I’m still pretty new to Python packaging and open-source contributions, so this project is as much a learning experienceas it is a useful tool. If you’re an experienced Python dev, I’d love your feedback or help making this more “production-ready.” Things I’d especially appreciate help with: Making the code more Pythonic (e.g., better use of pathlib). Adding tests and CI workflows. Improving error handling with custom exceptions. Documentation improvements (I’m still figuring out best practices). Designing a simple CLI tool. <!-- SC_ON --> submitted by /u/karthikeyjoshi (https://www.reddit.com/user/karthikeyjoshi)
[link] (https://pypi.org/project/findpath/) [comments] (https://www.reddit.com/r/programming/comments/1mahtup/findpath_give_it_just_the_filename_and_itll_hand/)
Ivory: Streamlining PostgreSQL Cluster Management for Devs and DBAs
https://www.reddit.com/r/programming/comments/1makioc/ivory_streamlining_postgresql_cluster_management/

<!-- SC_OFF -->Ivory: Streamlining PostgreSQL Cluster Management for Devs and DBAs If you're managing PostgreSQL clusters, especially with Patroni for high-availability (HA), you know the pain of juggling complex CLI commands and APIs. Enter Ivory, an open-source PostgreSQL management tool designed to simplify and visualize cluster management. Here's a quick dive into why Ivory might be your next go-to for PostgreSQL administration, perfect for sharing with the Reddit community! What is Ivory? Ivory is a user-friendly, open-source tool built to make managing PostgreSQL clusters—particularly those using Patroni—more intuitive. It provides a centralized interface to monitor, troubleshoot, and optimize your PostgreSQL HA setups, saving you from endless command-line gymnastics. Whether you're a developer or a DBA, Ivory aims to streamline your workflow with a focus on usability and security. Note: Don’t confuse Ivory with IvorySQL, a different project focused on Oracle-compatible PostgreSQL. This article is all about the management tool! Key Features That Shine Patroni Management Made Easy Ivory wraps Patroni’s complex CLI and API into a clean UI. Need to perform a switchover, failover, restart, or reinitialization? It’s just a few clicks away. You get a dashboard showing all your Patroni clusters, their statuses, and any warnings, with tagging support to keep things organized. Query Builder for Quick Troubleshooting Tired of writing repetitive SQL queries? Ivory’s query builder simplifies running specific PostgreSQL queries for troubleshooting and maintenance, saving time and reducing errors. Multi-Cluster Management Manage multiple PostgreSQL clusters across different locations from one interface. No more copy-pasting commands between clusters—Ivory handles it all in one place. Security First Authentication: Optional Basic authentication (username/password) for VM deployments, with LDAP/SSO support planned. Mutual TLS: Ivory supports secure PostgreSQL connections with mutual TLS (set your PostgreSQL user to verify-ca mode). Certificate Management: Add and reuse certificates for Patroni, making secure requests a breeze. Bloat Cleanup Ivory integrates with pgcompacttable to tackle table bloat, helping keep your database performance in check. Metrics and Dashboards Get simple charts for instance metrics, with future plans to integrate with Grafana for advanced dashboarding. It’s a great way to keep an eye on your clusters’ health. Flexible Deployment Run Ivory locally on your machine or deploy it on a VM for team collaboration. It supports Docker with environment variables like IVORY_URL_PATH for reverse proxies and IVORY_CERT_FILE_PATH for TLS certificates (auto-switches to port 443 when configured). Why You’ll Love It Saves Time: No more digging through Patroni docs or memorizing commands. Ivory’s UI makes cluster management fast and intuitive. Centralized Control: Monitor and manage all your clusters from one place, even across different environments. Community-Driven: As an open-source project, Ivory welcomes contributions. Got an idea for a new feature, like support for other failover tools? Jump into the discussion on GitHub! Getting Started Ivory is easy to set up via Docker. Check the GitHub repo (https://github.com/veegres/ivory) for installation instructions. Be mindful that major/minor releases may not be backward-compatible, so install from scratch for big updates. Patch releases are safer, focusing on bug fixes and minor tweaks. For secure setups, configure TLS certificates and environment variables as needed. If you’re running locally, you can skip authentication for simplicity. What’s Next for Ivory? The roadmap includes: PostgreSQL TLS connection support. Integration with other failover tools (based on community demand). Import/export
functionality for smoother upgrades. Grafana integration for richer metrics. Join the Conversation Ivory is a game-changer for PostgreSQL HA management, but it’s still evolving. Have you tried it? Got tips, tricks, or feature requests? Share your thoughts in the comments! If you’re curious about specific use cases or need help with setup, check out Andrei Sergeev’s Medium posts (https://anselvo.medium.com/) or the GitHub repo for more details. Let’s talk about how Ivory’s making your PostgreSQL life easier—or what you’d love to see added to it! 🚀 <!-- SC_ON --> submitted by /u/aelsergeev (https://www.reddit.com/user/aelsergeev)
[link] (https://github.com/veegres/ivory) [comments] (https://www.reddit.com/r/programming/comments/1makioc/ivory_streamlining_postgresql_cluster_management/)