Suggestions
Marcin Zajkowski
Chief Technology Officer at Cogworks, CTO/CKO at WOW School, Consultant and Public Speaker
Marcin Zajkowski is a seasoned technology professional currently serving as the Chief Technology Officer (CTO) and Senior Solutions Architect at Novicell Norge.13 He is known for his leadership skills, positive attitude, and proactive approach to challenges.1
Professional Qualities
Marcin is recognized for several key attributes:
- Natural leadership: He demonstrates an innate ability to guide and inspire teams.1
- Supportive attitude: Colleagues appreciate his consistent support and motivation.1
- Problem-solving skills: He approaches challenges with a positive mindset.1
Recent Activities
Marcin has been actively sharing insights and experiences on various professional topics:
- He recently participated in discussions about commit contents and their importance in development practices.2
- Marcin has been involved in creating video content, sharing his professional journey and insights.3
- He has engaged in podcasts focusing on time management and leadership.4
Personal Development
Marcin has shown a commitment to personal and professional growth:
- He has reflected on the challenges of balancing work and life demands.5
- Marcin has openly discussed his experiences with time management, including the importance of learning to say "no".4
Technical Expertise
As a CTO and Senior Solutions Architect, Marcin has demonstrated interest in advanced technical solutions:
- He has been involved in evaluating multi-tenant realtime and search index setups, showing his engagement with cutting-edge technologies.6
Marcin Zajkowski's LinkedIn profile reflects a professional who is not only technically proficient but also focused on leadership, time management, and continuous learning in the technology sector.
Highlights
Finally, this year I did not miss the CFP for Beyond Code (https://www.beyondcode.pl/) and just submitted my 3 proposals for talks, all of which I'd love to present to a wider audience.
Fingers crossed now as the vibe and theme of the conference strongly resonate with all what I do in my recent activity 🤞
🤖 Devs.. how do you keep your commits clean (or within convention)?
We had an internal debate in our PL office recently... There is plenty of people who completely doesn't care about the commits contents (SHAME SHAME!). On the other hand, there are perfectionists and purists (#me 🙃 ) who would love to have a convention on top of everything.
My ideal commit message is built with:
<type>[optional scope]: <description>
[optional body] [optional footer(s)]
Where:
👉 type: fix/feat/BREAKING CHANGE/chore/build/ci/docs/style/refactor/perf/test - type from the Conventional Commits convention (see: https://lnkd.in/d5X5KEiX) 👉 description: {Past Simple Verb} {WHAT} (optional) {WHAT_FOR} 👉 body: additional context, details, information, e.g. JIRA ticket or information for other developers
👨💻 Łukasz for example suggested keeping ticket numbers directly in the commit - as it's exposed in the repo directly and immediately points towards history of the changes.
I'm not against, but I think it'd loose a little bit of clean state and would force having ticket for everything - what is not a bad thing and side effect hmmm. Not even going into the area of SQUASHING vs. NOT SQUASHING commits yet...
But let me feed my curiosity and share how do you approach it? Do you care about the content of your commit messages? Do you keep any convention around it?
