Cariyaga
Handsome Gentleperson
- Location
- United States
Yeah, I know someone with a wife and a kid that spends almost all of his unoccupied freetime programming
Yeah, I know someone with a wife and a kid that spends almost all of his unoccupied freetime programming
Some of these things I've heard of--others are a complete mystery to me. Well, computer science certainly won't run out of things for me to learn. I've saved your list in a text file. Hmm...I'd better start a spreadsheet of "someday" things to learn.An incomplete list of things that I would suggest learning about at some point, and/or books to read, listed in no particular order:
* Internet Core Protocols from O'Reilly Press
* Database administration (PostgreSQL, SQLite)
* Security (cf CISSP for defense and CEH for attack)
* Books: "Grey Hat Hacking" and "The Little Schemer" and "How to Design Programs"
* Graph theory
* The Racket programming language
* Nginx web server
* A job server (e.g. 0MQ or Gearman)
* Chef (configuration management tool)
This is just off the top of my head and just a taste. Computer science and programming are wonderful fields to be in. They are immensely wide and immensely deep; there is always more to learn about the thing you're working in and if you decide you want a change there is another subfield that is related but completely different. It's exciting.
Note: They have some duds, but as a general rule the O'Reilly books are some of the best out there.
(If you haven't already, I'd encourage you to put a chunk of time into meta-learning, such as Barbra Oakley's material on learning how to learn (can be found for free in many places, including on Coursera).)Some of these things I've heard of--others are a complete mystery to me. Well, computer science certainly won't run out of things for me to learn. I've saved your list in a text file. Hmm...I'd better start a spreadsheet of "someday" things to learn.
Thank you very much, @eaglejarl, @Veedrac, and @Cariyaga. If anyone chooses to share any more thoughts or comments, my thanks to that person as well.
It's a good thought. Thanks!(If you haven't already, I'd encourage you to put a chunk of time into meta-learning, such as Barbra Oakley's material on learning how to learn (can be found for free in many places, including on Coursera).)
The problem would be if he was ditching his responsibilities to his wife and kid in order to program...Yeah, I know someone with a wife and a kid that spends almost all of his unoccupied freetime programming
Like I said, unoccupied.It's a good thought. Thanks!
The problem would be if he was ditching his responsibilities to his wife and kid in order to program...
He has the bloodline that makes people forget about him. It's crazy OP for assassination missions.[X] Sakura,Akane and Haru exchange information about the ninja clans they know
I like this one. Who's Haru, though? /s
Oh, so it's MfD's version of ... wait, what was I talking about?He has the bloodline that makes people forget about him. It's crazy OP for assassination missions.
The best part about this joke is it works on two levels.Oh, so it's MfD's version of ... wait, what was I talking about?
I bet you can't remember what the second is.
I dunno, the rabbit behind you distracted me.Oh, so it's MfD's version of ... wait, what was I talking about?
Immediate concerns as far as readability goes: Explanations of phrases should be ordered such that you can read it linearly: Stats should come before the summary, or at least an explanation of the various terminology (actions, stat pools, etc).Unrelated to MfD:
I have been working on the basic mechanics of a quest idea similar to Paths of Civilization and I think I am just about ready to start posting. I would love to hear what people in this thread think of the mechanics writeup I just finished drafting re: whether it's understandable and whether you'd be interested in participating
[x] Someone beats Hazou over the head with an explosive telescope
I *think* it's better now, at least somewhat?[x] a meeting of the merchant council
Immediate concerns as far as readability goes: Explanations of phrases should be ordered such that you can read it linearly: Stats should come before the summary, or at least an explanation of the various terminology (actions, stat pools, etc).
Oh good lord....