Malleable software: Restoring user agency in a world of locked-down apps
https://www.reddit.com/r/programming/comments/1q2kz3k/malleable_software_restoring_user_agency_in_a/
submitted by /u/misterolupo (https://www.reddit.com/user/misterolupo)
[link] (https://www.inkandswitch.com/essay/malleable-software/) [comments] (https://www.reddit.com/r/programming/comments/1q2kz3k/malleable_software_restoring_user_agency_in_a/)
https://www.reddit.com/r/programming/comments/1q2kz3k/malleable_software_restoring_user_agency_in_a/
submitted by /u/misterolupo (https://www.reddit.com/user/misterolupo)
[link] (https://www.inkandswitch.com/essay/malleable-software/) [comments] (https://www.reddit.com/r/programming/comments/1q2kz3k/malleable_software_restoring_user_agency_in_a/)
How Uber Shows Millions of Drivers Location In Realtime
https://www.reddit.com/r/programming/comments/1q2o00b/how_uber_shows_millions_of_drivers_location_in/
submitted by /u/Sushant098123 (https://www.reddit.com/user/Sushant098123)
[link] (https://sushantdhiman.substack.com/p/how-uber-shows-millions-of-drivers) [comments] (https://www.reddit.com/r/programming/comments/1q2o00b/how_uber_shows_millions_of_drivers_location_in/)
https://www.reddit.com/r/programming/comments/1q2o00b/how_uber_shows_millions_of_drivers_location_in/
submitted by /u/Sushant098123 (https://www.reddit.com/user/Sushant098123)
[link] (https://sushantdhiman.substack.com/p/how-uber-shows-millions-of-drivers) [comments] (https://www.reddit.com/r/programming/comments/1q2o00b/how_uber_shows_millions_of_drivers_location_in/)
Research found indentation depth correlates with cyclomatic complexity. A language-agnostic approach to measuring code complexity
https://www.reddit.com/r/programming/comments/1q2q1ib/research_found_indentation_depth_correlates_with/
submitted by /u/itaymendi (https://www.reddit.com/user/itaymendi)
[link] (https://softwareprocess.es/static/WhiteSpace.html) [comments] (https://www.reddit.com/r/programming/comments/1q2q1ib/research_found_indentation_depth_correlates_with/)
https://www.reddit.com/r/programming/comments/1q2q1ib/research_found_indentation_depth_correlates_with/
submitted by /u/itaymendi (https://www.reddit.com/user/itaymendi)
[link] (https://softwareprocess.es/static/WhiteSpace.html) [comments] (https://www.reddit.com/r/programming/comments/1q2q1ib/research_found_indentation_depth_correlates_with/)
Why Developer Expertise Matters More Than Ever in the Age of AI
https://www.reddit.com/r/programming/comments/1q2qa5m/why_developer_expertise_matters_more_than_ever_in/
<!-- SC_OFF -->Read “Why Developer Expertise Matters More Than Ever in the Age of AI“ <!-- SC_ON --> submitted by /u/iammidhul (https://www.reddit.com/user/iammidhul)
[link] (https://medium.com/understanding-javanoscript-developwithmi/why-developer-expertise-matters-more-than-ever-in-the-age-of-ai-a45a93ffc14f?sk=046291f3b71ef1fc8dbeaa5c1f96e6c7) [comments] (https://www.reddit.com/r/programming/comments/1q2qa5m/why_developer_expertise_matters_more_than_ever_in/)
https://www.reddit.com/r/programming/comments/1q2qa5m/why_developer_expertise_matters_more_than_ever_in/
<!-- SC_OFF -->Read “Why Developer Expertise Matters More Than Ever in the Age of AI“ <!-- SC_ON --> submitted by /u/iammidhul (https://www.reddit.com/user/iammidhul)
[link] (https://medium.com/understanding-javanoscript-developwithmi/why-developer-expertise-matters-more-than-ever-in-the-age-of-ai-a45a93ffc14f?sk=046291f3b71ef1fc8dbeaa5c1f96e6c7) [comments] (https://www.reddit.com/r/programming/comments/1q2qa5m/why_developer_expertise_matters_more_than_ever_in/)
Encapsulating audio metadata and edit logic in a single text format
https://www.reddit.com/r/programming/comments/1q2rvgs/encapsulating_audio_metadata_and_edit_logic_in_a/
<!-- SC_OFF -->CUE sheets describe audio timestamps and metadata, but I wanted something a bit more expressive.
I built a CUE-based text format and a tool with SQL-like methods, keeping it small and easy to implement while allowing simple but effective edits.
In the demo, an album medley is created using only MP3 drag & drop and text copy/paste—no waveform editing required. <!-- SC_ON --> submitted by /u/cutandjoin (https://www.reddit.com/user/cutandjoin)
[link] (https://youtu.be/-beNsYuPZaQ) [comments] (https://www.reddit.com/r/programming/comments/1q2rvgs/encapsulating_audio_metadata_and_edit_logic_in_a/)
https://www.reddit.com/r/programming/comments/1q2rvgs/encapsulating_audio_metadata_and_edit_logic_in_a/
<!-- SC_OFF -->CUE sheets describe audio timestamps and metadata, but I wanted something a bit more expressive.
I built a CUE-based text format and a tool with SQL-like methods, keeping it small and easy to implement while allowing simple but effective edits.
In the demo, an album medley is created using only MP3 drag & drop and text copy/paste—no waveform editing required. <!-- SC_ON --> submitted by /u/cutandjoin (https://www.reddit.com/user/cutandjoin)
[link] (https://youtu.be/-beNsYuPZaQ) [comments] (https://www.reddit.com/r/programming/comments/1q2rvgs/encapsulating_audio_metadata_and_edit_logic_in_a/)
identity is a physical property, not a digital permission
https://www.reddit.com/r/programming/comments/1q2vf8z/identity_is_a_physical_property_not_a_digital/
<!-- SC_OFF -->The Problem
Almost every anti-counterfeit or authentication system today starts with a digital identity and tries to attach it to a physical thing. QR codes, serial numbers, NFC tags, cloud verification, even ML-based "real vs. fake" image checks—they all share one assumption: the digital layer is the source of truth. The physical object is just a carrier. That assumption started to feel backwards. The Core Idea: Extract, Don't Assign
What if a physical object already has a unique, measurable identity formed during its creation (microscopic misalignments, printing imperfections, layer offsets)?
What if, instead of gluing a digital code onto it, we just measure what's already there and make the digital layer a reference to that physical fingerprint? That’s the premise of PBM (Perspective-Based Markers). It's a simple physical-layer experiment. How It Works (The Simple Version)
The setup is deliberately low-tech: Print two high-frequency grid patterns, one on top of the other, with a tiny, fixed physical gap (millimeters) between them. Capture an image from a slight angle. The physics part: If a real 3D gap exists, you get parallax (the grids shift relative to each other in the image). If it's a flat photo, a screen replay, or a reprint, the parallax field collapses. The math is binary. What It Does NOT Use
This is the important part: No neural networks No "AI confidence score" No cloud API calls for the core verification No training data or heuristics What It DOES Use Deterministic signal processing: FFT and phase correlation. A simple signal-to-noise threshold. Output is PHYSICAL, NON_PHYSICAL, or UNDECIDABLE. The UNDECIDABLE result is intentional. If the signal is ambiguous, the system declares "I don't know." It won't guess. This feels healthier than systems that hallucinate certainty. Tested Bypass Methods (They Fail)
I tried the obvious attacks: Taking a photo of the token and printing it Showing the token on a phone screen High-resolution reprinting To the human eye, they look perfect. They might even pass a "strong signal" check. But the relative parallax between the two grid layers? Zero. Physics doesn't negotiate. You Can Try It Yourself (Seriously)
You don't need a lab. To see the parallax effect: An inkjet printer A4 paper A spacer like a CD case to create the gap A drop of cooking oil (to make the top paper translucent and see both layers) That's enough to observe the core principle. Why Publish This Openly?
I don't want this to turn into: "Trust our proprietary model" "Upload to our verification API" "Enterprise pricing available" This describes a physics-based constraint, not a product. If the method is flawed, I want it broken in public. If it's valid, it should belong to anyone who understands the math. The repository and full technical specification are public (link in comments). I'm happy to discuss why this might be a dead end, or where it could be genuinely useful. Happy New Year. https://github.com/illegal-instruction-co/pbm-core <!-- SC_ON --> submitted by /u/Humble-Plastic-5285 (https://www.reddit.com/user/Humble-Plastic-5285)
[link] (https://github.com/illegal-instruction-co/pbm-core) [comments] (https://www.reddit.com/r/programming/comments/1q2vf8z/identity_is_a_physical_property_not_a_digital/)
https://www.reddit.com/r/programming/comments/1q2vf8z/identity_is_a_physical_property_not_a_digital/
<!-- SC_OFF -->The Problem
Almost every anti-counterfeit or authentication system today starts with a digital identity and tries to attach it to a physical thing. QR codes, serial numbers, NFC tags, cloud verification, even ML-based "real vs. fake" image checks—they all share one assumption: the digital layer is the source of truth. The physical object is just a carrier. That assumption started to feel backwards. The Core Idea: Extract, Don't Assign
What if a physical object already has a unique, measurable identity formed during its creation (microscopic misalignments, printing imperfections, layer offsets)?
What if, instead of gluing a digital code onto it, we just measure what's already there and make the digital layer a reference to that physical fingerprint? That’s the premise of PBM (Perspective-Based Markers). It's a simple physical-layer experiment. How It Works (The Simple Version)
The setup is deliberately low-tech: Print two high-frequency grid patterns, one on top of the other, with a tiny, fixed physical gap (millimeters) between them. Capture an image from a slight angle. The physics part: If a real 3D gap exists, you get parallax (the grids shift relative to each other in the image). If it's a flat photo, a screen replay, or a reprint, the parallax field collapses. The math is binary. What It Does NOT Use
This is the important part: No neural networks No "AI confidence score" No cloud API calls for the core verification No training data or heuristics What It DOES Use Deterministic signal processing: FFT and phase correlation. A simple signal-to-noise threshold. Output is PHYSICAL, NON_PHYSICAL, or UNDECIDABLE. The UNDECIDABLE result is intentional. If the signal is ambiguous, the system declares "I don't know." It won't guess. This feels healthier than systems that hallucinate certainty. Tested Bypass Methods (They Fail)
I tried the obvious attacks: Taking a photo of the token and printing it Showing the token on a phone screen High-resolution reprinting To the human eye, they look perfect. They might even pass a "strong signal" check. But the relative parallax between the two grid layers? Zero. Physics doesn't negotiate. You Can Try It Yourself (Seriously)
You don't need a lab. To see the parallax effect: An inkjet printer A4 paper A spacer like a CD case to create the gap A drop of cooking oil (to make the top paper translucent and see both layers) That's enough to observe the core principle. Why Publish This Openly?
I don't want this to turn into: "Trust our proprietary model" "Upload to our verification API" "Enterprise pricing available" This describes a physics-based constraint, not a product. If the method is flawed, I want it broken in public. If it's valid, it should belong to anyone who understands the math. The repository and full technical specification are public (link in comments). I'm happy to discuss why this might be a dead end, or where it could be genuinely useful. Happy New Year. https://github.com/illegal-instruction-co/pbm-core <!-- SC_ON --> submitted by /u/Humble-Plastic-5285 (https://www.reddit.com/user/Humble-Plastic-5285)
[link] (https://github.com/illegal-instruction-co/pbm-core) [comments] (https://www.reddit.com/r/programming/comments/1q2vf8z/identity_is_a_physical_property_not_a_digital/)
Native Android Application Development in Swift
https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/
<!-- SC_OFF -->Hi all, imike here. I just released Swift Stream IDE v1.17.0, which adds full native Android application development written entirely in Swift. That means you can now build Android apps without touching XML, Java, or Kotlin. Swift Stream IDE is an open-source VSCode extension that sets up a ready-to-use Swift development environment in Docker, supporting server-side, web, embedded, and now full Android development. With this release, you can create Android applications using familiar templates like Empty Activity, Basic Views (two fragments), or Navigation UI (tab bar), all in Swift. Under the hood, all projects are powered by SwifDroid, a framework I built to wrap the entire native Android app model. It handles the application lifecycle and manifest, activities and fragments, Android, AndroidX, Material, and Flexbox UI widgets, and even automatically wires Gradle dependencies. Supported SDKs are 28 to 35, and with Swift 6.3, it might go down (https://forums.swift.org/t/android-api-minimum-for-the-swift-sdk-for-android/82874) to 24+. Example UI code: ConstraintLayout { VStack { TextView("Hello from Swift!") .width(.matchParent) .height(.wrapContent) .textColor(.green) MaterialButton("Tap Me") .onClick { print("Button tapped!") } } .centerVertical() .leftToParent() .rightToParent() } The first time you create a project, make yourself a cup of tea/coffee. The IDE pulls the Swift toolchain, Android SDK, and NDK, and caches them in Docker volumes. After that, new projects are created instantly. The first build compiles Swift, generates a full Android project (ready to open in Android Studio), and creates a Gradle wrapper. After that, builds take just a few seconds. Once Swift is compiled, you can simply open the Application folder in Android Studio and hit Run or Restart to see your changes. All the necessary files from Swift Stream IDE are already in place, so iteration is fast and seamless. This is the first public release. Android is huge, and there are still widgets in progress, but the system is real and usable today. Documentation: https://docs.swifdroid.com/app/ <!-- SC_ON --> submitted by /u/imike3049 (https://www.reddit.com/user/imike3049)
[link] (https://docs.swifdroid.com/app/) [comments] (https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/)
https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/
<!-- SC_OFF -->Hi all, imike here. I just released Swift Stream IDE v1.17.0, which adds full native Android application development written entirely in Swift. That means you can now build Android apps without touching XML, Java, or Kotlin. Swift Stream IDE is an open-source VSCode extension that sets up a ready-to-use Swift development environment in Docker, supporting server-side, web, embedded, and now full Android development. With this release, you can create Android applications using familiar templates like Empty Activity, Basic Views (two fragments), or Navigation UI (tab bar), all in Swift. Under the hood, all projects are powered by SwifDroid, a framework I built to wrap the entire native Android app model. It handles the application lifecycle and manifest, activities and fragments, Android, AndroidX, Material, and Flexbox UI widgets, and even automatically wires Gradle dependencies. Supported SDKs are 28 to 35, and with Swift 6.3, it might go down (https://forums.swift.org/t/android-api-minimum-for-the-swift-sdk-for-android/82874) to 24+. Example UI code: ConstraintLayout { VStack { TextView("Hello from Swift!") .width(.matchParent) .height(.wrapContent) .textColor(.green) MaterialButton("Tap Me") .onClick { print("Button tapped!") } } .centerVertical() .leftToParent() .rightToParent() } The first time you create a project, make yourself a cup of tea/coffee. The IDE pulls the Swift toolchain, Android SDK, and NDK, and caches them in Docker volumes. After that, new projects are created instantly. The first build compiles Swift, generates a full Android project (ready to open in Android Studio), and creates a Gradle wrapper. After that, builds take just a few seconds. Once Swift is compiled, you can simply open the Application folder in Android Studio and hit Run or Restart to see your changes. All the necessary files from Swift Stream IDE are already in place, so iteration is fast and seamless. This is the first public release. Android is huge, and there are still widgets in progress, but the system is real and usable today. Documentation: https://docs.swifdroid.com/app/ <!-- SC_ON --> submitted by /u/imike3049 (https://www.reddit.com/user/imike3049)
[link] (https://docs.swifdroid.com/app/) [comments] (https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/)
Who Owns the Memory? Part 1: What is an Object?
https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/
submitted by /u/Luke_Fleed (https://www.reddit.com/user/Luke_Fleed)
[link] (https://lukefleed.xyz/posts/who-owns-the-memory-pt1/) [comments] (https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/)
https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/
submitted by /u/Luke_Fleed (https://www.reddit.com/user/Luke_Fleed)
[link] (https://lukefleed.xyz/posts/who-owns-the-memory-pt1/) [comments] (https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/)
Bold December Summary (text editor with lsp and dap support)
https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/
submitted by /u/levodelellis (https://www.reddit.com/user/levodelellis)
[link] (https://bold-edit.com/devlog/25-12-summary.html) [comments] (https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/)
https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/
submitted by /u/levodelellis (https://www.reddit.com/user/levodelellis)
[link] (https://bold-edit.com/devlog/25-12-summary.html) [comments] (https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/)
Naughty Words Every Programmer Should Know - a free eBook that uses NSFW Acronyms as mnemonic devices
https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/
submitted by /u/Mrsomud007 (https://www.reddit.com/user/Mrsomud007)
[link] (http://filipristovic.com/) [comments] (https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/)
https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/
submitted by /u/Mrsomud007 (https://www.reddit.com/user/Mrsomud007)
[link] (http://filipristovic.com/) [comments] (https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/)
Software craftsmanship is dead
https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/
submitted by /u/R2_SWE2 (https://www.reddit.com/user/R2_SWE2)
[link] (https://www.pcloadletter.dev/blog/craftsmanship-is-dead/) [comments] (https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/)
https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/
submitted by /u/R2_SWE2 (https://www.reddit.com/user/R2_SWE2)
[link] (https://www.pcloadletter.dev/blog/craftsmanship-is-dead/) [comments] (https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/)
Stackoverflow: Questions asked per month over time.
https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/
submitted by /u/lelanthran (https://www.reddit.com/user/lelanthran)
[link] (https://data.stackexchange.com/stackoverflow/query/1926661#graph) [comments] (https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/)
https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/
submitted by /u/lelanthran (https://www.reddit.com/user/lelanthran)
[link] (https://data.stackexchange.com/stackoverflow/query/1926661#graph) [comments] (https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/)
21 Lessons From 14 Years at Google
https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://addyosmani.com/blog/21-lessons/) [comments] (https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/)
https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://addyosmani.com/blog/21-lessons/) [comments] (https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/)
Building a Monitoring System for Jobs That Never Ran
https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/
<!-- SC_OFF -->Most monitoring systems tracks success and failure, but the hardest problems come from jobs that never ran at all. The article covers the architecture, the tricky parts such as detecting jobs that never ran, and some lessons learned along the way. <!-- SC_ON --> submitted by /u/Mythikos (https://www.reddit.com/user/Mythikos)
[link] (https://www.vincentlakatos.com/blog/building-a-monitoring-system-that-catches-silent-failures/) [comments] (https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/)
https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/
<!-- SC_OFF -->Most monitoring systems tracks success and failure, but the hardest problems come from jobs that never ran at all. The article covers the architecture, the tricky parts such as detecting jobs that never ran, and some lessons learned along the way. <!-- SC_ON --> submitted by /u/Mythikos (https://www.reddit.com/user/Mythikos)
[link] (https://www.vincentlakatos.com/blog/building-a-monitoring-system-that-catches-silent-failures/) [comments] (https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/)
Managing database schema changes for beginners
https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/
submitted by /u/tanin47 (https://www.reddit.com/user/tanin47)
[link] (https://medium.com/@tanin_90098/the-basics-of-managing-database-schema-changes-fc31b4264297) [comments] (https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/)
https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/
submitted by /u/tanin47 (https://www.reddit.com/user/tanin47)
[link] (https://medium.com/@tanin_90098/the-basics-of-managing-database-schema-changes-fc31b4264297) [comments] (https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/)
Databases in 2025: A Year in Review
https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://www.cs.cmu.edu/~pavlo/blog/2026/01/2025-databases-retrospective.html) [comments] (https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/)
https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://www.cs.cmu.edu/~pavlo/blog/2026/01/2025-databases-retrospective.html) [comments] (https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/)
Gossip Gloomers in Rust
https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/
submitted by /u/glassycrow (https://www.reddit.com/user/glassycrow)
[link] (https://pureframes.eu/blog/gossip-gloomers) [comments] (https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/)
https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/
submitted by /u/glassycrow (https://www.reddit.com/user/glassycrow)
[link] (https://pureframes.eu/blog/gossip-gloomers) [comments] (https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/)
Simple and efficient visualization of embedded system events: Using VCD viewers and FreeRTOS trace
https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/
<!-- SC_OFF -->Relying on printf or simple breakpoints for real-time embedded debugging is often like flying blind - especially when dealing with complex timing and RTOS scheduling. The RTEdbg toolkit (https://github.com/RTEdbg/RTEdbg) has been extended to solve this, adding VCD-based (https://en.wikipedia.org/wiki/Value_change_dump) event and data visualization, native FreeRTOS trace support, and enhanced trace macros for deeper system insights. Because RTEdbg is open-source, it is accessible for any project, regardless of budget. It supports application and RTOS event visualization (see FreeRTOS trace demo (https://github.com/RTEdbg/FreeRTOS-trace-demo)) and allows for flexible data export and custom visualization—you can see it in action here: Various Data Export and Visualization Possibilities (https://github.com/RTEdbg/RTEdbg/blob/master/Views.md). <!-- SC_ON --> submitted by /u/BrankoP88 (https://www.reddit.com/user/BrankoP88)
[link] (https://github.com/RTEdbg/RTEdbg) [comments] (https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/)
https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/
<!-- SC_OFF -->Relying on printf or simple breakpoints for real-time embedded debugging is often like flying blind - especially when dealing with complex timing and RTOS scheduling. The RTEdbg toolkit (https://github.com/RTEdbg/RTEdbg) has been extended to solve this, adding VCD-based (https://en.wikipedia.org/wiki/Value_change_dump) event and data visualization, native FreeRTOS trace support, and enhanced trace macros for deeper system insights. Because RTEdbg is open-source, it is accessible for any project, regardless of budget. It supports application and RTOS event visualization (see FreeRTOS trace demo (https://github.com/RTEdbg/FreeRTOS-trace-demo)) and allows for flexible data export and custom visualization—you can see it in action here: Various Data Export and Visualization Possibilities (https://github.com/RTEdbg/RTEdbg/blob/master/Views.md). <!-- SC_ON --> submitted by /u/BrankoP88 (https://www.reddit.com/user/BrankoP88)
[link] (https://github.com/RTEdbg/RTEdbg) [comments] (https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/)
Functors, Applicatives, and Monads: The Scary Words You Already Understand
https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/
<!-- SC_OFF -->Do you generally agree with this? It's a tough topic to teach simply, and there's always tradeoffs between accuracy and simplicity... Open to suggestions for improvement! Thanks :) <!-- SC_ON --> submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/functors-applicatives-monads-elm/) [comments] (https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/)
https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/
<!-- SC_OFF -->Do you generally agree with this? It's a tough topic to teach simply, and there's always tradeoffs between accuracy and simplicity... Open to suggestions for improvement! Thanks :) <!-- SC_ON --> submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/functors-applicatives-monads-elm/) [comments] (https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/)
How Speeding Up RL Led to Pufferlib (4.8K Stars) | Interview with Joseph Suarez
https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/
submitted by /u/research_pie (https://www.reddit.com/user/research_pie)
[link] (https://youtu.be/Sirpfci74zU) [comments] (https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/)
https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/
submitted by /u/research_pie (https://www.reddit.com/user/research_pie)
[link] (https://youtu.be/Sirpfci74zU) [comments] (https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/)
The Data Triangle
https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/
submitted by /u/benlorantfy (https://www.reddit.com/user/benlorantfy)
[link] (https://www.benlorantfy.com/blog/the-data-triangle-and-nestjs-zod-v5) [comments] (https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/)
https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/
submitted by /u/benlorantfy (https://www.reddit.com/user/benlorantfy)
[link] (https://www.benlorantfy.com/blog/the-data-triangle-and-nestjs-zod-v5) [comments] (https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/)