Writing code is about making your computer do what you need. Writing good code is about enabling teams of strangers 5 years from now to make their computers do what they need.
-
-
What, then, do you call people who learned something, usually taught, from books and practice instead? I think you're reaching too hard. There's something there - associated positively with passion and negatively with incompleteness - which deserves a name.
-
You call that "self-taught". As I do in this thread.
End of conversation
New conversation -
-
-
Indeed but no feedback, it's like supervised vs unsupervised learning :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
knowledge distillation is all you need :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
All coding learning resources out there are the outcome of collective work, so it's impossible to learn coding without being exposed to the wisdom of a networked community. Eventually the issue is with collaborative work, which requires every other skill, not learned by coding.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is where open source projects are possibly the greatest way to learn collaborating in software projects, where one can put coding skills to work and learn how to effectively collaborate. That's the part of the skill set, which isn't to be found in books or videos ...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The VC group that seed funded the first startup I work with, had this policy, spelled out on the wall of their pitch room: Ass****s are not worth your time, and certainly not our money. That was 2003 in Berkeley California
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.