29
.
04
.
2024
31
.
05
.
2022
HR
Visuality

Successful way to transfer technical knowledge in organization

Mariusz Kozieł
Chief Executive Officer

As you may know, our Youtube channel (https://www.youtube.com/c/Visualitypl) is not as active as was before. There are a few reasons:

  • pandemic time, when offline presentations ware cut off and we was pushed to remote work

  • the new way of sharing knowledge in Visuality absorbed Lighting Talks completely

At the beginning of last year, I decided to introduce meetings where engineers could share knowledge. As Visuality is most about Ruby we name them backend meetings. There were so many topics to discuss which didn't have a place to be faced. Even when we have our standards and way of doing things, we have to sometimes update them and each of our developers has to know why. Quickly we have realized that bi-weekly meetings are not enough, so we have started to meet each week.

share knowledge wit

We have talked about so many things over the last 15 months, like:

  • our internal standards
  • developers seniority levels, so what we expected on each level with some materials to achieve that. We are not orthodox so it's only a path.
  • expected outcome form recruitment exercise
  • different ways of auditing code
  • how to estimate projects
  • event sourcing, DDD, CQRS - we are still into that topic :D
  • tools and tips & tricks for daily work
  • real problems in our projects
  • real-time workshops where we updated Rails in our internal platform
  • and a lot of more

the best meeting ever

Our meetings are flexible. People can join online or come into the office to interact in a one-room. We are planning topics ahead or spontaneously. It could be a prepared presentation or not, for example, engineers can bring code/problem from their projects. The funny fact that in my opinion, the most interesting discussions are about: bad architecture, refactored code, crazy bugs, or how to implement something.

bugs meme

From time to time we invite former employees or experts from other companies. They can also come with any topic. If the topic could be interesting for frontend devs we are inviting them too.

We are recording our meetings for those who couldn’t join or for future employees. On top of that, we have notes and logs to easily find what the meeting was about.

To sum up, our meetings are a great way to share knowledge, but we have other ways to do that, namely: mentoring, conferences, courses, pair programming, and sharing resources. Maybe it’s not a modern approach but it’s still working properly. Based on the success of backend ones we have reactivated also frontend meetings, as those worked great before the pandemic world.

Additionally, a good atmosphere and flexible approach have helped to unblock people and they are more active, or at least some of them 😛 On top of that, I feel that engineers act more as a team, even if they don’t work in the same project. And some of the topics have been transformed into PRUG (Poznań Ruby Users Group) and WRUG (Warsaw Ruby Users Group) presentations so we are back to share knowledge in the community.

Mariusz Kozieł
Chief Executive Officer

Check my Twitter

Check my Linkedin

Did you like it? 

Sign up To VIsuality newsletter

READ ALSO

Ula Sołogub - SQL Injection in Ruby on Rails

The Deadly Sins in RoR security - SQL Injection

14
.
11
.
2023
Urszula Sołogub
Backend
Ruby on Rails
Software
Michal - Highlights from Ruby Unconf 2024

Highlights from Ruby Unconf 2024

14
.
11
.
2023
Michał Łęcicki
Conferences
Visuality
Cezary Kłos - Optimizing Cloud Infrastructure by $40 000 Annually

Optimizing Cloud Infrastructure by $40 000 Annually

14
.
11
.
2023
Cezary Kłos
Backend
Ruby on Rails

Smooth Concurrent Updates with Hotwire Stimulus

14
.
11
.
2023
Michał Łęcicki
Hotwire
Ruby on Rails
Software
Tutorial

Freelancers vs Software house

14
.
11
.
2023
Michał Krochecki
Visuality
Business

Table partitioning in Rails, part 2 - Postgres Stories

14
.
11
.
2023
Jarosław Kowalewski
Backend
Postgresql
Ruby on Rails

N+1 in Ruby on Rails

14
.
11
.
2023
Katarzyna Melon-Markowska
Ruby on Rails
Ruby
Backend

Turbo Streams and current user

29
.
11
.
2023
Mateusz Bilski
Hotwire
Ruby on Rails
Backend
Frontend

Showing progress of background jobs with Turbo

14
.
11
.
2023
Michał Łęcicki
Ruby on Rails
Ruby
Hotwire
Frontend
Backend

Table partitioning in Rails, part 1 - Postgres Stories

14
.
11
.
2023
Jarosław Kowalewski
Postgresql
Backend
Ruby on Rails

Table partitioning types - Postgres Stories

14
.
11
.
2023
Jarosław Kowalewski
Postgresql
Backend

Indexing partitioned table - Postgres Stories

14
.
11
.
2023
Jarosław Kowalewski
Backend
Postgresql
SQL Views in Ruby on Rails

SQL views in Ruby on Rails

14
.
11
.
2023
Jan Grela
Backend
Ruby
Ruby on Rails
Postgresql
Design your bathroom in React

Design your bathroom in React

14
.
11
.
2023
Bartosz Bazański
Frontend
React
Lazy Attributes in Ruby - Krzysztof Wawer

Lazy attributes in Ruby

14
.
11
.
2023
Krzysztof Wawer
Ruby
Software

Exporting CSV files using COPY - Postgres Stories

14
.
11
.
2023
Jarosław Kowalewski
Postgresql
Ruby
Ruby on Rails
Michał Łęcicki - From Celluloid to Concurrent Ruby

From Celluloid to Concurrent Ruby: Practical Examples Of Multithreading Calls

14
.
11
.
2023
Michał Łęcicki
Backend
Ruby
Ruby on Rails
Software

Super Slide Me - Game Written in React

14
.
11
.
2023
Antoni Smoliński
Frontend
React
Jarek Kowalewski - ILIKE vs LIKE/LOWER - Postgres Stories

ILIKE vs LIKE/LOWER - Postgres Stories

14
.
11
.
2023
Jarosław Kowalewski
Ruby
Ruby on Rails
Postgresql

A look back at Friendly.rb 2023

14
.
11
.
2023
Cezary Kłos
Conferences
Ruby

Debugging Rails - Ruby Junior Chronicles

14
.
11
.
2023
Piotr Witek
Ruby on Rails
Backend
Tutorial

GraphQL in Ruby on Rails: How to Extend Connections

14
.
11
.
2023
Cezary Kłos
Ruby on Rails
GraphQL
Backend
Tutorial

Tetris on Rails

17
.
03
.
2024
Paweł Strzałkowski
Ruby on Rails
Backend
Frontend
Hotwire

EURUKO 2023 - here's what you've missed

14
.
11
.
2023
Michał Łęcicki
Ruby
Conferences