5,068 karma · joined February 22, 2007
Contact me: akapal@gmail.com
1)how well do you understand your customers (are you your customer)? Have you talked to at least 10-20 potential customers to understand what their big problems are?
2) Why do you believe that 'advancing the state-of-the-art' is needed to solve a meaningful problem? Maybe there's an easier problem you can solve for them, use the opportunity to learn and iterate.
It's technology without any sense of history, humanity, or culture.
For example in Los Gatos, appreciation has been 5% on average for many years, and so the 200k you put down on a 1m house will typically appreciate by 50k. 25% roi in year 1, increasing each year. Of course, property appreciation doesn't happen in a straight line, and houses cost money to maintain (property taxes, etc) but the larger point is valid.
This seems like a promising opportunity for startups to tackle...I wonder if there are any out there, would love to hear more.
source: http://www.bloomberg.com/news/articles/2014-11-12/fossil-fue...
btw, I'm not sure why but Tabli isn't searchable on the Chrome store for me.
https://en.wikipedia.org/wiki/The_Superinvestors_of_Graham-a...
I clicked on the link and hoped this was your company (we met at Startup School).
Great press, looking forward to seeing your company own this space.
My hiring bias skews towards people with a good engineering background or concrete examples of meaningful contributions to non-trivial coding projects.
Sure, vocational school is fine while demand for programmers is outstripping supply. But those who lived thru 1999 and the resulting downturn have seen that these things can turn on a dime and a 6-month certificate may not provide much job security.
Also: Manresa is a great reason to skip out on a diet!!
http://blogs.wsj.com/moneybeat/2014/06/23/a-list-of-the-bigg...
1. Meet in person
2. The coder should print out copies of the diffed code for each attendee
3. Have roles in the meeting - someone to read the code, someone to capture bugs + severity, and the rest are there to review the code
4. Coder takes documented defects, fixes them and reports back to the group with diffs.
5. Metrics can be kept, used as feedback to improve process.
Usually 4-5 people are sufficient for a large chunk of functionality.
Is this process slower than gerrit? yes. Do you get better feedback, and better understanding (at a team level) of the code base? yes.
I haven't seen software that really emulates this experience - there is an interesting opportunity here.
Just like Apple let Creative Labs foot the bill on R&D and market building with the Nomad before the iPod was introduced?
Perhaps the next edition of his textbook (bible for computer architecture) should use RISC-V, it would probably help as a learning aid and spread the gospel about RISC-V.
Of course, it's possible that the current edition of the text already does this.
Here's a nice piece NPR did on him: http://www.npr.org/templates/story/story.php?storyId=4111253