Maybe people should stop putting Bootstrap in their resume when companies stop putting Bootstrap in their job postings.
Sorry devs, Twitter Bootstrap isn't a "skill"
21–25 of 25 posts
Re: Sorry devs, Twitter Bootstrap isn't a "skill"
#22bs article. agree with all the comments. imo, i'd rather know that an applicant knows twitter bootstrap than not. although not exactly similar...it's like saying you know how to use jquery. sure you didn't write jquery, but you can utilize it's libraries. bootstrap is like that for css and some js. why not put it in?
Re: Sorry devs, Twitter Bootstrap isn't a "skill"
#23Earlier quoted context omitted.
As an applicant, you'd be stupid not to target your resume with buzzwords based on trends you see in job descriptions. You are trying to get past the recruiter, who is literally going to crosscheck buzzwords on your application with those in the description. To call applicants kiddies for playing that game the way it's supposed to be played... well, it's just seems naive.
Except that "Twitter Bootstrap" isn't a buzzword at all; it's a collection of CSS, Javascripts, and HTML coding conventions that make it possible to quickly build websites. We put things in our job listing like, "familiarity with Backbone required". Is Backbone a buzzword? Is someone who uses Backbone less of a developer? Should I just automatically assume that anyone with developer after their name knows Backbone? W…
I think to a recruiter, bootstrap, backbone, c++, CAD, flask, etc... Are all just words to match up. That's all I meant when I called it a buzzword.
Re: Sorry devs, Twitter Bootstrap isn't a "skill"
#24The amount of times I have heard: "You don't need to write CSS, just use Bootstrap" or some variation is uncountable. Some thing that just adding a "class='btn...'" to an input instantly makes it a button (without linking the stylesheet or adding a "type=".
I've all but forgotten the intricacies of the DOM due to jQuery. There's probably plenty of developers who have begun their careers in the past 5 years who probably don't know JavaScript as anything other than where they put their document.ready block. Ditto for frameworks like ActiveRecord and the ability to write SQL, etc. Is the lack of underlying knowledge the fault of the framework?
The blame may not entirely be on the framework, but it is certainly on their documentation.
If something goes wrong, a developer should know which resources to use to solve the problem. Abstracting away the lower level stuff should not be synonymous to keeping it completely hidden and inaccessible.
A good example is the AngularJS source code, which is commented enough for anyone to make sense of it after a read-through.
Re: Sorry devs, Twitter Bootstrap isn't a "skill"
#25As much as I want to agree with the backlash here, the pervasiveness of bootstrap as a "solution" to frontend by managers and engineers without frontend experience who then want to make it not look like every other startup website on the planet is what attributes to articles like this one. I can see it asa convenient mock-up tool, but iit's tight couplingto tthe markup and copious counter intuitive default styling does in fact lead to bloat in production websites. I understand that not all devs know frontend well enough to rapid prototype from scratch, but in production bootstrap is duct tape andchewing gum.