471 karma · joined October 13, 2011
Many of the same problems plague colleges that plague high schools though...professors that either don't care or aren't very good at teaching, students that are just there for the degree, books that don't really challenge, and papers that just require following the formula "5 paragraphs, 3 summary sentences". Very little learning took place for me in any of that. The learning I did was from outside of college and was from learning what is considered generally graduate school work for C.S.
I really hope that most people's experiences aren't that way, and that colleges do teach young people. It just wasn't my experience through 3 different colleges. An Oxford style school with mentors and customized content probably would have served me much better than colleges that continue on the same factory system setup that is broken at the lower levels.
The workplace hasn't been difficult for me, but I definitely learn a lot more than I ever did in school. I come across actual challenges that require research and stretch me. Perhaps that's just being a software engineer though.
1.) Read your code after you write it. I do this via git diff --cached. It's amazing how many bugs you catch this way. Be critical of variable names, code layout or confusion, lack of documentation. It's basically doing your own code review. Is it documented? Is it tested? Does it make sense logically? Is it easy to read?
2.) Document stuff. Fluff documentation is even fine to start with, you'll eventually learn to separate the important documentation from fluff. Ultimately you need to get to the point of the "why" code does what it does, not the "what" it does. "What" it does should be evident by the code itself and the variable names/etc.
3.) Plan ahead. I don't mean pseudo-code per-se...more thinking or writing down how code will fit together. Mind mapping is great for this, particularly with a white board or tile. I have a Galaxy Note that I bought partially for this purpose and use Papyrus for it now. Basically, how do the abstractions and parts fit together? Is it logical? Not everything requires a whiteboard, but a few minutes of thinking ahead can help spaghetti code a lot.
4.) Learn different programming paradigms. OO style can quickly become un-maintainable even to pros. I suggest learning functional programming in a language like Scheme/Clojure, Lisp, or Erlang. I now pick up a new language every year in different paradigms...not so much to learn the language or to brag, but to learn different way things can be architected, and the way other languages do things.
5.) Do refactor. Outside of budget constraints, don't be afraid to rewrite code that doesn't seem to flow properly.
You mentioned sitting with a senior dev...that was pretty huge for me too, even in limited times. (I'm not sure I'd pay for it, but it did cut the learning curve down quite a bit) Having someone do code reviews of your code that knows what they're doing and invests time in it is helpful too. I've found though that not every Senior dev is good at reviewing code or teaching...
Sorry, I don't have any actual resources for this other than well structured code like Django (mostly) or sqlite. I now have a B.S. in CS and I don't really think they teach this well in schools either. Patterns will only get you so far in OO too...generally, trying new languages, reading code, and refactoring has made the largest impact on me.
(copied from the other post)
As a slightly above average 5'11" guy, I feel though that the average coach airline seat is designed as a torture device. The arms are too low to properly rest my shoulders (forcing me essentially to either severely slouch or fold my arms the entire flight), the seats are too close to fully extend my legs, the seat itself has a slight incline so that your knees get particularly more uncomfortable, and the space to the next person (particularly with shared armrests, and overweight people) requires me to slightly bend away from them. All of this combines to muscle cramps in the back for a couple of days after flying. It's really a miserable experience that I feel could be largely fixed by the airlines, if they weren't in debt, greedy, or dieing. I don't really blame the people in front of me for wanting to recline (I often do a couple of inches, though never the full length). I blame the airlines (and in essence the manufacturers, though I'm convinced they build what the airlines are demanding) for designing horribly uncomfortable seats with no space.
You're right though, that it doesn't completely prove the point, but I think it definitely makes a point. People who wouldn't buy the e-book at 14.99 are probably unlikely to go out and buy the same book from another retailer for 14.99. The question is if it really increases the market share of the book, or if instead lowering the price on amazon makes everyone who would buy the book would just go to amazon for the cheaper price. (Given that e-books cost nearly nothing to distribute, I would think that the price drop would pretty easily pay for itself though)
But the author has a good point, if poorly served by the examples.
Criticism is one thing, aggressive oppression is another.
Would I support a member of the KKK, or any other known "hate" group? It is their right of speech, and they are still free to have it, so long as it is not in a manner of defamation (such as slander, or libel), which looks much more like how Mozilla responded.
I won't lie...it is tough, particularly with a family. But I think in a way it gives you both the practical viewpoint and the theoretical viewpoints of programming both together.
Also, school doesn't have to cost 50-100k...unless you get into a top 10 school and are favored, it may not be worth it to go to such an expensive school.
If you're already good at development though, I think that getting the experience is more lucrative, but the degree more rewarding.
I'm really just jealous that the people I know don't all use Linux and aren't as passionate about it. :-/ But there's a certain blindness when you're the fan to how much you fan out about things.