110 karma · joined May 16, 2011
Conceiving simple tests to prove a simple piece of programming works, keeps it simple. Simple is powerful.
I don't know if I entirely agree with his conclusion. The smartest people I know code with a pen and paper. When they're on the bus or subway. When relaxing, or thinking carefully while away from a computer.
Those who program in the shower and then write it down after before they forget. Analogue programming tools (pan/paper) are great tools.
I thought the article was going to end with him pointing out that he found a great practice that we can all benefit from now. Planning code ahead of time is still better than typing away, we're just not forced to do it anymore.
It's awesome what they've done to showcase the community examples
As always, nice work!
Originally intended to be part of D3, he's now set it up as its own library.
I'm sure he'd be super impressed to see how dramatically the numbers have fallen.
9223372036854775807 == 9223372036854775808
true
9223372036854775807 === 9223372036854775808
true
The professors are also well respected brand names in their own right. Having your introduction to probabilistic robots come from Thrun to me carriers weight
Over time advances in technology and increases in capital (capital defined as production goods here not cash) tend to dramatically reduce the cost of production.
Not to mention the insane decrease in the cost of raw materials once you start collecting from asteroids (again assuming we're 500 years out and can build a moon sized ship we can certainly snag an asteroid or two for materials).
There's different use cases, without listing them all just think how many times you've had to calculate the one you don't have access to
Not the end of the world for me, I can copy from the address bar but I wonder if you're missing out on conversions.
Cool story though. I got a kick out of the customer responding back "...bitches"
Justice Ruth Ginsburg said “some restriction on expression is the inherent and intended effect of every grant of copyright.”
Without knowing the details of projects X, Y and Z it's hard to say what to stick with but at this stage in your career, it's not good to burn bridges. If you do exit X, make sure it's on good terms. Who knows, they may need you again in the future to join another project they're working on.
Long story short, you've clearly communicated that there is more work available than you have time to do. Seems like it's just a matter of determining which projects are most likely to yield positive results (financial or personal/general interest) and sticking with those. In the meantime, hold onto that salaried job. Having that solid fallback when you're uncertain about side projects is extremely valuable.
like this