buserror

I did the same, also, the fact the tools evolve so fast, I dont want to waste time on a particular one while it might be obsolete next week. So either it works now, other I pick something else.

There was a well known Firstclass server in France in the 90s called Ellis, dedicated to everything Apple/Macintosh. I still have real-life friends I made back then on that server.

Damn, just when we of the emulator and vintage stuff scene thought we were safe using the old colors as they hadn't any relevance anymore, booom, it suddenly becomes trendy again.

Modern transceivers can do 10G on absolutely garbage twisted pair. My house was wired with absolutely dire cat5 cabling. Zero shielding and barely any copper in the pairs. I thought I'd barely be able to do 1G on them, but modern transceivers (amazon) easily do 10G over like 30M of that sort of cables.

In fact I had more trouble getting quality fiber working for that sort of distance than El Cheapo cat5. They do heat up a bit, but they work wonder.

I got fired off pair.com because I had a wildcard email, and was receiving (and to my credit, discarding) millions of emails... a day... on my personal domain. Whoops.

I still use my super optimized c++ email filter to this day, 25 years later. Beats anything else I ever tried.

Thank you for not calling film photography "analog" -- I've been at it for 25 years and I'm also an engineer, and I cringe still everytime I hear/read "analog" photography, while there are plenty of accurate adjective that could be used. Like, as you did, "film" or "chemical" or even "Silver" as the french do.

As for medium format, there are hundreds of Folding cameras that are pretty much as good as the obvious massive SLRs people are so keen on. I own and use a dozen of them, some of them absolutely legendary, like Zeiss Ikontas or Super Isolettes or the russian Iskras and Moskvas.

Quite frankly, having owned a few SLRs myself (I only kept a Bronica S2A with a 50mm lens) I more often than not use the folders because, well, for one thing I can literally have 3 in my bag with 3 different films! The good ones are as good or better than the SLRs, and as long as you don't mind a fixed lens, they do the job very well and often as way more character than the "system"'s ones.

Keep on rolling :-)

At last, something that isn't about python!

:>

Thats why they've been increasing the service interval to silly numbers. 3 years ago, 10k miles, now... 18k miles for the same model of car for the first service! Absolutely insane.

Another thing if you are recovering and have limited dexterity in your hands, after trying pretty much ALL the voice recognition I could find, the VScode/copilot assistant is the best by far!

I've now recovered enough that I can type/edit faster, but I still use it; I keep a Worksheet.md tab around and keep a whole running log of stuff, LLM prompts etc

Had a stroke 2 months ago at 55, after an entire life (professionally since I'm 16) as a dev. I mostly followed these rules apart from when I got dragged into a project that was sufficiently interesting that I started overworking. 12-14h days.

Just don't do that. I used to do that just fine and that's why I thought I was OK. I mean, I USED to go on in huge coding benders, did'nt I ? Well apparently not at 55, when the pressure has been on for months instead of weeks.

Other things to watch -- diet! With the work came less free time, put on weight etc and all the good habits I had built for years, disappeared.

And the worst bit you can think of is "Oh but I'm so CLOSE to being done, I'll just fix it up later when I can relax". Just don't.

I lost all sensation on the right side. It is coming back slowly. I can still work, didn't lose speech or mobility or strength, I consider myself super-mega-lucky in that.

Pro tip: Do not use on your internet router if it is ALSO the DHCP server, as the JetKVM is by default DHCP (with no backup fallback to a LL address) so if your server somehow needs serious attention...

Well yes, your JetKVM no longer has a lease.

Don't ask me how I discovered this one :-)

No they won't. I've seen them coming a looooong way. I even re-baptised arduidiots [0] quite a while ago. Since the "branding" fiasco I've stayed well clear of them.

[0]: https://github.com/buserror/simavr/blob/master/examples/shar...

I use NFS as a keystone of a pretty large multi-million data center application. I run it on a dedicated 100Gb network with 9k frames and it works fantastic. I'm pretty sure it is still use in many, many places because... it works!

I don't need to "remember NFS", NFS is a big part of my day!

I'm amazed to see kids and adult wearing shorts going out for forest walks. We are in an area of dense woods filled with deer, and even the fields are full of sheep that also carry ticks... There is zero awareness in the general population of the dangers of tick bites!

Same here, nnn feels so much lighter too. It also works out of the box, no need to carry around "your" .rc file on dozens of systems as you work

I have a debian box I installed in 2002. Trust me, it works :-)

Interesting, I actually do have a coding-guidelines.md file for that purpose, but I hadn't thought of having the LLM either generate it, or maintain it; good idea! :-)

In my experience, this is a problem without LLM anyway; many times you cannot just tell coworkers (junior, or not) to completely trash their patch and do it again (even using nicer words).

Very often it comes down to HR issues in the end, so you end up having to take that code anyway, and either sneakily revert it or secretly rework it...

Ahaha you likely haven't seen as many Junior Programmer as I have then! </jk>

But I agree completely some juniors are a pleasure to see bloom, it's nice when one day you see their eye shine and "wow this is so cool, never realized you made that like THAT for THAT reason" :-)

I personally treat the LLM as a very junior programmer. He's willing to work, will take instructions, but his knowledge of the codebase, and patterns we use is lacking strongly. So it needs a LOT of handholding, very clear instructions, description of potential pitfalls, and smaller, scoped tasks, and reviewed carefully to catch any straying off pattern.

Also, I make it work the same way I do: I first come up with the data model until it "works" in my head, before writing any "code" to deal with it. Again, clear instructions.

Oh another thing, one of my "golden rule" is that it needs to keep a block comment at the top of the file to describe what's going on in that file. It acts as a second "prompt" when I restart a session.

It works pretty well, it doesn't appear as "magic" as the "make it so!" approach people think they can get away with, but it works for me.

But yes, I still also spend maybe 30% of the time cleaning up, renaming stuff and do more general rework of the code before it comes "presentable" but it still allows to work pretty quickly, a lot quicker than if I were to do it all by hand.

Also, make it it auto-pushes somewhere else, I use aider a lot, and I have a regular task that backs everything up at regular interval, just to make sure the LLM doesn't decide to rm -rf .git :-)

Paranoid? me? nahhhhh :-)

Same here, I also have a env key which I use with Aider. Mind you aider+gemini has gone excruciatingly slow these days.

Have you tried Fluorocarbon? this has replaced Nylon for many fishing use (fly fishing in any case), it has a different refraction index -- not sure if it would be closer, or further from the resin, but at least it is different! :-)

Very nice article, seems to mention all the modern bits that helps making makefile so, SO much easier than in decades past...

The interesting bits are for example the -MMD flag to gcc, which outputs a .d file you can -include ${wildcard *.d} and you get free, up to date dependencies for your headers etc.

That and 'vpath' to tell it where to find the source files for % rules, and really, all the hard work is done and your 1/2 page Makefile will stay the same 'forever' and wills still work in 20 years...

Well apart from tinc, which has been doing that for decades [0] :-) -- and has been doing that since Linux was something that still ran on 8MB of RAM.

[0]: https://www.tinc-vpn.org/

The hilarious bit is that this page will soon be scraped by ai-bots as learning material, and they'll all learn to draw pelicans on bicycles using this as their primary example material, as they'll be the only examples.

GIGO in motion :-)

I am absolutely amazed at the amount of garbage being "logged", enough that it is not just a huge business, but also one of the primary task for some devops guys. It's like a goal in itself, you have a look at the output and it is absolutely scary, HUGE messages being "logged" for purpose unknown.

I've seen single traces over 100KB of absolute pure randomness encoded as base64... Because! Oh and also, we have to pay for the service, so it looks important.

Sure they tell you it is super helpful for debugging issues, but in a VERY large proportion of cases, it is 1) WAY too much, and 2) never used anyway. And most of the time what's interesting is the last 10 minutes of the debug version, you don't need a "service" for that.

/me gets down his horse :-)

While I don't use UTC for my local devices, I use UTC for any logs on remote machines, servers etc. It solves all kind of problems of trying to remember or have to care about where they are (I have machines in multiple time zones).

But yes I wish sometimes everyone had one standard time, trying to book a meeting with Chinese people AND west coast people while I am on the GMT line are a nightmare, as it isn't even the same day anymore!

It is entirely possible the IT was outsourced to the highest bidder, probably with limited liability clauses etc etc. See Post Office for reference, they are still reaping contract money out of the government, years after having been proven as responsible for ruining people's lives for decades, and coverups.

Works! Thanks for spending the time replying :-)