RNDOM notes from Laracon 2018

Laravel by the Numbers by Jason McCreary

— — — — — —

Keynote by Taylor Otwell

— — — — — —

Patterns that Pay Off by Matt Stauffer

— — — — — —

People pay them to audit codebases.

Konstantin Kudryashov == Cost of Change (Laracon EU)

Write code that is easy to delete. do just what you need right now. new code comes along you know the future because you’re in the future

Pay off is greater than patterns. Goal is to write better software (not for you to learn more patterns) :key emoji:

• No Precogs
• Amazing illustrator and designer (Minority report: Precogs)
• You think you can predict the future….. you can’t
• over architect to try and reduce The Cost Of Change [only build for what you have in front of you]
• Codebase Consistency
• establish and enforce standards.
• don’t want to be able to tell who wrote the code just from looking at it
• Bin scripts
• shell scripts for common tasks (init, update, precommit, deploy)
• easier onboarding, less cognitive load
• devs don’t read docs (they will read the code)
• Four eyes
• one developer, one reviewer.
• pair programming still alright. Reviewing brain is different from the writing brain.
• shared responsibility
• read your code before you ask anyone else to read your code
• Document the weird
• self documenting code
• business requirements
• Lower case agile
• stay light, respond quickly, adjust ofter
• read the agile manifesto
• don’t worry about the charts and the graphs
• Monolith first
• API first and micro-services have more costs on smaller teams.
• build API when you’re making your iOS app. You can’t predict the future.
• Don’t introduce them until you need them
• Don’t do them until the costs are worth the benefits.
• Seeds not dumps
• Robust, randomized seeders not dumps of
• Less scared to make changes. reduces fragility
• Test to save your job
• what part of the app, if broken would make me worried for losing my job
• testing for value that comes from it not because someone told me
• Custom Requests (smaller controllers, easier testing)
• View data composition
• class PostPresenter __construct(Post $post) public function
• model
• responsables: reads the toResponse() method. implements Responsable
• Slim controller methods. Don’t do the things until you need the thing

Perennial Sellers, Ryan Holiday

— — — — — —

• Create your own category.
• The only hire-all-you want recruiting platform
• Really awesome to a core group of people.
• Piss off everybody else.
• The best art divides the audience. — Rick Rubin
• Timelessness: focus on what you’re doing and what greats have lasted
• Not chasing fads. Is this trend going to last or am I just riding the wave?
• You gotta make sure you’re on your path and not get mixed up with people who’s path cross yours, especially the hopelessly lost.
• Timeless principles. Who are your peers?
• Why are you comparing yourself to anyone but yourself?
• Slack completely different workplace cultures. [ Basecamp free plan! ]
• Focus on the things that don’t change.
• Timeless, not going to change. Finding timeless in the timely.
• Effectiveness: the product has to do it’s fucking job. (Redwing boots)

This is a _________ that does _________ for ____________.

• what you’re doing, why you’re doing it, who you’re doing it for

It’s not what it is, it’s what it does. Does it pass the use case test for what you’re doing. Real and compelling need

Will this business still be around a decade from now?

Do the marketing → want people to discover it. Get your work in people’s hands.

===== Enemy is not piracy it’s obscurity. =====

• how many people DISCOVER things via advertising. Advertising is gas on the fire. The car has to be moving.

Community. people in a room, you can tell them about things. a faithful following. People that look forward to whatever you do next.

We’re farmers. We only care what we’re doing in our field. You’re in whatever you make space (not tech space)

Crazy love affair with each other.

Email list → nothing that recommend books by other people. 90–95,000 people. 7 times in 7 years to promote his own books. Hardcore fanbase around what you’re doing.

Are you giving it time? Slow and steady relationships with your fans. You can’t just quit. What happens after the launch? Nothing if you quit.

• No time for Hacks. Make my mind adaptable to any circumstances, not tell me what to do.
• Is this the legacy I want to leave?