@WordCampLanc @aaronjorbin The first rule of code reviews to help someone (and most things in general) is to not be an asshole.
@WordCampLanc @aaronjorbin Finding complexity early is a hallmark of a senior developer.
@WordCampLanc @aaronjorbin Changing data formats in WordPress is hard. There is one site that has over a billion posts (WordPress.com)
@WordCampLanc @aaronjorbin This is @aaronjorbin’s favorite WordPress trac ticket: core.trac.wordpress.org/ticket/1…
Custom Post Status bug that has been open 9 years.
@WordCampLanc @aaronjorbin Everyone is bad at estimating how long something will take.
“How long will it take to build a website?” is almost as hard as “How much does a website cost?”
– @aaronjorbin
@WordCampLanc @aaronjorbin Part of being a senior developer is mentoring other people, helping them grow, helping them break down work into small manageable steps.
@WordCampLanc @aaronjorbin @aaronjorbin’s super powers:
– Writing code that gets thrown away
– Being in meetings
@WordCampLanc @aaronjorbin We need to expand beyond WordPress to other things like Drupal, Rails, React etc. How are they solving problems? How can that come back to WordPress.
@WordCampLanc @aaronjorbin When you only know one skill in web development you miss out on solutions using other technologies. Going broad about different knowledge expands your base and the potential to see new solutions.
@WordCampLanc @aaronjorbin @aaronjorbin spends less time coding PHP or JavaScript these days and more time coding in Excel as a director.
@WordCampLanc @aaronjorbin Being intermediate is not bad.
@WordCampLanc @aaronjorbin The biggest part of your developer career will be as an intermediate developer. Being a senior developer is not easy. Not everyone wants to be a senior level developer.
@WordCampLanc @aaronjorbin You’ll see junior developers, developers, and senior developers. But not intermediate developers.
@WordCampLanc @aaronjorbin “My first job I was a Senior Backend Engineer. How could I be a senior engineer in my first job?” @aaronjorbin
Ignore job titles. Job titles are worthless in tech.
Last talk before the panel @WordCampLanc
“Intermediate Topics in WordPress Development” by @aaronjorbin
@WordCampLanc It’s actually at kingkool68.com/wp-templating/
Up next is me! Slides for my talk “From Template Tags to Twig: A Journey Through WordPress Templating” at @WordCampLanc are available at v.gd/wptemplating
@WordCampLanc @erikteichmann Another core difference is instead of actually pulling in a stylesheet you’re bringing in inline styles when that block is loaded.
@WordCampLanc @erikteichmann What is the core difference between doing editor styles in classic editor versus Gutenberg editor?
tinyMCE was a walled garden. You could put any styles within that iframe and do whatever you want. Gutenberg is more open. It takes more care and forethought.
@WordCampLanc @erikteichmann “What about Google fonts or any custom fonts?”
“You can enqueue them just like any other CSS file. Gutenberg will wrap the styles in an editor-styles wrapper and then you can use it.”