
My favourite tech discussions - or how to lose time and piss people off
- Shem
- April 26, 2024
Meet My Personal Favorite Tech Archetypes ๐
Swollen Mark - SAD Developer ๐ค Strategic Ambiguity Development (SAD) Swollen Mark embodies the Strategic Ambiguity Development style. He is the master of corporate speak and is known for his exceptional ability to remain indecisive under pressure. Mark can wrap any decision (or lack thereof) in a strategic package, making SAD a critical part of his development arsenal.
Turret Dave - DAD Developer ๐ Dynamic Action Development (DAD) Turret Dave is all about Dynamic Action Development. Known for his YOLO mindset, Daveโs development style is impulsive and action-oriented. He prioritizes moving projects forward at breakneck speeds, often eschewing extensive planning for the thrill of rapid progress.
Asperger Peter - CAD Developer ๐ ๏ธ Craftsmanship Advanced Developmend (CAD) Asperger Peter is dedicated to Craftsmanship Advanced Development. With a total commitment to the craft of software development, Peterโs approach is meticulous and precise. He prides himself on his sophisticated and well-honed coding techniques, making CAD an essential part of his development philosophy.
Commit Message Formats
Asperger Peter: Commit messages should meticulously detail every change for future reference. ๐
Turret Dave: Why waste time? โFixed stuffโ does the trick. ๐ ๏ธ
Swollen Mark: Well, you know, from a strategic standpoint, it really depends on aligning our commits with our broader objectives and operational frameworks. ๐
The Most Elegant Code
Asperger Peter: Our code must dance elegantly with the compiler, a true ballet of logic. ๐ฉฐ
Turret Dave: If it runs without tripping, it’s elegant enough for me. ๐
Swollen Mark: Elegance is subjective, and really, our approach should be flexible and scalable to leverage synergies across platforms. ๐
Endless Arguments Over Naming Conventions
Asperger Peter: Names should convey meaning and context, a beacon of clarity in the dark. ๐ฎ
Turret Dave: Short and sweet wins the race. Next issue! ๐
Swollen Mark: Naming is crucial, but letโs pivot to how this impacts our brand integration and cross-functional visibility. Itโs about strategic alignment. ๐
The Best Code Commenting Style
Asperger Peter: A well-commented code is a well-maintained garden. Each comment a flower. ๐ผ
Turret Dave: Gardens are high maintenance. I prefer a desert landscapeโsparse and clear. ๐๏ธ
Swollen Mark: Comments should foster an ecosystem of knowledge sharing, though we must balance this with our resource allocation and operational bandwidth. ๐
Git Branching Model (Trunk Based vs GitFlow etc.)
Asperger Peter: GitFlow organizes development like a finely tuned orchestra. ๐ป
Turret Dave: Trunk-based development is rock and roll, fast and loud. ๐ธ
Swollen Mark: The choice of branching strategy should reflect our strategic priorities and market positioning, ensuring we remain agile and market-responsive. ๐
Rubocop vs StandardRB
Asperger Peter: Rubocop allows for a tailored approach to maintain our coding standards. ๐งต
Turret Dave: StandardRB, set it and forget it. Efficiency is key. ๐
Swollen Mark: Itโs imperative we drive value through best practices that enhance our operational efficiencies and compliance posture. The tool should align with our corporate ethos. ๐ข
The Correct Way to Organize Project Files and Folders (e.g., MVC vs. MVVM vs. Clean Architecture)
Asperger Peter: Clean Architecture is like a well-organized library, everything in its right place. ๐
Turret Dave: Keep it simple. Too many shelves and you canโt find anything. ๐๏ธ
Swollen Mark: Ultimately, the architectural framework must not only support but also amplify our strategic initiatives, driving forward our core business objectives. ๐
Choosing Between GraphQL and RESTful APIs for a New Project
Asperger Peter: GraphQL precisely fetches what is needed, no more, no less. ๐ฏ
Turret Dave: REST is straightforward and time-tested. Stick to the classics. ๐ฐ๏ธ
Swollen Mark: We need to leverage a solution that optimizes our data delivery mechanisms while remaining robust and scalable across diverse application scenarios. ๐
Functional Programming vs. Object-oriented Programming Paradigms
Asperger Peter: Functional programming reduces side effects for cleaner concurrency. ๐งผ
Turret Dave: Objects have identity, state, and behavior. Thatโs natural. ๐ฑ
Swollen Mark: The decision here should be aligned with our strategic goals, ensuring we adopt a paradigm that enhances our capability to deliver scalable and resilient solutions. ๐
Too Terse vs Too Verbose
Asperger Peter: Why write in novellas when a haiku will do? Comment: โIt works.โ Done. ๐
Turret Dave: Every line of code should tell a story. If Iโm not writing a Tolkien epic in my comments, am I even coding? ๐
Swollen Mark: It’s paramount to strike a strategic balance between
Use Library vs Roll Our Own
Asperger Peter: Why reinvent the wheel?
import antigravityand letโs float away to the next task. ๐Turret Dave: But crafting our own gravity! Imagine the customizations! The glory! The control! ๐
Swollen Mark: Leveraging existing technologies enhances our operational throughput, but bespoke solutions can provide us with a competitive edge. We should deep dive into our core competencies to evaluate our capacity for innovation versus the necessity for rapid deployment. Letโs calendarize a workshop to ideate on this. ๐๏ธ