When writing code, we need tools and best practices. This is where we can share about those.
If you’ve been using Spring for a while, or copy-pasting some web tutorials or examples, you’ve probably put some @Autowired annotations on private fields.
This does work, but it’s not the best way to do it.
Last week, Tony asked me about the technological stack behind my website. It’s a subject I wanted to write about once the website was stable, but I keep tinkering with it. As such, it’s far from finished and I still have many ideas, but let’s talk about it now nonetheless.
Read moreToday’s Valentine’s day, the best day in the year to tell you how I fell in love with editorconfig.
Read moreI’ve discussed with several people, this year. Technical leads, technical supervisors, architects… You get the gist. Among those discussions, I heard a recurring complaint, which I previously feared to be my demanding nature expressing itself.
But no! Other people noticed it too, and it basically boils down to something like this: we’re facing a new generation of developers, who like to do things fast and don’t care much about how things work deep down, and we’re living in an era proposing a new framework to help them go faster and not understand. The two together won’t make for great developers. Good developers, maybe, but not great ones.
Read moreWe developers often spend a great deal of attention choosing our tools: computer, editors… Yet, we often fail to see the gain of choosing an appropriate font.
Here is some food for thoughts on this topic, and some of my favorite coding fonts.
Read moreMore than once in my—no-so-long—career, I’ve had to work on machines that were not appropriate to my development needs. These were most often the result of company policies designed to reduce the cost of machines to a reasonable level, but that doesn’t take the specific case of developers into account. In the (not-so-)long run, it’s actually often money sent down the drain nonetheless.
Read more