Linux Job Opportunities
Based on the latest data published below, are you prepared for a job working on Linux? via linux.com
I'm thrilled to know that this is a growing trend. Linux FTW.
Passionate with front end development; Skillful in hand-coded HTML & CSS; ♥ jQuery, web standards, open source. Interested with progressive enhancement, mobile first & responsive web design.
- CSS grows with site size. Depending on your site, this can be a serious issue — not just for performance, but because CSS is code. More code tends to lead to more problems — maintaining code size is a serious concern.
- CSS best practices encourage what would otherwise be bad programming: repetition, bad grouping, loose coupling. Again, if you treat CSS as code that needs to be maintained, reviewed, and refactored, these are negatives.
- CSS is often contextually unreadable. For example,
.about .main ul li li amight be very clever CSS, using a nesting in the markup to trigger a style, but it’s very bad code — without a strong understanding of the HTML, this code can be ambiguous, and its HTML target hard to pinpoint.- CSS encourages overrides, which are the death toll for maintainability. The more styles you override, the more styles you will eventually have tooverride again.
- CSS encourages bad coupling and distant dependencies — for example, let’s say all LIs inherit a margin-bottom we set early in the CSS, and the features we code design with this spacing in mind. Despite the fact that the art director says a particular feature MUST look the way the comp looks, said feature now depends on a very remote line of code, a line that anyone might change without realizing the consequences.
Found at Viget.com, CSS Strategy Square-off.
The approaches highlighted, OOCSS & SMACSS, in the article are also what I consider to adapt going forward with CSS development/authorship.
Comments (0)
SMACSS (pronounced "smacks") is more style guide than rigid framework. There's no library within here for you to download or install. SMACSS is a way to examine your design process and as a way to fit those rigid frameworks into a flexible thought process. It's an attempt to document a consistent approach to site development when using CSS. And really, who isn't building a site with CSS these days?! Feel free to take this in its entirety or use only the parts that work best for you. Or don't use it at all. I understand that this won't be everybody's cup of tea. When it comes to web development, the answer to most questions is "it depends".
Comments (0)
Will this be marked as the end of paper books? Will this invite future iPad market? No one knows. As the device is being priced at $199, I'm sure it'll become a big hit. I quoted below Amazon's CEO, Jeff Bezos, letter which can be found in their website.
There are two types of companies: those that work hard to charge customers more, and those that work hard to charge customers less. Both approaches can work. We are firmly in the second camp. We are building premium products and offering them at non-premium prices.
Although, I own a Kindle 3, which they re-branded as Kindle Keyboard, I found this device as amazingly great. It just saddens me to think that I've bought Kindle pretty early. I shoud have waited for this.
Comments (0)
MJ and I tried brogramming at work. Maybe this is the effect of too much caffeine and sugar-free Red Bull intake.
Caught up brogramming again. Thanks to Raymund Tuquero for this capture.
Comments (1)
Our Best Practices Are Killing Us via Slideshare
For years, we have been suffering with the myth that if we just tried harder, our CSS would stay clean. Each time we start a new project, we valiantly follow best practices and commit ourselves to writing beautiful code. Then, a few months into the project, we're once again faced with a mess. Maybe it was the contractor who committed crappy code? The project manager who would never give us time to refactor? The truth is that our best practices are killing us. In this talk, we will debunk the best-practice-myths that are making a mess out of our sites.
Nicole Sullivan @stubbornella
What are those flawed best practices?
- Classitis!
- Never add an non-semantic element
- Or, a non-semantic class
- Use descendant selectors exclusively
- Sites need to look exactly the same in every browser
There are a lot of points you can get from this slide. One point is that when I get around favoring ids over classes, I found it hard to override the CSS rules or selectors. Specifity becomes really hard to manage and on some point I'm relying so much on the !important derivative which is just the end of the game for overrides. I highly recommend front-end developers and web designers to read the slide and internalize the points it tries to convey.
Comments (1)
Copyleft 2010 Andrew Abogado. Some Rights Reserved. // Jump to Top
Comments (0)