We all are so stupid sometimes that we can not see significant faults in our approach and blame the system.

I have been there countless times when I blamed the architecture design, software, network and whatnot for the things not working due to my wrongdoings, some silly, stupid mistakes which killed my days.

And then, most of the time, someone came playing the role of devil's advocate, as I felt at first. Felt like my intellect was being questioned, but then I found my silly mistake. I called myself stupid, but I learnt after a few incidents that we all need someone like this around sometimes -- asking us to check if everything is correct at our end, ask us to re-verify, try to get on the call to provide a different set of an eye or work together doing peer-programming -- even though making us feel bad this whole thing for the time being.

Many times they don't get any praise. But once we cross that blocker and retrospect, we can quickly identify their help and support on a personnel level. And when you do, keep them close -- they are not enemies. Even if they can't help you several times, it saves lots of time and energy when they hit the bull eye.

So when something like this happened recently, I remembered all those heroes without the cape, who didn't mind my occasional arrogancy and helped me save lots of time and energy, and gave me this thought to write down in dairy.

#SoftwareEngineering #Coding #Programming #Team #Leadership #DevilsAdvocate #PeerProgramming

If a business analyst is not from a technical background in the project, their requirements gathering is rarely precise enough for a developer.

And if that is not precise, the development team won’t be able to choose the most fitting development approach, select the right tools, or develop the functionalities well enough to excel in the competition.

So someone from the development team should be included in outlining and finalizing projects' requirements and specifications as early as possible.

If someone says, "but these people are only skilled with programming languages and frameworks, etc.," ask them, "what do they do with those programming languages and frameworks?"

Teach/inform them about developers -- inform them that "these people develop all these features dozens of times in their mind when they see it somewhere, even though they may never have to build it in a project".

It doesn't matter how beautifully other profiles are presented at the top for discovery, requirements gathering etc. -- Developers can't be beaten with defining technical business requirements precisely as needed.

#SoftwareEngineering #Developer #BusinessAnalyst #Projects #RequirementsGathering #Management #Coding #Programming #Development #Business #Team #People #DigitalTransformation

The 5 most crucial traits of a Senior Drupal Developer:

-- Should always be curious and have great empathy for junior developers, similar to any other senior developer

-- Shouldn't miss checking the Drupal.org planet feeds even if only a few articles are worth reading; being senior And always catch up till the last visited items

-- Always try to keep track of the essential channels on Drupal and other open-source technology-related Slack/Discord as per need and be active in the community wherever involved

-- Follow all the Drupal security and Drupal as product-related social media handles, and inform the team to create tickets in advance for minor release updates

-- Keep track of technical debts and push for the time required to code and essential architecture changes on a monthly or quarterly basis

#Drupal #PHP #SeniorDeveloper #SoftwareEngineering #Career #OpenSource #Developer #Team #Technology #Community #Architecture #Security #Empathy

No regular team meetings on Friday is a very good idea for well adopted self managing teams.

#Agile #Team #ProjectManagement