Details
-
AboutSoftware ?
-
SkillsLaTeX, TS, NodeJS, C/C++, Java, a bit of C#, tell recruiters I have never heard of JS to avoid the slightest possibility of having to use it.
Joined devRant on 3/22/2023
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Discords update "policy" is really annoying.
I daily-drive Manjaro and discord refuses to allow you to log in with an older client version when they release an update.
Manjaro's stable takes about two weeks to catch up so when this happens I'm stuck looking for an alternative way to update.
Usually I go for the AUR or (if available) unstable branch package but today the AUR wasn't up-to-date yet when I encountered this problem.
This is a minor inconvenience and was fixed about an hour later when the AUR was updated with the newer discord-electron-bin but I just don't get discords game here?
Why not allow the previous client version to connect and alert users of an available update like any other sane chat application does?
You could go for a time period like two weeks or a month and AFTER that start forcing users to update. I don't get why they force it the instant they release the update.
Just wanted to share this annoyance here, maybe someone encounters this possibility when designing update cycles for their application. I urge you not to instantly lock-out older versions. It's annoying, useless and restrictive. Or if you do so, opensource it so repositories can immediately build from source and sync and don't need to wait for a maintainer to update the bin in the repo.23 -
Massive backpain yesterday. Was okay when I woke up but still 4/10. Went to the gym. Pain is gone. Yay3
-
> Get sent to local client that manages most services on prem themselves
> We just deliver the software and setup instructions, client is self-proclaimed "technical enough" to handle the rest
> Never had issues with them, client for about 1,5year, we assume they are indeed technical enough
> Local client needs me for some help with their "backup solution"
> Cron job that dd's entire disk every week to external ssd.
> External ssd finally caved in after what was most likely years of torture
> Has nothing even remotely to do with our software (which has built-in backups, which they apparently don't use)
> I get scolded and screamed at when I say not our problem
Fml2 -
They told the intern to "just rebase". The unflawed masterminds of HR also gave the intern more permissions than they did me on Stash.
Now I can't even fix our interns "just rebase" without waiting two days on a permissions ticket.
It's going to be a good week. 😑2 -
Markdown is useful for a quick note, AsciiDoc is useful if you want to go a bit deeper into customization and features.
But I find myself reaching for (Xe)LaTeX quite often once the document I'm trying to compose requires even a little custom content. Am I alone in this? What's your favourite go-to for quickly setting up not-so-standard documents?5