Stop me if you heard this one before: “agile has too many meetings“. This is the most common complaint for teams adopting scrum or other similar agile methods. Developers feel that they are wasting their time instead of “doing stuff”.
I could make a post with the perfect tone mix of “amusingly angry” and “cynical tech guy” on how no one ever reads the manual, but this is not about making a point on how clever “we” are versus how
I’ve always found that, when interviewing someone for a technical position, the round of time talking about actual technical knowledge is the one taking the smallest fragment of the conversation. And this is because all technology can be learnt with
I’ve heard many times the statement “technical guys talk another completely different language” after a demo meeting. And although it’s usually passed on as a joke between folks outside the development chain, it reflects the lack of connection to those
Manual processes and authorization bottlenecks tend to become the proverbial nail in the coffin when automatization initiatives are adopted. The refusal to bypass these old-fashioned control gates can doom the project, so let’s review the reasons that can lead this
Allow me to start this post quoting the first principle of the Agile Manifesto: “[We value more] Individual and interactions over processes and tools“. The aim of this postulate was to benefit human exchange and improve communication between workers rather
You know what’s wrong with your development or integration environment? That, most probably, is “broken”. Meaning that a component isn’t working as intended, or a dependency wasn’t upgraded to the required version, or maybe a legacy application still in production
Thinking outside the box, as a skill, can help solving issues in a non-conventional way… Unless the basis for your lateral thought process involves a spreadsheet. So far in my career, I’ve witnessed this application being used as an ALM,
One of the most difficult security business rules to enforce in companies is the “mandatory lock account” when you are not in front of your computer. Entering your credentials over and over again is seen as a waste of time.
Software factory defines a paradigm of development that mimics a production line factory. Each component is processed as a physical product, adapted, assembled and configured to make a whole item with a specific purpose. However, I am going to refer