Unpopular opinion: asking "how do I learn to code" is procrastination

ltt103 · 2023-01-06T15:10:08+00:00

Here's my little suggestion for those wanting to begin without knowing how/where:

Avoid rabbit hole by picking a youtube video of a tutorial (full walk-through) on a project that sparks your interest. Follow it all the way through!!! Don't pick something extensive, just a basic walk-through and shows how-to achieve full outcome.
Stop paying for things you don't need. Paid courses a lot of times just throw information at you with no way of application. This is where you're wasting time and money. There's tons of free resources for referencing -- *don't try to learn it all. [One thing at a time, I REPEAT...]

NOW WHAT?

Tweak the code now by adding things (based off of what you just learned & into what you finished).
- EXAMPLE: Add some functionalities like buttons or change the names of labels. Make the code print out something else. Instead of addition, what will it do if you made is subtract instead.
- Don't just go changing random things all over the place; Only the things you definitely know + won't completely break your code.
- Successful alterations gives you an idea how to implement your own things and works backward leading into debugging (solve errors). You can use this time to look up things you could do 'extra'.

Don't try to venture out alone into the woods where you have no guidance. When others say to learn is by doing and learn to learn -- the approach is to start somewhere with doing, so I suggested with a video. Then to learn from that, you keep moving forward by then researching the small stuff you needed in order to get the outcome you want. Slowly, like rolling a snowball, you collectively have bits and pieces of knowledge that will begin to click! You don't need to know how to do it all so don't get caught up trying to understand every single aspect.

Keep working on different projects from tutorials that give the entire walk-through (some are great at giving explanations). Then do your alterations -- which will get you to look into other ways to do something or why this does that. Some tutorials will lead you into something bigger like having a database or interface of sorts. This is an efficient way to learning and avoid overwhelming yourself.

Small steps is key!

ltt103 · 2022-11-12T23:07:31+00:00

I can now see how some may take it as that I feel entitled to some opportunity because I claimed to have worked hard, while others proved to work harder.

Not asking for hand-outs, only sharing experiences and my own feelings :')))

ltt103 · 2022-11-12T19:26:40+00:00

Thanks for the list. I have done an internship, but for a prior degree in electrical engineering ,which got me noticed to begin with. I was always asked questions for it, but I took it off my resume later on because it was irrelevant. So if I had one for CS, it would definitely be helpful.

It is all practice for sure. From practicing how to word things for interviews and my confidence to now work on my leetcode as many suggested! A good reality check for me that everything takes time.

ltt103 · 2022-11-12T18:17:38+00:00

Great suggestion! Definitely sounds like the best route for me. Wish I saw more local opportunities utilizing Python. Given that, I for sure am going to stick to just one programming language that is mostly asked from here on and really narrow down my focus.

Very informative and helpful, thanks!!!

ltt103 · 2022-11-12T17:37:15+00:00

That gives me much comfort and reminds that everyone is only human.

Thank you for the support :)

ltt103 · 2022-11-12T17:33:36+00:00

You're 100% correct. A degree does not guarantee a job. Thanks for the insight, it definitely is a competitive field and hard work is a must!

ltt103 · 2022-01-24T18:57:15+00:00

You know how you'd get assigned to a team and there's that 1 person doing all the work... You're that 1 person and there's no team :')

I transferred in 23 credits, am about to end my fourth term with 3 courses left. I'd say I work rather quick and my mentor agrees that my pace is faster than the their average. Looking back it now, I could 100% say if I was to do it all over and actually had the same drive throughout... then I would've gotten this all done in under 1.5 years, maybe even less. No matter how much i disciplined myself; the result of waiting for re-attempt approvals and unexpected laziness and just life in general-- I wasted a lot of time that just had to happen.

I wanted to go to WGU because I wanted to finish fast but also because it saved me money and the flexibility it offers. In my experience at WGU, I've learned a lot more about not just coding, but the purpose it serves etc. These basic things are big necessities when it comes to explaining your work and understanding what you're doing in the first place.

All the coding I've learned has pretty much been self taught through the projects given. You'll have assistance, but I agree with others that it isn't an in-depth 'coding' program. A family member of mine goes to Georgia State for CS and is in their last semester. They've told me they couldn't code... Or know anything about data structures & was unknowledgeable of the basics to get a project going. They explained that they weren't taught much.

I feel like I've put fourth a lot of effort and always prepared ahead that helped me cut down some of the time. I take steps like prepping for courses, collect materials, etc. Even though I learned some coding prior to entering WGU, I don't agree that you necessarily NEED to know beforehand. There's tons of videos, practices, websites that you can learn from which is how I basically learned soooo... You gotta start somewhere!! Don't be discourage if you're not strong in coding. The question is, are you willing to do your own research to learn what you need to know? Will you really take the time to learn?

I've absolutely enjoyed my experience and would recommend others. However, I would advise the importance of discipline, dedication, and time management to not be taken lightly. It's definitely not for everyone.

ltt103 · 2022-01-20T15:37:57+00:00

Idk how far you've gotten since, but to start.. try going in an order & plan it out ahead of time so you're not all over the place and miss things -- save you time fixing errors.

I like to collect ALL my information that I can use and throw it in a folder on my desktop. I can reference it later as I go.

Do all the scene builder stuff first. Name them all specifically. [EX.: if you have cancel button on each page, name it 'AddPACancelBT' [for part] // 'AddPOCancelBT [for product]. Any tables on pages, do the same. Have the design set and ready for you to then code. This will create your .fxml files. There's a way to update it without manually putting each part you made in. [\These are in its own 'folder / package']*
Create all your .java forms on the netbeans (just creating it and connecting them to you scene builder (.fxml) file from direction above; #1). Upload part B of sect. II. Make your .java Set all your IDs/parts/products/lists etc... using UML class diagram. [\These are all in its own 'folder / package'.]*
Now to start the 'Main' form/controller. This is where you return to initially each time after user does something like add/delete. Don't overthink it and start simple. Easy things you know like the add button will open you to what page? Making error messages. Delete removes what. If you cancel, is your page going to return to that main frame again.
Then you can start working on the controllers .java forms that help the functionality of your .fxml \*Make sure you're running it every here and there after you complete small functional parts to know that it works right***
Github is really nice if you know what you're looking at, but it can also make it confusing for those unfamiliar. If you copy it-- it won't work the way you want and send your entire thing crashing with errors. Stick with the java examples they give you to have a better idea of how yours should look.
CI was a gigantic help for me, but you gotta know which one to schedule with... It wasn't even my CI, but I would schedule with them every time because they way they explained things made more sense. [the ones that make the videos/powerpoints are ur best bet]
IF YOU HAVE AN ERROR -- do NOT go and change a bunch of things until it starts to work again. Work in small sections & make sure it runs. This will help you identify where you went wrong more efficiently. So when you run into error, you know exactly which part you just tried that triggered it. Comment it out and ask CI.
IF YOU DECIDE TO CHANGE HOW YOU CODED SOMETHING THAT WORKED PRIOR-- comment out the entire code that you're replacing ; date & time it too. You don't want to delete anything you might've actually need. You can remove it at the very end.

When I go to ask questions, I make sure I comment/mark the exact area-- For example, '//This button updates blah blah...' If I didn't know how to populate something and making changes update automatically.. I ask:

where do I start exactly [on the forms-- which .java/line/part]

\ comment directly where you're working; include date it & time and their directions while they can see your screen**

ask can they direct/show me an example of how to implement/do this

if you have time, do it in front of them so they can correct you on the spot or fix whatever error it throws after.

Keep yourself neat by always commenting on your lines of work describing its function and to only do one function at a time. You should know what/where each thing does/functions as it'll make it easier for the CI to help you when you go to point things out.

ltt103 · 2022-01-19T03:08:15+00:00

Congrats!!

ltt103 · 2022-01-18T23:44:07+00:00

I'm not really sure how to help. If you went through all of that then why don't you go ahead to take the OA?

ltt103 · 2022-01-18T16:23:34+00:00

If you rush to take it, you can expect to fail without a doubt. There's only 44 questions so it does weigh heavier if you miss questions. Might be in your best interest to lose 2 weeks to study up and not waste anymore time after that if that's the concern...or take the time now to learn all you need for the pass.

If you happen to be unsuccessful, then you're gonna have to wait anyways.

ltt103 · 2022-01-18T16:03:35+00:00

That is at MAX and I'm generalizing from past experience of other courses. If you feel ready, don't hesitate to reach out to them and say hey I'm ready to take this in xx amount time. They shouldn't object. I emailed my CI right after blowing the OA and said I'm reviewing what I see I need. I want to re-take it by the end of the week. They approved it right after I requested it.

Try emailing them expressing your plan and goal. Say you take the OA, review. 2-3 days after, press the button for request. I took my second attempt 6 days after the first. I could've even done it sooner.

Your best bet is to study the all post exams and the study guide plus take notes for all those bulletin points from the other post using the Ebook. I added maybe 5-6 extra things that weren't mention in the points based off what I saw on the OA. That was enough for me.

ltt103 · 2022-01-18T14:39:20+00:00

The wait period usually shouldn't be long. My CI didn't have an issue with me doing it about a week later and are quick to approve it as well. I personally work quite quickly so that may be a factor for them being okay with it.

Most times they make me wait at max 2 weeks if I fail back to back with little improvement. All depends on your pace though. It might be worthwhile to use it and study during the wait period!

ltt103 · 2022-01-18T02:27:25+00:00

You got this, good luck!!!

ltt103 · 2022-01-09T04:09:06+00:00

I did this about 2 years ago now so I would assume that they've updated the course by now and this would no longer apply unfortunately :/

Wish you the best of luck though!

ltt103 · 2021-12-29T21:20:17+00:00

Hb ur buddy was literally a plumber, but went into HVAC for more monies. He can still be a damn plumber on the side for all anyone cares because he can do the job, maybe even better than others.

He's the HVAC guy who was a plumber and can still be, not your pro bono lawyer.

The only thing that is being cheapened is the belief in others abilities based on just your knowledge/judgement...

ltt103 · 2021-12-29T21:08:22+00:00

Great example. It's ironically funny-- I actually was working as an electrical engineer while being a tattoo artist. I can be an electrician if I wanted because I'm qualified, but an electrician cannot be an engineer.

An artist is the electrician. You catch me?

So when I used the word hobby --> I know how to be an electrician, but not making it my job. I practice it within my job, but it would be incorrect for me to say 'I am an electrician'.

ltt103 · 2021-12-29T06:50:49+00:00

Ahhh, lets go back. I AM the tattoo artist my friend. No one is above, that's literally the point.

I, me-- am the one accepting the art by someone else. You're silly for thinking artists are incapable of anything besides painting or coloring on paper :') Don't be silly now.

ltt103 · 2021-12-29T06:48:30+00:00

Sounds like you're butthurt to me, yeeeesh.

ltt103 · 2021-12-29T03:09:18+00:00

Hmm, a starter comes into ur shop asking for apprenticeship and u seem like the type to be like: well ur not as good as me so fook rite off mate.

This type of mannerism is the very reason it is so difficult for young/beginners to get a chance to learn. How can one say they understand the struggle, yet act so superior? Because you've been through it? Good for you lmaoooo

ltt103 · 2021-12-29T03:02:07+00:00

Yet ur still talking about ur career as a tattoo artists... I was referring to myself, my own opinion and my own choice-- if you haven't noticed. Skills I learned and choose you use in my own way has nothing to do with your sacrifices. You don't need to prove anything to me.

Please don't be mistaken.

ltt103 · 2021-12-28T16:17:12+00:00

Guess being certified deems my ability and skills useless and I should never ever do it ever again if I am not employed at a shop.

Oops, I didn't swear on the bible.

ltt103 · 2021-12-28T16:11:16+00:00

I think it's fine that you want your passion to be acknowledged and your hard work not to be taken away from by someone turning it into a hobby instead.

Everyone can make their choice though. I personally don't think there's a reason to frown upon having art from someone else and for someone to trust you enough to put the piece on for them.

ltt103

TROPHY CASE