• 0 Posts
  • 440 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle







  • It doesn’t have to be one or the other. It’s just a rhetoric that was jokingly pushed on back when communication wasn’t worldwide, immediate, and lacking context. It has now been repeated ad-nauseam by people that have no idea of why it was said in the first place.

    Some GUI tools are efficient. Some CLI tools are efficient. Sometimes, both are efficient. It depends on the tool AND the task at hand. Unless you’re taking internet memes at heart, then use whatever.

    Well, to be honest, I do sometimes mock (in a friendly manner) some coworker that are using GUI almost exclusively. The only reason I do that is because the exact same task could be accomplished in a fraction of the time with minimal CLI knowledge. But even then, it gets the job done.







  • When it gets to the point where it does work to produce usable documentation, without extraneous content, with no mistakes, can be checked quickly, and it is faster to generate + check than to write it, maybe. Assuming a stellar history of being correct from the tool.

    As it is right now, once you reach the point where you actually need proper documentation to be written to keep things maintainable, these tools have low accuracy, lots of issues, and using them takes longer than it takes a competent person to just write/update whatever needs to be.







  • Technically, all the boot options were on the same drive (same EFI partition, on the disk that was initially used for years by windows), but for some reason, the motherboard decided “nope, there’s no bootloader there”.

    I ended up repartitioning the “first” drive seen by the bios to make a 100MB partition at the beginning, named it “EFI system partition”, copied all the content of the old one from the other drive, and nuked the actual windows install in the process (not the boot entry though). Now all is good… I hope :D