I am a web developer from Heidelberg (Germany) with specialization in front-end, working at chocoBRAIN. I have been working on the web professionally since 2015 and unprofessionally since the mid of the 2000s, when I made my first websites and internet forums.
For that reason I mastered those first when I became a Web developer.
With Bootstrap and jQuery one is still able to create a good looking, professional website or interface quickly. With version 4 Bootstrap has been implementing modern CSS techniques, but I feel that jQuery has outlived its purpose and that it is time to move on.
With the demand for more complex design cases and better user experience, the need to write the CSS for it quicker while having it more extensible and flexible at the same time arose. After some time Sass/SCSS became the answer to this problem. However, PostCSS is so performant, powerfull, and integratable in modern front-end stacks that it really has the potential to dethrone Sass.
More modular and modern CSS frameworks like Bulma were more useful here than more monolithic ones like Bootstrap, but still were not flexible enough. It seems like Utility-First frameworks like Tailwind CSS can deliver here, because they are composable, predictable, and therefore easier to maintain and to scale.
One might think that static Web pages are not relevant anymore, because of the very dynamic and interactive nature of the modern Web. However, this is not true, due to the fact how accessible static Web pages are for humans and (search) bots alike. At least if you want your Web pages to have a good SEO, you still will need static pages. But we developers do not want to miss the power and comfort of programmatically created Web pages. Static Page Generators come to the rescue in this.
Being a front end developer by definition means that my area of expertise is not in the back end. However, I take some interest in and worked often with Ruby and Ruby on Rails - mostly on the receiving part on the front end.
I like the programmer happiness and object oriented direction of Ruby as well as the strong mentality for clean code and testing within its community. Ruby on Rails’ huge set of functionality coupled with the convention over configuration paradigm seems very attractive.
Version control with Git became the standard in the last years for a good reason. Since I use it, it never let me down and it should be implemented even in small projects. However, I still have not mastered in the way I feel I should.
For organisational purposes I would argue that in a small project an issue system like those integrated in GitHub or BitBucket is enough. However, if the project gets bigger - may it be in terms of coworkers or product size - a real ticket system like JIRA should be used. BitBucket and JIRA tend to have some annoyances, but GitHub always served me very well.
Mails, calendars, office documents and files can be shared among team members very easily with G Suite.
As I started to create and lead bigger software projects I have begun to deepen my knowledge in the topics of software design and technological leadership of small teams.