• 2 Posts
  • 17 Comments
Joined 2 years ago
Cake day: July 7th, 2023
  • Schal330@lemmy.worldtoProgramming@programming.dev•need advices
    4·
    1 month ago

    I’m in my late 30’s and I’m a junior dev, having been in the role for just over a year. If you are persistent you can do it. From my experience it has been a hard and at times frustrating job simply because there is so much I don’t know, but that comes with the reward of the eureka moment, where when something works it is one of the best feelings.

    Now in terms of doing a school, if it’s a scheme where you pay for the training and they say they’ll get you a job at the end, please be cautious. I have a few friends that went down this route and they say they were the lucky ones to land jobs, but in their groups everyone else was left out in the cold at the end.

    This was just my process but I did the Java MOOC course that taught me enough to get going, I was doing this at the same time as working in IT. It’s completely free. For frontend learning I’ve been using Scrimba which has free content but also a paid for subscription, it has been alright and the way they merge the recordings with the IDE is good and the free content feels more substantial than what you’d get with Codecademy.

    I’m still just a noob at all of this, and there is so much I don’t know but I’m happy to try and answer any questions you have.

  • Schal330@lemmy.worldtoProgramming@programming.dev•Why Learning to Code is So Damn Hard
    111·
    1 month ago

    Over a year in as a junior dev and I’m still in the second stage. I did 6 months backend and now I’m now entering my 6th month as frontend. I still know so little, but I know more than I did yesterday.

    My biggest challenges:

    • I don’t know what questions to ask when it’s about something I don’t know.
    • Having a rough idea as to how I want to try and solve a problem, but not knowing how to code it
    • Trying to retain so much new information on a daily basis and then remember everything from the days before
    • (What I hope is) Imposter Syndrome on a weekly basis

    I just keep on trying, try to understand what I can and ask for help when I feel I’m at a blocker.

  • Schal330@lemmy.worldOPtoProgramming@programming.dev•Software Engineering Documentation Best Practice?
    4·
    4 months ago

    Thanks for this. As part of onboarding I have been trying to update where I can. There are times I wonder if I am adding to docs what others may perceive as fluff as it may be something obvious to them. I like to work with a “If we’re all on a bus that goes over a cliff, does someone new have everything they need?” mentality.

    At present the team is using GitHub Pages, which almost feels like a hurdle itself in updating the documentation quickly and keeping it organised and consistent. Being a junior I personally prefer a WYSIWYG. From your experience is there any pros/cons in using a WYSIWYG vs Markdown?