3 ms·
Writing is always going to be slower, especially if done well. When it comes to UI, tight feedback loops are crucial at virtually every step of the way.
by incrudible 4y ago
Writing is always going to be slower, especially if done well. When it comes to UI, tight feedback loops are crucial at virtually every step of the way.
- db48x 4y agoA feedback loop can be tight, or high–bandwidth, without having low latency. You just have to increase the sending window. Either that, or delegate more. If your designer tells you to implement X, and after that is done tells you to do Y, have them increase the sending window by telling you to do X, Y, Z and W up front. Then, when you implement W and it doesn’t feel quite right to you, you can implement W’ instead; that’s delegation.
- incrudible 4y agoThat is not a solution. You do not get to just decide on whether latency or bandwidth is the bottleneck of your task.
- db48x 4y agoThere’s no law of physics saying that a company cannot delegate decision–making authority to individual employees. If your employer doesn’t let you make that kind of decision, then that is a social problem rather than a physical one. Note that I have not said that an individual employee can decide how their employer does business, only that your development processes can be arranged so that they do not require low–latency in–person meetings between employees. You can do your business with or without any overlap in working hours between employees that interact with each other; the overlap is not required.
- incrudible 4y agoI am not saying it is impossible, I am saying it is slower. Maybe that is a worthwhile tradeoff for you, but at least to me, in this particular scenario, it is not. It would be a frustrating process. I do generally hold a favorable view towards remote work, but if I can not get you on the phone at all, that makes your work less valuable to me.