Yeah he doesn’t.

… But he still should, if he knows what’s best for him

Sadly is the only article on there

Guess what? Just use curl

Yes, but it’s “oh”, not “oo” (as in football)

So it’s read “foh-oh”. If you want to be correct, it’s “Fou - barre - base” (“foo - bar - baz”)

I love git flow but the GitHub tooling is bad. It forces you into GitHubflow which is very confusing for those building from source

I LOVE TRAITS. YOU’LL HAVE TO TAKE THEM FROM MY COLD DEAD HANDS

[Insert SpongeBob screaming meme]

It’s lolcat for “borrowing”

I personally don’t see it?

CSS in JS match the style more closely imo

I have yet to hear a good reason to use tailwind instead of a CSS file

And windows want to go that way…

TBF it could be hidden behind a fancy spinner, making you incapable of seeing what the AI is generating, like devin.

For exemple: https://www.youtube.com/watch?v=927W6zzvV-c

You say tasteless I say dark humour

I feel this pain. Having to deal with an inheritantly sync database in an async app is painful. You need to make sure at no point the transaction is stopped, make sure to set the timeout to a reasonable time instead of an iPad kids’s attention span, and a whole deal of other things

Can’t wait for turso to be stable.

I am guilty of this but for a different reason: setting up debugging for clis in rust is hard

I love the debugger. I use it all the time I can. But when debugging cli it’s a pain as you need to go back in the launch.json file, remake the argument list, then come back to run debug, find out why tf it doesn’t find cargo when it’s the PATH… again, then actually debug.

I oversimplified it but the actual process was to zip files to send to an FTP server

The cron zipped the files to send in the same directory as the zipped files, then sent the zip, then deleted the zip

Looks fine, right? But what if the FTP server is slow and uploading take more time than the hourly cron dispatch? You now have a second script that zip all the folder, with the previous zip file, which will slow down the upload, etc…

I believe may have been started by an FTP upload erroring out and forcing an early return without having a cleanup, and progressively got worse

… I suppose this happened. The logs were actually broken and didn’t actually add the message part of the error object, and only logging the memory address to it

Well it’s not that simple… Because whoever wrote that made it way too complicated (and the production version has been tweaked without updating the dev too)

A clean rewrite with some guard clauses helped remove the haduken ifs and actually zipping the file outside of the zipped directory helped a lot

Oh no need. The client didn’t noticed anything in 6 years, and the reason why we had to check is because they wanted us to see if we could add this feature… That already existed.

Meanwhile, had to debug a script that zipped a zip recursively, with the new data appended. The server had barely enough storage left, as the zip took almost 200GB (the data is only 3GB). I looked at the logs, last successful run: 2019

TBF, if your step by steps instructions works, it doesn’t matter how complicated the command is.

Oh come on! I at least type the beginning so that it filters the history