Sock Puppet Society@lemm.ee to Linux@lemmy.mlEnglish · 22 hours agoA big part of learning Linux is screwing up computers and starting over.message-squaremessage-square64fedilinkarrow-up1209arrow-down16file-text
arrow-up1203arrow-down1message-squareA big part of learning Linux is screwing up computers and starting over.Sock Puppet Society@lemm.ee to Linux@lemmy.mlEnglish · 22 hours agomessage-square64fedilinkfile-text
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up22·21 hours agoAnother big part is learning how to set it up in a way that it’s functional and productive the first time and then STOP FUCKING WITH IT.
minus-squareAda@lemmy.blahaj.zonelinkfedilinkarrow-up6arrow-down1·20 hours agoThat also sounds like a good way to stop learning!
minus-squareumbrella@lemmy.mllinkfedilinkarrow-up3·11 hours agoyou can either have a system to learn on, or a stable system to work on.
minus-squaredeadbeef79000@lemmy.nzlinkfedilinkarrow-up4·17 hours agoNot quite. But sorta, yeah. Learning to “not fuck with it” or ways to do so and rollback are valid lessons themselves. Being able to segregate “production” and “development” environments is very valuable.
minus-squareFauxLiving@lemmy.worldlinkfedilinkarrow-up3·15 hours ago Being able to segregate “production” and “development” environments is very valuable. This is a best practice that pretty much everyone, eventually, discovers on their own.
Another big part is learning how to set it up in a way that it’s functional and productive the first time and then STOP FUCKING WITH IT.
That also sounds like a good way to stop learning!
you can either have a system to learn on, or a stable system to work on.
Not quite. But sorta, yeah.
Learning to “not fuck with it” or ways to do so and rollback are valid lessons themselves.
Being able to segregate “production” and “development” environments is very valuable.
This is a best practice that pretty much everyone, eventually, discovers on their own.