exciting times ahead - we're going for our first remote meetup! You're welcome wherever you're from as long as you adhere to our Code of Conduct - the meetup is in English.
The schedule will be two ~20min talks including Q&A, followed by splitting the audience into smaller groups for virtually hanging out (optional) :) Joining the meetup
Joining the meetup
The meetup will be on zoom see Zoom information to join
We're aware of the privacy concerns surrounding zoom and we share them. We're looking for better tools, we haven't found them yet.
- if you don't want your video to be visible to others, then turn it off/leave it off
Meanwhile, if you don't want to use the desktop client the zoom browser link above should work for you. If it doesn't you can usually get to it like this: the join link should also show a tiny "join from browser" link at the bottom of the window. Sadly, this requires you to create a zoom account. If the link doesn't show up, open the "Download and Install Zoom" link in a separate tab, that should make the link appear.
Participating in the meetup
- We'll take Q&A questions in Zoom via the "raise hand" feature (click on participants, there's a little raise hand link)
- the "socializing" part is optional, naturally, our aim is to not lose that part of our meetup - we'll try to split you into random groups and give you some ice breaker questions to kick it off
It's the first time we're doing a remote meetup. Your feedback is very welcome. Things will go wrong, we'll try to fix them. See you
Looking forward to seeing y'all Rubyists from Hamburg and maybe all over the world.
Irina & Jan
In almost all situations software is created by a group of people contributing their skills and knowledge to the effort at hand. This requires a great deal of collaboration and teamwork.
In most development organizations we find ourselves collaborating in the least effective ways possible. We are plagued with queues and waiting, inventory, countless meetings, context switching, interruptions, disruptions, and multitasking.
What if we could find a way to address these difficulties?
Mob Programming is a very simple concept: Let’s “turn up the good” on collaboration. This is the Power of Mob Programming. Let’s find ways to make it easy to collaborate well, to limit work in progress, and to shorten or even eliminate most feedback loops.
Let's explore the Power of Mob Programming.
This is going to be a new and improved version of a similar talk I gave at RUG::Berlin some weeks ago.
Certain psychological aspects of being a developer have been discussed in quite some detailed already:
- Imposter syndrome - A popular topic with many, for some time. It is common, I think to some extent we have the answers on how to handle it now, but it is not a solved problem.
- Crunch - The days in a sprint or in general, before a deadline, when the pressure is on and you have to finalize something. I think this problem is not that specific in the way it manifests itself for developers, it has also been discussed quite a lot.
Other things, however, have not been discussed as much yet, and I will give more emphasis on them:
- Finding your place, as a developer, in terms of your career path. Being "Full stack" or not. Doing DevOps or not. Finding the right balance between always challenging yourself and trusting the things you are already good at.
- Finding your place in a community, like the Ruby Berlin or Hamburg one, versus being an "Einzelkämpfer". Active and passive participation in communities and conferences and the effects or benefits you can expect on your sanity and well-being.
- Dealing with day-to-day realities of being a developer in a startup, versus the ideal world we aspire to in the settings of meetups such as Software Craftmanship.
- Dealing with annoying / ignorant recruiters and how to understand where they are coming from - to the extent necessary. Dealing with "noise" in general.
- Going full remote and/or freelance. This is very much a current issue, given the Corona context. Who can help you when you work alone and how?
- Are you at the right stage of your journey as developer to mentor juniors already, or is it better to focus on yourself first, to not overwhelm yourself? If you are a mentor once, do you always have to be one?
I will also introduce some people and companies that concern themselves with mental health in startups, or at work in general, like Evermood in Berlin & Münster, who I interviewed with once, but never worked for, and Yariv Ganov, a "Startup Psychologist" based in the Startup Nation, Israel.
Teilnehmerinnen und Teilnehmer (15)