r/javahelp • u/Grewal_Creator • May 29 '21
As a Programmer How Much Should I Know?
Hey im 18 and ive been programming for about 4 months now making some small projects and following youtube videos to make programs. Ive gotten a decent understanding of the basic concepts in java and im able to use them but when asked to make certain programs i get confused and have no idea what to do. How much should i generally know as a programmer with my experience? and what programs do you recommend i build to test my abilities?
15
u/AccomplishedHornet5 May 29 '21
Hey kid you're definitely asking the right question at the right time! Hope someone gives you a good answer. I coded java w/GM for 3yrs and I can only tell you what I saw.
Everything we did was Spring framework and there was a high demand for CRUD operations on OracleDB. End users never cared about the technicals as much as the UI/UX -- probably 65%UI/30%functionality/5% on-time delivery.
Fair warning: A Comp-Sci degree won't teach you to be a better coder. It'll teach you to understand what makes the languages work -- which makes you a better coder. Some of the best on my team were heavily into Assembly in college.
Good luck and never stop learning!
As for me, I'm going back to my supply chain roots because jumping into OJT programming with nothing but CodeAcademy was a bad idea at 30.
3
u/fluffytme Java dev May 29 '21
Just wanna second this. If your goal is to do Java in the work place, the majority of companies will use Spring
2
u/JasburyCS May 29 '21
Fair warning: A Comp-Sci degree won’t teach you to be a better coder. It’ll teach you to understand what makes the languages work — which makes you a better coder.
I don’t totally see what you’re saying here, so I’d be curious to hear more about where you are coming from. I know different universities are different experiences, but in general here are just a few of my own experiences in a CS degree that helped me learn to be a better coder:
Rigorous projects and trial and error taught me how to tackle problems better and how to design better solutions in code
Professor feedback pointed out flaws in my code or gave me advice on how to write better code
Working in group projects showed me how other people think and come up with different solutions to problems. I could then try incorporating what I learned into my own code
Lectures often discussed design trade offs, pitfalls, language features, and programming constructs that I could use to make better code
1
u/AccomplishedHornet5 May 30 '21
It was an observation from working with a variety of new college grads on a dev team. The ones who went in to become great at java, came to the team as passable professionals. But if you asked them to think outside that narrow band and actually design something they mentally shut down.
The ones who truly embraced comp sci as a discipline were fantastic and it showed. Flexible designers across 2-3 languages, willing to experiment with new technologies, quality checking work for the weaker team members -- including me.
I mentioned it, probably poorly worded, to express an expectation of the discipline in terms of "Computer Science teaches you the science that makes coding work which in tern makes you a better coder." Rather than comp sci will teach you to be a better java coder. Language is secondary to the science.
1
u/JasburyCS May 30 '21
Ahh I see what you’re saying. I like the way you worded this and I agree completely!
1
12
u/throwaway0891245 May 29 '21
I mean, I'm not sure if this is the answer you're looking for - but I remember when I was your age I had this idea of progressing linearly. What I mean by that is that in general, a 12th grader knew more than an 11th grader. You know more in Spring than your did in Fall.
But the reality of programming in the real world is, the depth of knowledge and the areas of knowledge are all over in this industry. It is not correlated with time either. You will find people who have been working a long time that don't know very much about one area of programming - or perhaps not even deeply in any area of software. You will find people even as young as you are that are at the forefront of some push. For example, I'm a fan of the Odroid N2 and there's this very young woman - not even 22, who so far as I can tell is the lead developer for its open source graphics stack. To be clear, I'm not saying this to make you feel bad, this person is far more skilled than I am or perhaps ever will be.
The point is that in my opinion, programming is very much an art - perhaps more than a science. Computer science is definitely a science in that there are quantitative measurements that are definitely shown in the research papers - there is hard theory, provable theory. But programming is very much an art - much like cooking is both an art and a science.
What do I recommend for you to build and to test your abilities? Well, personally, what I'd do is go back to the certain programs you were asked to make - the ones that made you confused - and go back and try to figure out a way to do them. There are certain problems where the solutions that are needed are cutting edge approaches, innovative techniques that make companies millions or billions of dollars. But I'm guessing that these aren't the problems you are talking about. I'd go back to these programs and try to figure it out - introspect, what are you missing - how do you break this down into something solvable? What are the strategies that might help in iteration, what is the background you are missing? For me personally, I've found that these confusing situations yield the most insight - more insight than the mundane or the easy.
But as for how much you should know as someone who has been programming for 4 months, it's hard to say. My hunch is that you already know more than some working programmers, but that's not because you know a lot - it's because there really are some programmers out there that don't know much. My hunch is also that you know less than many working programmers, and that is fine. This is the thing about programming, and also something I've noticed - if anyone tries to tell you their skill by some unit of time, they are almost always not good. Please work hard and try to avoid falling into this group.
1
u/freeBobbyDAYVID May 29 '21
do you have a good understanding of constructors, methods, objects, and instances vs static?
1
u/Grewal_Creator May 29 '21
Yes I do
1
u/freeBobbyDAYVID May 29 '21
https://docs.oracle.com/javase/tutorial/java/nutsandbolts/_keywords.html
my recommendation then is going through here and if you don’t know a keyword, learn what it means and how to use it. maybe you feel different but for me transient and volatile i’d spend some extra time on
and of course the shit keywords (*) like goto just ignore
3
u/_jetrun May 29 '21
How much should i generally know as a programmer with my experience?
There is no such rule. Think of programming as a craft that you spend a lifetime refining. You'll never master it, but you should strive to be a little better every day.
1
u/khooke Extreme Brewer May 29 '21
This. You need to know enough to be able to effectively solve problems. There's always something new that you'll come across, it's a continual learning process. And that's ok. Don't think you need to learn/know 100% of everything because that's never going to be possible.
The other thing to keep in mind is everything in tech changes pretty quick. Trends come and go, new languages and frameworks come and go. Whatever you're learning or using now/today will probably not be what you're using on a daily basis say 5 years from now. Keep learning, and keep growing!
2
2
u/sparkless12 Jun 01 '21
Follow MOOC course. I think what you have fallen into is kinda black hole of programming education. Everyone will tell you how to declare variable, not everyone will tell you how java actually works, explaining environment and what to do when you are past the stage of messing about with variable declarations...
MOOC is great, skip what you already know, work on specific thing that you write down on piece of paper not leaving out any description of functionality of that program.
After 4 months, you know nothing, after 4 years, you will feel you know even less
1
u/dp_devel May 29 '21
You should be enthusiastic and have patience. That's key thing. Start thinking of something you would like to make. Do good google search or post on forum like this to know how would you make that. Start gathering the skills to make that.
In programming there is nothing like how much. Start building now and slowly you would know hoe much practical things you could do. This will make u interested more and gives you knowledge on using google and stackoverflow also provides you with knowledge of taking responsibility from scratch.
Most important things in programming
donot reinvent the wheel
have good knowledge of google search
do not get attached with your code, if you need to erase it to fix it then erase it.
learn to use version system like git, will help you in long run
always be ready to accept you mistakes, if someelse has better way to do something learn it, instead of making a fuss about it.
1
u/Rainbowusher May 30 '21
I am not sure as to your first question. But to your second, try creating the Fibonacci Series, start by just hardcoding a number of times the computer will run the code. Then, try taking input from the user as to how many times the series should go on.
1
May 29 '21
Programming languages are good to know and atleast 1 programming language is necessary to know.
You should exactly focus on those certain programs where you get confused and gain more clarity.
Data Structures and Algorithms is the real deal.
Programmers are extremely clever in handling these problems.
You can then focus on how programming languages inherently handle typical problems (Effective Java book, Design Patterns etc.)
-1
u/Arxidomagkas May 29 '21
At 4 month you should know basic CRUD functionality of at least one framework or the basic equivalent of javafx and how to google/search, the rest will follow through work.
If you really love the subject you'll find yourself searching for more stuff on your spare time in no time.
After that you'll find yourself encountering problems and slowly, the more things you encounter, those problems will have many solutions.
Coding is not what the school teach but what the market wants
•
u/AutoModerator May 29 '21
Please ensure that:
Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions
You include any and all error messages in full
You ask clear questions
You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.
Trying to solve problems on your own is a very important skill. Also, see Learn to help yourself in the sidebar
If any of the above points is not met, your post can and will be removed without further warning.
Code is to be formatted as code block (old reddit: empty line before the code, each code line indented by 4 spaces, new reddit: https://imgur.com/a/fgoFFis) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.
Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.
Code blocks look like this:
You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.
If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.
To potential helpers
Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.