Skip to main content

A bad way to design your software

A bad way to design your software is to expose sensitive information to the end user, who might be a potential attacker.

That is why you need to invest in quality specialists who will not only design the solution but also take their time to test it thoroughly!

One more example of a poor design. The service should connect to a register to verify the public key for authorization, but something went wrong and timeout.

I can clearly see that there was an expiration error, but the root cause might be wrong arguments send to the register. The application team should have received from the other service instructions about that change.

Here you can observe both issues with the product management on the receiving end and the issue of project management on the person responsible for the integration of the solution. As well as issue exposing the underlying software implementation by observing the stack trace.


Popular posts from this blog

The messy meeting

When you know there will be a messy meeting and there is nothing you can do about it, the best thing to do is to avoid it. Messy people produce messy meetings, and they take the time and the energy of everyone who is part of it. That is why instead of being part of this drama, find a better team and better meetings to invest your precious energy.

The recovery day

 What to do once all the presents are opened? Should we just move forward with our goals? As I wrote about recovery day after flying long distance. It is important to plan a recovery day after the holidays. This is your guilty free time.

New year preparations

 I stopped preparing for things since August this year. I decided to go with the flow. With no plans for the New Year, today I received an invitation to a party. Seems like not having any plan was the best plan in the end.