Just another reason to why you shouldn't use Lombok, in another saying another reason to why you should write unit tests: You have two fields in your class. Fields are in the same type. You use @AllArgsConstructor to auto-generate your all args constructor. It works for a moment, until you change the order of the field.

LazyDeveloper.java

import lombok.AllArgsConstructor;
import lombok.Data;

@Data
@AllArgsConstructor
public class LazyDeveloper {

    private String firstName;

    private String lastName;

}

LazyDeveloperTest.java

import org.junit.Test;

import static org.hamcrest.Matchers.equalTo;
import static org.junit.Assert.assertThat;

public class LazyDeveloperTest {

    @Test
    public void testAllArgsConstructor() {
        LazyDeveloper lazyDeveloper = new LazyDeveloper("John", "Doe");

        assertThat(lazyDeveloper.getFirstName(), equalTo("John"));
        assertThat(lazyDeveloper.getLastName(), equalTo("Doe"));
    }

}

@Kidlike great addition, thank you. I encountered such a situation when using Lombok and just noted it.