|
Camps cram a language into your head in a short amount of time and leave you believing you know what you're doing. To be fair, people do come out of these camps knowing a language, but my experience in interviewing these candidates is not a positive one.
Unfortunately, the compressed time schedule leaves no room for the really important things -- thinking and problem solving. These are learned with practice and experience. A new college grad who spent 8 semesters learning programming has had to solve numerous problems -- and has had the time to reflect on what worked, and what didn't. This takes elapsed time and realistically, most people need 1 to 3 years of professional work experience to honestly understand what they are doing.
That said, I give all candidates a fair hearing, and if they demonstrate problem solving and ability to think, their background is far less important.
Take a couple of free Intro courses to see if you want to do this.
|
|
|
|
|
Amen.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
LoganJM wrote: I currently live in Toronto
Which is where CodeProject is based ...
|
|
|
|
|
.. and yet: itself[^] ... flys the American flag. Must be an Iron Maiden fan.
|
|
|
|
|
If I recall correctly, US was the default country when you sign up.
Either that or he subscribes to the "America's Hat" theory.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Habs ... wow, that sounds racist doesn't it? I'll show'em ... "I had no intention of whiting any sepulcer in the posting of this comment". There. Habs.
|
|
|
|
|
Or during these days, “America’s Hat” conspiracy.
|
|
|
|
|
RedDk wrote: Must be an Iron Maiden fan
There's obviously some reference I'm missing here. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Elodia too!
|
|
|
|
|
2 for 2, you're batting 1.000.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
lol, it's definitely the default country. I changed it now :p
... and I'm definitely not an iron maiden fan.
|
|
|
|
|
Take a look at: best-websites-to-learn-to-code[^]
A lot of these websites are free, but of course you need some self-discipline to complete.
If you are more ambitious and want a certificate, EdX might be a good choice, the courses are free but you will have to pay for the certification.
More information here: learning-resources[^]
|
|
|
|
|
Thank you!
Ambition isn't a problem for me, I'm good at setting tasks for myself and working to complete them on a daily basis and am able to keep a pace over time well enough. But I also want to maximize my time and chart a somewhat efficient course towards employment at some point.
I know I'd rather focus on building things, (apps/web), as opposed to mining blocks of code for data, but that is still obviously a pretty wide open statement.
If employment is the ultimate goal, would you suggest EdX or some of the tutorials on slant? Or both? I'll be taking my first steps in actually learning in the next week or two, regardless of what I ultimately gravitate towards, but I'd also like to maximize the usefulness of the commitments I'll be making towards learning after the initial introductions.
|
|
|
|
|
If employment is the ultimate goal, a course that offers a certificate like edX seems best to me.
However web development is a broad subject, and you will have to learn several languages and preferably some SQL.
It makes sense to find out beforehand where you want to work and what technologies are used, there are also lists with the languages that are most in demand, see: index | TIOBE - The Software Quality Company[^]
Good luck, hope you don't get too scared 
|
|
|
|
|
Ambition is not the issue.
The real issue is the ability to handle stress and frustration.
At a certain point, and it WILL come, you are gonna face a period where you get stuck.
All programming languages and the development environments you use have the ability to frustrate you with the most simple things.
I wish you good luck with your ambition, and I hope that you are not giving up.
|
|
|
|
|
This is what I think...
First Thing To Do
Ask yourself what you'd like to build.
Do you just want to build a game? Is gaming your thing? Then start a simple project that allows you to build a game.
Would you like to build a journaling app? Something where you could save daily entries that store your activities? Then start a project that does that.
My point is that _programming is boring_ (for the most part). So you got to...
Keep yourself interested.
However, if you choose a project and try to get to it, you very well may fail (simply because you don't have the skills yet).
That's why the second thing you have to do is:
Don't View Missing the Goal as Failure
Even if you don't make it to the goal you will have learned a lot.
The Project Will Guide You
IF you do this, the project will guide you through learning the basics :
setting variable values
control structures (for, while, if, etc)
etc...
A Lot of People Who Just Try to Learn To Program End Up Quitting
Programming is full of nit-picky details and annoyances and options.
That's why if you just try to learn to program you may very well become bored and quit.
So, start thinking of what you'd like to build and then go build it.
Which technologies to focus on first?
I suggest HTML5, JavaScript, CSS.
Why?
1. It's everywhere. You can show your friends what you've done by loading it in a web page.
2. You don't need any special tools (just web browser and text editor)
3. No need to learn deep details (yet) like program compiling etc.
Beware JS!
However, as you start out with JavaScript, just beware. You can learn bad practices and do things that work that create problems in the future. Later you'll take the next step, but for now, just learn to get things working and promise to learn later why things should not be done certain ways.
Good luck.
PS - If you need some ideas of interesting projects, post back and I'll give you a couple.
|
|
|
|
|
Thank you so much!
I know of a few things I'd like to build already. I definitely want to build an odds website for sports metrics, (I'm a big leafs fan) and I have a couple ideas for different apps that I would personally find useful.
I sat in on a couple bootcamp recruitment video calls, and a lot of the instructors mention the same thing in regards to bad practices. It is something I'll have to be conscious of.
|
|
|
|
|
Related to raddevus's comment: find project's you like and find out what it took to make them. don't guess; even write to the companies to find out.
|
|
|
|
|
I agree with the above. However, I took a different path. I got a book like O'reilly's C# book. I created every example in the book from scratch. Most of them didn't compile, so I fixed them. Once I got it to run, then I moved on. Just reading the book, I wouldn't have learned anything. When one book was done, I grabbed the next.
My list of "things to learn" would include XML, SQL, and a C-based language (like C++, C#, or Java). Almost no matter what you are working on, these will be useful at some point. Many other skills and concepts build on these 3 basics.
As for SQL, don't worry about the advanced stuff, but at least learn the basics. Everything uses SQL at some point. There is a free version for all the major database management systems (DBMS) (Microsoft, Oracle, MySQL, etc.).
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
|
Matt Bond wrote: I agree with the above. However, I took a different path. I got a book like O'reilly's C# book. I created every example in the book from scratch.
Great point. I did the same way back in the day to learn C++ (with my trusty Dummies book).
|
|
|
|
|
Well said. You covered some thoughts I had but above and beyond and better than I would have been able to. So, yes, ditto on this. OP, you are probably going to want to go with web skills and yes, pick a project to help you learn. And always make sure to learn how (the tools, and get setup) to debug your code as you will hit a wall otherwise and not know how to overcome it - a debugger will bust through that wall and keep you moving.
|
|
|
|
|
Kent K wrote: And always make sure to learn how (the tools, and get setup) to debug your code as you will hit a wall otherwise and not know how to overcome it - a debugger will bust through that wall and keep you moving.
Agree 100%! Great addition. 
|
|
|
|
|
If its JavaScript you want to learn, as reported in one of our Newsletters recently, Microsoft has a free 51 part course on JavaScript at Beginner's Series to: JavaScript | Channel 9
Also intro to C# C# 101 | Channel 9
And starting at Page 3 of the Shows Listings, there are a number of free video courses on a number of topics and languages.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
When I first got into programming, what fascinated me was not the tools, but how you had to approach the problem in a very analytical, systematical manner. Break down the problem at hand in well identified sub-problems, in multiple levels, and understand how those sub-problems could be solved and combined into a complete problem solution.
I was fascinated by the formal, systematic approach to problem solution. Not by the tools themselves. There was recently another thread, about "The no-code dream". I still have that dream - that you don't have to have an M.Sci in programming to do something useful. Anyone with a full understanding of their problem, and with a full understanding of the solution to it, should be able to realize this solution without the help of any M.Sci programmer.
We are not there yet. Not even after fifty years of programming. Yet I just can't let go of this idea that the first and foremost responsibility of software developers is to help the customer understand his own problem. And then to help him devise the solutions required. Once that is in place, any coder may code the solution.
Making the customer fully understand his own problem, and then helping him to an understanding of the solution, does not have to require an M.Sci in programming (although to me, that was what taught me analytical problem solving methods).
I think far too many students (and more today than a generation ago) come to programming because they are fascinated by the tools, rather than by the challenge of problem solving regardless of tools.
Maybe you should seriously consider where your interests lie. You may aim at being a super-coder, caring just so-and-so about the customer's real problem, or you may focus on the problems, giving less attention to the wars between different languages and platforms. A generation ago, I think an education in programming was mostly program oriented, but today it is tool oriented. The tools have become so complex that you do not have time to worry about the customer, if you want to be fluent in all the platforms and frameworks and tool suites...
If that is what fascinates you, then you may of course go for it (and for a degree in programming tools), but even though I do have a Master's degree in that direction, I certainly wish that I had been much more focused on solving problems in the domain of the customer, rather than solving tool problems.
|
|
|
|
|
Saying "I want to program" is like saying I want to cook; then asking what to cook.
You at least need to start with what "type" of cooking: French, Asian, Italian, Fast, Cheap, etc.
You narrow your options by picking a "genre", like: scientific, gaming, data analysis, business apps, etc.
Then you can refine your plan and pick a learning strategy.
(Coding is not fun if it's your only job and you're not making money with it.)
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
modified 8-Oct-20 18:19pm.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
