Reading and Learning: June 17, 2015
Wednesday, 17 June, 2015 — learning improvement
I’ve been busy the last few weeks on a client project that consumed a decent chunk of my evenings recently. I learned a lot on the project, and I’ve been able to include a few links and lessons I used along the way.
Articles and books
You are an educated, successful person capable of abstract thought. A VP doing an SVP’s job. Your office, appointed with decent furniture and a healthy amount…
Paul Ford writes 38,000 in Bloomberg about the business of software. Yes, there are shorter books you’ll read. This has been highly spoken of elsewhere, particularly the online experience and the fact that corrections and clarifications are being handled by GitHub.
For an added treat on your desktop machine, open the article, then scroll to the bottom as quickly as you can.
A perceived benefit of a client-side JS framework is the responsiveness of its interface - updates to the UI are instantaneous. A large amount of application…
One of the knocks on Rails (and Ruby) is that they’re slow. Yes, they’re slower than a compiled language. But here are some thoughts on changing how we write Rails applications to deliver in 100 ms. No, not using a client-side framework. Turbolinks.
I feel it’s time to revisit the web vs. native debate, and concede defeat — or, at least, concede that the web cannot, and should not, compete with native when…
With the link above, these are opposite sides of the same coin. Let’s optimize our web applications accordingly.
Startups focus on speed since they are burning cash every day as they search for product/market fit. But over time code/hardware written/built to validate…
Building fast and making technical tradeoffs builds technical debt. The same thing happens at the organizational level and organizational debt is harder to recognize, more damaging, and harder to pay down.
One of the myths of SaaS is that the products are so good, so easy to use, so quick to deploy … that the product sells itself. Given the…
This week I found myself with the rather strange task of testing that styles had been correctly applied to the DOM. There was a good reason for it, honest.…
I just wrapped a client project recently that involves some user-facing customization. This is the technique I used to ensure the style in the customization was being applied correctly. Very helpful.
Recently I worked on a project that required an admin interface for the business owner to manage records within the application. To this end we considered a few different approaches.
…
Since the goal for this project was to build an MVP (minimum viable product) it was agreed building a custom solution would be too much work. After spending time reviewing both ActiveAdmin and RailsAdmin, a decision was made to go ahead with ActiveAdmin. We much preferred the ActiveAdmin interface and didn’t like the idea of applying configuration in our models for RailsAdmin.
Notwithstanding, ActiveAdmin does have a few of it’s own drawbacks. The first of which is it’s dependency on using Devise for authentication, which conflicts with our preference for using Clearance.
This article was helpful on a recent client project where I implemented ActiveAdmin using Monban for authentication
Late last week, it was revealed that Facebook has seemingly taken either lazy or apathy to a whole new level. Yes, you can apparently now reply to text…
I’ve spent the past 8 years or so looking at ugly code. This isn’t uncommon in software development but in my case, I’ve been looking at different ugly code…
About two months ago I saw a site called “ Stanford Nerd ” on Product Hunt . Stanford Nerd works by sending a text message from the website to a Stanford…
I was an economics major in college, and I’ve been grateful ever since for the few key concepts it drilled into me: things like opportunity cost, sunk cost, and…
Nolan Lawson Fellow JavaScripters, it’s time to admit it: we have a problem with promises. No, not with promises themselves. Promises, as defined by the A+…
Screencasts and presentations
I watched or attended the following:
- Ruby Tapas Ep. 287: “Mocking Smells”
- Ruby Tapas Ep. 289: “Mocking Smells 2”
- Ruby Tapas Ep. 296: “Mocking Smells 3”
- Ruby Tapas Ep. 297: “Test Spies”
- Attended Nate Hunzaker’s presentation on React.js at the May, 2015 Triangle Ruby Brigade meeting
- Watched The Weekly Iteration: “Surviving Your First Week in Vim (and beyond)”
- Watched The Weekly Iteration: “Managing Windows in Vim”
- Watched “Vim for Rails Developers”
- Watched Rails Casts No. 416: “Form Objects”
Podcasts
I listened to the following:
- Accidental Tech Podcast Ep. 116: “Women aren’t a
minority”
- A good episode where John, Casey and Marco look at how to expand their audience to include more women and girls
- Ruby Rogues Ep. 204: “Limerence with Dave
Thomas”
- Solid episode on the process of falling in love with development tools and balancing working with new tools against developing mastery with older tools
- Ruby Rogues Ep. 205: “Eight Years of Ruby and Rails with Piotr Solnica”
- Back to Work Ep. 220: “Canadian Gentle”
- The Bike Shed Ep. 15: “Might As Well Be About Trains (Sarah Mei)”
- The Bike Shed Ep. 16: “Wizards Are Hard to Kill”
- Giant Robots Smashing Into Other Giant Robots Ep. 147: “Cry Through it, and Keep Typing (Saron Yitbarek)”
- Ruby Rogues Ep. 207: “Rebuilding Rails with Noah Gibbs”
- The Bike Shed Ep. 17: “Railing About Performance (Sam Saffron)”
- Giant Robots Smashing Into Other Giant Robots Ep. 147: “Cry Through it, and Keep Typing (Saron Yitbarek)”
- Back to Work Ep. 221: “Minimally Viable Interruption”
- Accidental Tech Podcast Ep. 119: “Promoretired”
- Back to Work Ep. 222: “Full-Stack Obsessive:”
- The Bike Shed Ep. 19: “The Oncoming Storm (Sam Phippen)”
- Accidental Tech Podcast Ep. 120: “One Magical Wire”
For some background on what’s going on here, see the first tool sharpening post