I love this description by Carlos Ble of what makes a good community. Many important aspects are mentioned and hopefully inspire others to consider them for the communities they are part of! 👏🏻
#SoCraCan #SoCraTes #community
Your event’s #CodeOfConduct extends beyond the event and it’s digital spaces
We had an interesting discussion at #SoCraCan about whether we should allow people to attend the event, if they had behaved in a way that violates the event’s Code of Conduct *outside* of the event. What if that person “behaves” during the event? Wouldn’t it be unfair towards them to exclude them? Maybe they have changed?
Less than a month until I am back Nordic Testing Days in #Tallin where I will be speaking about, no encouraging you to start building better testing tools.
Tickets are still available, and the city and the conference is absolutely worth a visit: https://nordictestingdays.eu/
I think I got a few people excited about #serverless at #SoCraCan
Slides are here:
Now trying to figure out what the role of an Engineering Manager is.
Together with Gustavo Gutierrez we started a new #Kata at #SoCraCan: Develop a teaching lesson planner and learn about date and time zones.
The outline exists already, but I have to double check the test data.
Their problem was that they couldn't get DynamoDB to serve the queries they need so they had to switch to something else. They were also close to the 400 KB item size limit. After switching to PostgreSQL they reduced the cost by 90%.
He summarized the principles after the session:
- One to one relationship between entity and object
- Use Metaphor to understand the problem domain
- Favor immutable objects
- Create complete objects
- Create valid objects
- Do not use null/nil
- Do not use getters/setters, only when needed
- Do atomic changes: e.g. syncwith(newObject)
- Reify the architecture of the system in the system itself (subsystems)
Fourth one: represent the architecture of the system in the system itself, so it can reason about the system itself.
This allows to swap out parts of the system, and swap between a monolithic approach or a Microservice architecture.
A book recommendation is Rebecca Wirfs-Brock book: Designing Object-oriented Software
Third one: only allow valid objects (do not use setters to create an object step by step until you have what you need).
The first heuristic of Good Software Design is to model every concept in the business domain as a software model.
He recommends two books to draw inspiration from:
The Evolution of Physics (Einstein/Infeld)
The Design of Everyday Things (Dan Norman)
What makes a successful community? We've discussed this in a big group at #SoCraCan
Gustavo Gutierrez speaks about the time and date challenges they encountered in one project.
We didn't find a Timezone #kata, so we came up with our own very simple one: https://gist.github.com/coderbyheart/33ffc41a2023a643da75fdb543a0e6f2 ... it tool already a lot of time to understand the problem and so the 30 minute timeslot was over quickly.
Did a preview of my upcoming #NTD2023 talk about writing better test tools at #SoCraCan after lunch and nobody felt asleep! 😜
Got great feedback, which reminded me to add a main aspect that I previously only implicitly covered.
It's really cool that there are events like this where I can prototype talks.
We are sharing tools and methods we use in our development process in the third session:
First session is about non-verbal communication. And we picked the pool as the session room.
The first day of #SoCraCan is starting, and the attendees gather for the opening session.