yyparm

4 ms·

1. 1.▲
   by yyparm 9y ago

   I tend to think the problem identified by the author is more of a fundamental problem with long-lived development branches that diverge with master - stuff will change under you and it's not always easy to notice. It's also kind o
2. 2.▲
   by yyparm 9y ago

   This makes a lot of sense to me. If you're maintaining a large project having lots of non-cohesive commits make it much harder to figure out what the logical changes were. I care about the set of code changes that were required to add
3. 3.▲
   by yyparm 9y ago

   Last time I looked at Presto, it works fine for simple queries (e.g. scanning data and aggregating it into a small result set) but the performance was prone to falling off a cliff as queries got moderately complex - it comes up with a bad q
4. 4.▲
   by yyparm 9y ago

   One lesson to take from this is that it's often worth spending an extra half hour or hour validating that your assumptions about where time is being spent are true. I've seen two examples recently where a potentially impactful opt