zjyeung
Agreed. I would even say in these past 3 years or so, React Native development has smoothed itself out. The experience of setting up an app and being productive in it coming in as a web developer is phenomenal. One thing is that the community support is still small compared to native or even React itself. Peformance too is lacking. I've been waiting for the new architecture Fabric to come in replacing JSC with JSI but it's taking quite a long time. There still isn't a clear estimate on it's release yet.
All of the examples that the author gave just show that the tasks we think are really important or urgent, are not. In fact, perhaps what might help the most is using an Eisenhower Matrix and taking the time to categorize the tasks on hand. Another thing I noticed is the example of writing the essay for the volume of Philosophy. It's true that he was stressing over nothing as everyone else was late but wouldn't it be better if he didn't have to worry about it all this time.
Perhaps the best way to handle procrastination is to just do the "actual" important and urgent tasks early in the day so that you can do w.e tasks you want later. Also take more breaks. The author himself takes a break when he goes to the dorms and chills with the student. (although he mentions it as procrastination)
Maybe we just need to face the truth that we aren't superhuman. We have a finite amount of resources at our disposal including time, energy, effort (physical or mental) and emotions. We need to rest and recharge. Essentially, it's important to ruthlessly prioritize and frequently take breaks.
It was only in January that I started running or exercising intensely and noticed only a slight decrease in performance. Mainly that was due to not exercising for a month or so. However, overall I didn't notice that running/working out was significantly (>10%) harder but In my case, I took a very longer break than other. Just some food for thought
> I'll be gone in a year, so why bother writing software that's maintainable? It won't be my problem.
I would say that's why it's so important to have a core of competent technical employeers. One thing that is so underrated is company culture. If your technical managers or supervisors enforce stricter code quality, naturally everyone will follow on. Culture trickles down not up. The result you're seeing is from the effects of bad management or bad technical leadership.
>Also, as long as customers (including B2B customers) are happy with dreck, then dreck, they get. Why bother putting in the considerable extra cost for Quality, when the suc- um, customers, will be happy with garbage?
That's the thing. No customer likes garbage. Garbage here defined as buggy, slow or unusable product. They make do either because there's no other alternatives and/or this product meets their needs or is the market leader. However, there is still always a tradeoff between quality and time to market. It's impossible to get perfection and sometimes good enough is well... good enough.
Why? Every religion or non-religion is based on belief. Even if you are not religious, you have some fundamental beliefs that require some sort of assumption. Logic and religion are not incompatible.