I didn't learn any of those things in college. Maybe you just picked up the wrong things or are you just ignorant of what you really learned? I learned a good basis in information theory, maths and software engineering. Besides that I learned to analyze, research, work together on and write about software development processes. I also met many people who were interested in the same things as I am, and many people who…
All I learned in college was how to work for someone else
21–30 of 61 posts
Re: All I learned in college was how to work for someone else
#22"An Alternative, Practical Education"?
Re: All I learned in college was how to work for someone else
#23- College isn't only CS.
- Pure (computer or not) science isn't 'working for someone'. It's 'learning how to do (computer) science correctly', hopefully.
- Plagiarism is not what you are saying, which is superficial. Citing a paper and using previous work in academia isn't plagiarism, for example. Copying someone else's paper and putting your name on it is. Which IS bad. I can't take a linux distribution and tell the world I wrote it. But I can use it and (depending on the license) sell it. Or make something else with it and add my name on it.
- Performance matters or not depending on the users, obviously. But if you don't know that your algorithms are bad, or if you don't know how to fix them when you hit scaling problems, then what do you do with all your users? Sure, you can hire someone who went to college or learned that somewhere else, but then you'd be supporting the idea that there is no need to be technical to be founders, which is partly true but if google and others taught us something is that the technical founders tend to be able to understand some problems better (and solve them better).
- Learning the concepts behind the list you wrote isn't incompatible with college. If you take some business classes you can learn a lot of it. No one is forcing you not to take those classes or a major in CS and a minor in Economics.
- From college you don't get only the classes, but also the interaction with a lot of smart people, diversity, challenge and many other things. It changes you, hopefully in better.
- Getting excited about being entrepreneurs doesn't always mean the sooner the better. It depends if one is ready. Like with startup ideas, arriving too early may be as bad as arriving late. So, if you quit college for the sake of being an entrepreneur when you are 19 and then you fail, you lost the chance of getting 'more' ready through college.
- Same applies for grad school. You might not need to go to grad school to do anything. But a lot of people change the way they see the world going to grad school, which, if it made you wiser, could be a good quality to have when founding a startup (plus the extra knowledge).
All this to say that if you think that you can say "all this does is this" I think you might want to rethink a little bit, since it's rare that such absolutists ideas about things so controversial are ever correct.
Re: All I learned in college was how to work for someone else
#24This article was light on details, but I thought it was important to address at least the first point, which has a fundamental misunderstanding right off the bat: "1. Plagiarism is bad. Wrong! If the licensing is right, copy to your heart's content. If you're not in violation of copyright, trademark, or patent, you can do whatever you want with someone else's creation. Sometimes they even give you permission. Did you…
Most open source licensing requires 0 citation. If I copy your formula or recipe, I don't need to cite a thing - you don't own the copyright to your own formula. I could sell your work if I wanted to do so. Plagiarism, as it affected my grading, was copying without attribution. Attribution is rarely required for most licensing, except where it is. These sorts of distinctions are lost in the collegiate machine.
Re: All I learned in college was how to work for someone else
#25I didn't learn any of those things in college. Maybe you just picked up the wrong things or are you just ignorant of what you really learned? I learned a good basis in information theory, maths and software engineering. Besides that I learned to analyze, research, work together on and write about software development processes. I also met many people who were interested in the same things as I am, and many people who…
Re: All I learned in college was how to work for someone else
#26As a soon-to-be college graduate, I'd be very interested in hearing your answers to those 10 questions at the bottom.
5. The way I have done this is by a landing page to gauge interest and by getting a handful of customers willing to buy in a recurring fashion as a starting base before significant monetary investment on my part.
7. Get a partner in equity early and outsource or automate everything possible before hiring employees. Hire when the cost of failing to get the right employee will not harm you financially.
9. If none of the directions are obviously better or have data to show why they are better, find a way to get the data to show you which direction is best.
Just my 2 cents.
Re: All I learned in college was how to work for someone else
#27I'm a senior a very theoretical university and my friends in the CS department often complain:
- "Why should I learn all these sort algorithms? Let some grey beard figure out which one is best for me and wrap it up in sort()"
- "Why do I have to take all these required classes? Why do I have to do a semester of foreign language or a physic pre-requisite?"
- "Why do I have make an entire operating system in this class? When in the real world would I ever need that?" etc.
Bullshit! It's good to be "T" shaped - studying a very technical area like honest-to-god computer science trains you to dive deep, to be able to confront a problem and approach it analytically. All the prerequisites have given you a stepping stone into understanding, or at least appreciating, other areas. These are very useful skills to have and they certainly make you a more interesting person.
Sure, there are plenty things left out that would be useful for entrepreneurship. Half of my friends in the CS department haven't taken the initiative to learn "real world" development yet with all the shiny tools and most (myself included) have no idea what it takes to run a business. But to say college only "prepares you for the life of a corporate stooge" is a mistake.
Re: All I learned in college was how to work for someone else
#28Re: All I learned in college was how to work for someone else
#29This article was light on details, but I thought it was important to address at least the first point, which has a fundamental misunderstanding right off the bat: "1. Plagiarism is bad. Wrong! If the licensing is right, copy to your heart's content. If you're not in violation of copyright, trademark, or patent, you can do whatever you want with someone else's creation. Sometimes they even give you permission. Did you…
Most open source licensing requires 0 citation. If I copy your formula or recipe, I don't need to cite a thing - you don't own the copyright to your own formula. I could sell your work if I wanted to do so. Plagiarism, as it affected my grading, was copying without attribution. Attribution is rarely required for most licensing, except where it is. These sorts of distinctions are lost in the collegiate machine.
"The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software"
And GPL:
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice;
Re: All I learned in college was how to work for someone else
#30I understand what you are trying to say, but this article is silly from many points of view. I don't want to answer with wise-ass comments like "you went to the wrong college" and such, so I'll give you a couple of arguments: - College isn't only CS. - Pure (computer or not) science isn't 'working for someone'. It's 'learning how to do (computer) science correctly', hopefully. - Plagiarism is not what you are saying,…
I hear this a lot (frequently even about passing on college for lucrative, if short-term, opportunities), but I don't get it. This isn't amateur athletics where you have to worry about losing your eligibility and wouldn't be able to get in without an athletic scholarship. You could easily go back to college at age 21 after a year or two of trying to start a business.