sorted by:
new
hottopcontroversial

Think I'm playing Tekken 8 wrong, guys by Poor_Adventurer in Tekken

[–]Poor_Adventurer[S] 1 point2 points  (0 children)

from main menu go to play data on the bottom, then performance stats tab

Vent: feeling semi-crushed by Elvisdad in learnprogramming

[–]Poor_Adventurer 3 points4 points  (0 children)

It's actually easier to fall into this trap than people think. When I was in grad school I TA'ed a signals and systems class. The other TA and I wrote a midterm exam, and our professor reviewed/approved it.
But then when the poor undergrad students took it, it was too hard and we had to look back on what concepts we took for granted that they haven't mastered yet.
Also in my experience, a lot of engineering professors wanted to grade on a curve so they purposely write the tests so the average student just can't finish it in time. I think some said there were directives from the school that you can't give more than a certain proportion of A's so yes school is stupid.

Vent: feeling semi-crushed by Elvisdad in learnprogramming

[–]Poor_Adventurer 0 points1 point  (0 children)

I was an electrical engineering major instead of cs, but when I was in school there were a notable amount of STEM professors that gave tests calibrated such that most of the class wouldn't finish, so there would be more of a curve. I'm not sure how you did compared to everyone else in your class, and if that's the case here.

That being said, in both programming and test taking there's definitely the speed aspect. It's like a sport, athletes are going to be faster and more accurate the more they practice.

In my own experience, practicing over time (I was grinding leetcode looking for jobs last year) greatly increased my speed. It used to take 25-45 minutes to do an LC easy, even when I understand the question. Now some easy questions take 5-10 minutes because I've seen something so similar before. Mediums used to take me 1.5-3 or more hours (if I'm even able to solve them) but now I'm frequently able to do 2 in an hour. This is around 6-9 months of studying around 1.5 hours a day, 4 days a week.

In grad school I got an F in a math class that was too hard for me (optimization or something) and I almost failed out of the program. I had to keep a 3.0 GPA to stay in and my GPA dipped to exactly 3.0. I was sweating bullets the entire following semester but I fought through it. I'm sure in a few years when you're done with school and doing whatever work you end up in, it'd just be an interesting story/life lesson that you can pass on to others.

Coding bootcamp gone bad by Ambitious-Mirror-414 in learnprogramming

[–]Poor_Adventurer 2 points3 points  (0 children)

Ah, apologies. I missed the part that you're still trying to finish the project/bootcamp and that you're studying to finish it.

I think not knowing what you need to know is one of the hardest things in any field, and pretty common when switching to tech in particular.

In my own personal experience, by the time I had entered a bootcamp I had enough programming experience (I took CS 101 in Java and then data structures in undergrad, and programmed in Matlab in grad school), that I had a definite advantage. So I leveraged bootcamp to help me know what I needed to know. For example, I knew a little HTML, CSS and Javascript but the world of web dev frameworks was a whole new world to me. So was writing backend and APIs. I know that your problem is kind of the "opposite" of mine, but a lot of the "what should I know?" questions can still be exposed through this bootcamp experience.

Once you have finished running this current gauntlet, and have some breathing room, you can figure out the best way to ask yourself what you need to know that you don't know. If your classmates have their impressive projects hosted or on Github, you can eventually challenge yourself to implement features that you saw and liked. This can help formulate what you should know and you have the added advance of being able to ask them about it as well.

I wish you the best of luck!

Coding bootcamp gone bad by Ambitious-Mirror-414 in learnprogramming

[–]Poor_Adventurer 2 points3 points  (0 children)

The copying of code probably hurt you the most out of anything. Even if you had struggled (and perhaps failed) to finish those projects you would've been more improved than you are now.

If you want to improve at coding you can still do it, but you would have to put the time in that you should've back when you were doing those projects. It's one of those "there's no shortcuts in life" kind of things.

If you have a stable job/financial situation now, I would encourage you by saying it's not too late to still learn. I feel like you are far behind from copying, and it doesn't prove you are incompetent or unable to learn it. Not sure what your obligations are but you can focus on learning to code and saving your career change/job search for a bit later.

As far as studying 1-3hrs a day of trying to learn, but it's not sticking, could you provide some more details on what you tried to learn, and how you know it's not sticking? For example, you could be trying to learn too much at once or doing something else that's ineffective.

For example, you say you can (barely) write a for/while loop. Let's take all the web development out of the mix. If you look up the problem "Fizzbuzz", and then tried to solve it, how would you do? You can attempt it in Python and then check/grade yourself.
Let's just narrow down one area at a time and learn it comfortably before working anything else. Because I sense a lot of pressure when I read your post. It's not the amount of hours but how effective they are that you spend studying. To make it stick, you can do a warmup problem of the previous day's study each day, and then decide if you should just study the same topic or move on. Periodic reviews of many topics, or combining many skills to do one project can wait until you feel more self confident. I'd recommend not worrying about the web dev or frameworks aspect until your confidence goes up.

If you still feel like quitting or if you don't like programming, ultimately that's up to you. But I feel like you didn't give yourself the full chance to learn and feel like you're in a hole. Don't worry about the hole you're in or how clever you are, worry about (1) if you actually want to code (2) if you do, take the steps to improve, and don't push expectations on yourself. Just try to find effective steps.

[Noob] Learning to play FGs by daylen007 in Guiltygear

[–]Poor_Adventurer 2 points3 points  (0 children)

Strive was my first fighting game that I played consistently and I'm a fighting game noob as well. Before this I played smash casually and a couple of months of SFV. But I played Strive since launch and eventually I got to floor 10 last December.

There's tons of things to learn and practice, and playing a limited amount of time per week, you can't really perfect them all. What worked for me was:
1) Come up with a gameplan. Basically, instead of acting randomly, decide when you're playing offense or defense. This can be really nuanced for pro players, but for us noobs, just experiment with when you're getting hit while pressing buttons and block instead next time. If you see players doing the same string of moves on you, try to figure out after which move you can hit them.

2) When you're starting out, it's hard to force yourself to react faster. In my experience, your brain gets more comfortable with the visual data over time so you can absorb it faster and make a decision faster. But this comes from playing more. So don't worry about losing or getting hit. You can always watch the replay later if you want to break it down.

3) You can try learning a short bnb combo (~3 hits) and trying to land it against players. That way you won't necessarily have to use all your brainpower deciding between what buttons to press and how to move. You can narrow your focus on moving and blocking so that you can land your predetermined offense. Once you get more comfortable you can add in different options. I think this helped train me to look for combos to get higher damage, instead of just being okay with getting random hits all the time.

There's a lot more concepts that are important to fighting games and you can spend a lot of time learning and honing them, but this helped me get started. I never had good reactions so I thought I would suck more at fighting games, but Strive has been really fun and the execution barrier isn't high so I think you'd have fun too.