[Weekly Drip 039.1] Graphs (real and fake), Profilers, Firefox eats crow


alt text

Have you ever wanted to visualize a GitHub profile? Now you can, with GitHub Profile Summary. After you star the GitHub repo, you can enter your profile name to visualize your GitHub profile. Thanks for the awesome tool David!

alt text

You learned nothing from the above graph. Read a bogus study on code review to find out why. In it, Wesley Aptekar-Cassels dives into an oft-cited research set and points out numerous ways in which it is deficient. To coin a term, it is fake news. Wesley ends with I encourage you to think critically about the data being presented, find original sources to determine the methodology being used to collect data, and at the very least double check that the graph that you're being shown actually supports the claim that's being made.

Firefox is once again in the top stories, but not for a normal reason. There were some concerns when someone found a suspicious looking dev addon called Looking Glass 1.0.3. Drew DeVault wrote up a good explanation of Firefox’s slippery slope, which goes into more detail. The good news is that Firefox apologized. Firefox stated on the 18th “We didn’t think hard enough about how our actions would affect the community, and we’re sorry for letting you down.”

Ever wondered how Ruby & Python profilers work? The always-readworthy Julia Evans has a comprehensive post discussing tracing and sampling profilers in Ruby and Python. She cautions against naively accepting numbers from tracing profilers: For example, if you have 2 implementations of something – one with a lot of function calls and one without, which take the same amount of time, the one with a lot of function calls will appear to be slower when profiled. The post finishes with a list of detailed posts about pyflame, which is how she wants her Ruby profilers to work as well.

Rust had a great year in 2017. They had some big goals outlined in there 2017 roadmap, which they published in February. Some major milestones they met included lowering the bar for entry to rust. This included the start of creating several books for Rust (one available to preorder now). Also, improving the RustBridge workshop curriculum, which is available for free. Read more about what Rust achieved this year on their blog.

Development Dregs

Blog Posts this week from DailyDrip

alt text


This post was written by the DailyDrip team and syndicated via Inside.com's network of email newsletters.