sure, and you're the exception, not the norm. i've seen at least one senior dev in each shop too w/o a degree. there are 20 senior developers and 40 junior developers in said shop.
that's a completely made up statement. i have worked in lots of IT shops and the only place to find folks w/o a college degree is in the help desk/desktop support. i've came across but a handful of developers who didn't have a degree.
i've been involved in the hiring process for my companies, and the candidate's college status is a major part of the package. we expect someone to come in with "bright" eyes and to know deeply what they're talking about, not someone who can bs here and there. college only gives part of that. in addition, they need to be a go getter. the should know about code management processes, and about enterprise architectures, n-tier, etc. development patterns, etc.
Maybe you missed this part of the heading (not even TFA):
"Nearly half of the software developers in the United States do not have a college degree."
That isn't just saying not a "computer science, engineering, math, or physics" degree, it's saying any college degree at all. So, presumably a lot more have college degrees with other majors.
So how exactly is almost half plus every programmer with a non-STEM degree "The Exception"? It seems to me the STEM majors are the exception.
yep. we have an internal applet application that uses a self signed certificate. it's deployed to the local file system and launched from a remote page, thus we're stuck using java less than 1.6.24 due to a security change^^^bug oracle made.
True, same as getting a salad at McDonald's -- it's got more fat and sugar than the Big Mac.
i doubt the veracity of those statements.
the big mac has: 28g fat, 46g carbs, and 9 g sugars.
the "worst" salad has 22g fat, 24g carbs, and 7g sugars.
this is one of the largest buzzwords in the industry lately in concert with virtualization. i'm surprised i don't see many "articles" on
i'm not sure i quite understand how or why a software development methodology has become the defacto standard for the project management community as a whole. literally, overnight, project managers have become scrum masters and every project from developing a new predictive pricing solution for sales to an os upgrade project becomes managed as an "agile" project. did manifesto group envision (design/declare) a new project management methodology or good practices for developing (building) software?
your timing belt, water pump, other belt replacement is 350$? i just spent 1200 for mine. that's not chump change. most shops end up at 350 for a standard brake pad replacement every couple of years.
what are the odds.
i think it's ridiculous that it's expected to have to apply security updates. install the software, have a firewall protecting the inside, everything should be fine. most places have seemed to adopt this policy of auto applying patches every week or so regardless of weather the updates affect their usage. potential security issue found in the usb print drivers and puts it on the patches list. what's the probability of a security violation happening due to this potential risk? it's inside the corporate network! if some guy in data entry wants to be disgruntled and hack into the print server, you've really got bigger issues. management issues. maybe he's the same guy who turns on the bathroom faucet every night before leaving to let the water run and drip the company of some money.
ff's auto update really annoys and disrupts my personal workflow. i just learned to turn it off. i only use ff for some functions that don't see to work in chrome right now, citrix is one. it's really sucks to have your computer constantly remind you that it wants to disrupt your work so you have to close your browser and restart the browser to click through some authorize dialog boxes and finally be restored to the prior state.
my understanding is that the reason they don't take the patches is because there isn't a single point of license assignment for the patch source. if RH has a large patch, then RH doesn't take on the role of copyright assignment, but rather allows each single code creator to keep that duty. warm and fuzy of them, but not very practical at all i'm guessing