becomevocal

9 ms·

91.
by becomevocal 15y ago
Of course. But I'm thinking about it in terms of big data. A lot of us are and will be increasingly dealing with sets of data that should be thought of in parallel solutions. Not just a single process.
92.
by becomevocal 15y ago
Awesome book man. Thanks for the heads up!
93.
by becomevocal 15y ago
I think this could also be called 'can your brain think like this?'... Many programmers stray from thinking in a massive way and tend to problems with similar, familiar codebases.
94.
by becomevocal 15y ago
And to think I'm going to miss out on something I'll never know because I've read something about missing so many things.
95.
by becomevocal 15y ago
You definitely have time to work on a prototype, little by little. Product, product, product. Then work on your connections / traction / freaking out / loosing sleep.
96.
by becomevocal 16y ago
You don't need one if you have all the knowledge and time in the world, with the network to take advantage of it. So, yes, in most cases you need one. Now, if you can build a prototype or get traction using your existing team, do it first.
97.
by becomevocal 16y ago
I'd much rather read an article that has a couple quick insights, like this one, than the millions out there that are indeed just omg-how-great-is-this-product landing pages. + I give credit to those who code and create (valid) content. One
98.
by becomevocal 16y ago
With anything uninteresting, try and come up with a solution that challenges yourself to think. Say, instead of using that plugin you frequently rely on, come up with a solution of your own (of course, keeping time constraints in mind.)