dracos

aahed
aalii
aapas
aargh
aarti
abaca
abaci
aback
abacs
abaft

getify

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

dreammonkey

1. download PECL:
$ curl -O https://pear.php.net/go-pear.phar 

2.install PECL in MAMP PHP folder:
$ sudo php -d detect_unicode=0 go-pear.phar

!!! make sure the installation directories look like this: !!!

 1. Installation base ($prefix)                   : /Applications/MAMP/bin/php/php7.2.14
 2. Temporary directory for processing            : /tmp/pear/install

JMWebDevelopment

/**
 * Block dependencies
 */
import icon from './icon';
import SelectTeam from '../select-team';
//import './style.scss';
import './editor.scss';

/**
 * Internal block libraries

ataylorme

<?php
function register_books_cpt() {

	$args = array(
		'labels'          => array(
			'name'          => _x( 'Books', 'post type general name' ),
			'singular_name' => _x( 'Book', 'post type singular name' ),
		),
		'description'     => '',
		'hierarchical'    => false,

codehooligans

// We are using the WooCommerce Checkout Field Editor plugin in addition to WooCommerce. The Checkout Field Editor 
// does a nice job at providing a UI for manage additional fields. But doesn't provide any method to do validations. 
// So this code helps with that on a very specific implemention where we have a Gender select and a DoB date selector.
// On the Gender we want to ensure the selected value is 'Male' or 'Female' only. We don't want the 
default option 'Choose Option' to be valid. On the DoB we want to enforce the user is 18 or older. 

add_action( 'woocommerce_after_checkout_validation', 'woo_checkout_additional_field_validation' );
function woo_checkout_additional_field_validation() {
	if (!defined('WOOCOMMERCE_CHECKOUT')) {
		return;

Fab1en

// for debug : trace every event
/*var originalTrigger = wp.media.view.MediaFrame.Post.prototype.trigger;
wp.media.view.MediaFrame.Post.prototype.trigger = function(){
    console.log('Event Triggered:', arguments);
    originalTrigger.apply(this, Array.prototype.slice.call(arguments));
}*/


// custom state : this controller contains your application logic
wp.media.controller.Custom = wp.media.controller.State.extend({

chrisvanpatten

Huh?

Believe it or not, WordPress doesn't have a fully-fleshed out common tab style for plugins or theme authors to use in metaboxes.

The style exists for categories, but it hasn't been fully adapted for the half-complete wp-tab setup. Trac ticket #17959 has a solution that not only fleshes the style but it also adds a global JavaScript file to give the wp-tab HTML some action. Until that ticket is accepted into core, this Gist adapts that code so it's available to use independently in your theme or plugin.

How?

Just enqueue the CSS and JavaScript in the admin_enqueue_scripts script hook and drop the tab HTML in a metabox. It will automatically adapt to the normal and side column widths, much like category tabs.