In my career it took me some time to understand and be convinced of the importance of doing analysis. I still remember my first job experience, I just wanted to quickly write some code and refactor it n-times to get better results. Did not you?
Things are different today and I am writing this post to share with you my personal approach to analysis. It is not something new, it is just my tailored method based on experience and well known methodologies.
In general you get as input a problem domain (the observed system with all the entities and rules involved) and must produce as output a solution domain (the designed system that solve the original analysis problem). So a good start is to:
- Get a clear view of the problematic to solve,
- Reduce the problem domain to a minimum knowledge space
Cloud platforms come with a variety of options and constraints certainly driven by infrastructure and business needs which indeed diversify their pricing plans and customer adoption as well. But often they also have an implicit value: designing with certain constraints in mind would facilitate scaling and replication, would provide performance gains and increased revenues. Are constraints such as request timeout or limits on outbound traffic and datastore usage, so bad after all? However, when designing for your private hosting, you might skip or ignore few of them and miss an opportunity to improve your service design. Here are few points worth to consider: Read More
Exposing your idea supported by a presentation can be considered a form of art. It implies a creation and an exposition moment; like for any other artistic creation process an idea drives the conception and a good dose of practice can help to better describe the artist intention.
For this reason, during the years, I tried to develop a personal “Aesthetic Theory” of Doing A Presentation. In this “Theory“, beauty is related to three different but related factors:
To arrive to our goal, that is get as much closer as possible to the beauty, we can distinguish three different moments:
- Analysis time: it starts with your commitment to write a presentation, till the moment you start doing it.
- Creation time: it is all the time you spend creating the presentation.
- Presentation time: it is the moment of the truth, when you go live with your presentation.
I always try to bring my conversations to a productive conclusion. When this happens I consider it always a “We Win” situation, because my primary scope is not to win against the other, but to find the best compromise that is closer to the most rational and suitable solution.
This process requires a lot of efforts in listening, comprehension, abstraction, persuasion, calm and finding the good words. But sometimes, despite my efforts, conversation crashes into an irreversible “We Lose” situation… Why does it happen?
Starting a new job is certainly a mix of feelings and expectations, yet a pretty large amount of topics to learn and people to meet. Not an easy time indeed, which should however be faced as a new challenge, professiolnally and personally speaking, with regards to the new environment, new colleagues, new balance to quickly gain and maintain. If that’s happening often (as a consultant, as a job hopper or freelancer, for instance), then it would definitely be worth to optimize that time thanks to experience and lessons learnt, getting to a certain personal standard when starting a new job.
By the time, I have actually improved a sort of action plan to apply at each change in my career in terms of companies or projects within the same company, which I can resume in a list of tips hopefully worth to share. Read More