Hacker Bits, April 2016

More documents

Recommendations

Info

Interesting 56 hacker bits
Work for only 3 hours a day, but every day By NON UMEMOTO I am an indie iPhone developer, and I’ve been working for 3 hours every day for almost 2 years now. It may not work for everybody, but I started this habit in early 2014, and I have continued to do it since have I found that this is the most productive way to work for me. Taleb and DHH advices I first got this idea when I watched the talk by DHH (Rails creator) in the startup school. He was saying this: “Working long hours isn’t productive at all, if you work for 8 hours, try for 5 hours, or only for 4 hours. If you only have that time to work, you don’t have time to see Twitter while working.” Also, when I read the book Antifragile by Taleb, he mentioned that the trick to working in a productive way over a long period of time is to only work for a short amount of time every day. Making money on the App Store is really tough, and people don’t care how many hours I spend on my apps. They only care if it is useful or not. This is a completely result oriented world, but personally, I like it. I have always thought about how I can optimize my time to work effectively, and after I tried a lot of different ways, I found it best to limit my work time each session for the best result in the long run. Spaces are a very important factor in UI design, and that theory holds true for working. Why 40 hours a week didn’t work I can choose how I spend my time since I am making my own apps, so first I’d been searching for the most effective way to divide my work time weekly and monthly. hacker bits 57
Page 1 and 2:
hacker bits April 2016
Page 3 and 4:
content bits April 2016 06 We hire
Page 5 and 6: Non Umemoto Non is an indie iOS dev
Page 7 and 8: One of the most common pieces of ad
Page 9 and 10: I don't mean to be critical of anyo
Page 11 and 12: Look beyond People Like Us and imag
Page 13 and 14: About 50% of the Triplebyte candida
Page 15 and 16: similar to something you’ve seen,
Page 17 and 18: ace to answer. Practice writing the
Page 19 and 20: Companies going under is a real pit
Page 21 and 22: near insolvency or when the directi
Page 23 and 24: job of documenting that you did wha
Page 25 and 26: job. Think very carefully before ju
Page 27 and 28: There are storm clouds gathering ov
Page 29 and 30: These markets generally take a long
Page 31 and 32: It all started with an email I wrot
Page 33 and 34: David, I’m still interested in mo
Page 35 and 36: My "celebration" at In-N-Out So sur
Page 37 and 38: Figure 1: Wireshark happening on yo
Page 39 and 40: other day that those filter rules a
Page 41 and 42: What are those about? (see Figure 1
Page 43 and 44: Tell me about your program then, yo
Page 45 and 46: Figure 7: Person 1 nvd3.js, presuma
Page 47 and 48: Figure 9: Person 2 Figure 10: Pers
Page 49 and 50: “webStatus” goes to online? So
Page 51 and 52: Building a startup in 45 minutes pe
Page 53 and 54: Lean Domain Search — January 2012
Page 55: Wget's major strong side compared t
Page 59 and 60: With this method, I don’t get str
Page 61 and 62: The programming community has been
Page 63 and 64: I believed I was created to do this
Page 65 and 66: sions to build, over time. That is
show all

Hacker Bits, April 2016

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?