carucez
Few legal constructs cannot be run from. Few legal arrangements cannot be undone. For those that cannot... run!
... just considering this possibility is often enough to give you the strength to keep fighting through whatever current situation or struggle you find yourself in.
People selling cell phone mods don't usually know anything about electrical engineering, mechanical engineering, or manufacturing; yet they somehow can pull millions of dollars of profits out of plastic cases and LED mods simply by dangling a few slices of pizza in front of a hungry college student.
Point is, exploitation is everywhere -- don't be exploited, and computer science is at the stage where it's simple enough to follow some rules and slap a few APIs together to build a decent mash-up that's never existed before... that a fraction of people are willing to pay for, and "make bank bro".
I hate it. It's not just you feeling this frustration. Just see the writing on the wall, and know that app dev / pipelining of data feeds is going to be as "easy" as programming a VCR in the 90's.
M-F: 06:30 stock market alarm rings. I sleep in.
06:30-07:15 twitter alerts inform me of stocks to trade.
07:30 I get out of bed
08:00 showered, i head downstairs to read more twitter
08:30 leave for work
09:30 arrive at work (yea, suck)... do work all day, non-stop, no lunch, no break.
17:00 leave for home
18:05 arrive at home, turn on oven, crack beer, clean up
18:15 pizza in oven, read twitter, ebook, or other reading
18:45 eat dinner
19:00 watch video lectures, set stock alerts
20:00 write notes, draw pictures, prepare for tomorrow's code session
21:00 tea and quiet time, screens avoided.
21:30 prepare for bed
21:45 in bed, lights out
S-S: 08:30 get out of bed... naturally
08:35 coffee, cold water, email
09:00 notes for items to do today
09:30 eat oatmeal, clean kitchen/house/bathrooms... whatever
10:30 computer time
11:00 programming time (or venture outside for a change)
17:00 make rice
17:45 prepare dinner
18:00 eat
18:30 dishes, tv
20:30 twitter/news/world events
21:30 prepare for bed
22:00 in bed... (possibly read a book)
22:30 lights out
having said that, ... get a good lawyer. the original contract might be vague enough that the lawyer has had experience with similarly worded crap in the past.
any company that tries to steal your personal development for the entire time you're employed is not some company that you want to work with. a good fight is just a good american spirit. fight that crap that junk corporate throws at you.
tl;dr - fuck 'em. let the lawyers fight it out, but get a good lawyer. dollar-for-dollar, they're worth it. no matter, your education is worth the lawyer dollars regardless.
say you're a double-agent. the only thing that matters is if you're working against the common good. if you're totally on another level, you really have nothing to worry about.
the contracts you signed when you were new and stupid are an entirely different beast. get a good lawyer; you should be fine 9 times out of 10 as long as you're not violating a typical no-compete clause... or that no-compete clause over-steps its boundaries.
build 2 classifiers: #1 that classifies a sentence that contains the information you want, and #2 that classifies the actual data within that subset.
NLP
Hadoop is not exactly the best example of distributed, but it does contain all the core components. If you want a highly efficient, distributed system, then I suggest one tries to write their own. This ground is still being tested.
Sockets and asyncrony are tricky things, and I'm sure there exist better ways of achieving distributed computing.
1) Compute-intensive, job-centric? 2) Compute-intensive, parallel reductions? 3) Database-intensive, map-reduce? 4) Database-intensive, sharded, non-normalized? ...
The various forms of distributed systems is something that many people don't fully grasp. It's rather easy to build your own #1 or #3 (hadoop). Facebook has done an alright job at #4. Parallel reductions on distributed systems... I'm thinking million factor by billion-row matricies. That is something that we have yet to explore. Sure, we've done thousand-factor by billion row no problem. That's essentially a map-reduce. But doing the matrix reductions on 1e6 by 1e9+ is not something typically done. ... at all. One would need to find alternate ways of representing those 1e6 features as separate matrices... perhaps some form of Bernoulli/Bayes combination and increase the number of operations by 1000-fold.
// Forgive me for the rant. This is something I do like to think of in my spare time. You're right in that self-taught's don't have this skill. My value-add is that a lot of school-educated don't possess this skill either.
Why does this matter? Well: All my code is as efficient as possible, to the best of my working knowledge, all while meeting deadlines.
How did I do it? Well: Get it to work. Make optimizations. Repeat. Potentially refactor. You'll always have a fallback that works, because you had to in order to get a non-failing grade.
Screw SOPA! If we lose this, we lose the internet... and we built the damn thing... each in our own small way.
I've discovered that PHP makes me angry. Functional is good for small stuff. I need [much] more practice with OO. I don't know anything about ... a lot.
The next 2-4 wks are spent reading and comparing alternatives to doing whatever it was that was nagging me. These time blocks do actually include small coding problems (1-2hrs), but I can't really call it coding. I then begin with new optimism about the new language/skill/feature/paradigm that I've now incorporated into my daily programming.
I check back with the competency matrix semi-annually to re-evaluate where I'm at. Anything that I'm unfamiliar/unskilled with is fare game for the next 6 months.
If I were focused solely on global supremacy, I would check the matrix weekly, but alas, I have work to do, and I'm competent enough to do it now.
READ. It's the best way to discover the unknown unknowns.
Your ability compared to others only matters only when framed in the context of "What do I want?" What skills do you need for the career path you want? What skills do your future employer(s) need from you. What are the non-academic PhD guys working on, and does that interest you enough to wake up at 3am for?
* moving averages
* linear regression
* matrix operations
* matrix lu factorization
* polynomial interpolation.
* multiple linear regression
* cubic spline interpolation
* variance, covariance, correlation
* gamma function
* t-test, t-value calculations
One limitation of the above is that it doesn't explore all of a language's features. The above are mostly interested in array processing. There aren't any classes or generic types or what-have-you.As zedshaw says, do every exercise, type every bit of code, etc.
After learning javascript, I went on to learn something more immediately useful. It took me about a month before I had built and completed my own local file search engine with jscript (windows scripting) and ms access. I altered my sleep schedule to 34/14 (awake 34 hours, sleep 14). If your mind is actively engaged in the learning, you won't need to sleep regularly. Sleep was the only limiting factor.
3 months after first learning javascript, I had rewritten my file search engine in perl and C, and upgraded my database from ms access to mysql. I didn't know much about perl and C, but I was happy to now "know" 3 languages and 2 databases.
For me, bigger bankroll = higher score.
For my wife, a bigger bankroll = more shopping.
The trick is to break your money up into several purpose-driven accounts and automate that.2 Roth IRAs: maxed out (Vanguard S&P500 Index. 1 more year and it'll be 70/30 split with bonds).
1 brokerage: for fun, for research, for programming. Unfunded, no continuing additions. Go big or go home.
3 checking accounts: mine, wife's, joint - the paychecks
2 MMAs: mine, wife's - excess money must go somewhere. One of which is sub-divided into: health, gifts, emergency.
2 savings accounts: tiny siphons ($300/mo) that corrupt my sense of reality. It's money-out that looks like normal transactions.
Hacks: By having a high-deducible health insurance plan, I'm able to put 3k/yr that would have been my insurance premium into a health-related emergency fund. As long as I don't get injured in an at-fault car accident twice in one year, I'm saving tons of money
Edit: formatting.
I've published my findings, a complete ranking, and source code: http://log.largevoid.com/2010/12/ranking-colleges-by-reading...
I've published my findings, a complete ranking, and source code: http://log.largevoid.com/2010/12/ranking-colleges-by-reading...
SEC form 4 filings are in XBRL dating back to Jan 1, 2004 for every company. There are well over 1,000,000 forms filed between then and now... I know, I have them all locally right now.
You can scrape Google's Financial pages, obviously, and you can even get 2-minute data from a JSON "_5d" variable.
You can get fundamentals data from nasdaq pretty easily, too. Scraping it is a little difficult, but you can go 120 quarters back for many companies, and 5 years back for annual data.
I have a financial statements database populated with nasdaq scraped data right now. They update within a week or so after it's published to the SEC. You'll always be behind the curve, but you will have good information, and it is good information, albeit incomplete (missing things like the number of shares outstanding).
* Python + Pros: Concise, extensible, object oriented, package/class/method hierarchy, multi-platform, lots of frame-works, lots of scientific contexts, HUGE community (at this point really), scripted (quick to see changes) - Cons: Odd syntax (no more odd than VB really), scripted (teaching compilation step may be a requirement), requires C for high-performance fragments, v2 vs v3 package hangover.
I struggled to find real faults with Python, but I also struggled to find real positives with VB.Net.
From a pure $$$ play, you might be able to convince the administration to dump VB and go Python. Admitted, MS educational discounts are incredible.
Python is a bit more robust for all things higher-level, and I would recommend that before PHP any day (for someone starting out in).
Client side stuff is (for me) all JavaScript, always, using the JQuery library to ease my web pain.
HOWTO do divide Client from Server? Separate machines and insist that all back-end processing and storage goes on one set, and all client-side functionality goes on the other. Loading/parsing of archived data is a client-side process, as far as I'm concerned. Use standard protocols and formats to talk between the machines.
"Starting in November 2010, Groups will no longer allow the creation or editing of files and pages; the content will only be available for viewing, and only existing files will be able to be downloaded. If you would like to keep the content currently on the pages and files sections of your group, we highly encourage you to export and migrate it to another product. In February 2011, we will turn off the pages and files features, and you will no longer be able to access that content."
http://groups-announcements.blogspot.com/2010/09/notice-abou...