Recently had the fun experience of merging two C codebases at work and in the process implemented a sort of encapsulation and split high-level vs low-level control/logic. It's probably not the greatest implementation of these designs, but for a hand-rolled design, I'm pretty happy it works as well as it does.

Might have to look at setting aside time to write something up I can share. If y'all happen to know any good references for this sort of thing, I'm interested.

@OpenComputeDesign It's pretty simple, though not always logical:
* Insurance is sometimes state mandate gambling, sometimes just gambling that you won't need a large amount of money to fix certain problems

* laws are about control, always were, but some of them are hard to argue against

* credit score was likely initially meant as an objective measure of loan risk, and just became a good enough metric for other shit, like how social security numbers are terrible at their current use

Hot damn, I saw notifications blowing up while on vacation, pretty wild few days it seems

Had a great vacation with my girlfriend though. And then discovered that a pipe sprung a leak when I was getting ready to go back to work. This week's been way more stressful than normal

Following on this: the past few days I've been rewriting a build system. Rather than take the time to write out all the target combinations by hand, even with a good dash of magic macros, I settled on writing a Python script that generates another POSIX Makefile. So there's more process spawning than is ideal, but now it's like 10 lines of declarations or less to add new build configs that track dependencies and updates automatically when needed.

All POSIX and Python3.

Turns out a good portion of what I do at work is write programs that write programs. I should really look into finding excuses to get paid to work on making simple compilers/interpreters

@inventor this is a place primarily for tech, usually best to use the content warning system to let people know if you're straying into political discussions.

@BrodieOnLinux That's why the last good OS was OS/2

@OpenComputeDesign sounds like you need some practice... or maybe a better mentor

It's super fun seeing comments in code, comments you wrote, warning future devs not to repeat the mistakes seen in some file... repeated verbatim in new projects because the old code that mostly worked by mistake has been inherited to curse an all new dev team.

On a related note, I should find some time after making a simplistic #rust version of netstat(1) to figure out how the hell macros work in that language, since there seems to be some near-identical code paths that might be able to get folded (at least from a source code perspective) if I can't come up with a better solution.

@OpenComputeDesign might need 2, or n, but I'm sure it'll happen

Hello again fediverse, I've missed seeing what you wonderful people are up to

@BrodieOnLinux my package manager does that, and I'm happy to defer trust to the maintainers for most things I don't end up writing myself

It's been interesting working with #rust. Still don't like it as much as C, especially when you can leverage structs, unions, and more complex type aliases with `typedef`, but I've got to admit that traits make some aspects much nicer, like dropping a complex struct into a `println!()` call instead of always printing out fields directly (or writing your own wrapper(s).

@lattera gonna need new toilets on the 5th floor to boost productivity

@anjune Computer Information System