Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Let's take my compilers class as an example. I go to a 75 minute lecture 2 times a week and I do about 4 hours of homework a week. I do this over 18 weeks. That's only roughly 120 hours of study over the course of a semester. That's only as many hours as most full time employees work every 3 weeks!

The comparison doesn't seem fair. First, I suppose you have others classes at the same time. And if you don't, you're free to do additional work on your own. In any case, hard concepts take time to sink in. You're better off learning this over a longer period of time.

Besides, don't think full time employees do meaningful intellectual work 8 hours a day. There are always a lot of distraction. And even when coding, it's not the same as writing tons of boilerplate code than understanding new complicated concepts.

> And the sad thing is, I imagine if I spent 3 weeks reading a compiler book, reading though the source of lex and yacc, and implementing some kind of basic compiler using them, I'd be a much better programmer than what we're doing

Are you sure that you'd be able to do that? supervised education helps you to pace yourself, focus on what is important and to keep motivated over the long run. The actual content is maybe the least important.

Besides, going through lex and yacc sources sounds like a huge waste of time for someone who wants to learn about compilation. There may be some value in this, but it should be last on your priority list.



> Are you sure that you'd be able to do that? supervised education helps you to pace yourself, focus on what is important and to keep motivated over the long run. The actual content is maybe the least important.

I'm 100% sure. The motivation is all there. Why would I be in this class if I had to be coaxed into learning about it?

I think I can learn more in one long sitting than piecing away at any given topic. That's my personal experience. Instead I get distracted taking 5 courses at once and learn comparatively little.

> Besides, going through lex and yacc sources sounds like a huge waste of time for someone who wants to learn about compilation. There may be some value in this, but it should be last on your priority list.

I'm sorry but no. Compared to what we're actually doing, it's far far far better.

What am I going to come away with from the class? I guess I'll be a rock star interviewer, but I don't think I'll be much else.

Implementing something using only common tools and doing it without any code from the instructor would certainly result in more skills moving forward.


"I'm 100% sure. The motivation is all there. Why would I be in this class if I had to be coaxed into learning about it?"

So then why aren't you going through the lex and yacc sources in addition to your compiler class work? It's not like you have to ask for permission.


Because I'm stretched thin by my 5 other courses and other projects.

The point I'm trying to make is that at least for me, I'd be much better off devoting myself to one topic for 3 weeks than spread over 18. That may just be me personally.


Maybe that's the best lesson college is teaching you. In your professional life, you'll have to deal with a lot of frustration working with other people in a way that you haven't chosen!! you have to make the best out of it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: