Some things just don’t work out the way you intend them too, but it’s essential to at least give it a quick try. Because the faster you fail - the faster you’ll learn something. And the more you fail - the more you learn!
Paraphrasing Johnson & Fowler: "Software architecture is a shared understanding of the things that are important."
This really encapsulates everything about my approach to software architecture:
Make sure everyone understands how we want the software to be built.
Focus on the important stuff. Focus on the things that are hard to change later, focus on exit strategies for when you do need to change them.
Don't get lost in details. Strict adherence to patterns doesn't solve problems. Patterns are guidelines. Formalizing every piece of the architecture makes you lose sight of the bigger picture - the important stuff.
He/Him; Senior Software Developer, IT Swiss-army-knife.
Lots of coding, some hardware, some devops & sysops, some micro-controller electronics.
I used Arch BTW :)
Anti-GenAI
Any probability repeated often enough becomes a certainty.
Comes into play when i hear things like: "But that is unlikely to happen" or "It's too rare to consider".
Mostly heard by people who don't deal with a) the consequences of "rare" events, b) new devs/non-techies who don't understand the scale of how fast computers can make 1 error into milions c) people who don't grok Murphy's law
I'm a coder who has worn a lot of hats, from individual contributor to lead engineer to "CTO" (yes, in quotes, make of that what you will!). I've plenty to learn and hopefully some to share as well.
He/Him; Senior Software Developer, IT Swiss-army-knife.
Lots of coding, some hardware, some devops & sysops, some micro-controller electronics.
I used Arch BTW :)
Anti-GenAI
The nuclear option!
Employed well when no one group/person wants to Own a product/solution: "Ok so no own wants to own it? you want the Devs to own it? OK, we don't need it and we'll turn it off."
"NO NOT LIKE THAT! WAIT!"
As a nonbinary person, Meredith Whittaker's quote reminds me that technology should not only be inclusive of diverse gender identities, but that it has the potential to expand beyond the binary limitations of traditional societal structures.
I'm a technical advisor in the federal public service. I also mentor students in web application development and QA testing in the federal public service.
Location
Gatineau, Quebec
Education
Université du Québec en Outaouais
Pronouns
She / Elle
Work
Development Team Lead & Technical Advisor in web application development / Author
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
-Martin Fowler (co-author of Refactoring: Improving the Design of Existing Code
I keep that in mind whenever I modify existing code or write new code.
My favorite quote is from Frederick Brooks in his book, The Mythical Man-month:
The flawed nine pregnant women project management model, about adding more people to a project: "If it takes a woman Nine months to produce a baby, then nine pregnant women can produce a baby in one month.
"Never say never, just give it a try!" He is a web developer with plentiful experience in both FE and BE. His teammates describe him as a strong problem-solver and a reliable team player.
“Fail fast”
Some things just don’t work out the way you intend them too, but it’s essential to at least give it a quick try. Because the faster you fail - the faster you’ll learn something. And the more you fail - the more you learn!
Paraphrasing Johnson & Fowler: "Software architecture is a shared understanding of the things that are important."
This really encapsulates everything about my approach to software architecture:
The campsite rule: Leave the code cleaner than you found it.
Any probability repeated often enough becomes a certainty.
Comes into play when i hear things like: "But that is unlikely to happen" or "It's too rare to consider".
Mostly heard by people who don't deal with a) the consequences of "rare" events, b) new devs/non-techies who don't understand the scale of how fast computers can make 1 error into milions c) people who don't grok Murphy's law
"So then if it does happen, it must be okay for the servers to crash and all the data to be corrupted. Okay then, next topic :)"
The nuclear option!
Employed well when no one group/person wants to Own a product/solution: "Ok so no own wants to own it? you want the Devs to own it? OK, we don't need it and we'll turn it off."
"NO NOT LIKE THAT! WAIT!"
The harder your code is to read, the harder it is for people to replace you
"The future is not binary." - Meredith Whittaker
As a nonbinary person, Meredith Whittaker's quote reminds me that technology should not only be inclusive of diverse gender identities, but that it has the potential to expand beyond the binary limitations of traditional societal structures.
"Don't blame people from make mistake, or write regex each time you do that"
Simple just don't other feel bad, learn from mistake!
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
-Martin Fowler (co-author of Refactoring: Improving the Design of Existing Code
I keep that in mind whenever I modify existing code or write new code.
Keep it simple stupid.
PS: Keeping things simple is hardest part :)
My favorite quote is from Frederick Brooks in his book, The Mythical Man-month:
"Never say never, just give it a try!" - Gabriel Lee (and do you want to know who he is? yep, it's me. 🤗🤗🤗)
My favorite rule is: assumption is the mother of all f***-ups.
--RFC 761 of the TCP protocol
Everyone brings something to the table and by how he feels and acts regarding and about this fact tells a whole story. That's why I am as I am.
Talk is cheap,show me the code