|
Thread Rules 1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution. 2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20) 3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible. 4. Use [code] tags to format code blocks. |
On August 15 2013 16:37 WolfintheSheep wrote:Show nested quote +On August 15 2013 16:22 Tobberoth wrote:On August 15 2013 15:53 WolfintheSheep wrote:On August 15 2013 15:44 Tobberoth wrote:On August 15 2013 02:14 enigmaticcam wrote: What's the consensus for HTML5? Is it worth learning? How does it work when the website is data driven? Do you have to learn some other server side language to support server operations? Are there are good resources out there (books, online tutorials, etc) for learning HTML5? I know I can google that last part, which I have and am learning what I can, but I'd like to know what others' personal experiences are with learning or having learned it. HTML takes no time to learn, it's dead simple. Just search on google, find some decent tutorials and you're green. If you want to make a modern web site, especially if it's data driven, you definitely need to know a server-side language as well. Which one you go for is up to you, here's some options: PHP, ASP.NET, Ruby on rails, Django. node.js. Is he asking about HTML 5 or just HTML? HTML5 is HTML. Why would he learn HTML4 when HTML5 is an official standard? I mean, it's not like people ask "Is it worth learning .NET 2.0?". If you learn .NET, you learn .NET, and you obviously learn the latest version. Because quite a few people learned HTML before HTML5 was even on the drawing boards... So you're saying the question is actually "Is it worth taking 20 minutes out of my day to read up on the additions in the HTML5 standard?"?
Because if it is, the question is kind of dumb and the obvious answer is yes.
|
On August 15 2013 16:38 Tobberoth wrote:Show nested quote +On August 15 2013 16:37 WolfintheSheep wrote:On August 15 2013 16:22 Tobberoth wrote:On August 15 2013 15:53 WolfintheSheep wrote:On August 15 2013 15:44 Tobberoth wrote:On August 15 2013 02:14 enigmaticcam wrote: What's the consensus for HTML5? Is it worth learning? How does it work when the website is data driven? Do you have to learn some other server side language to support server operations? Are there are good resources out there (books, online tutorials, etc) for learning HTML5? I know I can google that last part, which I have and am learning what I can, but I'd like to know what others' personal experiences are with learning or having learned it. HTML takes no time to learn, it's dead simple. Just search on google, find some decent tutorials and you're green. If you want to make a modern web site, especially if it's data driven, you definitely need to know a server-side language as well. Which one you go for is up to you, here's some options: PHP, ASP.NET, Ruby on rails, Django. node.js. Is he asking about HTML 5 or just HTML? HTML5 is HTML. Why would he learn HTML4 when HTML5 is an official standard? I mean, it's not like people ask "Is it worth learning .NET 2.0?". If you learn .NET, you learn .NET, and you obviously learn the latest version. Because quite a few people learned HTML before HTML5 was even on the drawing boards... So you're saying the question is actually "Is it worth taking 20 minutes out of my day to read up on the additions in the HTML5 standard?"? Because if it is, the question is kind of dumb and the obvious answer is yes. Well, there's a vast difference between learning some new markup and, say, learning to use HTML5 as a complete replacement to Flash.
That said, the answer is still obviously yes, but it's not quite as simple to learn as making a standards valid website.
|
On August 15 2013 16:47 WolfintheSheep wrote:Show nested quote +On August 15 2013 16:38 Tobberoth wrote:On August 15 2013 16:37 WolfintheSheep wrote:On August 15 2013 16:22 Tobberoth wrote:On August 15 2013 15:53 WolfintheSheep wrote:On August 15 2013 15:44 Tobberoth wrote:On August 15 2013 02:14 enigmaticcam wrote: What's the consensus for HTML5? Is it worth learning? How does it work when the website is data driven? Do you have to learn some other server side language to support server operations? Are there are good resources out there (books, online tutorials, etc) for learning HTML5? I know I can google that last part, which I have and am learning what I can, but I'd like to know what others' personal experiences are with learning or having learned it. HTML takes no time to learn, it's dead simple. Just search on google, find some decent tutorials and you're green. If you want to make a modern web site, especially if it's data driven, you definitely need to know a server-side language as well. Which one you go for is up to you, here's some options: PHP, ASP.NET, Ruby on rails, Django. node.js. Is he asking about HTML 5 or just HTML? HTML5 is HTML. Why would he learn HTML4 when HTML5 is an official standard? I mean, it's not like people ask "Is it worth learning .NET 2.0?". If you learn .NET, you learn .NET, and you obviously learn the latest version. Because quite a few people learned HTML before HTML5 was even on the drawing boards... So you're saying the question is actually "Is it worth taking 20 minutes out of my day to read up on the additions in the HTML5 standard?"? Because if it is, the question is kind of dumb and the obvious answer is yes. Well, there's a vast difference between learning some new markup and, say, learning to use HTML5 as a complete replacement to Flash. That said, the answer is still obviously yes, but it's not quite as simple to learn as making a standards valid website. You have a point, but personally I think it's quite a big difference between asking if you should learn HTML5 to make websites, or learning to program the canvas element in HTML5 to replace flash... The point is that the difference between HTML4 and HTML5 is quite minor, though the possibilities of the new elements are ridiculously deep. However, learning to do those things (such as using canvas) is more about learning javascript than learning HTML.
|
On August 15 2013 16:26 KurtistheTurtle wrote: Actually, I'm gonna go give Effective Java another shot right now before bed. Might actively read it tomorrow if I grasp more this time
Heh, keep at it. When you can go trough it all and understand it I guarantee you will be ready for serious work. I know people that have worked in the industry with java for years, and don't know 10% of the things that book covers. But they should. It's not some exotic knowledge, you need to get this stuff down to be a good java dev (although a lot of what is said there carries nicely to other language, particularly C#).
Code Complete is completely awesome by the way 
For someone asking for book advice you seem to have a very good selection already. And that's coming from someone who reads a metric ton of books each year :D
|
On August 15 2013 16:28 sob3k wrote:OK calling CSS men! I'm working on a drop down type menu. Its basically some stacked Divs that then drop down and unstack when you hover over the top one with transitions. I got it to work but then when you slide your mouse down the menu they wont stay out. I made this all from scratch so its a bit wierd. Here is the html: + Show Spoiler +And here is the CSS: + Show Spoiler +![[image loading]](http://i.imgur.com/w54Eqol.png) ^This is just my divs ![[image loading]](http://i.imgur.com/nPJ11En.png) ^These are to try to keep the menu open when you mouse down it. I can get it to stay open when you mouse over the first div, and the second div, but when you go over the third one the 2nd one hides. Anyone help me out or suggest a much better way to do this? HERE is the little project if you wanna help me and see my cool menu.
Not sure if you are doing this for a school project or what, but the website I run uses a dropdown menu from this guy:
http://www.stunicholls.com/menu/pro_dropdown_1.html
There are several variations, so you can pick what you want, or just look at his css and figure it out if you want to do that.
|
I was asking about HTML5 mainly because I really don't know HTML at all, and wasn't sure which I should invest my time in learning. I've always been a back-end .NET developer, building business solutions that function and produce the right numbers but don't necessarily look pretty. But times are changing and I'm finding more and more that it would help if I knew a little HTML and Javascript to spice things up a bit. Thanks all for your answers!
|
On August 15 2013 09:15 berated- wrote:Show nested quote +On August 15 2013 06:35 one-one-one wrote:On August 15 2013 02:18 obesechicken13 wrote: Question: I'm using Maven and java to write some tests.
I have a class in src/test/java and src/main/java The one in src/test/java imports from src/main/java Then I tried to have the class in src/main/java also use the one in src/test/java
When I tried to run this in eclipse just using testng, it worked. But then I tried to run in maven and it kept saying that my class in src/test/java did not exist.
Are you supposed to have tests depend on resources and never the other way around?
As for tests it is my opinion that the only design choice that makes sense is to design your unit test classes to be optional. You should have build targets that don't build or run any tests. This makes for leaner and faster production releases. This way, your resources must not depend on any test classes. Next thing: Eclipse and Maven integration is a funny story. I would recommend tha you first set up your project to be Maven only, then use Eclipse's method to import existing Maven projects. In a perfect world, or if your project is small, it can work well. You'll have to post your pom.xml file so we can have a look at how you configured your Maven project. I must warn you. If you want this to work well you might need a lot of patience before you get things to work the right way. My recommendation is to do away with Eclipse and forget about full IDE integration. In my experience it works better if you just let Maven work on its own. You'll have to spend a little more energy on setting up a comfortable programming environment and learning another IDE than Eclipse. Eclipse is slow, buggy and never holds up to what it promises to do. It represents everything that is bad with JAVA. What? ... the java hate is just so overdone. I don't think that you necessarily need to setup your project to be maven only, sure it would eliminate the issue because well... you wouldn't even be running the tests with the testng plugin. But regardless of what people try to say, eclipse is a great ide and works well when you understand what its trying to do. The reason that you are experiencing the issues is because of the differences of maven and eclipse. Maven is a full build tool, but eclipse tries to circumvent some of the lifecycles and use their own compilation methods. m2e has come along way but its still not perfect. When setting up the classpath for eclipse it includes all of your dependencies which gives you a false sense of working. If you think about the maven lifecycle, I don't think what you are talking about makes a lot of sense. Sure it makes sense for your test resources to be able to access your source resources, that's the whole point of testing. When you are compiling your code thought in the compile phase it hasn't even tried to process the test files yet. After the tests are run, that's about the extent that those classes get to exist. When you are packaging your project (jar or war), the test sources won't even be included in the package. They are even compiled to separate places (target/classes vs target/test-clasess)
At my previous job I worked with Java EE web applications running on a WebLogic platform. WebLogic integrates pretty well with either Maven _or_ Eclipse. It was pretty much impossible to get everything to play along well. The programmers were supposed to be able to check out code from SVN directly in Eclipse, being able to use all Eclipse IDE functionalities while integrating with a local Weblogic server running on each developers station. The second condition was that the automatic test system was supposed to regurlarly check SVN for commits and then build the whole app using Maven build and test targets and then report eventual failures back to the developers.
This was complete hell for our customer to set up, so they called in us consultants to fix it for them. In the end, both Maven and Eclipse managed to play nice with each other, but I would not recommend anyone to try it out. There was hardly any documentation that covered the whole usage scenario. There was for Tomcat and Glassfish, but not proprietary platforms like WebLogic or WebSphere. It involved a lot of trial and error and guesswork. It is hardly a cost-effective solution for large projects. If you want all this you should probably use the .NET platform instead. Java EE has a lot to learn from Microsoft in this area.
But then again, YMMV. For small project using only open source tools it is much more feasible.
|
On August 16 2013 06:04 one-one-one wrote:Show nested quote +On August 15 2013 09:15 berated- wrote:On August 15 2013 06:35 one-one-one wrote:On August 15 2013 02:18 obesechicken13 wrote: Question: I'm using Maven and java to write some tests.
I have a class in src/test/java and src/main/java The one in src/test/java imports from src/main/java Then I tried to have the class in src/main/java also use the one in src/test/java
When I tried to run this in eclipse just using testng, it worked. But then I tried to run in maven and it kept saying that my class in src/test/java did not exist.
Are you supposed to have tests depend on resources and never the other way around?
As for tests it is my opinion that the only design choice that makes sense is to design your unit test classes to be optional. You should have build targets that don't build or run any tests. This makes for leaner and faster production releases. This way, your resources must not depend on any test classes. Next thing: Eclipse and Maven integration is a funny story. I would recommend tha you first set up your project to be Maven only, then use Eclipse's method to import existing Maven projects. In a perfect world, or if your project is small, it can work well. You'll have to post your pom.xml file so we can have a look at how you configured your Maven project. I must warn you. If you want this to work well you might need a lot of patience before you get things to work the right way. My recommendation is to do away with Eclipse and forget about full IDE integration. In my experience it works better if you just let Maven work on its own. You'll have to spend a little more energy on setting up a comfortable programming environment and learning another IDE than Eclipse. Eclipse is slow, buggy and never holds up to what it promises to do. It represents everything that is bad with JAVA. What? ... the java hate is just so overdone. I don't think that you necessarily need to setup your project to be maven only, sure it would eliminate the issue because well... you wouldn't even be running the tests with the testng plugin. But regardless of what people try to say, eclipse is a great ide and works well when you understand what its trying to do. The reason that you are experiencing the issues is because of the differences of maven and eclipse. Maven is a full build tool, but eclipse tries to circumvent some of the lifecycles and use their own compilation methods. m2e has come along way but its still not perfect. When setting up the classpath for eclipse it includes all of your dependencies which gives you a false sense of working. If you think about the maven lifecycle, I don't think what you are talking about makes a lot of sense. Sure it makes sense for your test resources to be able to access your source resources, that's the whole point of testing. When you are compiling your code thought in the compile phase it hasn't even tried to process the test files yet. After the tests are run, that's about the extent that those classes get to exist. When you are packaging your project (jar or war), the test sources won't even be included in the package. They are even compiled to separate places (target/classes vs target/test-clasess) At my previous job I worked with Java EE web applications running on a WebLogic platform. WebLogic integrates pretty well with either Maven _or_ Eclipse. It was pretty much impossible to get everything to play along well. The programmers were supposed to be able to check out code from SVN directly in Eclipse, being able to use all Eclipse IDE functionalities while integrating with a local Weblogic server running on each developers station. The second condition was that the automatic test system was supposed to regurlarly check SVN for commits and then build the whole app using Maven build and test targets and then report eventual failures back to the developers. This was complete hell for our customer to set up, so they called in us consultants to fix it for them. In the end, both Maven and Eclipse managed to play nice with each other, but I would not recommend anyone to try it out. There was hardly any documentation that covered the whole usage scenario. There was for Tomcat and Glassfish, but not proprietary platforms like WebLogic or WebSphere. It involved a lot of trial and error and guesswork. It is hardly a cost-effective solution for large projects. If you want all this you should probably use the .NET platform instead. Java EE has a lot to learn from Microsoft in this area.
How big was the company you were consulting for? It is true that bigger companies like to have someone to blame, so it's easier to pay for stuff so that way you have support and a scapegoat.
But then again, YMMV. For small project using only open source tools it is much more feasible.
The company I work for isn't large (10 developers), but our software helps run 3 different warehouses, system to system transactions, and a b2b website. We are a complete java shop with git maven and eclipse for local development. We deploy to tomcat servers with jenkins covering all of our continuous integration stuff. I can't say it's all that difficult, but, it's what I learned from the beginning and do everyday so I'm a bit biased.
|
On August 16 2013 11:01 berated- wrote:Show nested quote +On August 16 2013 06:04 one-one-one wrote:On August 15 2013 09:15 berated- wrote:On August 15 2013 06:35 one-one-one wrote:On August 15 2013 02:18 obesechicken13 wrote: Question: I'm using Maven and java to write some tests.
I have a class in src/test/java and src/main/java The one in src/test/java imports from src/main/java Then I tried to have the class in src/main/java also use the one in src/test/java
When I tried to run this in eclipse just using testng, it worked. But then I tried to run in maven and it kept saying that my class in src/test/java did not exist.
Are you supposed to have tests depend on resources and never the other way around?
As for tests it is my opinion that the only design choice that makes sense is to design your unit test classes to be optional. You should have build targets that don't build or run any tests. This makes for leaner and faster production releases. This way, your resources must not depend on any test classes. Next thing: Eclipse and Maven integration is a funny story. I would recommend tha you first set up your project to be Maven only, then use Eclipse's method to import existing Maven projects. In a perfect world, or if your project is small, it can work well. You'll have to post your pom.xml file so we can have a look at how you configured your Maven project. I must warn you. If you want this to work well you might need a lot of patience before you get things to work the right way. My recommendation is to do away with Eclipse and forget about full IDE integration. In my experience it works better if you just let Maven work on its own. You'll have to spend a little more energy on setting up a comfortable programming environment and learning another IDE than Eclipse. Eclipse is slow, buggy and never holds up to what it promises to do. It represents everything that is bad with JAVA. What? ... the java hate is just so overdone. I don't think that you necessarily need to setup your project to be maven only, sure it would eliminate the issue because well... you wouldn't even be running the tests with the testng plugin. But regardless of what people try to say, eclipse is a great ide and works well when you understand what its trying to do. The reason that you are experiencing the issues is because of the differences of maven and eclipse. Maven is a full build tool, but eclipse tries to circumvent some of the lifecycles and use their own compilation methods. m2e has come along way but its still not perfect. When setting up the classpath for eclipse it includes all of your dependencies which gives you a false sense of working. If you think about the maven lifecycle, I don't think what you are talking about makes a lot of sense. Sure it makes sense for your test resources to be able to access your source resources, that's the whole point of testing. When you are compiling your code thought in the compile phase it hasn't even tried to process the test files yet. After the tests are run, that's about the extent that those classes get to exist. When you are packaging your project (jar or war), the test sources won't even be included in the package. They are even compiled to separate places (target/classes vs target/test-clasess) At my previous job I worked with Java EE web applications running on a WebLogic platform. WebLogic integrates pretty well with either Maven _or_ Eclipse. It was pretty much impossible to get everything to play along well. The programmers were supposed to be able to check out code from SVN directly in Eclipse, being able to use all Eclipse IDE functionalities while integrating with a local Weblogic server running on each developers station. The second condition was that the automatic test system was supposed to regurlarly check SVN for commits and then build the whole app using Maven build and test targets and then report eventual failures back to the developers. This was complete hell for our customer to set up, so they called in us consultants to fix it for them. In the end, both Maven and Eclipse managed to play nice with each other, but I would not recommend anyone to try it out. There was hardly any documentation that covered the whole usage scenario. There was for Tomcat and Glassfish, but not proprietary platforms like WebLogic or WebSphere. It involved a lot of trial and error and guesswork. It is hardly a cost-effective solution for large projects. If you want all this you should probably use the .NET platform instead. Java EE has a lot to learn from Microsoft in this area. How big was the company you were consulting for? It is true that bigger companies like to have someone to blame, so it's easier to pay for stuff so that way you have support and a scapegoat. Show nested quote + But then again, YMMV. For small project using only open source tools it is much more feasible.
The company I work for isn't large (10 developers), but our software helps run 3 different warehouses, system to system transactions, and a b2b website. We are a complete java shop with git maven and eclipse for local development. We deploy to tomcat servers with jenkins covering all of our continuous integration stuff. I can't say it's all that difficult, but, it's what I learned from the beginning and do everyday so I'm a bit biased.
There was no support contract in the deal. If they would need more help they had to buy more consultancy hours. It was a case where their own CM:s couldn't get the job done.
The keyword in your company's success story is "Tomcat". I explained why above.
|
What's it called when you have a language like R or Python or the stuff on codeacademy or ruby where you can type one line of code, then it shows the output, then you can examine it and write another line and press enter and evaluate that line?
R
>>x = 5+3 8 >>x*2 16
|
its called a REPL (Read-Eval-Print Loop)
|
On August 19 2013 09:51 tec27 wrote: its called a REPL (Read-Eval-Print Loop) Thank you. I've been calling it something else and could never find the term's name through google.
I don't know what my problem is, but I can't develop quickly without REPL. I just don't have the mentality necessary to develop without seeing my inputs at every step and I hate compilation time.
|
I'm sort of confused about Computer Science education. Everyone says you should absolutely have a degree if you want to work in the field, while others say the degree itself "is not enough" for job.
What is the purpose of studying it then? Is it to have some foundation base which you can upgrade once you start working. In other words, to compliment it with experience. Otherwise, it kind of feels demotivating to study, and then to hear that it is not enough.
Edit: not exactly a programming related question, but I do want to work as a programmer, so CS/SE education is needed anyway.
While I'm on the education topic, how did famous IT guys like Steve Jobs and Bill Gates succeed even though they didn't complete their degree? Did they try to compensate for it by self-teaching themselves? I doubt just a better brain is enough for what they did.
|
On August 19 2013 13:06 darkness wrote: I'm sort of confused about Computer Science education. Everyone says you should absolutely have a degree if you want to work in the field, while others say the degree itself "is not enough" for job.
What is the purpose of studying it then? Is it to have some foundation base which you can upgrade once you start working. In other words, to compliment it with experience. Otherwise, it kind of feels demotivating to study, and then to hear that it is not enough.
Edit: not exactly a programming related question, but I do want to work as a programmer, so CS/SE education is needed anyway.
I always like to say "Programmers are born, not made", meaning if you didn't program before studying it, you most likely won't ever be a good programmer because your mind works the wrong way. I'm programming since more than 20 years and i have learned but a fraction of what the programming field has to offer. A 3 year study teaches you the absolute basics, barely enough to do something useful with it.
However, for degrees it boils down to the application process: Applicant A says he has skills A, B and C and he has a degree. Applicant B says he has skills A, B and C and he has no degree.
Who would you as the one responsible for picking candidates chose? B might be better than A but he has nothing to prove it, so A is the safer choice since the degree at least says "Yeah, he really knows the basics". Basically, the degree is a simple reassurance for companies that you really have the skills. Hiring someone costs a lot of money, not just wages but also advertisements, recruiter fees and all that stuff, so hiring someone without a degree is a risk that companies are usually not willing to take. You can be successful without it if you somehow get into a company (e.g. personal connections) and then get a few years of real world experience that you can then show other companies, but for starting your career, the degree is absolutely neccessary even if the education itself is insufficient.
On August 19 2013 13:06 darkness wrote: While I'm on the education topic, how did famous IT guys like Steve Jobs and Bill Gates succeed even though they didn't complete their degree? Did they try to compensate for it by self-teaching themselves? I doubt just a better brain is enough for what they did.
Bill Gates had the knowledge before he got his education, i.e. he was a "born" programmer, not "made" programmer. Then he found an oppotunity that lead him on the road to success. It was basically "the right person at the right place". Same for jobs, though iirc he was never a programmer.
|
Very nice post, Morfildur. Thanks for insights. Things are clearer for me now.
|
Bill Gates and Steve Jobs were more than just programmers. They were visionaries with good business and leadership skills.
On an unrelated note, I've got a question on image recognition software. I've got a friend of mine I do iOS freelance for, and he's looking for some help with one of his apps. He wants to design an app that can, among other things, take a picture of a wine bottle and determine what brand/vintage/varietal the bottle is straight from the image. The image will get sent to a server where it will be processed. Obviously there will be a lot involved, but the basic idea he needs help with is this: if I take an image of a wine bottle, it's likely the system won't be able to determine what it is the first time. But the system will catalog it and save it for later use. If someone else takes a similar photo of the same wine, shouldn't there be an image algorithm that can tell me there's a high chance the wine is the same in both images?
I know nothing about image recognition algorithms or how they work. Anyone know where I can start? I know there's http://opencv.org/ but there's a lot to be found there and I'm not entirely sure of what I'm looking for. Any help would be appreciated.
|
On August 19 2013 13:20 Morfildur wrote:Show nested quote +On August 19 2013 13:06 darkness wrote: I'm sort of confused about Computer Science education. Everyone says you should absolutely have a degree if you want to work in the field, while others say the degree itself "is not enough" for job.
What is the purpose of studying it then? Is it to have some foundation base which you can upgrade once you start working. In other words, to compliment it with experience. Otherwise, it kind of feels demotivating to study, and then to hear that it is not enough.
Edit: not exactly a programming related question, but I do want to work as a programmer, so CS/SE education is needed anyway.
I always like to say "Programmers are born, not made", meaning if you didn't program before studying it, you most likely won't ever be a good programmer because your mind works the wrong way. I'm programming since more than 20 years and i have learned but a fraction of what the programming field has to offer. A 3 year study teaches you the absolute basics, barely enough to do something useful with it. However, for degrees it boils down to the application process: Applicant A says he has skills A, B and C and he has a degree. Applicant B says he has skills A, B and C and he has no degree. Who would you as the one responsible for picking candidates chose? B might be better than A but he has nothing to prove it, so A is the safer choice since the degree at least says "Yeah, he really knows the basics". Basically, the degree is a simple reassurance for companies that you really have the skills. Hiring someone costs a lot of money, not just wages but also advertisements, recruiter fees and all that stuff, so hiring someone without a degree is a risk that companies are usually not willing to take. You can be successful without it if you somehow get into a company (e.g. personal connections) and then get a few years of real world experience that you can then show other companies, but for starting your career, the degree is absolutely neccessary even if the education itself is insufficient. Show nested quote +On August 19 2013 13:06 darkness wrote: While I'm on the education topic, how did famous IT guys like Steve Jobs and Bill Gates succeed even though they didn't complete their degree? Did they try to compensate for it by self-teaching themselves? I doubt just a better brain is enough for what they did. Bill Gates had the knowledge before he got his education, i.e. he was a "born" programmer, not "made" programmer. Then he found an oppotunity that lead him on the road to success. It was basically "the right person at the right place". Same for jobs, though iirc he was never a programmer.
I agree with most of what is said here. Being from an under developed country I never had access to computers until the age of 17 and even then I had no good guidance on what programming was and the ilk. I majored in Computer Science in college despite having no prior experience or knowledge and managed to graduate with honors. Am I a good programmer? Maybe, I personally think I am not compared to someone who was born programming. But luckily, computer science is such a vast field with many sub specialties that don't involve programming; you have database design & architecture, software design & engineering, algorithm design & analysis, cryptography, machine learning, artificial intelligence, etc and the list goes on and on. In my opinion the best computer scientists are those with a very strong foundation in mathematics, I'm talking graph theory, number theory, hashing analysis, algorithm complexities, database statistics and so on.
Point I'm trying to make is if you want to be a CS programmer and be able to compete with the best, and you do not have prior experience, you will need to exert an insane amount of effort in order to catch up.
|
You want a degree because it shows a certain level of dedication which is measurable to some extent. A degree from a good school will also provide you with a huge time-efficient boost so you can learn a lot really really fast. Going to school is just the most optimal way to kickstart your career. It is not the only way, and it alone can't get you there.
|
A degree from a good school will also provide you with a huge time-efficient boost so you can learn a lot really really fast University isn't time efficient at all, it's a really slow way of learning.
|
On August 19 2013 17:43 Birdie wrote:Show nested quote + A degree from a good school will also provide you with a huge time-efficient boost so you can learn a lot really really fast University isn't time efficient at all, it's a really slow way of learning. I disagree. My uni is very fast paced and provides many opportunities; in my opinion it's a good school.
|
|
|
|