drol3

5 ms·

1.
by drol3 6y ago
Cool :) Sometimes seeing the same concept from different perspectives makes it easier to understand. For a scala treatment of the same topic see https://underscore.io/blog/posts/2017/06/02/uniting-ch
2.
by drol3 6y ago
I like the idea. Not sure it works on its own, but something like "Investment in tools should be proportionate to your knowledge about the domain" seems reasonable. Beginner? Pick an cheap tool. Expert? pick the best tool :)
3.
by drol3 6y ago
I am working for a company that has moved from 3 to 15 backend developers and 25 to 50 services over the last year. The amount of services is really quite meaninglessness compared to the amount of developers. As with anything the efficiency
4.
by drol3 6y ago
Great news! Was my only blocker :)
5.
by drol3 6y ago
I am continually impressed with the changes Microsoft has made since Satya Nadella took over :)
6.
by drol3 6y ago
Huge fan of this kind of thinking. I try to recommend this technique with software all the time. Basically instead of the workflow bring this 1) follow some tutorial online 2) integrate into real work I do 1) follow some tutorial online 2)
7.
by drol3 6y ago
Thank you so much for all that you have done. Redis is a fantastic piece of work. It is everything software is supposed to be: it's simple and it just works :) Good luck exploring your other options
8.
by drol3 6y ago
I think we can all agree that software should be designed to last :) My experience tells me that when this fails to happen its usually not explicitly due to too many dependencies. Rather it is because the developers have a poor/partial
9.
by drol3 6y ago
In my mind it's surprisingly simple: you VERY honestly ask yourself the question of you know exactly what you are building. If you do then don't be afraid to plan ahead. If you don't, then ship the smallest thing that works :