

Maybe pls for the su command?
Futility is resistant


Maybe pls for the su command?


I use Joplin daily, but its main disadvantage is the huge resource footprint, specially compared to a regular text editor with markdown highlighting.
The main advantages are that its cross platform, mobile, self-syncable, and E2EE. I think it’s better then even Obsidian.
Mermaid support is the cherry on the cake, although I still use a simple text editor for quick markdown notes.
My first package manager was YaST, then RPM, then APT. Apt rules, and while I’ve tried some more, I’m not afraid to say APT became my comfort zone.


Yet they never explicitly state you’re allowed to make convenient assumptions. If the bulb was out of hand’s reach the problem would be unsolvable.
Assuming the electrician that wired the switches is in the room would be even a more out-of-the-box solution.


The biggest flaw is that it assumes you’ll add conditions you’re not explicitly told are allowed. Many, many problems in school would be trivial if changing the terms beyond what’s stated was allowed.
“Dude, where is nesc? Haven’t seen him for a week”.
“Oh, it’s the month of the year where he isolates at home to upgrade his numerous custom/made Linux boxen”


Whatever your place defines as a standard. I’ve seen ugly code in C, JavaScript, Java, etc., that uses them all over the place because they’re not mandatory.
If you don’t have consistent indenting, your code looks like copy/paste from several sources; but if you do have consistent indenting, then the indenting of Python is a non-issue.
Linus Torvalds pissing from the ceiling on everyone:
I don’t use Linux, I make Linux.


This meme template never gets old for me.


I seriously doubt your quality is maintained when an LLM writes most of your code, unless a human audits every line and understands what and why it is doing it.
If you break the tasks small enough that you can do this each step, it is no longer writing a full application, it’s writing small snippets, and you’re code-pairing with it.


Software engineering is a mindset, a way of doing something while thinking forward (and I don’t mean just scalability), at least if you want it done with quality. Today you can’t vibe code but proofs of concept, prototypes that are in no way ready for production.
I don’t see current LLMs overcoming this soon. It appears that they’ve reached their limits without achieving general AI, which is what truly would obsolete programmers, and humans in general.


Not possible, neighbor implemented Negative Trust.


Real programmers will write in a way that user’s resources are not being wasted because you need a full browser, a JS runtime, and DOM juggling, to show even the simplest application.
It’s not rare for simple JS applications to consume over half a gigabyte of RAM on startup, and way more CPU than their native counterparts. That this was normalized and even defended is stupid.


Comments and full-length names make the source way more accessible.
Ubuntu LTS? It can still have rough edges depending on your hardware, but solve them and you got five years of peace.


If they accepted the job, absolutely yes. ignorantia juris non excusat.


I’ve been happy with Calibre Web and downloading to the official reader apps, but I’m open to try new things.
What strikes me as odd is why starting a Java software in this day and age. Java in the server is the COBOL of the 2000s, mostly used for legacy software.
How dare you assume their gender? They are now referred to as theyists.
Real masochists: CubeOS
For Steam games.
To be fair, LLMs do really good translations, but as with everything you use them for, you need to be familiar with the subject so you catch their mistakes.
I’m thinking beginner level so the LLM can support instead of replacing you while you get better.