The Journey, the Destination, and What Comes Next
The journey is part of the destination. They’re both important. The journey takes place for the sake of the destination, and the destination matters because of the journey. It’s not a big deal just to be in Paris – but to have arrived in the city of love after a long trip and a heartbreaking romance … that’s something to remember.
How to defeat burnout and stay motivated?
You know that feeling. Where you’re that close to finishing a project, or achieving a goal, or crossing a task off your to-do list … but you just can’t muster the energy. You’ve lost interest. You’re exhausted and drained. And you don’t know why.
That’s burnout. It’s something many of us are all too familiar with. I’d like to share with you a few ways that I fight burnout – or prevent it from catching me in the first place.
How to Want Very Little?
Sincerely wanting little is difficult. It goes against our firmly rooted desire for certainty, for ownership. To cut through this psychological attachment requires more than step-by-step processes or following a list of tactics, it requires a shift in your thinking, a shift in the way you approach your day to day life and how you make decisions.
The Habit Change Cheat Sheet: 29 Ways to Successfully Ingrain a Behavior
Our daily lives are often a series of habits played out through the day, a trammeled existence fettered by the slow accretion of our previous actions. But habits can be changed, as difficult as that may seem sometimes.
Don’t Be a Victim of Politics (Rewind)
Politics and projects go hand in hand. Team conflict, competing agendas, stakeholder dysfunction, resource constraints, and a myriad of other challenges exist and will send your project careening out of control if not managed properly.
Software architecture is a platform for conversation
If you’re writing software as a part of your day-to-day job, then it’s likely that your software isn’t going to live in isolation. We tend to feel safe in our little project teams, particularly when everybody knows each other and team spirits are high. We’ve even built up development processes around helping us communicate better, prioritize better and ultimately deliver better software. However, most software projects are still developed in isolation by teams that are locked away from their users and their operational environments.
Software architecture document guidelines
The purpose of the software architecture document (SAD) is to provide information that is complementary to the code. At a high level, this might include:
1. an outline description of the software architecture, including major software components and their interactions.
2. A common understanding of the drivers (requirements, constraints and principles) that influence the architecture.
3. A description of the hardware and software platforms on which the system is built and deployed.
4. Explicit justification of how the architecture satisfies the drivers.