Reddit Programming
211 subscribers
1.22K photos
124K links
I will send you newest post from subreddit /r/programming
Download Telegram
Some Advice for First Time Job Seekers
https://www.reddit.com/r/programming/comments/1obwba5/some_advice_for_first_time_job_seekers/

<!-- SC_OFF -->This is based on my experiences finding work throughout my career. I had to find new positions much more often that I would have liked to and this informs the video. There is no silver bullet here, just some straightforward advice and analysis of the current job environment. <!-- SC_ON --> submitted by /u/stumblingtowards (https://www.reddit.com/user/stumblingtowards)
[link] (https://youtu.be/BAfs7UOmyl0) [comments] (https://www.reddit.com/r/programming/comments/1obwba5/some_advice_for_first_time_job_seekers/)
LogMod: What if C had a logging framework with modern semantics?
https://www.reddit.com/r/programming/comments/1oc2h8k/logmod_what_if_c_had_a_logging_framework_with/

<!-- SC_OFF -->In my own experience when looking into C logging libraries, I found that they either rely on hidden global state or quietly calls malloc behind the scenes. In environments where you need deterministic memory usage and explicit control over resources, that’s problematic. I wanted to see if it was possible to bring more “modern” logging semantics - things like configurable contexts, custom labels, colour coding, callbacks and thread‐safety - into plain ANSI C without using dynamic memory or preprocessor magic. (it is possible!) LogMod is the result. It’s a single‑header library that lets you initialise a logging context with a fixed table of loggers, pass that context around instead of using globals, define your own severity levels and colours, hook in custom callbacks, and even make it thread‑safe with a user‑supplied lock. It avoids malloc entirely. The challenge was fitting all of this into a few hundred lines of portable code and retaining C’s “zero-overhead” philosophy. <!-- SC_ON --> submitted by /u/LucasMull (https://www.reddit.com/user/LucasMull)
[link] (https://github.com/lcsmuller/logmod) [comments] (https://www.reddit.com/r/programming/comments/1oc2h8k/logmod_what_if_c_had_a_logging_framework_with/)
Walrus: a high performance storage engine built from first principles
https://www.reddit.com/r/programming/comments/1ocb0w2/walrus_a_high_performance_storage_engine_built/

<!-- SC_OFF -->Hi, recently I've been working on a high performance storage engine in Rust called Walrus, A little bit of intro, Walrus is an embedded in-process storage engine built from first principles and can be used as a building block to build these things right out of the box: Timeseries Event Log: Immutable audit trails, compliance tracking. Every event persisted immediately, read exactly once. Database WAL: PostgreSQL style transaction logs. Maximum durability for commits, deterministic crash recovery. Message Queue: Kafka style streaming. Batch writes (up to 2000 entries), high throughput, at least once delivery. Key Value Store: Simple persistent cache. Each key is a topic, fast writes with 50ms fsync window. Task Queue: Async job processing. At least once delivery with retry safe workers (handlers should be idempotent). ... and much more the recent release outperforms single node apache kafka and rocksdb at the workloads of their choice (benchmarks in repo) repo: https://github.com/nubskr/walrus If you're interested in learning about walrus's internals, these two release posts will give you all you need: v0.1.0 release post:https://nubskr.com/2025/10/06/walrus (yes, it was supposed to be a write ahead log in the beginning) v0.2.0 release post: https://nubskr.com/2025/10/20/walrus_v0.2.0 I'm looking forward to hearing feedback from the community and the works of a 'distributed' version of walrus are in progress. <!-- SC_ON --> submitted by /u/Ok_Marionberry8922 (https://www.reddit.com/user/Ok_Marionberry8922)
[link] (https://github.com/nubskr/walrus) [comments] (https://www.reddit.com/r/programming/comments/1ocb0w2/walrus_a_high_performance_storage_engine_built/)