Read on Twitter
I released my first real project as a project lead this week. We had to migrate a project to use Spring Boot.
Here's some of my takeaways from it:
Here's some of my takeaways from it:
1. Write down your rollout/rollback plan early.
Write down all the steps in detail. It'll probably change as you near completion, but you start to consider what needs to happen once all the code is written
Write down all the steps in detail. It'll probably change as you near completion, but you start to consider what needs to happen once all the code is written
2. Tests won't catch everything
Since this was a migration, we already had tests written. This way we knew if we broke something. Even with extra unit and integration tests there were some bugs we only found once we deployed to our dev environment.
Since this was a migration, we already had tests written. This way we knew if we broke something. Even with extra unit and integration tests there were some bugs we only found once we deployed to our dev environment.
3. Ownership
As a project lead I was able to make (some) decisions about how to approach the project. It took time for me to be comfortable as the point person.
As project lead you're responsible for the decisions that are made. And also be able to take feedback.
As a project lead I was able to make (some) decisions about how to approach the project. It took time for me to be comfortable as the point person.
As project lead you're responsible for the decisions that are made. And also be able to take feedback.
re: Spring Boot
I think Spring Boot is great, but getting to the reference documentation is a task ( w/o bookmarks).
When I search for Spring Boot docs there's always like 15 blogs in the results before Spring. And even then you usually get the API docs before reference docs.
I think Spring Boot is great, but getting to the reference documentation is a task ( w/o bookmarks).
When I search for Spring Boot docs there's always like 15 blogs in the results before Spring. And even then you usually get the API docs before reference docs.
Spring Security is great too, but it's a little confusing for me to get setup. There's 2-ish guides on the official Spring website, but I had to stitch together different blog posts and videos to really figure out what I needed to.
The other thing I like about Spring is that most of the libraries are 1 big strategy pattern. As long as you implement the right interface, you can do what you need to do.
But you have to know which ones to use.
But you have to know which ones to use.
Also, the Spring Developer youtube channel is excellent. I think the videos are really clear and informative
