GitArborist.com has now been live for five months. For previous info you can jump to the previous updates at five, four, three, two, and one months. August 2020 Stats First, the stats: Total Installations: 10 Scheduled PRs Merged: 25 PRs Merged: 60 (inc. scheduled) Repositories Watched: 1587 What's Changed Not many changes this month due to various personal circumstances. I've tried to add a few articles as a simple “content marketing” strategy.
It's no secret that developers who create toy apps, side projects, or tutorials, benefit from the process. Initially, I thought this could be boiled down to just being good forms of learning. Building something new, and even more so teaching something new, are both great ways to learn. There is another benefit, however: Developers who do this are building their own code library. Sure, maybe the code isn't production-ready, but it's at least a (hopefully) working example that can act as a combination of reference implementation, quickstart guide, and memory-jogger.
I remember the day my code comments died. It was 2012, I had moved up from Junior Developer to Developer. My project had started as pure R&D, then moved to prototyping, and finally to production. As part of the work, I had to develop an algorithm to run over an incoming stream of measurements and detect outliers. Once we had settled in on our approach my supervisor asked me to write it up.
Sprints My first “real” day job as a software developer was for a large and well-established company. When I started the software teams followed the Scrum form of Agile. I strongly dislike some of the terminology used in Scrum, the two main offenders are “velocity” and “sprint”. Poor naming aside, the general approach to software work in Scrum, and many other capital-A Agile methodologies, is to treat the work as a never-ending stream of tickets to be completed over time.
GitArborist.com has now been live for five months. For previous info you can jump to the previous updates at four three, two, and one months. July 2020 Stats First, the stats: Total Installations: 9 Scheduled PRs Merged: 21 PRs Merged: 46 (inc. scheduled) Repositories Watched: 1515 What's Changed Paid plans! The EarlyBird plan has been retired (any existing EarlyBird installations will continue, however). This also required removing GitArborist from the GitHub marketplace, as their TOS requires that you must list paid plans on the marketplace if they are also listed elsewhere.
There's a lot of information available about ways to improve performance in Ruby on Rails applications. I've even written about it myself. But one thing that's often skipped over is exactly how you are supposed to benchmark your performance improvements, particularly if you want to do a full end-to-end speed comparison. Benchmarking vs Profiling A quick refresher; to profile code (in performance terms) is to figure out which parts of the code are causing a slowdown.