The Rock & Roll with Ember band - Jonny Green
11 December 2020
The "Rock & Roll with Ember band" interview series introduces readers of the similarly titled book. They tell us about how they got acquainted with the framework, how they learned it, what they use it for, and a few other questions. I hope you enjoy reading them as much as I did.
Could you introduce yourself in a few sentences?
I'm Jonny Green. I've been in the digital industry for over 25 years now, fluctuating between software development and management, including an 8 year stint running my own digital agency plus several more years contracting.
For the last few years, largely inspired by Ember, it's the development that's getting more focus. Currently I'm an Engineering Manager at Phorest Salon Software. Although there's a huge amount of serendipity around why I work and love working at Phorest, their use of Ember was the initial draw.
Which part of the world are you from?
Originally from Wales - then living in London for many years before making the break for the country about 8 years ago and now living in more rural surrounds about an hour out of London.
When and how did your Ember journey begin? How did you learn about the framework?
A former employee and colleague of mine, Jamie White (organiser of Ember London a few years back), was a big fan and involved in Ember from quite early on. Jamie and I had worked together on a lot of Flash ActionScript projects back in the day. Although Flash has quite rightly been consigned to the digital dustbin of history, it did challenge conventions in terms of what was possible in a browser. I think Jamie recognised that would be its appeal to me, which eventually it was.
After the heyday of Flash, we understood we needed to build more open, accessible, standards-driven apps but missed the single, seamless environment of Flash. The development process instead became very fragmented with the need to dip into different technologies and libraries. The ingredients changed constantly too, meaning returning to legacy projects was tough.
Ember presented a holistic, opinionated way of working which allowed us to meet the modern requirements of UI whilst daring to dream again about what was possible in the browser.
How did reading the Rock & Roll with Ember book help you? Can you recall something that you learned from it?
It was my go-to book for many years, initially to work through on my own to learn about Ember, then as a regular source of reference. Closure actions were something I found myself returning to a lot, partly because they were quite a head-scratcher and partly because Balint's examples were so good. Thankfully, the community recognised this pattern as a cause of issues for learners and it's altogether more straightforward in Octane.
What Ember feature/RFC/etc. are you most excited about?
I think the
@use RFC. I like the way that Glimmer components stripped everything back. It allowed a sense of perspective on what actually needs to be there, and then if required to bring things back in a potentially better way. So for example, whilst the removal of many life cycle hooks felt quite brutal at first, and left a few gaps,
@use promises to solve those problems in a better way.
Other than reading the book, how did you learn to “speak" Ember?
Well the book is essential of course, though also, as a consultant, I selected Ember for a few projects and then hired Ember developers as leads to build them. I then worked "under" the developers I hired as a junior developer.
It's an unconventional strategy and you have to have a strong, honest, mutually-respectful relationship with the developer you hire. It took me a couple of attempts to get right to be honest, though when it worked, it was great. It gave me the ability to learn on live projects and be confident and have control that what was being developed met the project brief.
Is there something you’d like to see covered or explained in more detail in the book?
Are there any (side-)projects that you’ve built in Ember? What is it (are they) about?
However, I loved working with Ember on the bigger projects and it was always a pain to context shift to the smaller projects where a plethora of tools were in use, but none of which quite seemed to do the job as well as Ember. Also, I understood that projects of this nature have an unerring tendency to scale in terms of features and expectation. Without the power tools of Ember under the hood, meeting those increasing expectations is a challenge prone to producing sub-standard, Frankenstein solutions.
As a front-end developer usually working on my own, this model also meant I didn't have to worry about the development of a back-end, or the mainentance of it. Once up and running, it can essentially carry on without developer assistance or intervention.
One example left of that model is the website I built for my wife, www.heatherpollington.com.
Were there any challenges or stumbling blocks while you were building your app(s)?
I remember spending a long time getting Mirage to work against Contentful, which doesn't use any recognised json format.
How much time do you have to work on that project (those projects)?
None any more - but that's how they were designed. To run alone.
What do you like to do in your free time?
I've got massively into WattBiking with Zwift. I was already working remotely prior to lockdown, and my lack of movement and exercise was already bad enough. I would run frequently enough though it's necessarily quite seasonal where I live (either unlit roads with no pavements or boggy fields). For me, Zwift is the perfect marriage of exercise and tech.
If people would like to follow you (or your project), where can they do so?
In the past it would have been my own site but hey, the real world of full-time work has kind of stopped that. Going forward, it's my resolution for 2021 that you will be able to hear from me on Nothing Ventured, Phorest's blog.
If you've read the book, and would like to give a similar interview, please drop me a line at firstname.lastname@example.org.
If you'd like to join the Rock & Roll with Ember band, check out the book of the same name to learn Ember (and be part of a band).Share on Twitter