Reddit Programming
201 subscribers
1.22K photos
126K links
I will send you newest post from subreddit /r/programming
Download Telegram
Rust vs C++: The Memory Safety Standard in 2026
https://www.reddit.com/r/programming/comments/1s0q4rl/rust_vs_c_the_memory_safety_standard_in_2026/

<!-- SC_OFF -->C++ gives developers direct control over memory allocation and deallocation but Rust is the language at the center of this shift. It promises, and delivers, the performance of C++ with compile-time guarantees that eliminate entire classes of memory bugs. Not through garbage collection (which adds runtime overhead), but through a novel ownership system that catches errors before the code ever runs. <!-- SC_ON --> submitted by /u/Low-Trust2491 (https://www.reddit.com/user/Low-Trust2491)
[link] (https://rune.codes/hub/tech-trends/why-rust-is-replacing-c-as-the-standard-for-memory-safety) [comments] (https://www.reddit.com/r/programming/comments/1s0q4rl/rust_vs_c_the_memory_safety_standard_in_2026/)
Traditional user-interface graphics: icons, cursors, buttons, borders, and drawing style
https://www.reddit.com/r/programming/comments/1s0ymoh/traditional_userinterface_graphics_icons_cursors/

<!-- SC_OFF -->This open-source article (https://peteroupc.github.io/classic-wallpaper/docs/uielements.html) I wrote discusses aspects of the traditional visual design (up to about the year 2003) of user-interface (UI) graphics, such as button and border styles, icons, and mouse pointers. It also seeks to characterize the drawing style of traditional UI graphics, especially from 1990 to 2003, and gives advice on developing new graphical UI systems with a high degree of flexibility. User interfaces found in video games are outside the document's scope. <!-- SC_ON --> submitted by /u/peteroupc (https://www.reddit.com/user/peteroupc)
[link] (https://peteroupc.github.io/classic-wallpaper/docs/uielements.html) [comments] (https://www.reddit.com/r/programming/comments/1s0ymoh/traditional_userinterface_graphics_icons_cursors/)
TrainSec voucher
https://www.reddit.com/r/programming/comments/1s150d3/trainsec_voucher/

<!-- SC_OFF -->I have a $500 TrainSec voucher that I’m not planning to use, so I’m looking to sell it. I’m asking around $250-$300, but the price is negotiable. Let me know if you’re interested. Also, you can choose your course as per your need for $500 <!-- SC_ON --> submitted by /u/Salty-Ad9979 (https://www.reddit.com/user/Salty-Ad9979)
[link] (https://trainsec.net/) [comments] (https://www.reddit.com/r/programming/comments/1s150d3/trainsec_voucher/)
Software dev job postings are up 15% since mid 2025
https://www.reddit.com/r/programming/comments/1s1e4il/software_dev_job_postings_are_up_15_since_mid_2025/

<!-- SC_OFF -->Been watching this FRED data for a while. Software development job postings on Indeed hit a low point around May 2025, then climbed steadily for 10 months straight and are now sitting about 15% higher than that trough. The recent acceleration from January 2026 onwards is pretty sharp. This runs directly against the AI is killing developer jobs narrative that's been everywhere for the past two years. I might be wrong but i think AI might actually be creating more software demand, not less. More products get built because the cost of building dropped. Someone still has to architect the systems, build the tooling, maintain the infrastructure. that's all still dev work. Curious what people here are actually seeing. Are you busier or less busy than two years ago? And if you're hiring, is the bar different now? <!-- SC_ON --> submitted by /u/IdeasInProcess (https://www.reddit.com/user/IdeasInProcess)
[link] (https://fred.stlouisfed.org/series/IHLIDXUSTPSOFTDEVE) [comments] (https://www.reddit.com/r/programming/comments/1s1e4il/software_dev_job_postings_are_up_15_since_mid_2025/)
Governance: Documentation to support projects
https://www.reddit.com/r/programming/comments/1s1jeoz/governance_documentation_to_support_projects/

<!-- SC_OFF -->This is a summary of the main article, the real article goes into more details Two weeks ago I wrote an article about governance and documentation on an organisational scale. This is the follow-up post that focuses on the project scale. You could just read this post, but it’s probably better that you start with the previous one first For me, there are four main areas to support a (large) project. You require the Strategy, the foundation where you start and what the idea of the project is. The Logs, these are living documents that capture what is going on. Blueprint, these are mainly diagrams to support the project visually. And finally Program Management, where you keep everything that’s related to timing and execution. Strategy All of this starts with a Business Case. The “Why” we are doing this document. This can be high level, or very deep. You will also find a Kick-off document here. These are often PowerPoint slides that define the team, scope, way of working, and timelines. Logs I always like to have an Open Questions Log. A centralized document (everyone has access) to questions that need answers. The Decision Log is where you keep track of the closed questions. Again, very handy in an ongoing project, but extra useful once the project is over and it all becomes part of the bigger documentation. Meeting Notes are also handy to store here, probably best in a subdirectory. AI-generated documents are actually very welcome here (compared to other AI generated documentation everywhere else) Blueprints I like to keep my diagrams both in the raw format (visio, draw.io, lucid,…) and in static formats (like PNG). I always like to have diagrams that show both the Target and AS-IS states, and if it’s a big project, what the project phases look like Project related documents I always like a Gantt Chart. Make sure it’s up-to-date and accessible to everyone. Ideally you also have the Critical Path highlighted. Also, deadlines and gates should be present. Providing a central Gantt chart ensures that project management is democratised. The most important ones You pick and choose what you think is essential in the scope of the project. You can also add more later. That being said I like to always have at least the core documents. Even if it’s a project for an app that will be live for two weeks. The Business Case: If this isn’t clear, the architecture will drift. Decision & Question Logs: These are the most valuable “historical” nodes for future maintainers. TO-BE Diagram: A quick reference for everyone on what’s actually changing. Also, easy to copy and paste into presentations for higher-ups. The Gantt: That’s just basic project management and keeps everyone honest. Merging it back into the bigger documentation The diagrams can move towards the resources section with links to the applications. Going over the logs, you can remove the noise and keep the logs that are relevant to processes and applications to the logs of those processes and applications. You end up moving the rest to the archive section as a project folder. It’s very essential to not just delete here. If you have a similar project in the future, you can copy a lot of homework here. Organic documentation So these are my current views on documentation. To paraphrase this article and the previous one: Small documents that are interconnected. Accessible and owned by everyone. Organically grown and mainly written from a project perspective. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2026-03-22-governance-documentation-to-support-projects/) [comments] (https://www.reddit.com/r/programming/comments/1s1jeoz/governance_documentation_to_support_projects/)
DoG RANSAC DenGering SlitSpike algorithm for reading 9-segment Soviet Postal codes from grainy images
https://www.reddit.com/r/programming/comments/1s1kc5q/dog_ransac_dengering_slitspike_algorithm_for/

<!-- SC_OFF -->The Soviet Union introduced a special envelope for mailing letters in 1971. The envelopes contained standardized boxes at the bottom where the sended wrote out out the digits by connecting the dots. The intention of the GOST R 51506-99 standard was to make these envelopes machine readable. I have not been able to get any information about how the Soviet postal code optical character recoginition machines worked. So, I wanted to see if I could come up with a way to read the postal code from a grainy image. What started out as a simple project turned out to be a journey into finding an algorithm that could distinguish signal from the noise in wonky images, and then disambiguate between confusable pairs. This would've been much easier in the Soviet days, though. Because, in Soviet Russia, the algorithm finds you. <!-- SC_ON --> submitted by /u/reditzer (https://www.reddit.com/user/reditzer)
[link] (https://boreal.social/post/dog-ransac-dengering-slitspike-algorithm-for-reading-9) [comments] (https://www.reddit.com/r/programming/comments/1s1kc5q/dog_ransac_dengering_slitspike_algorithm_for/)