Just read the latest article at Fuel your Interface entitled “Three Big Mistakes that Can Make or Break your Design Career.” Super informative; one of the three tips were to never sit around waiting for work to come – go find it! In this day of social media, personal branding, and transparency, there’s no reason to wait for anything. Go out and get it!

The third tip was to not stretch yourself thin. I’ve personally committed this foul many a time. And everytime, it results in me stressing out, having a lesser quality of life (dramatic, but serious), and most importantly, my work suffers in one of two ways: It’s either terribly late or not as good as it can be. And both of those are unacceptable flaws; so don’t ever take more work than you personally can handle! Try to find someone who you can outsource work to; they may come back to you with work just when you need and don’t expect it.

But the second tip really interested me. Jokingly, it’s referred to as the “Garmon principle” – Garmon being some friend of the author (sorry to belittle your existence, dude named Garmon). From the article:

The first thing you should do is close your laptop, put away your cool bag of tricks, and think. Think, “What would be the perfect site for this? What would it look like? If there were no boundaries, what is the coolest thing, or the most functional way, to make this happen?” Also think, “What will make this worth existing as much or more than the next guy’s interface?” Once you have decided what the best possible solution would be, figure out how to do it. If there is something in your original idea that just simply isn’t possible, then amend it. “Re-idea,” if you will. But never, ever, EVER sit down and start doing things simply because you know how to do them. Because the truth is, no one really cares how much you know about coding or development. The people who are looking at this site aren’t thinking about what it took to make it, or how many advanced lines of code you wrote. They’re thinking about how it is now, as a whole.

So much sense! My feedback after the jump.

(more…)

Yeah, sure, I’d love to see all IE6 users stop using their browsers too, but that’s not what I’m proposing here for IE8 users.

IE8 is a huge improvement in comparison to browsers of the past. Unfortunately, it’s still another browser that we web developers have to perform a cross browser check.

What’s even more frustrating is that IE8 comes with a “compatibility mode,” where users can force IE8 to render code as if it were IE7. This is of course to “make up” for developers who didn’t check their code in IE8.

WTF would Microsoft ship a new browser, with the option to have it act like an older browser? Makes no sense to me; however, I WILL take advantage of this fact to save me time in producing a web site.

Just stick this meta tag RIGHT BELOW the opening head tag. Anywhere else and it’s libel not to work.

And that’s it! If you were having issues in IE8 but NOT IE7 – have issues no more. This meta tag forces compatibility mode to be “on” for whoever browses this site using IE8, and renders the code as if it were IE7. If it’s working, you should not be able to click on the torn page icon for compatibility mode on the right of the url bar.

Correct:

Incorrect:

So now, all you gotta do is make sure your code is Kosher with IE7 – if that’s true, then just stick this meta tag in and not worry about IE8!

Note to Microsoft: Just adopt webkit already! Let me use my rounded corners in your market share majority browser damnit! I’m sick of all this alpha filter crap! If you can do that for IE9, I’ll stop ignoring IE8 developments completely.

I spend most of my working hours on the front-end side of web development, so I tend to be pretty anal about… everything. Work related, that is.

So my buddy Neil Sarkar recently wrote about being lazier when it comes to programming. Though there’s some wavering of topic, the main idea is that as programmers, it’s not so important to know everything all the time – it’s more important to know what you need, when you need it.

This is all based on the premise that everything you don’t know – or used to know – is only a Google search away.

While reading, I found myself agreeing and disagreeing all at the same time. Or maybe separate times. Anyways, more past the break!

(more…)

Skip reading me, and read Brad Frost’s review of the book to your left.

Magento is a beast. While it continues to pickup accolades for it’s robust e commerce feature set, developers round the world can’t help but find it difficult to work with.

As someone who’s been working with the system for some 6 or so months now, I’m nowhere near an expert. But one thing I know, is that unlike other CMS’, you can’t just jump right into it… not easily at least.

With wordpress, I started learning how to make custom themes + plugins before I really embraced blogging with it myelf; and for the most part this was fine. By the time I started blogging myself, I already knew the ins + outs of the whole system via development.

This just isn’t true with Magento. Even after I had figured out the difficult things like how to customize a theme, or how to make a extensible module, I was still learning about how the system did what it’s supposed to: manage products.

Packt publishing recently put out a new book on Magento, giving it the title of “Beginner’s guide.” If you’re just getting into Magento, or considering making the jump, this might be agreat read for you.

But don’t take my words for it. Read Part 1 of Brad Frost’s review here.

Whenever I see pictures like the one to the left, I wonder how long it took the designer to do.

But that’s because I’m stupid, and often forget that I’m something of a computer programmer.

Check out this site Wordle. It’s f*ckin awesome. Just enter in your own text, or choose a url to read text from – the image I made off of their site is in fact generated from text off of my blog.

It takes seconds, and there are a bunch of font / color / styling options. And all of them = awesome.