We are problem solvers...with software.
Everyday we go to work to address some issues, solve problems, somebody else's problems, but that's our job....that's what we do best.
Every problem has multiple solutions, different algorithms, different constructs, different frameworks...and usually similar results.
Some solutions are better than others, so there is always a challenge to choose the best solution... you never know which road to take.
Some of us are more conservative and others are more open to new and keeping things in balance is hard work, requires attention and care...so how do you do it?
If I need to make a change I ask myself these questions:
- am I satisfied with this change? did I give my best in doing the change?
- is this covering and solving every (or most of the) use-case?
- will someone be able to understand and maintain this in a year from now?
On a crossroads of deciding for a framework / technology I consider the following:
- do I understand the new fwk/technology enough to develop in/on top of it?
- will this technology be alive in 2 years (if the project lives at least that long)?
- how much experience does the team have (in case you work in a team) in that fwk/technology? can we learn fast enough?
- do you have a solution in case something goes wrong due to the fwk/technology? how fast can you act?
- is this an exclusive technology or can be used in combination with others?
Jumping to the shiniest, new thing, trending these days, might be fun but will it always benefit us?
...or you will just work fancier...so that you can add this to your CV?
Should I make selfish decisions or always comply with the project?
There is always another way...and people will sometimes force you to accept their solution (because it's shiny or because everyone does it like that, or just because they said so), but you can always say no.
Trust your gut, and if that does not give an answer ask yourself some questions, make a decision and take responsibility for it.
No comments:
Post a Comment