kidding right?
He closed an html image tag the way you would close an image tag using forum code.
It took me 15 seconds or so before I figured it out
In html it’s like:
<img src="whatever.jpg">
You just close it with a bracket thing.
He closed it with </img>, as if it were:
[img]whatever.jpg[/img]
At least I think that’s it. I’m not very good at coding.
|
He closed an html image tag the way you would close an image tag using forum code.
It took me 15 seconds or so before I figured it out In html it’s like: <img src="whatever.jpg"> You just close it with a bracket thing. He closed it with </img>, as if it were: [img]whatever.jpg[/img] At least I think that’s it. I’m not very good at coding. |
you’re assuming he knows forum coding.
it’s probably just a stupid mistake.
|
you’re assuming he knows forum coding.
it’s probably just a stupid mistake. |
No. Look at the other mistakes in the code. That’s NOT the only one.
These guys are "senior" developers, too. I have no fucking clue how they got this far.
|
Toad, do you close img, meta, li, etc. tags? HTML5 has a lot of tags that don’t need to be closed but I still close them because I like the XML look more.
Agree or disagree? |
I close them out, always. Mainly because it’s out of habit and I as well have grown accustomed to the XML look.
|
He closed an html image tag the way you would close an image tag using forum code.
It took me 15 seconds or so before I figured it out In html it’s like: <img src="whatever.jpg"> You just close it with a bracket thing. He closed it with </img>, as if it were: [img]whatever.jpg[/img] At least I think that’s it. I’m not very good at coding. |
it’s just xml format. whoever wrote it probably doesn’t know anything about html so they just assumed it was the same for all elements
|
Toad, do you close img, meta, li, etc. tags? HTML5 has a lot of tags that don’t need to be closed but I still close them because I like the XML look more.
Agree or disagree? |
always close them. and fyi, not closing form elements like input can actually break functionality in old browsers (:cough: IE). I painfully found that out when building a Drupal6 site 2 years ago for a bank that still used IE6 and IE7. input elements that weren’t closed couldn’t be selected in javascript, but afaik Drupal6 didn’t have field templates or anything for form elements and I never did find a fix for it.
tru.dat
|
Toad, do you close img, meta, li, etc. tags? HTML5 has a lot of tags that don’t need to be closed but I still close them because I like the XML look more.
Agree or disagree? |
I am with Toad, I close them because I am used to it
|
What about nesting block elements within anchors?
I still don’t do that. I figure that might have unpredictable results with older layout engines. |
Yeah, I still can’t do that either.
Crazy.
how much do these "senior" developers get paid?
The indentation is the most bothersome
8? wtf?
Depends on the employer. Some of them conduct really shitty interviews and get "talkers". Basically, people who have an understanding of the internet and web development, but aren’t actually that good at what they do. I’ve seen shitty developers in LA make around 100k. But I’ve also seen not-so-skilled developers have more sr. titles simply because they have good leadership capabilities. In which case, it’s often worth it to bring them in if you want someone who can strengthen the team.
I’m responsible for all the technical interviews in the firm I work for, and I gotta tell you, it’s actually pretty rare to find competent people. I’d say out of the last dozen or so people I’ve interviewed, two or three of them I’d consider solid developers. The last dude I interviewed pretty much owned me in the interview and was the first person that scored well on all of the problems presented and got all the questions correct. He accepted Yahoo’s offer instead.
To give you some context, I start with easy problems and they progressively get more difficult. All problems are are given to them verbally and the interviewee is required to solve the problem on a whiteboard and marker.
I ask people how they would score themselves in each of the skills they specialize in on a scale from 1-10 (ie: javascript, etc). 1 being novice, 10 being genius. Most people say "9-10", when they’re usually around 4-6.
EVERYONE who’ve I’ve given a javascript problem to and they start with "$(‘#blah’)", have all performed like shit. Too much framework dependence in this industry.
|
Depends on the employer. Some of them conduct really shitty interviews and get "talkers". Basically, people who have an understanding of the internet and web development, but aren’t actually that good at what they do. I’ve seen shitty developers in LA make around 100k. But I’ve also seen not-so-skilled developers have more sr. titles simply because they have good leadership capabilities. In which case, it’s often worth it to bring them in if you want someone who can strengthen the team.
I’m responsible for all the technical interviews in the firm I work for, and I gotta tell you, it’s actually pretty rare to find competent people. I’d say out of the last dozen or so people I’ve interviewed, two or three of them I’d consider solid developers. The last dude I interviewed pretty much owned me in the interview and was the first person that scored well on all of the problems presented and got all the questions correct. He accepted Yahoo’s offer instead. To give you some context, I start with easy problems and they progressively get more difficult. All problems are are given to them verbally and the interviewee is required to solve the problem on a whiteboard and marker. I ask people how they would score themselves in each of the skills they specialize in on a scale from 1-10 (ie: javascript, etc). 1 being novice, 10 being genius. Most people say "9-10", when they’re usually around 4-6. EVERYONE who’ve I’ve given a javascript problem to and they start with "$(‘#blah’)", have all performed like shit. Too much framework dependence in this industry. |
Can you post some of your interview questions? Just curious
|
I’m responsible for all the technical interviews in the firm I work for, and I gotta tell you, it’s actually pretty rare to find competent people. I’d say out of the last dozen or so people I’ve interviewed, two or three of them I’d consider solid developers.
|
Sounds like a pretty good ratio
|
[b]i think a white board would be too weird to me. you’re alienating anyone who can’t write code by hand on a white board. people are all wired differently, and some, including myself, might get a little tripped up having to hand write it. shit, with my luck i might just start writing in php when you want javascript because the whole thing is just too different.
i code on a computer with a keyboard using a program that has syntax highlighting. expecting anything besides that is a waste of your time and mine. on the other hand, maybe i’d do just fine. |
Any web developer can write some degree of code on a whiteboard, even if it’s just psuedocode. They may find it difficult to perform under those conditions, but it’s really up to the interviewer to create optimal conditions for the candidate. If we’re hiring a developer that wants 60k+ for their skills, they better be able to handcode.
And the fact that you might trip up writing PHP instead of javascript, that’s fine. You’re really looking for problem-solving ability. Syntax is easy to learn, easy to teach, and easy to pick up. I’ve hired people based off their ability to write psuedocode because they were able to solve problems optimally and correctly. There are a variety of ways to discover highly talented and intelligent individuals that will rock your apps.
I’ve been in all kinds of interviews. I’ve been in interviews that were extremely easy to pass. Firstly, why would I want to work for a company where you won’t be able to learn off ANY of the people conducting the technical interviews? I wouldn’t. I’ve been required to whiteboard in front of a five chinese dudes in business suits. Talk about nerve wrecking. One interview I went on for a reputable gaming company (as a fucking DRUPAL developer, none the less) pretty much had me write and walk them through the creation and modular components of an asteroids application. I’ve also been in interviews where I’ve had to blindly handcode in front of a group of developers that were highly more technical than I am.
I’ve walked away feeling like I’ve failed a number of times, only to have to have them call give me an offer a few days later.
If you ever want to work for a reputable firm that has a highly technical team, you should probably start working on your whiteboarding skills. Thankfully, I had C++ professors that forced us to whiteboard in front of the whole classroom. Years later, I’m kind of thankful for that.
I’m not really the "solo developer" that I was years ago. I actually learned a lot from working with teams. Right now I lead four teams and support one other. You might recall me recruiting on OT a while back. The teams I work with are pretty much badass. That includes the people I decide to work for, and the people that I want to hire.
Depends on the level the candidate is applying for. Novice devs are usually tested on simple shit. HTML semantics, CSS specificity, cross-browser compatibility, etc. More experienced devs are tested on scoping, optimization, logical problem solving, etc. More senior people are tested on patterns, performance, browser memory and behavior, closures, prototyping, etc.
|
Any web developer can write some degree of code on a whiteboard, even if it’s just psuedocode. They may find it difficult to perform under those conditions, but it’s really up to the interviewer to create optimal conditions for the candidate. If we’re hiring a developer that wants 60k+ for their skills, they better be able to handcode.
And the fact that you might trip up writing PHP instead of javascript, that’s fine. You’re really looking for problem-solving ability. Syntax is easy to learn, easy to teach, and easy to pick up. I’ve hired people based off their ability to write psuedocode because they were able to solve problems optimally and correctly. There are a variety of ways to discover highly talented and intelligent individuals that will rock your apps. I’ve been in all kinds of interviews. I’ve been in interviews that were extremely easy to pass. Firstly, why would I want to work for a company where you won’t be able to learn off ANY of the people conducting the technical interviews? I wouldn’t. I’ve been required to whiteboard in front of a five chinese dudes in business suits. Talk about nerve wrecking. One interview I went on for a reputable gaming company (as a fucking DRUPAL developer, none the less) pretty much had me write and walk them through the creation and modular components of an asteroids application. I’ve also been in interviews where I’ve had to blindly handcode in front of a group of developers that were highly more technical than I am. I’ve walked away feeling like I’ve failed a number of times, only to have to have them call give me an offer a few days later. If you ever want to work for a reputable firm that has a highly technical team, you should probably start working on your whiteboarding skills. Thankfully, I had C++ professors that forced us to whiteboard in front of the whole classroom. Years later, I’m kind of thankful for that. I’m not really the "solo developer" that I was years ago. I actually learned a lot from working with teams. Right now I lead four teams and support one other. You might recall me recruiting on OT a while back. The teams I work with are pretty much badass. That includes the people I decide to work for, and the people that I want to hire. |
can people actually live on 60k in LA?
When I first moved to LA I lived a decent life making 36k.
|
Toad, do you close img, meta, li, etc. tags? HTML5 has a lot of tags that don’t need to be closed but I still close them because I like the XML look more.
Agree or disagree? |
LET’S LEAVE OFF BRACKETS AND SEMICOLONS CAUSE WE CAN. don’t be a noob and do that shit since it’s annoying to read and shit still breaks when its done that way.
How does this make the code any better?
|
no but 4rlz, that was a good post. i’ve never been interested in joining a firm but you certainly gave me some insight as to what i can expect if i ever have a change of heart.
fact is that i hate this industry a lot and i’m only in it because i’m good at it and it pays the bills. it’s so unfulfilling for me. i do NOT see myself doing this shit when i’m in my 40’s. |
Yep. I don’t want to be coding when I’m 40 either. I suppose that’s why I began focusing on the team aspect of things.
|
[b]i think a white board would be too weird to me. you’re alienating anyone who can’t write code by hand on a white board. people are all wired differently, and some, including myself, might get a little tripped up having to hand write it. shit, with my luck i might just start writing in php when you want javascript because the whole thing is just too different.
i code on a computer with a keyboard using a program that has syntax highlighting. expecting anything besides that is a waste of your time and mine. on the other hand, maybe i’d do just fine. |
Any web developer can write some degree of code on a whiteboard, even if it’s just psuedocode. They may find it difficult to perform under those conditions, but it’s really up to the interviewer to create optimal conditions for the candidate. If we’re hiring a developer that wants 60k+ for their skills, they better be able to handcode.
And the fact that you might trip up writing PHP instead of javascript, that’s fine. You’re really looking for problem-solving ability. Syntax is easy to learn, easy to teach, and easy to pick up. I’ve hired people based off their ability to write psuedocode because they were able to solve problems optimally and correctly. There are a variety of ways to discover highly talented and intelligent individuals that will rock your apps.
I’ve been in all kinds of interviews. I’ve been in interviews that were extremely easy to pass. Firstly, why would I want to work for a company where you won’t be able to learn off ANY of the people conducting the technical interviews? I wouldn’t. I’ve been required to whiteboard in front of a five chinese dudes in business suits. Talk about nerve wrecking. One interview I went on for a reputable gaming company (as a fucking DRUPAL developer, none the less) pretty much had me write and walk them through the creation and modular components of an asteroids application. I’ve also been in interviews where I’ve had to blindly handcode in front of a group of developers that were highly more technical than I am.
I’ve walked away feeling like I’ve failed a number of times, only to have to have them call give me an offer a few days later.
If you ever want to work for a reputable firm that has a highly technical team, you should probably start working on your whiteboarding skills. Thankfully, I had C++ professors that forced us to whiteboard in front of the whole classroom. Years later, I’m kind of thankful for that.
I’m not really the "solo developer" that I was years ago. I actually learned a lot from working with teams. Right now I lead four teams and support one other. You might recall me recruiting on OT a while back. The teams I work with are pretty much badass. That includes the people I decide to work for, and the people that I want to hire.
Depends on the level the candidate is applying for. Novice devs are usually tested on simple shit. HTML semantics, CSS specificity, cross-browser compatibility, etc. More experienced devs are tested on scoping, optimization, logical problem solving, etc. More senior people are tested on patterns, performance, browser memory and behavior, closures, prototyping, etc.
|
Any web developer can write some degree of code on a whiteboard, even if it’s just psuedocode. They may find it difficult to perform under those conditions, but it’s really up to the interviewer to create optimal conditions for the candidate. If we’re hiring a developer that wants 60k+ for their skills, they better be able to handcode.
And the fact that you might trip up writing PHP instead of javascript, that’s fine. You’re really looking for problem-solving ability. Syntax is easy to learn, easy to teach, and easy to pick up. I’ve hired people based off their ability to write psuedocode because they were able to solve problems optimally and correctly. There are a variety of ways to discover highly talented and intelligent individuals that will rock your apps. I’ve been in all kinds of interviews. I’ve been in interviews that were extremely easy to pass. Firstly, why would I want to work for a company where you won’t be able to learn off ANY of the people conducting the technical interviews? I wouldn’t. I’ve been required to whiteboard in front of a five chinese dudes in business suits. Talk about nerve wrecking. One interview I went on for a reputable gaming company (as a fucking DRUPAL developer, none the less) pretty much had me write and walk them through the creation and modular components of an asteroids application. I’ve also been in interviews where I’ve had to blindly handcode in front of a group of developers that were highly more technical than I am. I’ve walked away feeling like I’ve failed a number of times, only to have to have them call give me an offer a few days later. If you ever want to work for a reputable firm that has a highly technical team, you should probably start working on your whiteboarding skills. Thankfully, I had C++ professors that forced us to whiteboard in front of the whole classroom. Years later, I’m kind of thankful for that. I’m not really the "solo developer" that I was years ago. I actually learned a lot from working with teams. Right now I lead four teams and support one other. You might recall me recruiting on OT a while back. The teams I work with are pretty much badass. That includes the people I decide to work for, and the people that I want to hire. |
can people actually live on 60k in LA?
When I first moved to LA I lived a decent life making 36k.
|
Toad, do you close img, meta, li, etc. tags? HTML5 has a lot of tags that don’t need to be closed but I still close them because I like the XML look more.
Agree or disagree? |
LET’S LEAVE OFF BRACKETS AND SEMICOLONS CAUSE WE CAN. don’t be a noob and do that shit since it’s annoying to read and shit still breaks when its done that way.
How does this make the code any better?
|
no but 4rlz, that was a good post. i’ve never been interested in joining a firm but you certainly gave me some insight as to what i can expect if i ever have a change of heart.
fact is that i hate this industry a lot and i’m only in it because i’m good at it and it pays the bills. it’s so unfulfilling for me. i do NOT see myself doing this shit when i’m in my 40’s. |
Yep. I don’t want to be coding when I’m 40 either. I suppose that’s why I began focusing on the team aspect of things.