JanNov 11, 2024
Dennis Doomen
I like to think of us—developers and architects—as professionals. While we don’t have formal certification processes like doctors in hospitals, that’s probably because our field evolves so quickly that no one has managed to compile a static list of requirements for all developers. But being a professional goes beyond maintaining high standards, knowing your craft, and continuously investing in your knowledge and (soft) skills. (cont'd)
Nov 11, 2024 at 3:10pmWeb
Show threadDennis DoomenNov 11, 2024
Being a professional also means acting like one. You take responsibility for your actions, provide constructive feedback, challenge ideas with real alternatives (instead of simply blocking them), show up on time for meetings, and keep them on schedule. But there’s more to it—when asked to act unprofessionally, you stand your ground. If a manager, tech lead, or product owner asks you to skip unit tests without valid reasoning and a plan to address it soon, challenge it. (cont'd)
Show threadDennis DoomenNov 11, 2024
If they suggest bypassing code reviews to merge a pull request immediately, challenge it. If they downplay a critical vulnerability in a dependency, challenge that too, and ensure there’s a plan to address it. This doesn’t mean you need to be a stubborn developer. It means taking your responsibilities as a professional seriously, understanding the circumstances behind requests, and agreeing only if there’s a reliable plan to resolve any concerns promptly. (cont'd)
Show threadDennis DoomenNov 11, 2024

If there isn’t, make sure to formally record your disagreement to avoid repercussions—or, if necessary, find a job that values professionalism.

#lessonslearned #consultancy #avivasolutions #professionalism #softskills