emoran

Map<Id, List<Id>> userRoleToUsers = new Map<Id, List<Id>>();

for(User newUser : [SELECT UserRoleId FROM User LIMIT 50000]) {
	if(userRoleToUsers.containsKey(newUser.UserRoleId)) {
		List<Id> usersId = userRoleToUsers.get(newUser.UserRoleId);
		usersId.add(newUser.Id);
		userRoleToUsers.put(newUser.UserRoleId, usersId);
	} else {
		userRoleToUsers.put(newUser.UserRoleId, new List<Id> { newUser.Id });
	}

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

girliemac

Conference & Meetup Talks

I have done many conference talks and I honestly do not recll everything, after lanyrd.com, where I used to keep tracks of all my conferences, has shut down. So this is the list where the talks were recorded && I remember. I am pretty sure some are missing!

⭐️: As a keynote speaker

Web, JavaScript, and other technical Conferences

• POST.Dev (Tokyo | Online) - October 2022 📺 YouTube