I used to do a lot of hiring for LAMP resources and found that often, someones framilarity with any language had little relationship to their ability to troubleshoot and debug code. If you are looking for project work with clearly defined objectives and deliverables (what IT project is EVER clearly defined) then LAMP proficiency is good enough).
Peronsally, like to give them a busted website running on an issolated VM and two hours to fix it. They can have google, and whatever reference material they need and ask any questions they want. To torture them, do everything from messed up permissions on directories, bad apache configs, bad code, dynamic code, wonky databases, and bad SQL Queries. See how far they get but also how they troubleshoot. What do they prioritize first? Do they write quick scripts from the command line to test database connectivity?
The goal is not to get the website functioning but to see what they fix, how they fix it, and what priority they placed which pieces.
This is just like all the other fluff bills out there. Politicians want to create a reputation of being tuff on drugs, guns, health, etc. So they introduce bills as rediculous as this so they can say they worked hard on whatever issue they are grandstanding about during election season. This is just normal politics, it will get assigned to a comittee and then forgotten...
Well, this strikes me as a good way to create one large highly vulnerable target. I understand conserving energy and creating a single uniform and tight security standard, but putting all your eggs in one basket is like putting up a neon sign that reads "ALL HACKERS WELCOME, HOURLY RATES APPLY"
Slashdot Mirror
I used to do a lot of hiring for LAMP resources and found that often, someones framilarity with any language had little relationship to their ability to troubleshoot and debug code. If you are looking for project work with clearly defined objectives and deliverables (what IT project is EVER clearly defined) then LAMP proficiency is good enough). Peronsally, like to give them a busted website running on an issolated VM and two hours to fix it. They can have google, and whatever reference material they need and ask any questions they want. To torture them, do everything from messed up permissions on directories, bad apache configs, bad code, dynamic code, wonky databases, and bad SQL Queries. See how far they get but also how they troubleshoot. What do they prioritize first? Do they write quick scripts from the command line to test database connectivity? The goal is not to get the website functioning but to see what they fix, how they fix it, and what priority they placed which pieces.
This is just like all the other fluff bills out there. Politicians want to create a reputation of being tuff on drugs, guns, health, etc. So they introduce bills as rediculous as this so they can say they worked hard on whatever issue they are grandstanding about during election season. This is just normal politics, it will get assigned to a comittee and then forgotten...
Well, this strikes me as a good way to create one large highly vulnerable target. I understand conserving energy and creating a single uniform and tight security standard, but putting all your eggs in one basket is like putting up a neon sign that reads "ALL HACKERS WELCOME, HOURLY RATES APPLY"