We're hiring at Panasonic! Come on Chris get back in the trenches and let's sling some code. :)
I just hear from Ciprian that you're departing, I have to say you being there was one of the reasons I began the engagement with omni so you'll be missed. Wish you the best!
I think whats starting to scare people is the talk of PHP6 already when PHP5 has been so slow to be adopted. With that the talk of once again not caring about backwards compatibility.
Its pretty much impossible to find enterprise level php developers. Here at McAfee we've been looking for two years and have hired one person. I attribute alot of it to wanting someone on site and the high cost of living in this area however the resumes we get are pretty weak. A ZCE would certainly stand out in the pack.
yeaaaaaa! just what we need... another IM client to sync to, another browser (eventually) to code to... thanks google 2@#$$%T@@!#
google went from being innovative to going public and having to play catchup to what yahoo offers. Google does some things better but still just playing catch up.
I've justed started to get some free time to start implementing Unit Testing using PHPUnit. I'm finding it a really valuable tool in the enterprise world.
also glad to see an ecommerce company worried about security.
Before I fixed my old company's ecommerce site they used to manually download the orders off the web, print them out in the office and type them in another system WITH CREDIT CARD #'s on all the printouts ;)
just out and about for all to see who walk by. they did millions on that site too, sad sad.
Perhaps a better way to actually solve the issue is to have "certified" sites. Much like IE verifies SSL certs.
Financial Institutions, Government Sites, etc would need to register as a certified site and IE and other browsers could download cert info from a trusted resource.
A big red X would appear somewhere in the browser letting the user know its not a certified site. Something like that perhaps.
I've traced alot of these phishing emails, getting the whois info, cross referencing that against the registered blocks of ip addresses that server is on and you get to the ISP which is usually located in a place where they could care less about taking legal action against these sites.
what you "could" do is get the ip address of the server hosting the site, run a vulnerability scanner like Foundstone's SuperScan or Nessus's version and take down the server with known exploits. Usually you can bring down a few that way and what are they gonna do to you? :)
Latest Comments
1
2
3
4
5
6
7
8
9
10