My 5¢ (AKA the blog)
Because I just don't feel like I can get enough rant into 140 characters and my wall is already full of juice fasts, pictures of everybody's kids and CLICK LIKE IF YOU <3 PUPPIES!!1!!!eleven
RT @evcricket: Largest e-petition to the House ever, at 159,000 sigs. I'd like to see this hit 250k, then it's 1% of Australians. This is…
Freedom of religion is the only freedom protected under the constitution. This bill protects bigotry, not religion.… https://t.co/sT4GmYBvBr
Working with team members that aren't at your physical location can be difficult at the best of times. I've recently had the pleasure of working with some less-than-reliable consultants—let me paint you a word-picture of how that turned out.
Challenging your current development style and practises can be hard. You spend days and weeks learning, discovering and eventually settling on The Right Thing To Do™ (or, at least, the thing that suits you best), but before you know it things have changed and it's time to renew.
Although business process improvement is an essential undertaking for any business, I get a lot of blank stares when I talk to clients about it. The ability to streamline, adapt process to new technologies, standardise and automate are excellent ways for small and medium businesses to reduce cost, improve efficiency and performance, reduce errors, minimise waste and get people spending more time on important value-adding activities rather than repetitive, mundane tasks.
There's plenty to love about adopting an Agile approach to building websites. While I don’t apply all the agile principles and techniques out there, I’ve learned to balance my approach, use what makes sense and works best for everyone. I believe this has improved the success of projects; clients have found that it provides a richer, more involved experience and they're generally much happier with the design, development and the finished product.
CSS has given us many things. The separation of content and semantics has moved the web forward in the last 10 years more than even the most evangelical could have hoped. But there's always been a nagging issue with many developers: the falling behind of many browsers to support the necessary parts of the specifications to allow easy layouts. As older browsers start to die off and we can stop supporting dinosaurs, so too some of the tried-and-true techniques can be left behind.
This final part of Understanding the Cascade introduces the concept of !important declarations and an overview of how all the aspects of the cascade fit together.
Part two of Understanding the Cascade details one of the most intriguing (and least understood) concepts of the cascade, CSS specificity as well as the role that rule order plays.
There are people who work in CSS all day, some amateur and some professional, who may not be entirely familiar with exactly how the cascade in CSS works. Here’s a short overview.