At the risk of alienating two constituencies with one suggestion, it is possible to build a secular, open source moral code on GitHub.

Memory leaks, NULL pointer dereferences, use-after-free: I suffered writing those for many years. I finally simply learned not to do them anymore.

Statically-typed equivalent of Python's `struct` module?

Resources on Writer's Workbench (wwb)

I'd even go to the extreme of saying the coding skills/brains fade by inverse cube law. Skill =~ 1/t^3 (t = time since last practiced the skill)

There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.

As a software engineer having never worked in COBOL, I could pick up a COBOL project in an afternoon with nothing more than a syntax manual and a few hours.

cppgir - tool for automatically generating C++ wrappers for GObject-based libraries

Here is the formal spec in the most formal and precise way to describe non-trivial stuff: https://github.com/rust-lang/rust

Monomophisation should never be slow to compile (if done explicitly)

Thinking of literally starting a Linux maintainer hall of shame. Not for public consumption, but to help new kernel contributors know what to expect.

By the time I reach age 40, PhD's will be coming to be for advise. Because I didn't study computer science in college. I'm studying it for life.

only humans are able to implement errors like buffer oberflow. machines are perfect after a critical point, they wont do mistakes anymore.

I really love the simplicity of Go, but unfortunately, I’m currently unemployed

A noble idea, but Github is literally littered with hobbyist home-grown Unix-like kernels in C. As an industry are we not supposed to be trying to move away from hoary old unsafe C?

they require you to change your ways to such an extent that you would be unable to contribute to cURL anymore and all your work, except for compatibility work would be obsolete (it technically has been... for a long time; ...you are lucky that almost everyone on this planet is incompetent).

It's Okay to Code on Nights and Weekends [...] most of the engineering org quit and mentioned it was because they couldn’t work with me in their exit interview

"Not only do I avoid using LSP features, but I’m also opposed to their use. While they can help with navigation, they may prevent developers from experiencing and addressing the underlying structural issues in their code."

I'm 100% sure I could write Git itself without any trouble whatsoever (assuming I learned how it worked first).

To Rust advocates, you can have the US government and big tech. You can even have Linux. Just leave my existing C++ process alone.

It's tedious by design. Modern language utilities like filter, map or reduce are considered too complex for go, and simple for loop is preferred instead.

As Graydon worked harder, he envisioned code as not just a sequence of instructions but a symphony of performance and security. And so, our hero was born — Rust, a programming language that fused systems-level programming with unparalleled safety and speed.

These days it should be considered immoral to write software that uses inefficient languages/runtimes/abstractions, we simply cannot afford to waste energy doing useless computations anymore.

NATO Military Chief Says Troops Would Be on Ground if Not for Russian Nukes

Note that a declared type of "FLOATING POINT" would give INTEGER affinity, not REAL affinity, due to the "INT" at the end of "POINT"