• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Listing Thymeleaf as a skill and in a project list

Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello! I'm an experienced Ruby/Rails developer preparing to switch to Java/Spring. I'm working on a pet project and decided to use Thymeleaf for the UI. This wasn't too difficult for me, given my Rails experience with similar technologies. I planned to use React/Redux/TS for my next project. However, I'm considering if it might enhance my CV/GitHub profile to have two React projects instead of one with React and one with Thymeleaf. From job listings and Reddit discussions, it seems Thymeleaf may not be as valuable. Still, I'm unsure if it might still be useful. For instance, in Rails, job listings rarely mention erb/haml/slim, focusing on more current technologies, yet many companies still use erb for the UI.

In summary, if you were hiring, would you prefer someone with extensive React/Angular/API experience and minimal Thymeleaf knowledge, or a candidate with decent skills in both React and Thymeleaf?

P.S. I understand that I could list anything on my CV and that many other factors are important. However, I'm currently focused on solving this specific issue.
Posts: 208
Mac OS X IntelliJ IDE
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I always tune my CV for a specific job and remove keywords and technologies which I'm sure that either won't be relevant or that can be implied. In some countries recruiters use tools that could discriminate against CVs with too many keywords (or not enough matched ones). My rule of thumb is to look at the job advert and see what they mention there. You basically want to have just the right number so the AI/non-technical person won't bin it but at the same time doesn't look weird to the rest of us.
    Bookmark Topic Watch Topic
  • New Topic