Finding & Fixing Missing Indexes in Under 10 Minutes
https://www.reddit.com/r/programming/comments/1m9w67v/finding_fixing_missing_indexes_in_under_10_minutes/
<!-- SC_OFF -->https://medium.com/@rohansodha10/finding-fixing-missing-indexes-in-under-10-minutes-891dd1289800?sk=5c94e0b05df6342ce94bca4f24fe3ea0 <!-- SC_ON --> submitted by /u/Temporary_Depth_2491 (https://www.reddit.com/user/Temporary_Depth_2491)
[link] (https://medium.com/@rohansodha10/finding-fixing-missing-indexes-in-under-10-minutes-891dd1289800?sk=5c94e0b05df6342ce94bca4f24fe3ea0) [comments] (https://www.reddit.com/r/programming/comments/1m9w67v/finding_fixing_missing_indexes_in_under_10_minutes/)
https://www.reddit.com/r/programming/comments/1m9w67v/finding_fixing_missing_indexes_in_under_10_minutes/
<!-- SC_OFF -->https://medium.com/@rohansodha10/finding-fixing-missing-indexes-in-under-10-minutes-891dd1289800?sk=5c94e0b05df6342ce94bca4f24fe3ea0 <!-- SC_ON --> submitted by /u/Temporary_Depth_2491 (https://www.reddit.com/user/Temporary_Depth_2491)
[link] (https://medium.com/@rohansodha10/finding-fixing-missing-indexes-in-under-10-minutes-891dd1289800?sk=5c94e0b05df6342ce94bca4f24fe3ea0) [comments] (https://www.reddit.com/r/programming/comments/1m9w67v/finding_fixing_missing_indexes_in_under_10_minutes/)
Write “freehold” software
https://www.reddit.com/r/programming/comments/1m9zrem/write_freehold_software/
submitted by /u/LlaroLlethri (https://www.reddit.com/user/LlaroLlethri)
[link] (https://deadbeef.io/freehold_software) [comments] (https://www.reddit.com/r/programming/comments/1m9zrem/write_freehold_software/)
https://www.reddit.com/r/programming/comments/1m9zrem/write_freehold_software/
submitted by /u/LlaroLlethri (https://www.reddit.com/user/LlaroLlethri)
[link] (https://deadbeef.io/freehold_software) [comments] (https://www.reddit.com/r/programming/comments/1m9zrem/write_freehold_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/)
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/)
Machine Learning para Desarrolladores Web
https://www.reddit.com/r/programming/comments/1ma1ikc/machine_learning_para_desarrolladores_web/
submitted by /u/Israelsarmiento5 (https://www.reddit.com/user/Israelsarmiento5)
[link] (https://www.hgaruna.org/blog/machine-learning-par.html) [comments] (https://www.reddit.com/r/programming/comments/1ma1ikc/machine_learning_para_desarrolladores_web/)
https://www.reddit.com/r/programming/comments/1ma1ikc/machine_learning_para_desarrolladores_web/
submitted by /u/Israelsarmiento5 (https://www.reddit.com/user/Israelsarmiento5)
[link] (https://www.hgaruna.org/blog/machine-learning-par.html) [comments] (https://www.reddit.com/r/programming/comments/1ma1ikc/machine_learning_para_desarrolladores_web/)
GraphQL vs REST: Cuándo usar cada uno
https://www.reddit.com/r/programming/comments/1ma1ik5/graphql_vs_rest_cu%C3%A1ndo_usar_cada_uno/
submitted by /u/Israelsarmiento5 (https://www.reddit.com/user/Israelsarmiento5)
[link] (https://www.hgaruna.org/blog/graphql-vs-rest-cund.html) [comments] (https://www.reddit.com/r/programming/comments/1ma1ik5/graphql_vs_rest_cu%C3%A1ndo_usar_cada_uno/)
https://www.reddit.com/r/programming/comments/1ma1ik5/graphql_vs_rest_cu%C3%A1ndo_usar_cada_uno/
submitted by /u/Israelsarmiento5 (https://www.reddit.com/user/Israelsarmiento5)
[link] (https://www.hgaruna.org/blog/graphql-vs-rest-cund.html) [comments] (https://www.reddit.com/r/programming/comments/1ma1ik5/graphql_vs_rest_cu%C3%A1ndo_usar_cada_uno/)
Most Unit Tests Are a Waste of Time, but You Need to Write Them Anyway
https://www.reddit.com/r/programming/comments/1ma1oir/most_unit_tests_are_a_waste_of_time_but_you_need/
submitted by /u/bizzehdee (https://www.reddit.com/user/bizzehdee)
[link] (https://www.darrenhorrocks.co.uk/most-unit-tests-are-waste-time-but-you-need-to-write-them-anyway/) [comments] (https://www.reddit.com/r/programming/comments/1ma1oir/most_unit_tests_are_a_waste_of_time_but_you_need/)
https://www.reddit.com/r/programming/comments/1ma1oir/most_unit_tests_are_a_waste_of_time_but_you_need/
submitted by /u/bizzehdee (https://www.reddit.com/user/bizzehdee)
[link] (https://www.darrenhorrocks.co.uk/most-unit-tests-are-waste-time-but-you-need-to-write-them-anyway/) [comments] (https://www.reddit.com/r/programming/comments/1ma1oir/most_unit_tests_are_a_waste_of_time_but_you_need/)
Introducción
https://www.reddit.com/r/programming/comments/1mahr3a/introducci%C3%B3n/
submitted by /u/Israelsarmiento5 (https://www.reddit.com/user/Israelsarmiento5)
[link] (https://www.hgaruna.org/blog/microservices-arquitectura-distribuida.html) [comments] (https://www.reddit.com/r/programming/comments/1mahr3a/introducci%C3%B3n/)
https://www.reddit.com/r/programming/comments/1mahr3a/introducci%C3%B3n/
submitted by /u/Israelsarmiento5 (https://www.reddit.com/user/Israelsarmiento5)
[link] (https://www.hgaruna.org/blog/microservices-arquitectura-distribuida.html) [comments] (https://www.reddit.com/r/programming/comments/1mahr3a/introducci%C3%B3n/)
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/)
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/)
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/)
Help 😭
https://www.reddit.com/r/programming/comments/1mahze6/help/
<!-- SC_OFF -->Please someone help with an alternative. <!-- SC_ON --> submitted by /u/Wild_Peace6443 (https://www.reddit.com/user/Wild_Peace6443)
[link] (https://www.reddit.com/r/Btechtards/comments/1mahy76/please_someone_help/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button) [comments] (https://www.reddit.com/r/programming/comments/1mahze6/help/)
https://www.reddit.com/r/programming/comments/1mahze6/help/
<!-- SC_OFF -->Please someone help with an alternative. <!-- SC_ON --> submitted by /u/Wild_Peace6443 (https://www.reddit.com/user/Wild_Peace6443)
[link] (https://www.reddit.com/r/Btechtards/comments/1mahy76/please_someone_help/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button) [comments] (https://www.reddit.com/r/programming/comments/1mahze6/help/)
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
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/)
[link] (https://github.com/veegres/ivory) [comments] (https://www.reddit.com/r/programming/comments/1makioc/ivory_streamlining_postgresql_cluster_management/)
HDR & Bloom / Post-Processing tech demonstration on real Nintendo 64
https://www.reddit.com/r/programming/comments/1makmqs/hdr_bloom_postprocessing_tech_demonstration_on/
submitted by /u/r_retrohacking_mod2 (https://www.reddit.com/user/r_retrohacking_mod2)
[link] (https://m.youtube.com/watch?v=XP8g2ngHftY) [comments] (https://www.reddit.com/r/programming/comments/1makmqs/hdr_bloom_postprocessing_tech_demonstration_on/)
https://www.reddit.com/r/programming/comments/1makmqs/hdr_bloom_postprocessing_tech_demonstration_on/
submitted by /u/r_retrohacking_mod2 (https://www.reddit.com/user/r_retrohacking_mod2)
[link] (https://m.youtube.com/watch?v=XP8g2ngHftY) [comments] (https://www.reddit.com/r/programming/comments/1makmqs/hdr_bloom_postprocessing_tech_demonstration_on/)
Become an Engineering Leader Everyone Wants to Work With
https://www.reddit.com/r/programming/comments/1mapgly/become_an_engineering_leader_everyone_wants_to/
submitted by /u/gregorojstersek (https://www.reddit.com/user/gregorojstersek)
[link] (https://www.youtube.com/watch?v=58TAuoEFC7g) [comments] (https://www.reddit.com/r/programming/comments/1mapgly/become_an_engineering_leader_everyone_wants_to/)
https://www.reddit.com/r/programming/comments/1mapgly/become_an_engineering_leader_everyone_wants_to/
submitted by /u/gregorojstersek (https://www.reddit.com/user/gregorojstersek)
[link] (https://www.youtube.com/watch?v=58TAuoEFC7g) [comments] (https://www.reddit.com/r/programming/comments/1mapgly/become_an_engineering_leader_everyone_wants_to/)
How to Make AI Agents Collaborate with ACP (Agent Communication Protocol)
https://www.reddit.com/r/programming/comments/1maphoz/how_to_make_ai_agents_collaborate_with_acp_agent/
submitted by /u/Flashy-Thought-5472 (https://www.reddit.com/user/Flashy-Thought-5472)
[link] (https://www.youtube.com/watch?v=fABcNHKVqYM&list=PLp01ObP3udmq2quR-RfrX4zNut_t_kNot&index=24) [comments] (https://www.reddit.com/r/programming/comments/1maphoz/how_to_make_ai_agents_collaborate_with_acp_agent/)
https://www.reddit.com/r/programming/comments/1maphoz/how_to_make_ai_agents_collaborate_with_acp_agent/
submitted by /u/Flashy-Thought-5472 (https://www.reddit.com/user/Flashy-Thought-5472)
[link] (https://www.youtube.com/watch?v=fABcNHKVqYM&list=PLp01ObP3udmq2quR-RfrX4zNut_t_kNot&index=24) [comments] (https://www.reddit.com/r/programming/comments/1maphoz/how_to_make_ai_agents_collaborate_with_acp_agent/)
Autovacuum Tuning: Stop Table Bloat Before It Hurts
https://www.reddit.com/r/programming/comments/1maqe0l/autovacuum_tuning_stop_table_bloat_before_it_hurts/
<!-- SC_OFF -->https://medium.com/@rohansodha10/autovacuum-tuning-stop-table-bloat-before-it-hurts-0e39510d0804?sk=57defbd7f909a121b958ea4a536c7f81 <!-- SC_ON --> submitted by /u/Temporary_Depth_2491 (https://www.reddit.com/user/Temporary_Depth_2491)
[link] (https://medium.com/@rohansodha10/autovacuum-tuning-stop-table-bloat-before-it-hurts-0e39510d0804?sk=57defbd7f909a121b958ea4a536c7f81) [comments] (https://www.reddit.com/r/programming/comments/1maqe0l/autovacuum_tuning_stop_table_bloat_before_it_hurts/)
https://www.reddit.com/r/programming/comments/1maqe0l/autovacuum_tuning_stop_table_bloat_before_it_hurts/
<!-- SC_OFF -->https://medium.com/@rohansodha10/autovacuum-tuning-stop-table-bloat-before-it-hurts-0e39510d0804?sk=57defbd7f909a121b958ea4a536c7f81 <!-- SC_ON --> submitted by /u/Temporary_Depth_2491 (https://www.reddit.com/user/Temporary_Depth_2491)
[link] (https://medium.com/@rohansodha10/autovacuum-tuning-stop-table-bloat-before-it-hurts-0e39510d0804?sk=57defbd7f909a121b958ea4a536c7f81) [comments] (https://www.reddit.com/r/programming/comments/1maqe0l/autovacuum_tuning_stop_table_bloat_before_it_hurts/)
asyncio: a library with too many sharp corners
https://www.reddit.com/r/programming/comments/1maqxdp/asyncio_a_library_with_too_many_sharp_corners/
submitted by /u/pkkm (https://www.reddit.com/user/pkkm)
[link] (https://sailor.li/asyncio) [comments] (https://www.reddit.com/r/programming/comments/1maqxdp/asyncio_a_library_with_too_many_sharp_corners/)
https://www.reddit.com/r/programming/comments/1maqxdp/asyncio_a_library_with_too_many_sharp_corners/
submitted by /u/pkkm (https://www.reddit.com/user/pkkm)
[link] (https://sailor.li/asyncio) [comments] (https://www.reddit.com/r/programming/comments/1maqxdp/asyncio_a_library_with_too_many_sharp_corners/)
Learn SOLID principles: Single Responsibility Principle
https://www.reddit.com/r/programming/comments/1mas8pw/learn_solid_principles_single_responsibility/
<!-- SC_OFF -->Writing clean code is a must for any developer who wants their work to shine. It’s not just about getting your program to run; it’s about making code that’s easy to read, test, and update. One of the best ways to do this is by following the Single Responsibility Principle (SRP), the first of the SOLID principles. <!-- SC_ON --> submitted by /u/abhijith1203 (https://www.reddit.com/user/abhijith1203)
[link] (https://abhijithpurohit.medium.com/write-better-c-code-with-the-single-responsibility-principle-080c6d252964) [comments] (https://www.reddit.com/r/programming/comments/1mas8pw/learn_solid_principles_single_responsibility/)
https://www.reddit.com/r/programming/comments/1mas8pw/learn_solid_principles_single_responsibility/
<!-- SC_OFF -->Writing clean code is a must for any developer who wants their work to shine. It’s not just about getting your program to run; it’s about making code that’s easy to read, test, and update. One of the best ways to do this is by following the Single Responsibility Principle (SRP), the first of the SOLID principles. <!-- SC_ON --> submitted by /u/abhijith1203 (https://www.reddit.com/user/abhijith1203)
[link] (https://abhijithpurohit.medium.com/write-better-c-code-with-the-single-responsibility-principle-080c6d252964) [comments] (https://www.reddit.com/r/programming/comments/1mas8pw/learn_solid_principles_single_responsibility/)
How Spotify Saved $18M With Smart Compression (And Why Most Teams Get It Wrong)
https://www.reddit.com/r/programming/comments/1masbln/how_spotify_saved_18m_with_smart_compression_and/
<!-- SC_OFF -->TL;DR: Compression isn't just "make files smaller" - it's architectural strategy that can save millions or crash your site during Black Friday. The Eye-Opening Discovery: Spotify found that 40% of their bandwidth costs came from uncompressed metadata synchronization. Not the music files users actually wanted - the invisible data that keeps everything working. What Most Teams Do Wrong: Engineer: "Let's enable maximum compression on everything!" *Enables Brotli level 11 on all endpoints* *Black Friday traffic hits* *Site dies from CPU overload* *$2M in lost sales* This actually happened to an e-commerce company. Classic optimization-turned-incident. What The Giants Do Instead: Netflix's Multi-Layer Strategy: Video: H.264/H.265 (content-specific codecs) Metadata: Brotli (max compression for small data) APIs: ZSTD (balanced for real-time) Result: 40% bandwidth saved, zero performance impact Google's Context-Aware Approach: Search index: Custom algorithms achieving 8:1 ratios Live results: Hardware-accelerated gzip Memory cache: LZ4 for density without speed loss Handles 8.5 billion daily queries under 100ms Amazon's Intelligent Tiering: Hot data: Uncompressed (speed priority) Warm data: Standard compression (balanced) Cold data: Maximum compression (cost priority) Auto-migration based on access patterns The Framework That Actually Works: Start Conservative: ZSTD level 3 everywhere Measure Everything: CPU, memory, response times Adapt Conditions: High CPU → LZ4, Slow network → Brotli Layer Strategy: Different algorithms for CDN vs API vs Storage Key Insight That Changed My Thinking: Compression decisions should be made at the layer where you have the most context about data usage patterns. Mobile users might get aggressive compression to save bandwidth, desktop users get speed-optimized algorithms. Quick Wins You Can Implement Today: Enable gzip on web assets (1-day task, 20-30% immediate savings) Compress API responses over 1KB Use LZ4 for log shipping Don't compress already-compressed files (seems obvious but...) The Math That Matters: Good compression: Less data = Lower costs + Faster transfer + Better UX Bad compression: CPU overload = Slower responses + Higher costs + Incidents Questions for Discussion: What compression disasters have you seen in production? Anyone using adaptive compression based on system conditions? How do you monitor compression effectiveness in your stack? The difference between teams that save millions and teams that create incidents often comes down to treating compression as an architectural decision rather than a configuration flag. Source: This analysis comes from the systemdr newsletter where we break down distributed systems patterns from companies handling billions of requests. <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://systemdr.substack.com/p/data-compression-techniques-for-scaling) [comments] (https://www.reddit.com/r/programming/comments/1masbln/how_spotify_saved_18m_with_smart_compression_and/)
https://www.reddit.com/r/programming/comments/1masbln/how_spotify_saved_18m_with_smart_compression_and/
<!-- SC_OFF -->TL;DR: Compression isn't just "make files smaller" - it's architectural strategy that can save millions or crash your site during Black Friday. The Eye-Opening Discovery: Spotify found that 40% of their bandwidth costs came from uncompressed metadata synchronization. Not the music files users actually wanted - the invisible data that keeps everything working. What Most Teams Do Wrong: Engineer: "Let's enable maximum compression on everything!" *Enables Brotli level 11 on all endpoints* *Black Friday traffic hits* *Site dies from CPU overload* *$2M in lost sales* This actually happened to an e-commerce company. Classic optimization-turned-incident. What The Giants Do Instead: Netflix's Multi-Layer Strategy: Video: H.264/H.265 (content-specific codecs) Metadata: Brotli (max compression for small data) APIs: ZSTD (balanced for real-time) Result: 40% bandwidth saved, zero performance impact Google's Context-Aware Approach: Search index: Custom algorithms achieving 8:1 ratios Live results: Hardware-accelerated gzip Memory cache: LZ4 for density without speed loss Handles 8.5 billion daily queries under 100ms Amazon's Intelligent Tiering: Hot data: Uncompressed (speed priority) Warm data: Standard compression (balanced) Cold data: Maximum compression (cost priority) Auto-migration based on access patterns The Framework That Actually Works: Start Conservative: ZSTD level 3 everywhere Measure Everything: CPU, memory, response times Adapt Conditions: High CPU → LZ4, Slow network → Brotli Layer Strategy: Different algorithms for CDN vs API vs Storage Key Insight That Changed My Thinking: Compression decisions should be made at the layer where you have the most context about data usage patterns. Mobile users might get aggressive compression to save bandwidth, desktop users get speed-optimized algorithms. Quick Wins You Can Implement Today: Enable gzip on web assets (1-day task, 20-30% immediate savings) Compress API responses over 1KB Use LZ4 for log shipping Don't compress already-compressed files (seems obvious but...) The Math That Matters: Good compression: Less data = Lower costs + Faster transfer + Better UX Bad compression: CPU overload = Slower responses + Higher costs + Incidents Questions for Discussion: What compression disasters have you seen in production? Anyone using adaptive compression based on system conditions? How do you monitor compression effectiveness in your stack? The difference between teams that save millions and teams that create incidents often comes down to treating compression as an architectural decision rather than a configuration flag. Source: This analysis comes from the systemdr newsletter where we break down distributed systems patterns from companies handling billions of requests. <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://systemdr.substack.com/p/data-compression-techniques-for-scaling) [comments] (https://www.reddit.com/r/programming/comments/1masbln/how_spotify_saved_18m_with_smart_compression_and/)
Inheritance vs. Composition
https://www.reddit.com/r/programming/comments/1matz74/inheritance_vs_composition/
submitted by /u/bowbahdoe (https://www.reddit.com/user/bowbahdoe)
[link] (https://mccue.dev/pages/7-27-25-inheritance-vs-composition) [comments] (https://www.reddit.com/r/programming/comments/1matz74/inheritance_vs_composition/)
https://www.reddit.com/r/programming/comments/1matz74/inheritance_vs_composition/
submitted by /u/bowbahdoe (https://www.reddit.com/user/bowbahdoe)
[link] (https://mccue.dev/pages/7-27-25-inheritance-vs-composition) [comments] (https://www.reddit.com/r/programming/comments/1matz74/inheritance_vs_composition/)
Engineering With Java: Digest #57
https://www.reddit.com/r/programming/comments/1mavu0o/engineering_with_java_digest_57/
<!-- SC_OFF -->𝐓𝐡𝐞 𝐥𝐚𝐭𝐞𝐬𝐭 𝐞𝐝𝐢𝐭𝐢𝐨𝐧 𝐨𝐟 𝐭𝐡𝐞 𝐉𝐚𝐯𝐚 𝐧𝐞𝐰𝐬𝐥𝐞𝐭𝐭𝐞𝐫 𝐢𝐬 𝐨𝐮𝐭! 𝐓𝐡𝐢𝐬 𝐰𝐞𝐞𝐤'𝐬 𝐜𝐨𝐥𝐥𝐞𝐜𝐭𝐢𝐨𝐧 𝐢𝐧𝐜𝐥𝐮𝐝𝐞𝐬: > Self-Healing Microservices: Implementing Health Checks with Spring Boot and Kubernetes > JEP targeted to JDK 25: 520: JFR Method Timing & Tracing > Agent Memory with Spring AI & Redis > A Sneak Peek at the Stable Values API > Java 22 to 24: Level up your Java Code by embracing new features in a safe way > Spring Cloud Stream: Event-Driven Architecture – Part 1 > Undocumented Java 16 Feature: The End-of-File Comment > Service Mesh in Java: Istio and Linkerd Integration for Secure Microservices 𝐂𝐡𝐞𝐜𝐤 𝐨𝐮𝐭 𝐭𝐡𝐞 𝐧𝐞𝐰𝐬𝐥𝐞𝐭𝐭𝐞𝐫 𝐚𝐧𝐝 𝐬𝐮𝐛𝐬𝐜𝐫𝐢𝐛𝐞 𝐟𝐨𝐫 𝐰𝐞𝐞𝐤𝐥𝐲 𝐮𝐩𝐝𝐚𝐭𝐞𝐬: https://javabulletin.substack.com/p/engineering-with-java-digest-57 #java #spring #newsletter #springboot <!-- SC_ON --> submitted by /u/Educational-Ad2036 (https://www.reddit.com/user/Educational-Ad2036)
[link] (https://javabulletin.substack.com/p/engineering-with-java-digest-57) [comments] (https://www.reddit.com/r/programming/comments/1mavu0o/engineering_with_java_digest_57/)
https://www.reddit.com/r/programming/comments/1mavu0o/engineering_with_java_digest_57/
<!-- SC_OFF -->𝐓𝐡𝐞 𝐥𝐚𝐭𝐞𝐬𝐭 𝐞𝐝𝐢𝐭𝐢𝐨𝐧 𝐨𝐟 𝐭𝐡𝐞 𝐉𝐚𝐯𝐚 𝐧𝐞𝐰𝐬𝐥𝐞𝐭𝐭𝐞𝐫 𝐢𝐬 𝐨𝐮𝐭! 𝐓𝐡𝐢𝐬 𝐰𝐞𝐞𝐤'𝐬 𝐜𝐨𝐥𝐥𝐞𝐜𝐭𝐢𝐨𝐧 𝐢𝐧𝐜𝐥𝐮𝐝𝐞𝐬: > Self-Healing Microservices: Implementing Health Checks with Spring Boot and Kubernetes > JEP targeted to JDK 25: 520: JFR Method Timing & Tracing > Agent Memory with Spring AI & Redis > A Sneak Peek at the Stable Values API > Java 22 to 24: Level up your Java Code by embracing new features in a safe way > Spring Cloud Stream: Event-Driven Architecture – Part 1 > Undocumented Java 16 Feature: The End-of-File Comment > Service Mesh in Java: Istio and Linkerd Integration for Secure Microservices 𝐂𝐡𝐞𝐜𝐤 𝐨𝐮𝐭 𝐭𝐡𝐞 𝐧𝐞𝐰𝐬𝐥𝐞𝐭𝐭𝐞𝐫 𝐚𝐧𝐝 𝐬𝐮𝐛𝐬𝐜𝐫𝐢𝐛𝐞 𝐟𝐨𝐫 𝐰𝐞𝐞𝐤𝐥𝐲 𝐮𝐩𝐝𝐚𝐭𝐞𝐬: https://javabulletin.substack.com/p/engineering-with-java-digest-57 #java #spring #newsletter #springboot <!-- SC_ON --> submitted by /u/Educational-Ad2036 (https://www.reddit.com/user/Educational-Ad2036)
[link] (https://javabulletin.substack.com/p/engineering-with-java-digest-57) [comments] (https://www.reddit.com/r/programming/comments/1mavu0o/engineering_with_java_digest_57/)