i'm speaking here as a grad school grad, interviewee, (inexperienced) interviewer, with a few years amongst different startups, and have switched jobs to get better pay and positions when things go horribly south.
my experience sez: if you demonstrate you're motivated and want to dive into a new environment, and that you have done so successfully in the past, you will be viewed as a good hire. couple that with communication skills and a confidence about what you've done, and you're golden. a lot of the time it seems that job openings may attract at least a couple smart people that could _maybe_ stay focused enough to get the job done. however, what the hiring engineer really wants is someone whom they can get along with. this lets them know that the inevitable differences in coding and work style can be resolved positively and productively. because remember, you're going to be maintaining or writing new stuff within an existing framework and culture, so you need to be able to get along with your coworkers and bosses.
** this may only be valid for the startup realm. but they're fun! and you get a lot of responsibility and flexibility.
I develop web apps every day, and the variable browser support for CSS has generally been a huge pain for me, since I develop on Linux/Firefox, and need to test in Windows/IE, Firefox, Safari, etc. I installed IE7 on its own virtual machine (seems like a huge deal to have it live nicely with IE6), and am pleasantly surprised. Not only does it look and act more like firefox/safari/galeon/etc, it's rendering is more in line with other browsers as well.
From initial testing, CSS support in IE7 is a great improvement. Little niceties like tr:hover now work, and the inheritance of characteristics is much more consistent. So, out of the box, it renders exactly the same as Firefox and other browsers on the pages I've tried so far. Though I have yet to get into much of the positional CSS, which will probably be more of an issue. Has anyone worked with this in any depth? Previously, very poor IE support for positional CSS, and to a much lesser extent with Safari, led me to abandon reworkings of some web apps to move from tables to completely CSS-based designs.
I suppose the most we can hope for with IE7 is that it stays broken in the same ways as previous versions, so we don't have to learn a whole new raft of ugly hacks just to a get a page to look presentable.
Not really. I'd say the most we can hope for is that it fixes itself. I have as strong a dislike of Microsoft as anyone, but I'm so tired of getting angry at IE and having to do all the extra work to claim cross-browser compatibility. Let's recognize an improvement when it's made--even though it's really just doing what it should in the first place. If it makes our lives a little easier on the web dev side, then I'm happy.
Slashdot Mirror
and sad songs are nature's onions.
Nice how the release note is used to complain about Debian maintainers specifically.
i'm speaking here as a grad school grad, interviewee, (inexperienced) interviewer, with a few years amongst different startups, and have switched jobs to get better pay and positions when things go horribly south. my experience sez: if you demonstrate you're motivated and want to dive into a new environment, and that you have done so successfully in the past, you will be viewed as a good hire. couple that with communication skills and a confidence about what you've done, and you're golden. a lot of the time it seems that job openings may attract at least a couple smart people that could _maybe_ stay focused enough to get the job done. however, what the hiring engineer really wants is someone whom they can get along with. this lets them know that the inevitable differences in coding and work style can be resolved positively and productively. because remember, you're going to be maintaining or writing new stuff within an existing framework and culture, so you need to be able to get along with your coworkers and bosses. ** this may only be valid for the startup realm. but they're fun! and you get a lot of responsibility and flexibility.
I develop web apps every day, and the variable browser support for CSS has generally been a huge pain for me, since I develop on Linux/Firefox, and need to test in Windows/IE, Firefox, Safari, etc. I installed IE7 on its own virtual machine (seems like a huge deal to have it live nicely with IE6), and am pleasantly surprised. Not only does it look and act more like firefox/safari/galeon/etc, it's rendering is more in line with other browsers as well. From initial testing, CSS support in IE7 is a great improvement. Little niceties like tr:hover now work, and the inheritance of characteristics is much more consistent. So, out of the box, it renders exactly the same as Firefox and other browsers on the pages I've tried so far. Though I have yet to get into much of the positional CSS, which will probably be more of an issue. Has anyone worked with this in any depth? Previously, very poor IE support for positional CSS, and to a much lesser extent with Safari, led me to abandon reworkings of some web apps to move from tables to completely CSS-based designs. I suppose the most we can hope for with IE7 is that it stays broken in the same ways as previous versions, so we don't have to learn a whole new raft of ugly hacks just to a get a page to look presentable. Not really. I'd say the most we can hope for is that it fixes itself. I have as strong a dislike of Microsoft as anyone, but I'm so tired of getting angry at IE and having to do all the extra work to claim cross-browser compatibility. Let's recognize an improvement when it's made--even though it's really just doing what it should in the first place. If it makes our lives a little easier on the web dev side, then I'm happy.