Reddit Programming
209 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
I implemented secure password hashing in a Java Swing Library Management System (SHA-256)
https://www.reddit.com/r/programming/comments/1pr6i2u/i_implemented_secure_password_hashing_in_a_java/

<!-- SC_OFF -->Hi everyone 👋 I’m building a real-world Java Swing Library Management System, and in Part 32 I focused on something many beginner projects ignore: secure password storage. In this video, I implemented: 🔐 Password hashing using SHA-256 No plain-text passwords in MySQL Proper login preparation for real applications Java Swing + 🛢 MySQL integration This is part of a User Management Module, not just a demo — it’s designed like a real system you’d see in production (for learning purposes). 🎥 Video: Part 32 — Java Swing Library System | User Management – Secure Hashed Password
Part 32 — Java Swing Library System | Part 9 User Management Module – Secure Hashed Password (https://www.youtube.com/watch?v=tZGDawjVaD4&t=219s) I’d really appreciate feedback from experienced Java developers: Is SHA-256 okay for learning projects? What would you recommend next? (salt, bcrypt, login verification, forgot password?) Thanks for reading 🙏
I hope this helps other Java Swing learners too. <!-- SC_ON --> submitted by /u/Substantial-Log-9305 (https://www.reddit.com/user/Substantial-Log-9305)
[link] (https://www.youtube.com/watch?v=tZGDawjVaD4&t=219s) [comments] (https://www.reddit.com/r/programming/comments/1pr6i2u/i_implemented_secure_password_hashing_in_a_java/)
Mastering AI Coding: The Universal Playbook of Tips, Tricks, and Patterns
https://www.reddit.com/r/programming/comments/1pr7wc9/mastering_ai_coding_the_universal_playbook_of/

<!-- SC_OFF -->A very useful, neither hype'y nor shilly, set of universal principles and approaches that makes AI-assisted coding (not vibing!) productive - for many, but not all, programming tasks. We are not talking about vibe coding here, were you don't know what's going on - we're talking about planning your changes carefully and in a detailed way with AI and letting it to write most, but not all, of the code. I've been experimenting with this approach as of late and for popular programming stacks, as long as you validate the output and work in incremental steps, it can speed up some (not all) programming tasks a lot :) Especially if you set up the code repo properly and have good and cohesive code conventions <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://www.siddharthbharath.com/mastering-ai-coding-the-universal-playbook-of-tips-tricks-and-patterns/) [comments] (https://www.reddit.com/r/programming/comments/1pr7wc9/mastering_ai_coding_the_universal_playbook_of/)
We revoked our v1.0 status. Why we're rolling NalthJS back to v0.9.0 to prioritize security architecture.
https://www.reddit.com/r/programming/comments/1pr8mhf/we_revoked_our_v10_status_why_were_rolling/

<!-- SC_OFF -->We made a mistake that I think a lot of open source maintainers make: we chased the "v1.0" label before the architecture was truly battle-hardened. NalthJS is designed to be a security-first framework (enforcing headers, sanitization, and encryption by default). But we realized that keeping the v1.0 badge implies a "finished" state that discouraged the kind of radical architectural improvements we're currently making. So, we're doing something unpopular: we're rolling back to v0.9.0 Beta. We're choosing to break things now so they don't break in prod later. I'd love to hear from other maintainers have you ever "undone" a major release to save the project's long-term integrity <!-- SC_ON --> submitted by /u/Evening-Direction-71 (https://www.reddit.com/user/Evening-Direction-71)
[link] (https://nalthjs.com/) [comments] (https://www.reddit.com/r/programming/comments/1pr8mhf/we_revoked_our_v10_status_why_were_rolling/)
Modeling Large Codebases as Static Knowledge Graphs: Design Trade-offs
https://www.reddit.com/r/programming/comments/1priv8c/modeling_large_codebases_as_static_knowledge/

<!-- SC_OFF -->When working with large codebases, structural information such as module boundaries, dependency relationships, and hierarchy is often implicit and hard to reason about. One approach I’ve been exploring is representing codebases as static knowledge graphs, where files, modules, and symbols become explicit nodes, and architectural relationships are encoded as edges. This raises several design questions: - What information is best captured statically versus dynamically? - How detailed should graph nodes and edges be? - Where do static representations break down compared to runtime analysis? - How can such graphs remain maintainable as the code evolves? I’m interested in hearing from people who have worked on: - Static analysis tools - Code indexing systems - Large-scale refactoring or architecture tooling For context, I’ve been experimenting with these ideas in an open-source project, but I’m mainly interested in the broader design discussion. <!-- SC_ON --> submitted by /u/codevoygee (https://www.reddit.com/user/codevoygee)
[link] (https://github.com/yunusgungor/knowgraph) [comments] (https://www.reddit.com/r/programming/comments/1priv8c/modeling_large_codebases_as_static_knowledge/)
Launching Remy
https://www.reddit.com/r/programming/comments/1pry78w/launching_remy/

<!-- SC_OFF -->Hey everyone — I’ve been working on a consumer app called Remy that’s meant to help in the moment when an alcohol craving hits. Most sobriety apps focus on tracking days or staying sober long-term. Remy is different — it’s designed for the day-to-day moments where you actually feel the urge to drink and need something right then to get through it. When a craving hits, you open the app and use: • Short grounding exercises (like urge surfing) • Simple games to distract and ride out the craving • An AI character (Remy) that gives personalized motivation based on your goals, stressors, and usual trigger times The idea is to reduce the intensity of the craving long enough for it to pass. It’s a mobile app (App Store launch soon — finishing up a few things), and I built it myself using Lovable and ElevenLabs for voice. I’m steadily adding more exercises and games, and I’m looking for early users / beta testers who are open to giving honest feedback — what works, what doesn’t, and what would make this actually useful. Let me know if you want to test it out and I will add you as a user. <!-- SC_ON --> submitted by /u/remy-the-fox (https://www.reddit.com/user/remy-the-fox)
[link] (https://remy-the-fox.lovable.app/) [comments] (https://www.reddit.com/r/programming/comments/1pry78w/launching_remy/)
A systematic framework to eliminate all UB from C++
https://www.reddit.com/r/programming/comments/1ps0m3w/a_systematic_framework_to_eliminate_all_ub_from_c/

<!-- SC_OFF -->This is a high-level interesting on-going paper about how C++ plans to improve safety. This includes strategies: feature removal refined behaviour erroneous behaviour insertion of runtime checks language subsetting (via profiles, probably) the introduction of annotations the introduction of entirely new language features The paper takes into account that C++ is a language that should keep compiling with older code but should do it with newer code in a safer way (via opt-ins/outs). <!-- SC_ON --> submitted by /u/germandiago (https://www.reddit.com/user/germandiago)
[link] (https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3100r5.pdf) [comments] (https://www.reddit.com/r/programming/comments/1ps0m3w/a_systematic_framework_to_eliminate_all_ub_from_c/)