I usually stick with tools with a good reputation and some history. For some POCs/MVPs, I might give a try to new tools and experiment, but I'm aware that I might throw everything in the end.
This is a really good way to look at future options for software developers. A lot I guess will also depend on the career stage of an individual and the type of experience they already have. Either way, work is there and that is the most important thing.
Sure, many factors influence this. And to be honest, I wrote this article with more senior engineers in mind. I’d imagine that as a beginner, you’d first want to experience both a bit. Seasoned professionals are probably already familiar with “today's path.”
I usually stick with tools with a good reputation and some history. For some POCs/MVPs, I might give a try to new tools and experiment, but I'm aware that I might throw everything in the end.
Thank you for the shoutout, Akos!
You're welcome, Petar! Are there any particular constraints to choosing a new tool? What stats are you looking at?
I usually check the latest commits and updates, # of issues, etc. Basically, I'm looking for signs whether it's active or not.
Thanks for the shout-out Akos, it's a privilege being in the same list with Anton and Petar!
You’re welcome Marcos! Loved your last article! :)
This is a really good way to look at future options for software developers. A lot I guess will also depend on the career stage of an individual and the type of experience they already have. Either way, work is there and that is the most important thing.
Also, thanks for the mention!
Sure, many factors influence this. And to be honest, I wrote this article with more senior engineers in mind. I’d imagine that as a beginner, you’d first want to experience both a bit. Seasoned professionals are probably already familiar with “today's path.”