I’m a Christian, a dad, an open source fan. I have a blog: https://daviewales.com/

  • 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle


  • Reformed Christian. I was raised in a Christian family, and always believed in the basic concepts of God, heaven, hell, etc. But I mistakenly thought Christianity was about trying to be “good enough” for God until my mid teens. Around this time I realised that I couldn’t be perfect, which was super distressing for a time. But then I read Ephesians 2:8-9 which says:

    For it is by grace you have been saved, through faith—and this is not from yourselves, it is the gift of God— not by works, so that no one can boast.

    This was a big relief, as it meant that I didn’t need to rely on trying to be good enough for God. I just needed to accept God’s free gift of salvation. That’s the moment I would say I became a Christian.

    Since then, I’ve had times where I’ve questioned it all, but I always come back to the resurrection of Jesus. I find the non-miraculous explanations of the resurrection account to be so implausible that it makes more sense to accept that it’s a historical fact. And if the resurrection’s true, then it makes sense to believe the rest of it as well.



  • Depends what you’re trying to learn, and how much of a beginner you are. If you want to learn the shell, try the Software Carpentry tutorials:

    If you know the basics, you might try honing your skills with CLI Mystery (murder mystery puzzle).

    You’ll probably want to learn how to use the following:

    • SSH
    • Command-line text editor. Choose one of the following:

    The final tip is: It’s usually better in the long run to spend 2 hours reading the documentation than 2 minutes searching the web. Reading the documentation helps you to understand the big picture, and gives you a much better foundation. Of course, if you’re reading the documentation and don’t understand something, searching the web is an OK way to figure it out.





  • I mainly use Python, so my workflow is the same on every OS: Neovim and a shell, usually one of each in a vertical split. This transfers nicely to remote SSH sessions too, and even works in Termux on my phone!

    Have you investigated whether it’s possible to test your cross-compiled builds in Qemu, rather than copying them to the host?





  • The first step is to make sure your hardware is supported. I’ve found the linux hardware database to be invaluable getting new systems configured. The site is overwhelming at first, but the easy path is to just click the big ‘Probe your computer’ button and follow the instructions. Once you’ve done a probe, you’ll get a web-page with a listing of all your computer’s hardware and the support status. Even better, you get links to additional drivers or kernel modules required to get stuff working which isn’t supported out of the box.