The most difficult thing in software engineering is managing complexity.
We manage complexity with mental models - conceptual frameworks.
But those models can always improved via: test, refine, refactor.
One approach to doing this is inquiry-driven, ego-free conversation with other software devs/engineers where conceptual understanding tested.
This type of discourse - if done right - enable both parties to learn quicker. Both leave with better questions, new views, and lower cognitive load+higher resolution models.
If you're a proficient software engineer & communicator, and you'd like to engage in such with me, shoot me a msg. I'm testing this out :)
Potential topics:
problem solving approaches, design patterns, tech-specific conceptual shortcuts (e.g web, ML techniques, programming lang.-specific), under-utilized functions/mechanisms, common misunderstandings, tech topic/domain essence, intersections with other domains (e.g math, physics, bio) etc.
ethdevs@gmail.com
deepb#4778