I know you've said you're trying to avoid screwing it up, but if you want, the CentOS wiki is pretty good for explaining what and why, and since it's a kernel firewall, it applies to Ubuntu too. In fact, I suspect all other "firewall tools" are basic GUI frontends to iptables. If you are indeed concerned about firewalling (though not quite as concerned as crypto-specialists), you probably at least want to have a go at it manually with some easy to understand notes
When in doubt, try it on a virtual machine of course.
Where have we seen in consumer space the ability to rollback an uncompleted install? Once it's installed, the only way back is to find a previous installer, nuke, and reinstall.
This has been standard IT procedure since Microsoft invented "service packs."
Indeed, and since way before too.
It used to be that you never went for the x.0. Nowadays, we have to be wary of getting any x.y.0
Nevermind what the distro or the desktop environment is (well, within reason). So long as you can help her, even on the end of a crackly phone line, it's fine.
When installing for any non-techie, Desktop Environment aside, show them how to find their browser and applications, show them how to find the file manager, and install Synapse so that they can search for pretty much anything (for bonus points, set the Synapse shortcut to something simple like Super+Space). Basically, give them their starting points, and show them how to search.
Whether you choose to move your mother/relative/neighbour to KDE, Xfce, GNOME 3 or even Unity if you like (or even Windows or Mac at that) it has no bearing. Once you have set them up and you have installed the applications and configured all shortcuts, it's you who needs to know the system.
I support my dad on his Mac (he's die-hard Mac which is why I haven't moved him to Linux) piloting him blind because I know the system inside out, I know if he clicks in one place, I can predict the set of dialogs he'll see. I use Manjaro Xfce for Linux because it's install-once and sufficiently light. When setting up for a non-technician, I customize shortcuts my way, show them the ropes in person and hand them a cheat sheet based on my setup choice. If they mail me or call me, I know how to pilot them back to safety.
First off - if you're happy with your current role, why leave? Greener grass, etc. Talk to people in the area of activity first to get an idea of what it's like. The "private sector" (if there is much distinction) may work at a different pace with different imperatives than what you're used to, and the difference will be more business politics than actual technological differences/merit.
Secondly, what industry do you want to work with? I've worked 2nd level and 1st level support, mainly enterprise and some helpdesk, in a variety of industries; some experiences were enjoyable on average complex tech, some tech was amazin but for dull projects or industries... Make sure you're iterested in what the technology is applied to, and not just the technology itself. Applying great server products to manage a ball-bearing packing facility is not necessarily the most enriching experience after a few months, since most of the time it will just be maintenance.
Thirdly, if you want to learn about Microsoft products, you'll either need to shell out for them yourself, or find a job that makes use of them. Most likely is indeed tech support, from an entry level perspective. I can tell you that some support jobs teach you little by way of actual tech, some teach you lots, depending on the support level, and whether you're supporting users or integrators. Be on the lookout for technologies that interest you within the job descriptions, and go after those.
Finally, to learn about the underlying technologies before you can buy the software licenses, you would still do well to have a look at setting up enteprise Linux systems. I know you said you like Microsoft products but hear me out - administrative skills, troubleshooting, and many network-related tasks translate directly across platforms. You could be on CentOS, Ubuntu Server, Windows 200x server or OS X Server; from an administrative, and infrastructure and maintenance point of view, it's the same difference. Examples are setting up such things as web servers, SSL, LDAP, network troubleshooting, data migration, backup, SMTP server setup, database configuration, app server clustering, etc; and some non-technology stuff like change management, some minor project management, requirements gathering, system design, etc.
You can't teach yourself Enterprise stuff straight on Microsoft products on a hobbyist budget. Or you can, but it's an expensive hobby, which is why the normal route if you really want to pursue Microsoft tech, would be to change job. Your other option would be to convince your employer to invest in Microsoft.
But if it's specifically for your spare time, Linux is definitely what you want to look into.
Out of curiosity, what was the name of the feature? All I can see on this thread are "mitm" and "proxy" - but how is this feature actually called from a vendor point of view? I doubt it was being called as "SSL defeater" or something alarming like that...
"We have investigated US and allied European factories and found that they constituted weapons of mass desctruction posing a threat the security and safety of the world.
"We have declared war on these rogue factories, drones will be sent to all related company towns, and blackops have been deployed to known CEOs mountain hideaways in the Alps."
CentOS is the freebie that anyone can use - but that nobody is under any obligation to provide support or patches for. This means that small companies who are waiting to grow before buying proper RHEL, can still use the software, though they can't file bugs or get a support hotline. But it also means that CentOS can be used for anyone training in skills for "Enterprise grade" Linux can get their feet wet on a system that is already in use in industry. When the time comes to work with Linux in a real business environment, they've a head start on those who chose systems closed to non-customers.
Why does this matter to RedHat? The more people whose yardstick and gold standard is RedHat-related technology, the better; and ensuring all you can do on the derivative can be done exactly the same way on the commercial (down to the version of a command, the dot in a package name and the quirks of the brand) goes a long way to provide this promise.
How does this benefit RedHat if CentOS is given away for free? CentOS is RedHat's technology already in the hands of the client. But having the software is one thing - having access to support, formal enterprise training offerings, consultancy services and a dedicated rapid response for business-critical bugs is vital in business. Once the small company who could not afford RHEL becomes big, suddenly they are aware that they are on systems that RedHat knows perfectly, and migrating from CentOS to RHEL is painless - being systems different only at branding level. Migrating to anything else, even to SUSE Linux for Enterprise or Oracle's Linux (the latter being a part-clone of RHEL), becomes more involved. CentOS really now is RHEL.
Indeed, the good karma from being seen helping the community is peanuts compared to the advantage the offering of an easy transition and self-trained fans and already-committed users brings.
For the TL/DR: graphical programming is inefficent, and error prone; better methods of viewing source code during read-back is more interesting.
Apple has the Automator, which takes actions and chains them together. You can define variables, and operate on them.
I used to work with an enterprise software called Adobe LiveCycle, which does business process automation -- the approach was that rather than defining the business workflows in a chart diagram, and handing it over to a programmer to implement, the diagram itself WAS the program - business workflow designers (often managers and business consultants who were not technical) could build the workflow as individual steps, and more tech savvy people would add the variables and stuff to make it work.
A quick search on Google images turns up a lot of interesting stuff, including this graphical programming tool. The techniques have been in the making for a while.
Needless to say, even with these visual aids, to get something worthwhile done, you need to have actual programming knowledge - the Automator is good for home use but cute at best in production environments due to lack of finer configurability, and the business process workflow programming I mentioned still required in-depth computer knowledge: the workflow creators' work was often computationally inefficient, and often had to be refactored to take into account finer points of logic flow from both efficiency and data management points of view.
On top of that, it's easier to search on the Internet and on forums for code snippets, and discuss these when they're already in text form - no programmer actually works in isolation, communication is essential. Some advantages in reading back code might be had in graphical representation, and certainly creating a "visualization tool" for reading back code or designing high-level ideas might be helpful - but making it the implementation language is probably a bad idea.
On that matter, I recently came across the LightTable IDE which facilitates programming by doing live demonstrations of what happens to variables directly in the code flow. This also catches syntax issues early, bad type casting, and other relevant issues. Much better than a graphical abstraction I think, but that may just be preference.
The linked article indicates that visual programming has had success with casual creators in very specific scenarios (education of young kids, and use in LittleBigPlanet) - not in the general purpose programming arena for business critical solutions, high throughput systems, etc. Also, it says nothing concrete apart from "it's a matter of opinion" - nothing about the advantages or disadvantages of either.
Ultimately, it's like asking why bread shops don't use bread making machines. Tools for the job, tools for the desired outcome. If the simpler method works at home, that's great - but if you want to work professionally, the more sophisticated method yields better control over the final product.
The wording of the first two traits is strong, and easily misinterpreted, like mistaking humility with being a pushover. "Superiority complex" might be better rendered as "the knowledge one can do better than this"; "insecurity" is crippling compared to "the sense that the present condition is unttnable")
I'll add one last one to the trio though: "fails often" or rather, being able to recognize that failure is a milestone in an endeavour, not a gravestone; failure is a better teacher than success. This concept is alive and well amongst entrepreneurs of all cultures, and is essential to not erode the forward drive offered by the "superiority complex."
The ability to digest one's own failure is also an essential trait to continue to foster curiosity and experimentation - an ability easily lost in our obsession of being right first time, embodied by our acceptance of "do or do not, there is no try."
If the NSA were likened to Nazism - powerful entity oppressing the populace - that would be a validly debatable point.
In this occurrence, it's more like he's sitting in Versailles employing the plebes to trim his wigs into topiary. The "we're doing so much so good for these people" argument does not fly when you're on the receiving end of so much wealth, and it's the surrounding citizens that are unhappy.
The freedom to run the program, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
Secondly the consequence: Nobody but vBulletin is allowed to patch the hole, from a legal standpoint, lacking freedom 1, and thus lacking freedoms 2 and 3. Legally, SUSE cannot modify/improve/patch the software - they can only purchase upgrades.
If you know C, and it's not going anywhere soon, why change? Are you bored of the current projects you're on? Or do you think you'll be better off elsewhere? Greener grass etc
Some are being a bit more meta and suggesting fields to apply computing to, like data mining, marketing, etc. Worth investigating if you float that way, but I didn't think that was the point of the question.
You could also consider going into management as a techie, to at least have someone sane at meetings where the majority know more business than technology.
In web programming specifically? I'd say, make sure you know the fundamentals first and foremost.
As a previous poster said, knowing the HTTP protocol well (RFC2616 - be familiar with RFCs in general) will be important (more than you'd think - a misused verb led to Google's standard webcrawlers hosing a site because said site didn't implement forms/links properly), I'd recommend also getting intimate with some of the other building blocks such as SMTP, POP, FTP, SSL,... you get the picture. They'll come in handy when trying to piece together/troubleshoot a larger solution.
On top of that, know the roles and differences between different server apps (app servers like JBoss/WebSphere; web servers like Apache, nginx), know at least 2 popular database engines (I personally favour MariaDB and SQLite but that's up to you; you might want to look at PostgreSQL or CouchDB for something radically different), after learning HTML and XML/DOM fundamentals, know about cookies and AJAX specifically (which are part of your HTTP knowledge, but revisit later) and a take a web security course, or at the very least read far and wide on the matter. Someone suggested focusing only on back-end - fine if that's what you want to do, but at least be aware of how things behave in theory on the front end. Again, fundamentals.
After (all) that (a fortnight's worth of reading, not counting any experimentation?), the choice of languages to work with these building blocks is entirely up to you. Most commonly mentioned are PHP and Ruby in different setups (honourable mention to JSP), Perl and Python for CGI and general scripting, Ruby on Rails as language+framework...
When staring out and for longevity, choose fairly popular languages that run in open source runtimes (they're durable, they're documented, there are plenty of communities), and stay nimble with frameworks - a previous ask.slashdot showed how some of them can easily get canned despite a strong user base, and frameworks are just a flavour of the year... more likely than not, someone else (project lead, customer, policy...) is going to tell you what framework to use, so just make sure you've mastered your chosen language set.
For iOS devel you're not going to escape Objective C. Android I understand is purely Java. But most things you're likely to want to do that are web facing, you might as well do in a web page.
And, in general, stay nimble. But you knew that, right?
I've seen solution features designed around security holes before, and when we finally patched the breach, we received emails demanding that the decision be reversed and how dare we break customer solutions by surreptitiously patching things!
It certainly is good money for someone — whatever their race
In which case, why was the "for an Indian" phrase even mentioned, unless to single them out as opposed to other persons?
Unless Mr. Spandow's own dismissal was due to racism or some other illegal discrimination against him, I doubt, the suit will be found to have much merit.
I'd be surprised if the court finds that context and lead-up is not relevant to their decision. If the senior managers are found to have been violating equal opportunities regulations, their handling of Mr Spandow, who was effectively trying to rectify their ill behaviour, could be a direct consequence of their violation, and encompass him. Possibly a grey zone to be clarified.
The salary and cost of hiring is secondary to the main issue here.
Mr Bambling will have to explain why he issued a "stern warning" in response to the request, rather than an explanation as to his reasoning; Mr Trudeau will have to explain his contemptuous choice of words, and failure in turn to explain his reasoning; both them and probably others will have to explain why firing the sales manager was considered fair and necessary, in the light of the previous two points.
I am trying to figure out the newsworthy part in this - it's been known for ages that you can get details out of reflxions and high-def images...
For the practical implications - we're not going to get any benefit from users' twitpics, blog images and fb photos, as those are rarely ever uploaded in full high-def+highest-quality, 41MP camera notwithstanding: I'd like to see
the resolution and quality actually used by the camera (user setting rarely push the camera to its max capcity to save on storage)
the resolution and quality of the image after the sharing app has had a go at it to improve bandwidth performance
the resolution and quality of the reflexion when the person photographing is more than say 6ft away
and finally, the quality of the reflection in sub-par lighting - which is generally the case for most average-Joe users
Yes, it is possible to get data out of reflections on small shiny objects (and I suspect forensics teams have been on top of this ever since cameras reached consumers), but the lighting conditions and capture mechanisms have to be set up perfectly.
From the Raytheon article key figures: "Young men (35 percent) are far more interested than young women (14 percent) in a career in cybersecurity." If that many people are interested in cybersecurity, I'd call that "an overwhelming proportion" of persons being interested in cybersecurity. By that count, that's an enormous population of paranoid technofreaks.
"The survey also found less than one-quarter of young adults aged 18 to 26 believed the career is interesting at all." And how much of the total population gets employed in computer security AS A WHOLE? Less than 0.1% easily. How many other types of jobs, areas of interest and careers are there WITHOUT EVEN leaving the IT world?
The study page even highlights that they didn't target IT graduates. This is from a general, untargeted smattering of 1,000 members of the population. That's not even a proper sample size.
Slashdot Mirror
I know you've said you're trying to avoid screwing it up, but if you want, the CentOS wiki is pretty good for explaining what and why, and since it's a kernel firewall, it applies to Ubuntu too. In fact, I suspect all other "firewall tools" are basic GUI frontends to iptables. If you are indeed concerned about firewalling (though not quite as concerned as crypto-specialists), you probably at least want to have a go at it manually with some easy to understand notes
When in doubt, try it on a virtual machine of course.
I put together a general, documented, script that I run on all my new installs; comment out any lines you don't need. nixCraft has some notes on restarting the Ubuntu iptables/firewall under what I assume is upstart.
Indeed, by physical standards he stole nothing as the owner (licensor) of the software still has it.
Normally software theft can be counted in lost sales due to leakage...
.... and let's face it. Microsoft lost nothing from the leak itself.
Where have we seen in consumer space the ability to rollback an uncompleted install? Once it's installed, the only way back is to find a previous installer, nuke, and reinstall.
This has been standard IT procedure since Microsoft invented "service packs."
Indeed, and since way before too.
It used to be that you never went for the x.0. Nowadays, we have to be wary of getting any x.y.0
Nevermind what the distro or the desktop environment is (well, within reason). So long as you can help her, even on the end of a crackly phone line, it's fine.
When installing for any non-techie, Desktop Environment aside, show them how to find their browser and applications, show them how to find the file manager, and install Synapse so that they can search for pretty much anything (for bonus points, set the Synapse shortcut to something simple like Super+Space). Basically, give them their starting points, and show them how to search.
Whether you choose to move your mother/relative/neighbour to KDE, Xfce, GNOME 3 or even Unity if you like (or even Windows or Mac at that) it has no bearing. Once you have set them up and you have installed the applications and configured all shortcuts, it's you who needs to know the system.
I support my dad on his Mac (he's die-hard Mac which is why I haven't moved him to Linux) piloting him blind because I know the system inside out, I know if he clicks in one place, I can predict the set of dialogs he'll see. I use Manjaro Xfce for Linux because it's install-once and sufficiently light. When setting up for a non-technician, I customize shortcuts my way, show them the ropes in person and hand them a cheat sheet based on my setup choice. If they mail me or call me, I know how to pilot them back to safety.
First off - if you're happy with your current role, why leave? Greener grass, etc. Talk to people in the area of activity first to get an idea of what it's like. The "private sector" (if there is much distinction) may work at a different pace with different imperatives than what you're used to, and the difference will be more business politics than actual technological differences/merit.
Secondly, what industry do you want to work with? I've worked 2nd level and 1st level support, mainly enterprise and some helpdesk, in a variety of industries; some experiences were enjoyable on average complex tech, some tech was amazin but for dull projects or industries... Make sure you're iterested in what the technology is applied to, and not just the technology itself. Applying great server products to manage a ball-bearing packing facility is not necessarily the most enriching experience after a few months, since most of the time it will just be maintenance.
Thirdly, if you want to learn about Microsoft products, you'll either need to shell out for them yourself, or find a job that makes use of them. Most likely is indeed tech support, from an entry level perspective. I can tell you that some support jobs teach you little by way of actual tech, some teach you lots, depending on the support level, and whether you're supporting users or integrators. Be on the lookout for technologies that interest you within the job descriptions, and go after those.
Finally, to learn about the underlying technologies before you can buy the software licenses, you would still do well to have a look at setting up enteprise Linux systems. I know you said you like Microsoft products but hear me out - administrative skills, troubleshooting, and many network-related tasks translate directly across platforms. You could be on CentOS, Ubuntu Server, Windows 200x server or OS X Server; from an administrative, and infrastructure and maintenance point of view, it's the same difference. Examples are setting up such things as web servers, SSL, LDAP, network troubleshooting, data migration, backup, SMTP server setup, database configuration, app server clustering, etc; and some non-technology stuff like change management, some minor project management, requirements gathering, system design, etc.
You can't teach yourself Enterprise stuff straight on Microsoft products on a hobbyist budget. Or you can, but it's an expensive hobby, which is why the normal route if you really want to pursue Microsoft tech, would be to change job. Your other option would be to convince your employer to invest in Microsoft.
But if it's specifically for your spare time, Linux is definitely what you want to look into.
Out of curiosity, what was the name of the feature? All I can see on this thread are "mitm" and "proxy" - but how is this feature actually called from a vendor point of view? I doubt it was being called as "SSL defeater" or something alarming like that...
Just goes to show how British the whole affair is. *sips tea*
"We have investigated US and allied European factories and found that they constituted weapons of mass desctruction posing a threat the security and safety of the world.
"We have declared war on these rogue factories, drones will be sent to all related company towns, and blackops have been deployed to known CEOs mountain hideaways in the Alps."
...one mused.
Wonder if this could be related to the rogue filezilla....?
Huh. Didn't know that. Well, the points still remain the same with that edit :-)
I wonder if beta could allow for adding errata #justkidding #donthurtme
CentOS is the freebie that anyone can use - but that nobody is under any obligation to provide support or patches for. This means that small companies who are waiting to grow before buying proper RHEL, can still use the software, though they can't file bugs or get a support hotline. But it also means that CentOS can be used for anyone training in skills for "Enterprise grade" Linux can get their feet wet on a system that is already in use in industry. When the time comes to work with Linux in a real business environment, they've a head start on those who chose systems closed to non-customers.
Why does this matter to RedHat? The more people whose yardstick and gold standard is RedHat-related technology, the better; and ensuring all you can do on the derivative can be done exactly the same way on the commercial (down to the version of a command, the dot in a package name and the quirks of the brand) goes a long way to provide this promise.
How does this benefit RedHat if CentOS is given away for free? CentOS is RedHat's technology already in the hands of the client. But having the software is one thing - having access to support, formal enterprise training offerings, consultancy services and a dedicated rapid response for business-critical bugs is vital in business. Once the small company who could not afford RHEL becomes big, suddenly they are aware that they are on systems that RedHat knows perfectly, and migrating from CentOS to RHEL is painless - being systems different only at branding level. Migrating to anything else, even to SUSE Linux for Enterprise or Oracle's Linux (the latter being a part-clone of RHEL), becomes more involved. CentOS really now is RHEL.
Indeed, the good karma from being seen helping the community is peanuts compared to the advantage the offering of an easy transition and self-trained fans and already-committed users brings.
For the TL/DR: graphical programming is inefficent, and error prone; better methods of viewing source code during read-back is more interesting.
Apple has the Automator, which takes actions and chains them together. You can define variables, and operate on them.
I used to work with an enterprise software called Adobe LiveCycle, which does business process automation -- the approach was that rather than defining the business workflows in a chart diagram, and handing it over to a programmer to implement, the diagram itself WAS the program - business workflow designers (often managers and business consultants who were not technical) could build the workflow as individual steps, and more tech savvy people would add the variables and stuff to make it work.
A quick search on Google images turns up a lot of interesting stuff, including this graphical programming tool . The techniques have been in the making for a while.
Needless to say, even with these visual aids, to get something worthwhile done, you need to have actual programming knowledge - the Automator is good for home use but cute at best in production environments due to lack of finer configurability, and the business process workflow programming I mentioned still required in-depth computer knowledge: the workflow creators' work was often computationally inefficient, and often had to be refactored to take into account finer points of logic flow from both efficiency and data management points of view.
On top of that, it's easier to search on the Internet and on forums for code snippets, and discuss these when they're already in text form - no programmer actually works in isolation, communication is essential. Some advantages in reading back code might be had in graphical representation, and certainly creating a "visualization tool" for reading back code or designing high-level ideas might be helpful - but making it the implementation language is probably a bad idea.
On that matter, I recently came across the LightTable IDE which facilitates programming by doing live demonstrations of what happens to variables directly in the code flow. This also catches syntax issues early, bad type casting, and other relevant issues. Much better than a graphical abstraction I think, but that may just be preference.
The linked article indicates that visual programming has had success with casual creators in very specific scenarios (education of young kids, and use in LittleBigPlanet) - not in the general purpose programming arena for business critical solutions, high throughput systems, etc. Also, it says nothing concrete apart from "it's a matter of opinion" - nothing about the advantages or disadvantages of either.
Ultimately, it's like asking why bread shops don't use bread making machines. Tools for the job, tools for the desired outcome. If the simpler method works at home, that's great - but if you want to work professionally, the more sophisticated method yields better control over the final product.
The wording of the first two traits is strong, and easily misinterpreted, like mistaking humility with being a pushover. "Superiority complex" might be better rendered as "the knowledge one can do better than this"; "insecurity" is crippling compared to "the sense that the present condition is unttnable")
I'll add one last one to the trio though: "fails often" or rather, being able to recognize that failure is a milestone in an endeavour, not a gravestone; failure is a better teacher than success. This concept is alive and well amongst entrepreneurs of all cultures, and is essential to not erode the forward drive offered by the "superiority complex."
The ability to digest one's own failure is also an essential trait to continue to foster curiosity and experimentation - an ability easily lost in our obsession of being right first time, embodied by our acceptance of "do or do not, there is no try."
If the NSA were likened to Nazism - powerful entity oppressing the populace - that would be a validly debatable point.
In this occurrence, it's more like he's sitting in Versailles employing the plebes to trim his wigs into topiary. The "we're doing so much so good for these people" argument does not fly when you're on the receiving end of so much wealth, and it's the surrounding citizens that are unhappy.
I know I'm late to the party, but I can't let this one slip :-). So, a bit of Free Software Philosophy 101 to serve up
First off, Stallman's definitions of Software Freedoms:
Secondly the consequence: Nobody but vBulletin is allowed to patch the hole, from a legal standpoint, lacking freedom 1, and thus lacking freedoms 2 and 3. Legally, SUSE cannot modify/improve/patch the software - they can only purchase upgrades.
I leave this here, you know, just in case.
Reading subsequent comments, 2 points stand out
If you know C, and it's not going anywhere soon, why change? Are you bored of the current projects you're on? Or do you think you'll be better off elsewhere? Greener grass etc
Some are being a bit more meta and suggesting fields to apply computing to, like data mining, marketing, etc. Worth investigating if you float that way, but I didn't think that was the point of the question.
You could also consider going into management as a techie, to at least have someone sane at meetings where the majority know more business than technology.
In web programming specifically? I'd say, make sure you know the fundamentals first and foremost.
As a previous poster said, knowing the HTTP protocol well (RFC2616 - be familiar with RFCs in general) will be important (more than you'd think - a misused verb led to Google's standard webcrawlers hosing a site because said site didn't implement forms/links properly), I'd recommend also getting intimate with some of the other building blocks such as SMTP, POP, FTP, SSL, ... you get the picture. They'll come in handy when trying to piece together/troubleshoot a larger solution.
On top of that, know the roles and differences between different server apps (app servers like JBoss/WebSphere; web servers like Apache, nginx), know at least 2 popular database engines (I personally favour MariaDB and SQLite but that's up to you; you might want to look at PostgreSQL or CouchDB for something radically different), after learning HTML and XML/DOM fundamentals, know about cookies and AJAX specifically (which are part of your HTTP knowledge, but revisit later) and a take a web security course, or at the very least read far and wide on the matter. Someone suggested focusing only on back-end - fine if that's what you want to do, but at least be aware of how things behave in theory on the front end. Again, fundamentals.
After (all) that (a fortnight's worth of reading, not counting any experimentation?), the choice of languages to work with these building blocks is entirely up to you. Most commonly mentioned are PHP and Ruby in different setups (honourable mention to JSP), Perl and Python for CGI and general scripting, Ruby on Rails as language+framework...
When staring out and for longevity, choose fairly popular languages that run in open source runtimes (they're durable, they're documented, there are plenty of communities), and stay nimble with frameworks - a previous ask.slashdot showed how some of them can easily get canned despite a strong user base, and frameworks are just a flavour of the year... more likely than not, someone else (project lead, customer, policy...) is going to tell you what framework to use, so just make sure you've mastered your chosen language set.
For iOS devel you're not going to escape Objective C. Android I understand is purely Java. But most things you're likely to want to do that are web facing, you might as well do in a web page.
And, in general, stay nimble. But you knew that, right?
Some people see "bugs," others see "features."
I've seen solution features designed around security holes before, and when we finally patched the breach, we received emails demanding that the decision be reversed and how dare we break customer solutions by surreptitiously patching things!
Sometimes you never can win.
Again, where is the need to single out the nationality, if the money is good for just about anyone?
It certainly is good money for someone — whatever their race
In which case, why was the "for an Indian" phrase even mentioned, unless to single them out as opposed to other persons?
Unless Mr. Spandow's own dismissal was due to racism or some other illegal discrimination against him, I doubt, the suit will be found to have much merit.
I'd be surprised if the court finds that context and lead-up is not relevant to their decision. If the senior managers are found to have been violating equal opportunities regulations, their handling of Mr Spandow, who was effectively trying to rectify their ill behaviour, could be a direct consequence of their violation, and encompass him. Possibly a grey zone to be clarified.
The salary and cost of hiring is secondary to the main issue here.
Mr Bambling will have to explain why he issued a "stern warning" in response to the request, rather than an explanation as to his reasoning; Mr Trudeau will have to explain his contemptuous choice of words, and failure in turn to explain his reasoning; both them and probably others will have to explain why firing the sales manager was considered fair and necessary, in the light of the previous two points.
I am trying to figure out the newsworthy part in this - it's been known for ages that you can get details out of reflxions and high-def images...
For the practical implications - we're not going to get any benefit from users' twitpics, blog images and fb photos, as those are rarely ever uploaded in full high-def+highest-quality, 41MP camera notwithstanding: I'd like to see
Yes, it is possible to get data out of reflections on small shiny objects (and I suspect forensics teams have been on top of this ever since cameras reached consumers), but the lighting conditions and capture mechanisms have to be set up perfectly.
Amusingly, fake bitcoins are probably the only ones that'll have a stable enough price to be trusted. http://www.amazon.com/999-Fine-Copper-Bitcoin-Commemorative/dp/B00DEY7JYO
In the UK, there are price comparison website who've been doing this for ages. With no pre-sign-up.
If the US gov asks nicely, maybe they can provide them with a readily designed platform...?
From the Raytheon article key figures: "Young men (35 percent) are far more interested than young women (14 percent) in a career in cybersecurity." If that many people are interested in cybersecurity, I'd call that "an overwhelming proportion" of persons being interested in cybersecurity. By that count, that's an enormous population of paranoid technofreaks.
"The survey also found less than one-quarter of young adults aged 18 to 26 believed the career is interesting at all." And how much of the total population gets employed in computer security AS A WHOLE? Less than 0.1% easily. How many other types of jobs, areas of interest and careers are there WITHOUT EVEN leaving the IT world?
The study page even highlights that they didn't target IT graduates. This is from a general, untargeted smattering of 1,000 members of the population. That's not even a proper sample size.
Bad journalism. Bad study report. Bad.