D is more than 20 years old (from 2001), so it’s due for a renaissance, Python was also in its 20s before it became fashionable.

I remember when sourceforge was a good place to get windows software, as I recall it took over from Tucows.

I like to treat warnings as errors and refuse releases with errors.

Occasionally I disable single warning in a specific file because it does not make sense.

Using TODO also makes sense, I’m mostly used to seeing them years after when debugging.

In your case it sounds like you may end up ignoring all the TODO’s as too many of them become noise. I would instead disable the specific warnings in the compilers options, instead of in the code, and then deal with the remaining.

Later you can disable one warning at a time and fix it.

What about GPL and BSD licensees, they could also be there, maybe they are still being kept back with the missing 3+ million files.

In Linux you get zombie processes hanging around when things go wrong, and you can’t get rid of those.

I definitely got weirded out asking a GPT3 model about something and it got clingy.

Now I see it more like a search engine, skim the wall of text to find the useful information. Today I gave it a lot of context and explained what I had done and the error I got and it more or less told me you did everything correctly, and suggested stuff I already tried. It’s way of saying “I don’t know”.

Can’t wait for vibe coded programs to use timeoutSort.

There’s always fraud…

Find a way to borrow against or short your technical debt and buy a small country.

Recently I roo-coded a node.js MVP without knowing too much about Node, but something about JS/CSS/HTML although it’s years ago I last used it.

I got something working decently by:

• Make a project plan and use cases
• Take (very) small steps
• Commit often
• Throw away bad attempts
• Make test cases
• Hand edit from time to time, especially CSS stuff.

Would I have been able to fling something together by reading some node.js guides and using stack overflow yes, would it have taken around the same time yes, but without test cases and documentation. Do I think vibe coding is the best thing since sliced bread no!

I mostly use git from the console.

• git with a bunch of aliases for common operations and making the log pretty.
• gitk when I need a UI to browse the history
• kdiff3 as mergetool

And then assign an int to a string just to mess with the interpreter.

Breaking news: New Delhi just discovered AGI, she is called Chetana…

LGTM 👍

Footage from a robot in skynet mode:

!it’s from the movie Runaway 1984!<

It’s time to sell your tesla stock and invest in cocaine!

Hear me out, what about using JSON to store the configuration in the Python backend?

Cool, good to know.

I wrote a script to do backups on a ESXi it uses Busybox’s ASH, one thing I learned after spending hours debugging my scripts was that ASH does not support arrays so you have to do everything with temporary files.

It took a while for me to get it, but it still read ngnix as “n.g. -nix” in my head.