I consider myself to be a very logical person. I tend to favor practicality to aesthetics. I feel like this lends itself well to being a developer. I think that logic is seen as a key trait when looking for a developer. I agree, a big part of being a good developer is about being able to think through a problem logically and come to a conclusion that will solve the problem. I think that one thing that separates really good developers is that they have at least some amount of creativity. Logic allows them to see the problem and work through how to best solve it given their past experience and knowledge. Creativity allows them to see a problem differently and come to a solution by seeing how things can work in a way that they have not done before. Creativity allows for connecting ideas not previously used together to creates something new. If you want to improve yourself as a developer, I would suggest that you do something creative outside of work. Expand what you do and gain new ex
Teams can spend a lot of time in meetings. Most meetings are held with good intentions and can lead to the desired outcome. However, I think most people would agree that they spend more time in meetings than they would like. I believe that the main reason for this is that too often a meeting is scheduled without having a clear plan or goal for the meeting. The thinking seems to be that there is a problem that needs to be addressed so if we gather everyone together we can figure it out. Teams work to plan and organize their work before actually starting the work, so why would we think that putting together a meeting without preparing for it would lead to positive outcomes? I think that a little work before a meeting is scheduled could go a long way to make meetings more engaging and leave the attendees feeling like it was worth their time. Introducing the SOLID meeting Developers use a mnemonic, SOLID , for describing how to structure good code. Using these same letters with d