|
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.
|
|
|
|
|
listen to this person!
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
|
Back in the day I started with a book. I bought books on C then C++ and learned the basics from them. A lot cheaper than boot camps. After that I started taking CS classes at the local college where ever I was stationed at in the evening. Never finished my BS in CS but have been working as a dev for over 20 years now.
|
|
|
|
|
Everyone has their own preferred way of learning, but I strongly prefer tutorials in which I set up a compiler or IDE on my own computer and create a functioning app. You first need to decide what interests you, pick an appropriate language, then pick a tutorial.
|
|
|
|
|
|
There are many ways to change careers and become a successful programmer. I have trained dozens of programmers using this method. It is not the quickest, nor the easest but all of the people I have trained have ended up being successful senior and principal-level programmers at major software companies.
The first step you should take before you even begin to think about programming is to learn how the computer hardware is organized, how information moves between disk, memory, video, network, and so on. Either sign up for an introductory computer hardware course or read some of the tutorials about CPUs and computer hardware that are freely available on the internet.
The next thing you should do is learn some assembly language. You don't need to spend a lot of time on this a few hours and writing a couple of hello world type apps will suffice. Your goal is to understand what the language the CPU understands and what it can and cannot do. This provides you with a foundation on which you can build your skillset.
The next step as many have stated is to decide what area of programming you want to focus on. Learn all you can about that area. While you are doing this read lots of code. Yes, read code don't bother about writing it yet. While you are reading other people's code spend some time analyzing it. What did the code do well? What might have been done differently what problems might exist? What do the authors say about their code? This will help you to understand how code is put together, how it solves problems, and increase your knowledge of algorithms. While you are at it get the Algorithms in C (Computer Science Series). Study all of these.
Finally, pick a program in your chosen area to solve and begin designing a program to address this area. Figure out what options should be available, how these options will work, and how they connect together. How will information be stored? How will it move from place to place? What will the user experience be? Once you think you understand how the program will work and operate you can begin writing it. Expect your initial progress to be slow, expect to discover that things don't work the way you thought they should. Regardless, keep at it. Eventually, you will work through the issues, learn a lot about programming, and build confidence.
At this point, you can start looking for entry-level positions in your area of expertise. Open source and publish your solution. Many employers love being able to see good code and documentation as it lets them understand how you solve problems and the quality level of your code.
If your solution is complete, choose another problem in your chosen area and repeat the process. Keep learning and adding to your knowledge.
One thing to note, your computer programming language is less important than being able to solve problems. Most computer languages now days are similar and have similar structures and concepts. Most are variants of C or C++. There are differences of course and each language has its own unique attributes but if you know how to solve programming problems you will not have any trouble moving from one language to another.
|
|
|
|
|
While I'm still fairly green myself, I find actually creating something is the best way for me to learn. I would think of some project you would like and start to build it. I also might suggest even starting with Arduino. It is very satisfying to code something and see the results instantly. It is C and C++ based IDE that is free and and easy to use. The Arduino microcontroller are very cheap. As some others have said it's not learnig the language but rather problem solving.
Bryan
|
|
|
|
|
|
Google copied some "method names"; Oracle says, you can't do that, those are "our names"; our vocabulary.
So, next time you decide to "build a better mouse trap", but use the same "word" to talk to it, I'll sue your **s off.
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
|
|
|
|
|
Gerry Schmitz wrote: I'll sue your **s off.
Maybe wait for the result of the G vs. O case before suing.
|
|
|
|
|
I was being rhetorical. Myself, I couldn't care less or have the time.
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
|
|
|
|
|
|
Do remember that the only people who get rich buy sueing is ... lawyers.
There was a British legal dispute between three brothers over their fathers will which ended in 2006: after 43 years, all of the estate had gone in legal fees and none of them received anything ... two of them had already died by that point!
"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!
|
|
|
|
|
I don't think it's about the money; it's seeing what you can get away with (and $9B). They're peeved that Google has Android. This is like WINE and Parallels.
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
|
|
|
|
|
|
Unfortunately we have the precedent of Lotus vs. Osborne's Paperback Software. OPS had a Lotus clone (menu structure) and lost this suit even though the underpinnings in the code were completely different.
|
|
|
|
|
The crux appears to be whether an API can be copyrighted, even if its implementation is independent of the original.
|
|
|
|
|
So along this line of thinking, if GM had come up with the automatic transmission and the letters "P R N D", Ford would not be able to come up with its own transmission with those same letters?
This is beyond ridiculous.
|
|
|
|
|
There was some discussion of this yesterday, which you might want to read. I gave some examples why I don't think it's necessarily ridiculous, although it would definitely depend on the specifics.
|
|
|
|
|
The problem is that google did use some of the code verbatim, and there is also legal precedent where code doesn't have to be a verbatim copy to violate copyright, it only has to be largely the same otherwise you could change some variable names and claim the code is yours. There are also licensing issues where many APIs want you to use them, Oracle don't want you using java for commercial purposes without a license so rather than pay for the license google adapted what was essentially a fork of the code and used it for commercial purposes. There is a lot going on basically, it's not as simple as "APIs can't be copyrighted".
|
|
|
|
|
|
To be honest... I don't care about google or oracle.
But...
Quote: More importantly, an Oracle win could reshape how copyright law treats APIs, giving incumbents the power to lock out competitors who want to build compatible software.
...
It could also directly affect the livelihoods of computer programmers, who might find they are more frequently forced to learn new programming languages or other software tools when they switch jobs.
This is what I fear.
Quote: The distinction between a program and an API makes intuitive sense to computer programmers who regularly use APIs (and write programs) in their daily work. But it's far from obvious to Supreme Court justices, all of whom are lawyers over the age of 50.
Exactly what I meant the other day in the other thread here in the lounge.
And coming up next...Quote: This is a widespread practice in the software industry. Oracle, for example, re-implemented Amazon's S3 API so that customers who built software for Amazon's cloud platform could easily switch to Oracle's rival cloud platform.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
We ran out of toilet paper and started using lettuce leaves - today was just the tip of the iceberg, tomorrow Romaines to be seen.
"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!
|
|
|
|
|
And someone above just yelled: lettuce have papers
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
