A very common pattern on the web is to overlay text on a photo. It’s a lovely effect but one that requires care to get right.
The difficulty arrises for the web developer wishing to produce an accessible site because they can never be sure what the colour of the photo will be.
For WordPress site owners wishing to use real cron via a crontab job, it’s fairly common to see advice to use curl to request the site’s wp-cron.php file on a regular basis.
In the days before the WordPress CLI (WP-CLI), using the wp-cron.php file was the only technique available to site owners wishing to use real cron events.
I’m in London visiting friends for a couple of weeks and, predictably enough, took them to see West End production of Hamilton the Musical. Unfortunately one of my friend’s health has deteriorated over the last few years so queuing for entry to the theatre is a problem. We needed an access ticket.
This doesn’t feel like an access ticket, it feels like a VIP ticket.
Vote Yes! Pull Request is a small collection of custom styles to replace the approve button in Bit Bucket. ?️?
Add the following to the bitbucket domain using Stylish.
@import url(https://peterwilsoncc.github.io/vote-yes-pull-request/bb.css);Why? Because I am not one to let an offhand comment go unimplemented.
Replaces ‘Approve’ button with ‘Vote Yes’ in bitbucket? 💯🌈💯
— Tarei King (@tareiking) October 6, 2017
Occasionally I look at the theme for one of the first WordPress sites I developed. I look at my early PHP, my early CSS, my early JavaScript & my HTML about ten years into my career.
The HTML has at least lost its font tags and table based layouts but my overall reaction is to wish I could curl up and hide.
Someone has started the the best developers shit storm on Twitter. Again.
The best developers are lucky enough to do work that pushes them to grow.
One of my earliest jobs was at Rove Live. I thought I’d hit the big league but, thinking back, my code could have been better. I improved as a dev.
I developed corporate sites next, small shops and sole traders. My code was better and I thought I’d hit the big league. I improved as a dev.
I’ve been lucky enough to spend the last year working at Human Made and on WordPress core…
I enjoy public speaking. I am very thankful to James for years of gentle cajoling to get me on stage at the WordPress Melbourne meetup.
I’ve realised the audience is at a meetup or conference to enjoy themselves, they’re on the speaker’s side and they want them to do well.
The audience will forgive a speaker stumbling over a sentence or fudging a line because the audience wants to learn from the speaker.
I still get very nervous and need to sit quietly before a talk but knowing the audience is looking to have fun does help settle the nerves.
The language of technology is easy. It’s evolving so new terms come in the lexicon gradually and we pick them up as they arrive.
At least, that’s how I find it. I’ve grown up with tech – right back to the secondhand Apple IIe given to me as a kid and the World Wide Web I discovered at university.
For someone obliged to use technology it’s harder. Mention browser tabs to them and they may ask what a browser is? What does it do?
When creating websites it pays to remember that for most people: the language of technology is hard.
The new WordPress default theme includes a block of CSS to fix layout of the headers in browsers supporting the object-fit property.
The CSS makes use of feature queries. It’s the first time a WordPress default theme has used @supports and I’m really pleased to see it.
Despite wide browser support, feature queries are rarely seen in the wild. Feature detection started as a JavaScript technique and it’s easy to ignore a method that comes along later.
I was reminded about feature queries earlier this year when I saw Jen Simmons speak. I’ll be keeping them in mind more often.
I just spent an hour or so debugging some JavaScript.
The code was simple, concatenate a string to form a selector: '#in-category-' . termId. Undefined. Always undefined.
I started dumping all sorts of things in the console to debug. termId was defined. The code was passing through conditional statements correctly.
I was just about to send the diff to my work mate Dzikri with the note “this is the general idea but I’ve made a silly mistake” when I saw it.
I was using PHP style concatenation in JavaScript.
I’ve noticed this immediately in people’s code. I’m sure you did too.