Displaying episodes 1 - 30 of 35 in total

Onboarding a new project

When you inherit a project, how do you draw a balance before making everything nice to work with and delivering value to the stakeholders?

Paying down technical debt

Is all technical debt bad? Can it serve a valuable purpose? We share our opinions along with some tips on how to be strategic when paying down technical debt in your project.

Knowing when and how to try something new

You just attended a conference or finished a book/course and you're all excited to try out some new "best practice". We discuss how to balance this enthusiasm with the needs of your team and project.

Wireframe before coding

As developers, coding is the fun part, but we share why we like to slow down and take some time to wireframe before diving into the editor

Continuous integration doesn't have to be hard

Maybe "continuous integration" sounds like a complex thing to setup. We explain why it doesn't have to be, how to start small, and what the benefits are.

Deciding what to build

So someone has asked you to build an app, or add a feature to an app. How do you decide exactly what to build and how much to charge? We share our approach to these important questions in this episode.

Are your logs too noisy?

Logs and error trackers are a vital tool for maintaining a production app. But if you're not careful, they can get so noisy they stop providing value. We discuss a few reasons why this is the case and our strategy for avoiding this problem.

How we decide whether or not to take on something new

This episode is a little different. We take a peek behind the scenes as to how we qualify projects, and the sorts of things you might think about before deciding whether or not to take on something new.

Are you allowed to do that?

Roles and permissions are a core part of most applications. Laravel provides some tools for managing and enforcing this, and third party packages provide even more features. Aaron and Joel share their techniques for enforcing roles and permissions, in a way that won't get harder to manage over time.

Are you a Laravel developer or a PHP developer?

When you're building a Laravel app, you're writing PHP code, but you're dealing with many patterns and conveniences provided by Laravel. So where do you draw the line between the two? Is it important? We discuss this topic and how you can get the most out of what both PHP and Laravel have to offer.

Should developers have access to production?

> Developer: "I just need to SSH in real quick" > Server admin: "No" Have you had this discussion? Listen in as Joel and Aaron talk about their experience on teams of different sizes, and how to handle this potential conflict, while still getting your work done.

Pick a coding standard, any one will do

Where should I place this curly brace? Trailing commas or not? Have you encountered disagreements about coding standards on your team. In this episode we explain the benefits of coding standards, how to adopt them on your project, and discuss the two most popular tools in the PHP community for enforcing them.

The art of asking and answering questions

We've all been stuck with something we didn't know. Should you ask for help? And how? Or if someone on your team asks you a question, how can you handle it best? We discuss it all.

Testing 1 ... 2 ... 3, let's talk testing

What are the big 3 types of tests we use on our projects? How do we decide which to use? Listen in as we discuss this and more.

Guarded vs fillable, fight!

It's no tabs versus spaces, but it's close. Do you use guarded or fillable in your Laravel models? Aaron and Joel share their default approach, as well as several reasons for that choice.

Don't ignore that pain!

It's easy to get used to things that cause us friction or pain in our development process. In this episode, we discuss how to avoid that trap and how to evaluate when to invest time in fixing that pain.

Validation is your friend

Validation may seem boring, but it's a vital part of any Laravel application. Joel and Aaron share some tips on validation along with exciting news about a new resource to master Laravel validation rules.

Always be ready to hand off the project

Why is it important to think about a future project hand-off at the beginning of a client relationship? Aaron and Joel share their approach.

Finding and fixing a performance issue

Last episode we discussed how to deal with a "slow app" complaint. This episode we discuss some technical approaches to find and fix the issue.

Someone said my app is slow. Now what?

The dreaded support ticket gets filed: App is slow! Before you get defensive or close as "Won't fix", consider a few tips on how to successfully approach this situation.

How long does it take to get your project running?

Aaron and Joel have joined a fair number of projects over the years. Listen as they share some tips on how to make process less painful for your team.

Is it a good idea to install that package?

Laravel and PHP have a rich ecosystem, but it's good to weigh the pros and cons before reaching for a new package. We share some things to consider.

Where do I start making things better?

Where are some good starting points for modernizing and improving a legacy codebase? Joel and Aaron discuss a few ideas where you could start.

How long is that going to take?

The eternal question that every developer hears: How long is that going to take? Aaron and Joel discuss some ways to frame that question, and how to provide an estimate that will avoid unnecessary disappointment.

Getting started with a legacy codebase

Stepping into an unfamiliar codebase with a long history can be a challenge. Aaron and Joel share some tips on how to get started and build confidence that you're making things better.

Why even review when my code is perfect?

Some shy away from code review, not wanting to be critiqued. Aaron and Joel share some tips on how to get the most out of code reviews, and things to look for as a code reviewer.

Are you testing me?

Aaron and Joel talk about why they write tests and what sorts of tests they find valuable.

What is the one true way to do this?

We discuss a couple scenarios where there's more than one way to do something, and how we think through our decision.

Did you just tell me to read the manual?

How do you learn a new technology? Or how do you find out what's changed in the latest version of something you already use? Aaron and Joel share some tips on what they do.

Do you have a clear mental model?

The technologies we work with are extremely detailed. Without a clear mental model of how things work together, it's easy to get lost or confused.

No Compromises, LLC