4 ms·
> Not to mention that what someone learned in uni a decade ago is probably not applicable anymore whatsoever (in tech). Working all night to meet a deadline is
by kazinator 6y ago
> Not to mention that what someone learned in uni a decade ago is probably not applicable anymore whatsoever (in tech).
Working all night to meet a deadline is applicable. You learn dedication at university.
University also teaches you to take a risk on something long term. You pay a bunch of money, and work hard without compensation for a number of years, hoping it will pay off somehow. Your risk not making the grade and dropping out, losing the investment of time and money.
I remember one assignment which was implementing floating-point addition in 68K assembly code. (Third year course on machine architectures.) Code was executed on an emulator that could provide cycle counts, and there was a cycle count maximum to meet on certain test cases.
Now the permanent lesson here wasn't 68K coding, and that's not what the experience memorable. Rather, the day before the assignment was due, the prof surprisingly dropped the cycle count requirements to significantly lower values. Everyone had to scramble to squeeze their code down, even those who had not procrastinated at all and completed their code days in advance. We learned about dealing with a change in external requirements close to the deadline, and still making it.
- simplyaccont 6y ago>Working all night to meet a deadline is applicable. You learn dedication at university. It's not dedication. It's simply a deadline that you must meet or face failure otherwise. >University also teaches you to take a risk on something long term. You pay a bunch of money, and work hard without compensation for a number of years, hoping it will pay off somehow. Your risk not making the grade and dropping out, losing the investment of time and money. Actually university is opposite of taking a risk. It's a safe choice. You get a degree - you get a good job. It's something that always drilled into everybody. Taking a risk is doing something that is opposite of common sense.
- kazinator 6y ago> You get a degree Not a given. A kid just has to walk down that hallway where the yearly grad photos hang, and take note of how less populated they are than just that one lecture he or she just came out of.
- simplyaccont 6y agoWell, with dedication that you mentioned above, or more realistically "persistence", pretty much given. Unless it's really not your thing and you switch to something different. But I personally won't know: I didn't graduate from high school, never got into university, yet now I am senior director level overseeing architecture at rather large company. I guess I made safe choice back in high school when I decided not to go to finals at math and instead to go to first day of full time employment with city level isp
- kazinator 6y agoYep; e.g., out of, say, 350 enrolled in first year, 300 might find it's "not their thing", eventually leaving a graduating class of 50. Or else, in some situations, the university finds that some of the students are "not its thing".
- simplyaccont 6y agoand how many of those 300 "dropouts" will switch to "liberal arts" or something else, just because having a degree is a "proper choice that will help later in life" as opposed to really dropping out ?
- deleted 6y ago[deleted]
- kaba0 6y agoThat is absolutely irrelevant to the point.
- rurp 6y ago> You learn dedication at university. Everyone I know, including myself, who came to software engineering outside of the standard academic route needed to make a huge commitment. Pretty much everyone who goes down this path faces a large cost in terms of the time commitment required to learn a new discipline, the price of training materials (boot camps, online courses, etc), and the opportunity cost of leaving an existing job to take a chance on a new entry level one. I personally switched to software development from a decent but mind-numbing career. The first couple years were really rough as I lived off of dwindling savings trying to learn and pick up enough entry level work to get by. Going the computer science degree > intern or entry level position > good engineering job route is both difficult and full of valuable experiences, but it's also the most cookie cutter approach with the clearest guardrails. The notion that only the most dedicated people can make it through the experience of a comp sci college course in their early 20s is hogwash in my opinion. I have a 4 year degree in an different field and that was a MUCH easier path than breaking into the software dev business with a self taught and boot camp background.