Across this vast Fediverse, I have encountered a trend of people answering questions with esoteric programming language speaking in tongues that I don’t understand, including under my own posts. I am a Boomer when it comes to coding and I am only 27. I don’t even know where I would start to learn it because programming is so diverse. I want to feel like I know what’s going on but I don’t. Coding is the future and the future is now and I am lagging severely behind. I guess I’m asking where a bumbling novice like me can learn more about where to start when it comes to programming.

  • @[email protected]
    link
    fedilink
    English
    15
    edit-2
    11 months ago

    Try “the Odin project”, which has an amazingly active community.

    But before you try too much, once you’ve learned to set up any programming tools, just use them to have fun. Find a way in which you can use programming in relation to your hobbies.

    With JavaScript you can manipulate any webpage you see or create your own interactive webapp. Even if it’s just a few ugly buttons and text fields, you could make an app that calculates good builds for a videogame you like, for example.

    If you want to interact with a windows operating system you can’t go wrong with C# using visual studio. This will literally allow you to manipulate files, folders or automate anything you want from the operating system.

    Try to find something that is fun and just enjoy yourself with small apps before you try to go too fast.

    • Xylight (Photon dev)
      link
      fedilink
      English
      411 months ago

      I agree. I can only learn languages by having an idea of something that’ll excite me. Making a to-do app rarely teaches me anything since I don’t have fun doing it.

      • @[email protected]
        link
        fedilink
        English
        2
        edit-2
        11 months ago

        Sorry for the late reply. If you’re interested in music, you could give both javascript or C# a try. C# works integrated with the operating system and is not sandboxed by the browser, which means that you could do nifty things like actual sound processing and interact with sound devices etc.

        In general you will want to start with a console application that receives user input, does something and even prints the output. Let me give you an example of playing an audio file in C#

        LINE 1: System.Media.SoundPlayer myAudioPlayer = new System.Media.SoundPlayer(@"c:\mywavfile.wav");

        LINE 2: myAudioPlayer.Play();

        In the first line we are calling a pre-existing blueprint (library) that knows how to create an audio player. This blueprint can be located in System > Media > SoundPlayer within the collections of libraries. We are giving this virtual audio player a name and called it “myAudioPlayer”. Then, after the “=” sign we are giving it the instruction to be created with a preloaded file that would be found in “C:\mywavfile.wav”.

        In the second file we are commanding our newly created virtual audio player and telling it to play the file. Please note that this audio player would not have a visual interface yet. You would hear audio coming from the speakers but no way to pause. Fortunately C# / .NET (.NET are the pre-existing libraries that you can use), has a drag-and-drop way to create windows application interfaces with buttons via the “Visual Studio” editor, so you could potentially create a drag-and-drop interface and bind a button with a Stop symbol to the instruction “myAudioPlayer.Stop();”

        This is just a very very basic example, but object oriented programming often boils down to this: create virtual representations of something and then command them to do something.

        If this has peaked your interest check out this playlist of a full complete programming course in C# which is what I used to learn programming years ago. https://www.youtube.com/watch?v=umAcMO3d9_E&list=PLFqasLx4-AErVMCWiIyJe9uA3yQMPBukG

        In the end it’s all about creating a series of instructions that the computer will follow. The trick is to learn what these instructions mean and to not be scared by their syntax, because behind every scary looking syntax there’s just an instruction that can be explain in human language.