ZackOfAllTrades
Joined 16 years ago
Joined 16 years ago
What I ended up doing by mistake which I really like is that when I get to the end of a diary, I have usually written only on the front side of pages. So I start writing on the back sides of the pages and I watch as my life unfolds in reverse. I can see how I felt yesterday, then 3 days ago, then 5 days ago, and then it gets to several months. And I am looking back on how I thought/felt and seeing all these patterns. You start looking at what you wrote in a different like. Patterns, like maybe a person in your life being sad often or a certain idea that you keep writing about, start to really emerge clearly.
I think it is a worthwhile habit if you want to understand your mind. It also helps me sleep most of the time by letting me get stuff out of my head.
[Edit: This was in response to someone asking why it wasn't on the front page.]
If you come from a javascript background, you will have a leg up on most people in terms of learning clojure. You get used to inlining functions pretty regularly.
What I am encountering as I chew through Programming Clojure though is that I had no idea what I could have been doing in javascript all this time. I would look at C and laugh about how they have to define an extra function for event handling. It just seemed so verbose.
Looking back at the javascript I wrote/write, I really wish I had understood what I could have been doing with functions, mappings, and apply. I didn't/don't write javascript: it's just C with some in-lined functions.
Moral of the story: Inhale the Zen of Crockford(http://javascript.crockford.com/) and exhale the suck of W3 schools.
They are marketing to the schools and universities first and foremost because they are the ones who actually make the buying decisions. All the publishers try to do is make something that looks better their competitors and lets colleges cram more students into the classrooms. I don't ever remember them saying "students need this" but rather "universities want to see this". It is a broken system that relies on lazy/overworked teachers and massive hulking collegiate bureaucracies.
Good electronic textbooks won't come from companies that made shitty paper textbooks.
People might not know what they really need, so any advice people give might just be a weird version by what they want to hear.
Desire to make neat web pages. Learn enough jQuery so that you can make something move and change colors with maybe two lines of javascript instead of 20. Keep trying to one up yourself in what kinds of cool shit you can make (I use the term shit because you won't be making anything useful persay, but it will be something that will make friends say "Shit, that is cool. How did you do that?")
Start to learn more and more jQuery until you think in callbacks and events. Use the canvas to make weird patterns (treeowls.com). Make something using Ajax (try the hnsearch api: pretty fun http://zacharymaril.com/HNSearch/Topics/testing-api.html). Try to solve a hard problem with JS that requires lots of computing (some work with Ramsey theory: http://zacharymaril.com/thoughts/constructionGraph.html) . Mess around with Three.js (http://mrdoob.com/blog/post/693) and Processing (http://zacharymaril.com/). Use chrome or firefox with the debugger.
Then get bored with frontend stuff and jump into node on heroku or whatever hosting service is popular but has good documentation. Make a chatroom with a lazy bot(zackbot.com) and a static file server. Look into the database bindings. Look at the stuff DailyJS puts out on node(http://dailyjs.com/tags.html#lmawa old with bugs, but very in depth for the time). Make something neat (still working on that part).
Read a bunch of Javascript/jQuery blogs. If you learn that way, pick up JS The Good Parts. Read anything/everything by Steve Yegge, John Resig, and Ryan Dahl. Use the jquery documentation from the website, then get frustrated with it and use jqapi.com
But that is all based on one approach. It sounds like you are interested in more backend stuff. Starting out with node would probably be what you looking for, but without much know how of how to make things work, you might not get thrilling enough results to actually stick with it. I would say stick with the frontend to learn how javascript works and where it came from and then when you get really really bored go mess around with node.
How do you make money though? Who is paying for what?
Also, let's say that anyasq isn't a YC company (not sure if they are or not). Then all they have going for them is better moderation. To me that just sounds like retweeting on twitter without the character limit and a cleaner interface. I am not so sure that is a winning combination. One would think that YC would pick a company that didn't need to be in YC to succeed.
Also, how does anyasq beat reddit ama?
Sounds like a program that accelerates your chance of getting recruited by Mozilla to keep working on your project. None of this is a bad thing, it just depends on your particular bend in life. If I was trying to make the next jQuery or Modernizer, for example, I would be bouncing off the walls trying to get into this.
Keywords for search: college station, math, tamu, texas a&m
http://hnofficehours.com/profile/ZackOfAllTrades/