It’s also rather important to many web applications, in that it’s what we ask our customers to give us in exchange for goods and services. And when we do, both us and our customers want those financial calculations to be very precise. Even tiny rounding errors add up, given time.
Career development is a huge problem for many software shops. The software industry (or at least our corner of it) doesn’t rely on certifications or other external validations. So how can we ensure that our team continues to grow, learn, and improve?
Since the launch of the first responsive website we have had fluid grids and images, but our typography has been static. That is, until recently. The rise of support from the browser vendors for viewport units of measurement has changed that and we can now build sites where the type adjusts to the size of the screen. With a little bit of planning and a dash of sass, we can control our fluid type through all of our breakpoints and ensure a proper text line length across all variants of our design. In this edition of XI to Eye I'll give you an introduction to vw units and how we're using them.
The rise of web standards made authoring CSS easier than ever. However, the browser vendors wanted to move quicker. Their solution was to implement features before the standard was finalized using a vendor prefix for the property.
Here's the situation. You've written your tests. You run your test suite one last time before checking in, and just when you think you are done, you see the big red F indicating test failure.
"Why Me?" you ask. "What now?"
This video discusses strategies for discovering what may have made your test fail, and for exploring what happens during the test run. If you take nothing else away from this video, learn that sometime in the next six months, there's a good chance that git bisect will save you.
Which of these will work for you? For this week's XI to Eye, I've posted my RailsConf presentation on the topic.
I was stuck. I didn't know what to do for the next XI to Eye video. Then I realized that being stuck is a topic.
What do you do when you are stuck in a TDD process? How do you decide where to start when testing? How can you pick what to text next? Why do birds suddenly appear every time you are near? Some of these questions are answered in this video, which also talks about why tests are valuable, and how to approach using tests to drive your application design.
Estimation. Every project does it. Most projects dread it. In this short video, we'll explain why estimating complexity is easier and more manageable than estimating time, and why points are actually a more concrete measure than hours.
For many web projects, a good estimation process is quick and simple: Time spent estimating is not time spent building. Time spent watching an XI to Eye video, on the other hand, is time well spent, indeed.
As web developers, we read code all day. Many of us have used style guides to govern how we structure our code. In this video, I talk about what guides the style guides -- basic principles about what makes code readable and why readable code is easier to work with.
You want your code to be expressive, consistent, logically structured, uniform, and manageable. Also, remember the D.A. rule. Want to know what that means? Watch the video.