February 11th: How to Be a Better Engineer
InRhythm’s mission, in the work we do and the people we hire, is acutely focused on learning and growth. Through the development of InRhythmU, our internal professional growth initiative, we’re developing programs to ensure that our engineers reach the level of technical ability required by our clients. Being a great engineer involves more than keeping up with tech trends or mastering a framework, however.
We want to create bar-raisers who take our client relationships to the next level. The real goal is to train engineers who can approach engineering problems strategically and make good choices in a world of infinite options. As we develop this system of skill building and growth, a few key questions emerge. How do junior engineers learn to become senior engineers? How much technical ability should a UI designer aim for? Should every member of the team understand user experience design? Database design? What does “full-stack engineer” really mean? And what’s our role in building the next generation of software?
This month we dive into these issues, led by senior InRhythm engineer Brian Olore, whose article “Becoming a Senior Engineer” clearly lays out some tips, tricks, and time-tested strategies that will help you raise that bar.
Thanks and Keep Growing,
Becoming a Senior Engineer
(4 min. read)
“Looking to take your engineering career to the next level? These five tips will set you on the path to greater things and make you a standout in the field. As we all know, it’s not easy to be exceptional in this already-competitive field, but the reward for real leadership is high, and if you’re truly passionate about your craft, these tips—including mentorship and open source contributions—will be something to get excited about.”
What We’re Reading Around the Web
The Great Divide
(14 min. read)
Designing for the Web Ought to Mean Making HTML and CSS
(4 min. read)
Signal V. Noise
HTML, CSS and Our Vanishing Industry Entry Points
(6 min. read)
“It ain’t easy bein’ green. The leadership team at InRhythm spends a great deal of time improving the way we attract, train, and retain talent. Many of our hires are relatively new to this industry; Rachel Andrew has been thinking about what those new entries into this field face, worried that we’re excluding many people unnecessarily, especially those without formal training. What about those who learn ‘on the job,’ view source and copy, or futz around with a GitHub repo and learn on their own? Aren’t ambitious people to be valued? Didn’t the web grow so rapidly and profitably specifically because barriers to entry didn’t exist? ‘If we make it so that you have to understand programming to even start, then we take something open and enabling, and place it back in the hands of those who are already privileged.’ There may be implications here for society, and freedom; Andrew’s larger point is worth considering.”
What Happened to the Internet?
(11 min. read)
“Here’s to the crazy ones, the misfits, the rebels, the troublemakers. We’ve been told that technology companies value those who ‘Think Different.’ Is that still true on the Internet? Jared Sumner reminds us of a time when the web was ‘weird and fun,’ and we liked it! Is coding now a privilege, instead of a right? Wasn’t this technology supposed to be a great equalizer, rather than an opportunity to be monopolized by tech giants? Following this line of thinking and going deeper, Meghan Keaney Anderson asks us whether ‘what was once the closest thing we could imagine to a meritocracy more closely resembles an oligarchy ruled by a few powerful gatekeepers.’ Food for thought.”