I've recently started a new job and am now taking part in regular code reviews. The majority of these reviews take place over a video chat in which screen sharing is used in conjunction with Intellij's "Git > Compare with branch" to display the diff. We then talk through the changes and raise any concerns with the changes.
On several occasions, usually mid-sentence, I get the question "Woah, how'd you get your not equals to look like that?" Or equals, or greater-than-or-equal-to, or lambda operator, or ... the list goes on.
"Oh, that? That's a ligature, you can turn that on easily in your Intellij settings."Read More
I'd recently been on a job hunt (now fulfilled), and I was contacted through stackoverflow by a recruiter that had located my stackoverflow Developer's Story and was impressed. He'd asked me to complete a coding challenge which I passed with flying colors. I was then invited to participate in a technical interview with one of their team leaders and a developer - this is where the trouble began.
The first problem was that recruiter had informed me that this interview was to go over my code sample and take a deeper dig into my background; so I wasn't expecting a full-blown technical interview and therefore had failed to do any preparation.
The second problem is that I'd never taken part in a "real" technical interview and as such as I wasn't sure what to expect. I had, of course, read articles in the past about technical interviews, but it had been quite some time. It would have behooved me to reread some articles to have a better idea of what to expect.
So problems one and two are closely related and boil down to a lack of preparation and experience. It is my insight garnered from the third strike that I would like to share with you today: take all interview questions at face value.Read More
[MailCatcher] is a powerful and easy to use Ruby gem that acts as an SMTP server that allows you to inspect emails that your application is sending out in your dev environment.
Installation is pretty simple, these are the commands that I used on my Fedora 29 install to get it up and running. If Ruby is already installed on your machine, or if you've already installed other Ruby gems, you may not need the first few lines.Read More
Super short and simple post this time, because it's explaining a simple concept. The concept is so simple, that I'm slightly embarrassed, almost shocked, that it took me almost 7 years of professional programming, and 3 and a half years of college to see and use this pattern.
The tip? Any time you are writing code and the order of the lines is irrelevant, such as declaring class variables, creating a JSON object, populating an associative array, adding dependencies, configuring your configuration, ad infinitum, use alphabetical order.
Full stack application developer. Life-long learner. Pragmatic programmer. Believer in clean coding. Proponent for extensible and reusable code. Hobbies include (very) amateur photography, collecting old jazz records and going to live music performances.
North Central Ohio, US
All opinions are my own, probably wrong, and subject to change without notice.
© 2017-2019 Todd Eidson. All content is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
Hosted on linode