Ipstenu (Mika Epstein): Your First Plugin Sucked (And That’s Okay!)

Continue the discussion

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Published

June 4, 2017

You wrote a really awesome bit of code and submitted it to the directory, only to find out your code MAYBE wasn’t so great. And worse, even after it was approved, people can be pretty terrible about things. Judgmental. Mean. And now you have complaints, conflicts, bad reviews, broken code, security patches, and more. AUGH!

It’s OKAY!

Everyone’s first plugin sucks. Everyone runs into unexpected conflicts. Learning how to handle them is what will take you from a good developer to a great one.

In this talk, I’ll discuss :

* That first review (what really happens)
* Preventing name conflicts (classes, functions and when to use if-exists)
* Replying to reviews (and when not to)
* Replying to support tickets (and when to say ‘no’)
* Handling security reports (what we really mean by ‘responsible disclosure’)

Rate this:

Event

WordCamp Raleigh 2017 31

Speakers

Mika Epstein 16

Tags

plugin 26

Language

English 5453

Download
MP4: Low, Med, High
OGG: Low
Subtitles
Subtitle this video →
%d bloggers like this: