PFFFFFFFFFFTTT Hey Dustin. Long time!

http://ryanflorence.com/may24th.mp3 http://ryanflorence.com/nervous_again.mp3

(For anybody following along, Dustin is an old high school friend and loyal fan of Mookie Proofed--my high school band.)

twitter.com/ryanflorence/status/920428180527124480

Hey! Good! I'm getting hungry.

1. Sales. You're always selling. We all forget that we are literally selling our labor as suppliers in the labor market. So don't forget to negotiate your salary. You're selling your ideas on how to architect the app, the UX, whatever. You have to be able to sell you and your ideas. I'm glad I started my career in sales.

2. I have a list of what I want to be actually :P

Here it is, straight out of my life planner thingy that I built:

• Present, Kind, and Helpful Spouse
• Gentle, Fun, and Strong Dad
• Dependable, and Creative Business Partner
• Anxiously Engaged Latter-day Saint
• Physically Active/Capable
• Charitable

Then came everdimension to him, and said, Ryan, how oft shall my co-worker pass props down a level, and I forgive them? till seven times?

Ryan saith unto everdimension, I say not unto thee, Until seven times: but, Until seventy times seven.

Redux is a great way to get stuff deep too.

I graduated in economics and then sold life insurance before becoming a developer.

The cool thing about code is you don't need anybody to give you coding experience, you can get it yourself. Build something awesome, show it off and you'll get interviews, show it off at interviews and with any luck, you'll get a job.

...Hopefully!

I've interviewed tons of developers, I loved hiring people who came to us with some enthusiasm about something they had built at work or home that was awesome.

facebook.com has been running on it for months, so if you get more traffic than they do you might want to do your own testing 😇

that's true :P

Yeah, that's a hard balance. I think React Router keeps us grounded as technologists instead of just teachers. We have a lot of use-cases that come our way that we have to work out, so we're exposed to all the new stuff and have to figure out how it fits.

Uh ... I think just writing lots of code, and reviewing lots of code, and sitting back and thinking about it.

render props, function-as-children, and now render callback functions

That's all render props :)

Speaking of, I saw Cheng Lou do that in React Motion and thought "WHAT THE CRAP IS HE DOING?!"

Then I sat back and thought about it and realized how cool it was to be able to share state that way. With more thinking/teaching/coding I feel like I've found out how/when/why I would use it.

I dunno really. Just experience?

My dad invested in an ISP when I was a kid. So I had a homepage at www.fia.net/~caseyf an started putting HTML up there (there was no CSS or JavaScript). Back then you could view source and learn. I was lucky to be on the web as it was being invented: I remember when IE first supported CSS, when mozilla showed up, I got developer previews of macromedia shockwave flash, ms frontpage, etc.

I spent my time playing/recording music w/ my band and building websites for us and our friend's bands.

Then I left on an LDS mission where you don't have a computer. Two years later I got home and went to college, forgetting all about building websites. It was SO DIFFERENT from 2000 to 2002. Suddenly "view source" was full of craziness, JavaScript got big, CSS had great support in IE6 (don't laugh, it was amazing) etc.

It wasn't until 2005 that my wife needed an online portfolio or printed portfolio for her photography degree that I got back into it. A printed portfolio was going to be $200, so I busted out Notepad.exe and built her a website instead. It was hilarious. She'd ask for features, I'd say "not possible" and then the next day I'd figure it out and show her.

From there I got involved with MooTools just by publishing my code to github. A few of them noticed and invited me into the secret #mootools-dev channel. That group of people basically taught me how to program and got me contracts and eventually my first full-time job with clockfour.com. The rest is history.

I don't know if I'm the react guy, but being loud on twitter about stuff you're excited about helps you become something like one :)

Hey, haha.

Tyler is still a great friend and everything between us is good.

I think in January it'll make more sense why we split. Short story, we wanted to take React Training one way, it wasn't working as we'd hoped, had some new ideas, then moved forward with them.

I think vue appeals to a different audience and is a great fit for some teams. People say "right tool for the job" but the job is same, its more "right tool for the team".

Expressing UI as code instead of a template will work on some teams and be a disaster on others. In those cases, templates are perfect.

🤷🏼‍♂️

Sorry that's a bit specific. Good luck!

Atom. My front-end vim plugins were causing problems and I figured that the cool kids aren't going to be keeping vim stuff up to date, so I went to atom. I'm still sad, I haven't thought about my editor in YEARS, but now I have to whether I'm in vim or atom.

I'm mostly adjusted to atom though, vim-mode-plus has closed the uncanny valley enough that I'm productive again w/o thinking about my editor.

I hate thinking about my editor!

"Learn" less, code more.

Build stuff until it works, don't worry about if its "right" or "good" or "fast" or "secure". Just make it work.

Find a workflow in your life you want solved. Maybe its a simple shopping list app (ryanflorence.com/list) or a pregnancy contraction timer (ryanflorence.com/prego) or a people counter (ryanflorence.com/clerker), just build something you want for yourself and don't stop until its done, even if its butt ugly inside and out, you'll feel great when you finish it and its useful.

The browser doesn't tell us (and therefore we can't tell you) if they clicked the back or forward button, so not really something we can do right now.

We have some ideas on how to track some data to know which button they clicked, but we've never gotten it bullet-proof.

The react docs, tylermcginnis.com, and one of our workshops.

Hi C.!

Hmm ... the only reason I'd never use another UI lib again is if I stopped building UIs. It's inevitable that something more interesting to me will come along.

But, the staying power of React has been extraordinary. Individuals and teams continue to pick it over and over and over, which I've never seen before. Personally I used to carry around a "bag of misgivings" about the tech I was using to build UI. React's bag is very, very small.

So, yeah, I'll use something besides React eventually--which may just be an evolution of React or something totally new--but I'm not looking for anything new right now, pretty happy with it even after 4 years.

It's silly, but I still get excited when teaching our fundamentals workshop. React is a lot of fun.

Oh, Sean ... hard times.

Michael basically spearheaded that thing and we'd love to do it, but it's hard to make the time. Running a business, especially one that plans events, takes a lot of time. Also, we've both got spouses, kids (I have 3, he has 4), and community/church responsibilities. Mix in our travel schedules (we each travel 2 or 3 times per month) and we're just out of time for the podcast :(

We recorded one a few months ago but the guest was basically in a cafeteria and the audio quality was just too terrible. Maybe one day it'll come back, but at this point myHopes !== high.

Unfortunately I have to pay the bills, so it's hard to find time for that sort of thing, but I've got a lot of things I'd like to put out there. I actually have a document of notes on little free videos I want to make.

But when the choice is something that puts money in my pocket and something that doesn't, I'm gonna go for the money 😅, at the moment, the revenue generating activities are consuming my time!

Make it so fast that shouldComponentUpdate wasn't a thing at all and then context wouldn't be "broken".

If I can't get a faster horse though, I'd like a car, but I don't know what that looks like.

All growing up I loved performing. Whether it was on stage w/ my punk rock band, or wakeboarding past the beach and throwing a few flips to get some cheers. I served a proselyting mission for 2 years for the Church of Jesus Christ of Latter-day Saints and was told often I was a great teacher. I was a TA in college for my Economics professors. When I sold insurance/mutual funds I taught people about financial growth/risk etc. My first software job I was a trainer and implementation consultant. So my whole life I've been teaching/performing.

So I don't know if I ever realized I had a gift (if I even do?), I just know I've always enjoyed sharing what I know, and trying to entertain people. There are a lot of social situations that make me uncomfortable, but being on stage trying to make somebody laugh or think is my happy place.

It's always easier to come down, so start as high as you're comfortable!

I always think about our pricing as value based, and I definitely think our online advanced course is worth $250 if you're a few months into React and want to level up.

Consider this: if you make 100k/yr as a developer, that's only 5 hours of pay.

Learning how and when to use those patterns on your own will definitely cost your boss more money than that.

I built my own little thing, forgive the initial data, was a joke with a friend:

https://fulfillment.now.sh/2017/10/19

On its own, probably doesn't make a ton of sense, but with some explanation, its really awesome. Helps me track not just "todos" but what I want "to be".

I find working on becoming something, rather than doing or achieving stuff brings me far more fulfillment.

Other than that, google inbox "snooze" feature is amazing.

Eating apples from the bottom up and suddenly there is no core.

foodbeast.com/news/so-apparently-weve-been-eating…