Nitpicking terminology: are we using the right terms
Take a ride on a magical train looking through our every day terminology (buzzwords included).
While we are developers, first and foremost we are human beings, terms and their meaning do influence our daily lives and ways we do our work.
Is my code violating 'Single Responsibility Principle' or 'Separation of concerns'? What is 'technical debt' and is it comparable to 'financial debt'?
Some teams have leaders, some have managers, what is the difference and should we care about it? Definition of a team seems to be completely broken; legacy is considered a dirty word and project managers seem to manage nothing.
Having effective communication should not be 'a nice thing to have,' and I do hope you will join me in the discussion on these topics: your input is very valuable.
Saturday, 2018-10-06 @ 10:15
> Skill level: intermediate
> Duration: 45 min
I started using PHP as a student, back in 1999. At first I worked as a one man band web developer and from there I progressed, via focusing on PHP development in a team environment, to be a senior dev, tech lead & technical analyst.
I found much more happiness doing backend stuff so I focus on scalable backends and devops tasks this days.