01 Mar 2019
Git Workshop
I’ve written a Git Workshop site That is all. peace
Read more…
I’ve written a Git Workshop site That is all. peace
At work I’ve been recently exposed to a large and complicated React application written in ES6. Of all the refactoring I’ve been undertaking, I have noticed that there was not much defensiveness built into the classes and functions. By defensive programming, I mean writing the code in such a way that expects it to fail, and gracefully handles common and recurring problems in JS. You do this so your application will continue regardless of any unforeseen problems that occur.
We often get to a point where we have billions of local git repositories that have been merged already, or abandoned - it’s often difficult to see the wood from the trees.
Have you thought about what makes a good programmer? I mean have you sat down and thought hard about what it means? Of all the programmers you’ve met in your (maybe long) career, which ones were ‘good’ and why?
Adapted from a technical talk I gave at Frontend York about using the Google Maps JS badly on a website, the technical debt that can be accrued, and a few different modern techniques to use it well. Full code is available here. When we rely on Google Maps for it’s API (I.e. geocoding addresses, Places API) it becomes a hard dependency on your JS code that becomes a legacy problem and hard to remove.