Something that’s been on my mind for some time, but have never been able to find a way to put it across. Eevee does it perfectly:
So whenever you can, don’t expect your scripts to download, or work.
Or, as I like to think about it: if you are rewriting a browser control, ask yourself why.
It’s McrFRED next week, and it’s lightning talks. I will be practicing my talk about code reviews.
So, you do code reviews, and that’s great. But there’s always more that you can check during the review. More places you can check for any potential bugs or problems before deployment, before you find yourself with technical debt. Or worse: unforeseen downtime.
In this talk Clair will be going through the things that you should be checking to ensure confidence for developers, project owners and stakeholders. We’ll be looking at documentation, commit messages, and common code problems, with examples and tips along the way.
I’m really excited to be speaking at PHP South Coast this year.
It is their second conference, and for me has already become the highlight of the UK conference year. This year’s schedule is a fantastic one, and I’m proud to be part of it.
Early Bird tickets are still available.
I’ve recently had need to search for emails received after a specific time: as in, “After 3pm on the 1st January 2016”, and not “After the 1st January 2016”.
I disbelieved that this is something Google would neglect to allow for so long. Luckily, I was correct.
You can achieve this if you use the Epoch timestamp instead. For example, to get all emails sent/received since 3pm on the 1st January 2016 (in GMT), all I need to do is search for:
Katie Sherwin, for Nielsen Norman Group, nails it when it comes to TV spoilers on the HBO Now service:
Much to my dismay though, each time I click on the Game of Thrones thumbnail, it reveals a big image of the latest episode — complete with characters that I didn’t know were still alive, in contexts that give away the plot. I see who is together arm in arm, which villains are undeservedly still in power, and which heroes are alive and in jail.
I literally have to block the screen with my hands each time I go to watch an episode. A friend of mine uses the squint approach: half looking away in order to blur the revealing images and summary text, while he maneuvers the mouse to the correct season.
And she perfectly sums up the problem:
Satisfying multiple sets of user needs doesn’t mean designing for the lowest common denominator. It’s about empathy with the different use cases and making sure that the content for one audience, even if it’s a main audience, doesn’t ruin the experience for a different use case.
Absolutely. It’s the modern equivalent of looking away from seeing the football results.
Which reminds me: I’ve lost count the number of times BBC News have spoilt the F1 results for me beforethey air the extended highlights show…
A little last minute, but I will be speaking at North West Drupal User Group tonight, doing my code review lightning talk: “There’s more to code review than you might think”.
It all starts from 7pm at MadLab, Manchester.
When most people talk about cell phone signal strength, they talk about “bars” in reference to the signal strength bar indicator on the phone. While bars are an easy way to talk about signal strength, it turns out that it’s not a very accurate way.
This is something I try to turn on on my iPhone (scroll down to “Always show Decibels instead of Dots”) whenever I can, as I find dots very vague.
Sheffield PHP, 8th October
A repeat performance of the talk given at PHPNW in July, possibly with even more wittier jokes!
Here’s to the crazy ones. The misfits. The rebels. The troublemakers. The round pegs in the square holes. The ones who see things differently.
They’re not fond of rules. And they have no respect for the status quo.
You can quote them, Disagree with them, Glorify or vilify them.
About the only thing you can’t do Is ignore them.
Because they change things. They push the human race forward.
And while some may see them as the crazy ones, We see genius.
Because the people who are crazy enough to think they can change the world, Are the ones who do.
A fair number of passwords from the Ashley Maddison hack have now been cracked. Click through if you want to see the (NSFW) top 100 list, but you wont see many surprises.
As bad as it is that 11.7 million accounts were protected by weak passwords, there’s yet another number the underscores just how careless the Ashley Madison masses were: Only 4.6 million of the 11.7 million recovered passwords were unique.
If I did my maths correct, around 5% of all accounts (or 1 in 20) had passwords in that top 100 list.