If you're ever interested in a 15 minute speech about why let me know. Happy to spend time over a coffee (or 2 or 5) talking about how the difference between code design and architecture (or different levels for that matter) is just a matter of scale. For a quick overview, here's Uber's own Gergely Orosz talking about it.
Customer Journeys, User Stories, Personas, Use Cases. All different ways of trying to ensure that whatever you are building is actually useful for the customer. Whether you're putting together an architecture or a team, they're a good thing to keep in mind.
Metrics are good. You can't make data driven decisions without good data, but you have to be careful. Sometimes the data you collect and make visible drives behavior. From Dilbert to the Harvard Business Review, think about it.
I can assure you there's at least one person who will benefit from it, future you. How many times have you looked at a piece of code, cursed the author, then realized you were the one who wrote it? Do something for future you
History lesson today. James Gosling and Open Source.
How long is a string? Sounds like a simple question, but It’s Not Wrong that ":man-facepalming::skin-tone-3:".length == 7. It might not be wrong, but is it right? What are you measuring? What's your contract with the user? What are the expectations?
Here's an interesting approach
We've all heard of design patterns. They're ways of doing things. What about ways of thinking about things? What if there were a taxonomy of them? And what if there are 4 really important ones.
Campus recruiting is a great thing. Finding and hiring the right talent, the right coworkers for the future, is one of the most strategic investments we can make. 30 years after graduation and you can still learn things on campus. Yesterday I ran across this posting from an ECE Professor Martin's Somewhat Heretical Thoughts for Cornell Engineering Students.
