Yammayap | Senior Laravel (PHP) Developer | Full Time | ONSITE Bournemouth, UK | £50k - 60k

From our office in Bournemouth (Dorset, UK), we specialise in building bespoke business workflow software that enables growing, successful companies get to the next level. In line with our continued growth, we are seeking an experienced Laravel developer to join our development team.

Yammayap are a down to earth team of techies dedicated to helping business leaders solve their workflow issues through unique tailored software. The software systems we create are truly bespoke - we mould them around our clients’ internal processes, so they fit their business perfectly. We work closely with them and their teams to create something that is purpose-built.

Full details available here: https://www.yammayap.com/jobs/ - or email me if you have any questions, george [at] yammayap [dot] com

This is a big disappointment

how is this big?

it's a preview for new features, calm down

It's big because I want it now!

Love the cranes that appear for Construction Areas

Google cached version: http://webcache.googleusercontent.com/search?q=cache:gkzZ7YK...

No problems for me in the UK.

"Having your website design with Wordpress, Joomla or Drupal , will give your site a better look and feel."

Sorry, what? How on earth does an open source CMS give you a better look and feel?

It's not my project - just something I spotted.

Until they have a security breach.

Better rely on someone who's sole job is securing that info than doing it yourself.

Storing credit card info just helps make you a bigger target. If your a small company, better let someone else store card info, let them be the target.

Also you're fined by the credit card companies if you lose card information. I believe it's a per card fine, so it get expensive really quickly.

Actually I don't get why any company would choose to store credit card information, when most payment providers will do it for you.

Stripe is amazing... I trust them, someone hacks me, awesome, you got password hashes and stripe customer keys, all worthless.

Not exactly worthless, depending on the hack someone could still charge an awful lot to your customers and make you have a bad day.

But yes, significantly better than other situations.

True, but I'd rather fix the problem that got them in, force reset of passwords, and delete all customer keys and require them to create new ones than be like "uhhhh, our data was hacked and your credit card is safely encrypted... But we had the encryption key on the server too, oops"

But you still might need to consider data residency issues and making your customers aware of where their data is being stored.

Yes

But if that happens, it's not your responsibility (at least not 100%), it's theirs

Following the traditional responsibility/accountability dichotomy: They are responsible for storing the cc number securely but you are accountable when something goes wrong (because you gave them that task)

Much like Linode are responsible for hosting my clients site but I sigh am accountable when something goes wrong.