Immutables, Part 4 Welcome back to the last post in our immutables series! At this point, you’ve made a shift to using the Immutables library. If you missed our earlier posts,
Immutables, Part 2 Last time, we took a first look at the Immutables library, focusing on the basics of how to generate and use an immutable object.
Immutables, Part 1 A core part of coding in an object-oriented language is, well, creating objects. Plain Old Java Objects (POJOs) are the standard Java object, and they usually look something like this:
IntelliJ Tips and Tricks Yext is primarily a Java shop—aside from a smattering of Go, all of our backend systems are written in Java. For a long time we used Eclipse, which was the standard IDE at
Strange Loop 2018 We’re back from St. Louis! It’s our third year attending Strange Loop and, as usual, it was awesome!
Pure Functions Pure functions are one of the central concepts in functional programming—they’re the building blocks for several complex and powerful ideas. However, pure functions are also incredibly useful when used outside of a functional
Cracking Int To String One of our oldest interview questions is int to string, where we ask candidates to, well, convert an int to the corresponding string. Back when I wrote a series on technical interviews, I
Debugging Fundamentals Debugging’s a critical skill that every software engineer needs to learn. However, it’s something that’s rarely taught. For many engineers, you kind of just have to figure it out (often through trial and
Technical Interviews, Part 3: Communication Welcome back for the third and final part of our technical interview series! In case you missed the earlier parts, go check out part 1 on knowledge and part 2 on coding.
Technical Interviews, Part 2: Coding Last week we had the first post in our technical interview series, where we covered the knowledge you need to succeed in technical interviews. Today, we’ll be looking at the coding portion of
Technical Interviews, Part 1: Knowledge Technical interviews can be daunting, especially if you’re new to the process. I remember being flustered in my first few interviews—I had no idea what to expect and I sometimes didn’t understand what
Good Engineer, Bad Engineer Inspired by Ben Horowitz’s Good Product Manager/Bad Product Manager, I ended up coming up with my own version for software engineers—Good Engineer, Bad Engineer. Keeping the following ideas and principles in mind has
