Doing Leetcode is the worst way to prepare for a high-paying job as a software engineer, but the best way to get one.
Building real-world applications is is great way to prepare for a high-paying job as a software engineer, and a good way to get one.
Here's some things you can build:
https://t.co/4Sn0wRCEj9
New blog post: Modern Best Practices for #Testing in #Java. It contains many lessons that I learned over the years of writing tests. Featuring @junitteam, @testcontainers, #assertj, @java https://t.co/e3wf6shGGW
Refactoring in a separate project is often not the best of ideas. It might well be the most common form, but it's a terrible idea from an investment point of view.
Let's look at the investment profile of various forms of refactoring. First refactoring in a separate project :
@simonharrer@digitalocean Had a similar problem this week, turned out the format of the message is very specific: has to start with 'data: ' and end with \n\n
Petition to make this picture of Sean Lock the replacement for the Leonardo Di Caprio in Django Unchained picture for when you have absolutely got someone.
@mickaelistria@prahladyeri@EclipseJavaIDE@SonarLint I agree that there is a TON of code intelligence in SonarLint.
I did some evaluations at the end of last year, and I'm deeply impressed with how far they've come and how well it integrates with IDEs.
This article on pairing all day at Pivotal kind of blew me away. Thanks @nota_bennett for articulating something I've heard time after time about pairing all day.
https://t.co/KC7nlqmEtr
I think it's time to discuss the efficacy of Pull Request Reviews as a way to ensure code quality and shared understanding on software teams. Here's a little thread on some of the experiences I've had in my career, why I think this matters, and what we can do about it.
@bitshiftmask At my previous job we were using a Docker image to build the firmware. The build was reproducible everywhere and the Dockerfile was listing all the required dependencies. You can't lose it either!
@MrMasquime Un des seuls arguments qui fait que j'en utilise c'est les streams Java (ou mieux @vavr_io), si tu dois faire un map je trouve plus lisible de mettre la référence sur le getter. Sinon j'utilise les records ce qui enlève le boilerplate
Let's imagine for a little while that software devs applied their "techniques" to cooking. We usually don't refactor because it takes valuable time that we could spend cooking. So we would not cleanup the kitchen. 🔽 1/6