12

Stuck in tutorial hell....
I have a list of ideas for applications I want to create but I always feel like I never know enough to start them. So I end up signing up for another tutorial from most of the popular sites to only skip pass all 50-60%. Has anyone ever experienced this? I'm open for suggestions to get pass this!!

Comments
  • 6
    Yes. Honestly the best way to learn is just to start and learn as you go. I find it much more efficient than tutorials.
  • 3
    Welcome to devrant by the way :)
  • 0
    Thanks!! Been using the app for a while but just lurking in the shadows. Finally had something to rant about haha.
  • 1
    Well, i think you should just start, but decide for one way to go and build the app to finish in that style, if you choose something else later as you learn, you build version 2. :)
    Good luck! You will learn alot!
    And there is always help to get a google away :)
  • 2
    Do you all think it's okay to use React or Angular. Only reason I say this is because I'm a year out from getting it of the military and I need to build up my resume lol.
  • 1
    Whats more fustrating is when the solution descriptions out there are identical as the rest of the million of examples out there. I need a barney style examples for oop, c# and big O.
  • 1
    @gato-negro I've been running into a lot of tutorials that are just not update to date that's what lead me to the original question lol. I think I'm ready to struggle with the first project though, just need that "slap in the face" to get it done haha
  • 1
    There is noone who can answer that question here, that depends on your requirements (what app you are building) and of course your experience with it.
    But i think if you are interrested in that technology, go for it! And explore its boundaries! Next time you will know if it was the right choice or not :)
    You will always in anyway have gotten one experience richer!
  • 1
    @marcusp619
    Me too. 6 months out. Have you looked into the MSSA program at your post/base/airfield. Im currently doing a cohort at Bragg.
  • 0
    @gato-negro never heard of this thanks I will look into this!
  • 2
    If you have good idea but don't know how or where to start, I always find it helps to have a good plan, mockups and a list of utilities and/or packages that may be useful to that project... Sometimes it's difficult to build something programmatically when you don't have something visual to stimulate any type of structure to what you're doing. Start with something like Balsamiq and progressively build up the task, and when you're ready, focus on one thing at a time, the fundamentals, and get those nailed down...
  • 1
    1. Google: <language> "quick start"

    Read the tutorials/docs and see some sample projects

    2. Read a book that overviews the language. Should take maybe a day at most, should be trying and applying it to ur own app while you read. You can skim and pick only the stuff you actually need to use.

    The idea is still get enough so you can get started and learn as needed.
  • 1
    Also list ain't good. When I start any project, I outline and design the general components. Basically a top down plan. I know all the steps and what I need in general.

    Then I pick the most appropriate language to implement them in.

    Finally, I learn just what is needed to start and keep learning while I'm implementing each step.
  • 1
    To sum it up, it's basically problem solving. And first step is defining the problem.

    If your can't define the problem even if you start, you're probably going to be "solving" the wrong one or get side tracked by things that don't actually matter or need. This is actually a problem in the professional world. Users don't define what they want, results in a lot of wasted work, rework, bloated messy code, delays, and me wanting to punch someone.
  • 1
    @billgates hahah that is understandable. I will definitely utilize this. I'm actually sitting down right now putting the pen and paper to work trying to organize everything I want to accomplish in the web app, but also trying to restrict myself to things that are achievable without too much headache and then I can work on the other features I want add in later.
Add Comment