Leadership Profile
Summary
The ten leadership actions taken from the role description (Define, Assess, Align, Delegate, Oversee, Authorize, Mentor, Hire, Report, Evangelize) and the evidence behind each in 2019: sessions led, words from colleagues, projects, and meeting time. Every other page carries the same actions as chips.
Key insights
Actions describe how this work was led. The evidence in the folders shows Define, Assess, Oversee, Mentor, Hire, Report, Evangelize.
They come from the role and responsibilities document (supervisory role). Every session, message, project and meeting in this report carries up to three of them. 263 of 327 meeting hours carry an action; the rest are learning, company events and untitled meetings. The tags describe the type of action, not how well it was performed.
The ten actions
choose one to see what stands behind itMentor
Coaches and teaches people and communities so capability grows beyond the team.
In the role description: Mentors team members, coaches the coaches who deliver through Philips University, and trains software people on new practices.
| Sessions led | 15 | of the 15 sessions Recorded |
| Messages and emails from colleagues | 1 | that describe this action |
| Projects | 9 | · · · |
| Meeting hours | 66 | 44 meetings, from the calendar Recorded |
Meeting time by action
Hours per month, each meeting counted once under its strongest action
Executive Summary
Summary
A one-page account of 2019: the figures that matter most (sessions led, Anytime Feedback, Viva Engage, meeting hours), the actions behind the work, and what came of it.
Key insights
In 2019 I led 15 sessions, and the work shows in what others say: 93 people answered the session feedback forms and 18 colleagues gave Anytime Feedback.
Ten leadership actions
records and hours behind eachWhat came of it
Teaching
Sessions led, by series
In the participants' words
Written comments on the feedback forms
1. Better coding standard can reduce the code duplication (or some other potential code issues) indirectly, it is an implicit gift for coding standard. 2. The value to solve code duplications is the less code, the less risks,…
1. Spend ample time in figuring the expected behaviour of the system, rather than implementing straight away 2. Only write the minimum required code for the one test case under consideration, to pass. 3. For every new behaviour…
The session helped gain knowledge on Sonarlint tool for both C# and Java. The tactics said in the session for formatting ,spacing etc. are really useful. Simple brainstorming of tools available in the market for each category…
Projects
Where the year's project work went
Colleagues' recognition
Appreciation emails and messages
In their words
“You are such an exceptional person. You gave me such positive vibes when I interacted with you for the first time. You are a good motivator. One good attitude about you is getting connected to people very fast. It's all because of your helping attitude. I remember you helped me to write a logic sitting right next to me. This is the right sign of a dedicated person. Please carry on with the same attitude and spread…”
“The three highlights of the sessions were 1) The production level coding style is very different from the Development or college coding style. 2) One needs to extends its horizons for building the full proof system. 3) Be prepared for the worst case scenario for system failure and make sure your system is smart enough to handle it.”
Learning & Enablement Delivery
Summary
Every training session the folders show Datta delivering in 2019, and the .connect sessions from his record: its date, series, channel, how many people took part where a roster or screenshot says so, and what the participants answered afterwards.
Key insights
The year in sessions
one dot per session, by seriesSeries
Sessions led, with the answers to the feedback forms Recorded
| Series | Sessions | First | Last | Responses | Average |
|---|---|---|---|---|---|
| SWCoE hands-on workshops | 2 | 4 Jul | 9 Sept | ||
| JSCPD code duplication programme | 2 | 23 Sept | 7 Nov | ||
| Java Best Practices | 1 | 1 Feb | 1 Feb | ||
| Interview knowledge sharing | 1 | 17 Apr | 17 Apr | ||
| Crafting Code Quality | 1 | 11 Jul | 11 Jul | 14 | 8.93 |
| SWCoE technical workshops (Simao visit to Bangalore) | 1 | 1 Aug | 1 Aug | ||
| Tech debt awareness | 1 | 8 Aug | 8 Aug | ||
| New-hire onboarding | 1 | 19 Aug | 19 Aug | ||
| SWCoE talks | 1 | 11 Sept | 11 Sept | ||
| Clean Code initiative, 25 to 26 Sep 2019 | 1 | 25 Sept | 25 Sept | ||
| .share | 1 | 26 Sept | 26 Sept | ||
| Hands-on mentoring | 1 | 14 Oct | 14 Oct | ||
| Monthly SW community call | 1 | 15 Oct | 15 Oct |
How participants scored the sessions
93 responses to "how likely are you to recommend this session", 0 to 10
Every session
15 sessions, with the folder each comes from| Date | Session | Channel | People | Responses | Average | NPS |
|---|---|---|---|---|---|---|
| 1 Feb 2019 | Java Best Practices | Internal session (channel not stated) | 24 | |||
| 17 Apr 2019 | How to conduct interviews - knowledge sharing session | Internal session (channel not stated) | 17 | |||
| 4 Jul 2019 | Unit testing workshop | In-person or online workshop; channel not stated | ||||
| 11 Jul 2019 | CQC - Tooling for quality (Crafting Code Quality) | Internal workshop (channel not stated) | 22 | 14 | 8.93 | |
| 1 Aug 2019 | Test-driven development and clean-code practices workshop | In-person workshop, Bangalore | 16 | 8.12 | 38 | |
| 8 Aug 2019 | Tech Debt: What does that mean? | Session for PHDSI (channel not stated) | 16 | 4 | 8.25 | 50 |
| 19 Aug 2019 | New-hire clean code environment setup | Workshop for new hires (channel not stated) | 27 | 24 | 9.46 | 88 |
| 9 Sept 2019 | Duplication detection and elimination workshop (jscpd) | Workshop; channel not stated | 17 | 9.12 | ||
| 11 Sept 2019 | Program Behavior Metrics: a technique to track your code behavior live | Not stated in the folder | 4 | 8 | ||
| 23 Sept 2019 | JSCPD copy-paste detection session with the EOI team | Team session for EDI-EOI (Radiology Solutions) | ||||
| 25 Sept 2019 | Code duplication identification and elimination workshop (Clean Code initiative at PIC) | In-person hands-on workshop, PIC Bangalore | 17 | |||
| 26 Sept 2019 | JSCPD, a copy-paste detector tool: an experiment (.share session) | .share session (SWCoE knowledge-sharing broadcast) | ||||
| 14 Oct 2019 | Mutation testing session with RadOnc | Team session; channel not stated | ||||
| 15 Oct 2019 | Clean code workshops: JSCPD results to the CTO extended call and October monthly call | CTO extended call / monthly call (Tuesday 15 Oct 2019) | ||||
| 7 Nov 2019 | Code duplication identification and elimination workshop, CDI China | In-person workshop, Shanghai | 15 |
People: the count on the registration roster or meeting screenshot that the folder holds, as that source states it. Responses, average and NPS come from the feedback form for that day.
The .connect sessions
from the Dattas_Dot_Connects record1,127 people engaged; the list gives the month only Recorded
52 people engaged Recorded
261 h of meetings with colleagues, 1,220 colleague-meetings; 29 set up by me Recorded
Dot-connects by month
Meetings with colleagues on Software Excellence, from my own monthly exports
By kind, led by me
| Kind | Sessions |
|---|---|
| .connect - Workshop | 1 |
| .connect- General | 1 |
| .connect - jscpd | 1 |
By city, led by me
| City | Sessions |
|---|---|
| Bangalore | 3 |
The 3 .connect sessions led by me, with the team's remarks
| Month | Kind | City | Engaged | Remarks |
|---|---|---|---|---|
| Aug 2019 | .connect - Workshop | Bangalore | 22 | TDD Training :TDD workshop & clean code practices |
| Sep 2019 | .connect- General | Bangalore | 16 | |
| Sep 2019 | .connect - jscpd | Bangalore | 14 |
Month-by-month figures
| Month | Dot-connects | Set up by me | Hours | Colleague-meetings | Different colleagues | Cities | Most frequent cities |
|---|---|---|---|---|---|---|---|
| 2019-07 | 33 | 6 | 44.0 | 194 | 164 | 6 | Eindhoven, Best, UK, Shenyang, Shanghai |
| 2019-08 | 29 | 3 | 30.3 | 175 | 124 | 3 | Alpharetta, Eindhoven |
| 2019-09 | 32 | 3 | 50.5 | 294 | 177 | 17 | Eindhoven, Best, Shanghai, Andover, Amsterdam |
| 2019-10 | 28 | 15 | 30.0 | 94 | 81 | 5 | Aachen, Shanghai, Eindhoven, Best |
| 2019-11 | 39 | 2 | 78.5 | 344 | 251 | 18 | Shanghai, Eindhoven, Shenyang, Murrysville, Haifa |
| 2019-12 | 24 | 27.5 | 119 | 98 | 8 | Hamburg, Vantaa, Fitchburg, Shanghai, Beijing |
The team list gives the month only. Sessions led by me are those whose session lead includes my name. Participants' names and email addresses are not kept.
What participants wrote
259 comments, word for wordCodeScene tool
Gating is really a good one!!
Static code analysis tool Sonar Lint and Code Scene.
CodeScene introduction
Code scene
sonar lint is very good which I can save a lot of my time as a developer. I can ask my team members to start using it which saves a lot of time for reviewers also
Codescene importance and the way which it makes code quality a high priority
CodeScene , Sonar Lint
Sonarlint tool.
Code Scene
1. Tools 2. Insights into usage of tools 3. How to leverage them
Gating tool -> SonarLint is found very helpful. And the insight that codescene is able to give is quite helpful at a little high level
Sonarlint usage at IDE level Gating mechanism Different build tools Discipline to be followed
Code scene session was awesome and most relevant.
tools
IDE level gating, writing test cases for branching also, looking into the insights of code-reviews
Static code analysis tool Sonar Lint as a gateway.
Try CodeScene
Linting, code scene
sonarlint codescene
The most important aspect of development is writing unit testcase before development that is Test driven approach .The tools which i would like to use is sonar lint, sonar qube,codescene
Linter Identifying waste/dead codes
Integrating sonarlint IDE and try to use codescene tool.
Code Scene metrics Local build gating
CodeScene for a new feature branch.
SonarLint SonarCube CodeScene
SOnarlint TICS Codescene
Code scene and SonarLint
It would be very helpful if we have a small example project with some high code smell and the potential spots where it could be refactored, which will give us a fair idea of your thought process
Yes i am interested to contact for improving few processes we follow in daily development
In addressing lot of legacy code for which we don't have any idea.
Some Process for code reviewers to save their time
A overview of security measures would help
Great Session
Excellent!!
Appreciate the knowledge sharing session.
I will get in tough with you on email .
Good session had learnt few goods things
Thanks for letting us know about these tools.
Greate session
Good knowledge about the topic and is approachable.
He is good in explaining the concepts that he wanted to explain.
Would like to appreciative his inputs towads tech debts
Thank you for the session
The session gave a good insight specially for static analysis
The presentation of the topic was good with examples.
Thanks Datta for wonderful
BDD
Making the test pass with minimilistic code
Separation on coding and test cases. Usually we would start with coding and go to test cases but this was something different
TDD
The way they explained it .was really interesting
Test Driven Development and how we have to work through a problem.
The concept of tdd. We tend to jump into implementations as soon as the problem statement is given.
Test cases
BDD and clean up code tool
Use of lint and the way defects were caught earlier using TDD
Nothing was interesting, it was pretty much basic, it should be language independent when it comes to suggesting the tools,
To change in thought process while development. Shift from Implementation to TestFirst Technique
Test Driven Development Approach
The best practices discussed on the session along the lines of clean coding, developing error free code right from our local machine as well as the behaviour driven approach to problem solving were really informative
Hands-on Workshop
The initial part of the workshop that explored various test-cases/ conditions to be met for the given problem.
BDD
TDD
Cucumber Starting with test case and go to coding
TDD
Think corner Case Try to implement TDD as much as possible
test driven development workflow to approach a problem
Sonar limt TDD concept and how we can simplify the thought process.
TDD
BDD,TDD,Lint
Mutation testing
We are already using all the tools , nothing new has been presented
Sonarlint Mutation testing
Test driven development approach when building new functionality
1. Spend ample time in figuring the expected behaviour of the system, rather than implementing straight away 2. Only write the minimum required code for the one test case under consideration, to pass. 3. For every new behaviour identified, which the current code does not support, have a test case that fails, and then make it pass
The tools used for automatic code analysis like adding copyright strings and so on. Writing the minimum possible code to pass a test case and write new ones as a consequence.
Increase time .it should be at least one day workshop .
Couldn't have a walk through with cucumber plugin. It would be great to have that
conducting more session with full day workshops
Please extend the workshop for other languages and not just limited to Java
Course would have been designed at least for an intermediate developer
Extend the training hours
The pace of the training could have been higher.
TDD in detail and when to go for TDD or BDD with clear example
Using microservices
Good presentation
Thank you so much Datta
Was very interactive and knowledgeable
Nothing much
Good command on the subject
Good Jod and Nice presentation
Good initiative and presented well
Please extend the workshop for other languages and not just limited to Java
All the agenda topics to be covered in detail in time
Thank You
i flet it would cover more area of Test Driven development, over all i felt it went very slow
It was a very engaging session. Thanks
Liked how you spoke in detail about the tools you use in your day-to-day work
ABout tech debt, Common pitfalls Cost of tech debt
1. Identify debts at the earliest possible phase 2. Change our behavior towards technical debt 3. Make sure not to increase the baseline value which has an impact on the cost
1. Improving code quality by have complete knowledge of acceptance criteria and the technology i am working on 2. Following best practices .. using static code analysis ever before commiting the code. 3. No last minute changes .. cause it degrades the code quality
Finding reason fro tech-debt Choosing right solution Observing the cause regularly
More of hands on. Example project or current project.
Slide3s and KT videos will be helpful
Need more examples apart from theory. Real world examples would definitely help in better visualize.
Was very interesting the way such a complex topic simplified which touched a lot of dimensions.
Well its a huge topic and cannot be covered in such a small period of time ... will suggest to have multiple sessions ... including indepth discussion on each topic
Very good session and its helpful.
The ease of mentoring and interacting with the mentees.
1)how to write clean code. 2)code analysis 3)industry level code review guidelines
1) How to write a clean code 2) How to have maven plugin
clean coding, code quality, discipline
Tools used for writing clean code, How to install them and use them.
Gating your code, using linters to enhace code quality, setting up maven to enforce the previous two
Gating mechanisms, Production code necessities, Team work
Proxy, gating mechanisms and practical implementation of tiny urls
clean code practices and that reviews regarding indentation cause waste of time during actual code review
Gating Mechanism for coding, force coding standards, be able to switch and use coding standards
how to ensure clean code practice and multiple plugins that helps us ensure this.
lint functionality, installation and clean code setup
1) Resolve warnings and errors before they propagate further.2) Use appropriate tools before code review 3) Give a cleaner code for code review
Code gating, IDE configuration, Plugins & Extensions
1. How to use sonarLint. 2. how to remove warnings 3. how to read and remove the errors
1) Dire need of clean code 2) Don't ignore warnings 3)Importance of following indentation and analysing it
1.The extension will be present on almost all ides 2.pom must be changed with addition of dependency 3.vs code extension
using productivity tools
1. how to write a clean code 2. how to optimize the time required for coding 3. explored a lot of new things in eclipse IDE
Code optimization(Indention), Maven project building, setting up network proxy
The need for writing clean code and how to do the same.
linter, code formating and how to maintain a clean-code
learned how to add new tools in eclipse and vscode
how to use productivity tool to make our code clean, better and more readable.
I believe his sessions are objectively perfect.
very responsive
He approached everyone indivisually to solve their doubts
highly approachable
He makes everyone comfortable around him and overall he is approachable. So it makes easy to raise doubts and get them cleared without any hesitation
more depth to what we are doing can be added
Very polite and articulate, can follow his dialogue and steps very easily
He is good in guidings. Appreciated.
The style of teaching is appreciable. The choice of words give clearity about the subject.
We was quick at problem solving
Datta is very helpful and approachable.
He was prompt and was approachable to solve problems we faced.
No comments
He is good with his Skills. So no suggestions
He gives equal attention to everybody and solve everybody's problem/doubts before moving further.
Understand how to reduce code duplication
Simplify and make the code readable as much as possible.
Code duplicates between test code and production code which was not realized before Duplication found in test inputs
1. Better coding standard can reduce the code duplication (or some other potential code issues) indirectly, it is an implicit gift for coding standard. 2. The value to solve code duplications is the less code, the less risks, and the less test code you need (Easy for you to achieve good code coverage). 3. Try different CPD tools to learn code duplications better.
1. Identification of code duplication can be integrated easily. 2. With a little time and effort, it can be efficiently eliminated and avoided. 3. Judicious decision making in the trade-off between code complexity and duplication.
Understanding Single Source from Various Aspect How to Map Concerns with Class / Method responsibility Different Aspect of Design that missed to thought throw, when we do refactoring the code using JSCPD tool
-- Presence of dead code that should be removed like unused files -- commented code -- we can work on removing a lot of code duplicates which will reduce the project size.
Better ways of finding duplicates codes available using JSCPD Many unknown areas of duplicate found in our legacy code base Learnt about a new tools for code analysis
JSCPD Tool is measures attributes which TICS is not measuring on code base.
Most of the duplication are in unit test area. So many classes are there which can put in common utility.
Its a very useful tool where we can get a detailed report of duplication in the code base in less amount of time.
Good to have additional insights. Tool really helped. Additionally, the benefit is that the walkthrough through the tool openly helped to make the examples discussable.
Measure code duplicates and keep a check on it
Code duplication When it is good or bad Jscpd tool which allows us to set the token number
How to use jscpd Concept of tokens Why code duplication is bad
Understood the code duplications
- Code duplication can be removed for a lot of the cases easily - Code duplication has different root causes (not only laziness) - Identify code duplication can be easy with the right tool
Could have given some already analysed code and refactored the same to reduce the duplication. after that could have gone into our specific project codes
It was perfect.
The different techniques to eliminate duplicate code can be presented before we start hands on work
Show more examples from real product about the solving of code duplications, and the value the product got.
More focus on helping to eliminate duplication. I understand this could be a challenge considering diverse languages in which code is written.
it is great workshop ..Keep going ... No Comments
Very Effective . On the basis of audience and if it makes sense then we can do some of the activities like a prerequisite for the workshop like downloading and running (if runs fine) so that we have more and more time to interact.
Full day event will further help as we can get to know other persons duplicate code area and how it was improved.
Guide more on how to do customize the Tool like - how to ignore certain file types - Currently Tool does not ignore Copy right information & using statements across the files, shows as duplicate code. This has to be excluded from the Tool.
How to exclude a block of code for analyzing.
All good
Show more options in demo to use it in code base. Improve the content and show various options available
It was Great.
Extend the time and practically help to remove the duplicates
Nothing
JSCPD tool was good to understand
The mentors did a good job and demonstrated how can we simplify the code.
Working with real code than sample examples
All mentors have very broad experience on code duplication.
It was overall well organized and coming from diverse business units, all of us were able to relate and use the tool efficiently.
Mentoring...
Awesome workshop. Things explained very nicely and the idea to use for individual projects was really helpful.
Leant new tool JSCPD for code duplication.
Very well structured way of explaining the tool and helping us in use the Tool.
how to run this on our code base.
Explainations
Datta makes discussion practicable. Well done!
Content delivery
Understanding of tokens and tics may not always be a correct metric to judge the code.
Presentation and hands on working
Hands on experience was gdd
Installation and direct analysis of my code within the time frame of the workshop
Everybody gave great pointers! Keep up the good work.
Liked the whole session with Datta . Very good at explaining the details. Helpful and very descriptive answers from [name] and [name].
Appreciate Datta for having hands on experience.
I have to appreciate Datta for detailed explanation. I have to appreciate [name] for the support.
The preseter was very nice.
Data was good
Datta did a great workshop. Perfect mindset to educate without judgement.
Key value rending
All
Metrics in application
I liked the example shown.
Add event metrics
There are many possibilities to adopt this.
Performance and CPU utilization over the time
The teams need to understand the concept.
Analyse the data
More kibana matrix
This is off topic, but the seating and air-conditioning provided by the hotel was poor.
Interaction
Demo
The audience interaction was good.
Well done
Nice explanation and awesome demo.
Good job on presentation and really appreciate the idea behind it
I congratulate you on an informative session on a lesser known topic.
There can be some more example, for each and every tools suggested to improve the code quality.
Preparation steps for C# code as well.
It was good. You can try to cover other TICS aspects(fanout, Cyclomatic complexity, Code duplication etc) in order to improve quality while implementation itself.
Half of the time went in configuring for c# and Java people separately. May be if we can reduce the time in that and come up with more tools in improving the code quality
SonarLint code improvement suggestions were really good.
By using some volunteers to help the audience.
Can be more content to discuss.
More hands on, with sample programs given in a folder could have brought more clarity
More topics could have been included.
More tips for would have been better.
Overall session was useful. I hope we can conduct separate sessions for .net and Java so that we can save the time in Session.
The demo and explanations are very clear for the topics covered.
It provided us with foundation knowledge on the tools available which could be used effectively to maximize productivity.
Knowledge transfer, Significance of the eclipse plugins and how it can help to improve productivity and quality.
Hands on was really good. overall the presentation was very useful.
The session helped gain knowledge on Sonarlint tool for both C# and Java. The tactics said in the session for formatting ,spacing etc. are really useful. Simple brainstorming of tools available in the market for each category and also tools inside Philips was good
I already knew about Sonarlint and I got the information regarding that
Its good to learn new tools like Sonarlint and how to use that for improving code quality and saving overall development time.
SonarLint code improvement suggestions were really good.
software intro
Detailed Guidance during the session, Clear and Crisp acknowledgement of asked questions.
The way of presentation
Hands on session was great.
Plugins for making it easy to write effective code
Good to know about some tools available for us to improve the code quality.
Not for now.
Yes.
Yes, for security enhancement topics.
yes.
Yes
Not now but in future based on the project requirement, will connect with SCoE team.
Sure.
not for now
New to Project/Org. So yet to explore.
As of now NO
Yes. I want to be part of SCoE for future topics. Thanks
Anytime Feedback & Session Feedback
Summary
What other people said about the work in 2019: Anytime Feedback from 18 colleagues, answers to session feedback forms, emails and Viva Engage comments of thanks, and chat messages kept as screenshots.
Key insights
Everyone who gave Anytime Feedback
18 respondents| # | From | Role and place | When | Words |
|---|---|---|---|---|
| 1 | Anonymous respondent | Software, Intelligent Device Management, India | 2019-10-04 | 326 |
| 2 | Anonymous respondent | Software II, HSDP-IAM, India | 2019-10-08 | 260 |
| 3 | Anonymous respondent | Software II, Radonc, India | 2019-10-14 | 320 |
| 4 | Anonymous respondent | 2019-07-26 | 80 | |
| 5 | Anonymous respondent | 2019-07-26 | 70 | |
| 6 | Anonymous respondent | 2019-07-26 | 38 | |
| 7 | Anonymous respondent | 2019-07-26 | 39 | |
| 8 | Anonymous respondent | 2019-07-26 | 44 | |
| 9 | Anonymous respondent | 2019-07-26 | 41 | |
| 10 | Anonymous respondent | 2019-07-26 | 78 | |
| 11 | Anonymous respondent | 2019-07-26 | 78 | |
| 12 | Anonymous respondent | 2019-07-26 | 41 | |
| 13 | Anonymous respondent | 2019-07-26 | 49 | |
| 14 | Anonymous respondent | 2019-07-26 | 59 | |
| 15 | Anonymous respondent | 2019-07-26 | 29 | |
| 16 | Anonymous respondent | 2019-07-26 | 58 | |
| 17 | Anonymous respondent | 2019-07-26 | 71 | |
| 18 | Anonymous respondent | 2019-07-26 | 50 |
Anytime Feedback
18 colleagues repliedWhat colleagues wrote
word for word“You are such an exceptional person. You gave me such positive vibes when I interacted with you for the first time. You are a good motivator. One good attitude about you is getting connected to people very fast. It's all because of your helping attitude. I remember you helped me to write a logic sitting right next to me. This is the right sign of a dedicated person. Please carry on with the same attitude and spread more knowledge.”
“I liked the way Datta was trying to provide each small detail which will be useful for my team.”
To improve: I liked the way Datta was trying to provide each small detail which will be useful for my team.
“Helped us in brainstorming logging and usage of metrics for product development. On the similar lines, he helped us in getting us details of POCO framework being used within philips or not”
To improve: Helped us in brainstorming logging and usage of metrics for product development. On the similar lines, he helped us in getting us details of POCO framework being used within philips or not
“The three highlights of the sessions were 1) The production level coding style is very different from the Development or college coding style. 2) One needs to extends its horizons for building the full proof system. 3) Be prepared for the worst case scenario for system failure and make sure your system is smart enough to handle it.”
“1.code modularity, 2. writing the code in a clean way. 3. I also learned a lot of new tools that can make day to day task easy. I think Datta tried to share all the necessary and his additional knowledge pool with us that was of great help.”
“Learned how useful tools can be and we do not reinvent the wheel again and again”
“Don't hesitate to ask questions, Better to ask first, Understand and work with real-life scenario in mind”
“(1)Approaching the problem statement (2)Evaluating pros and cons and selecting one from potential solutions (3)Relating the problem statement to real world scenatio”
“to think in more than one way of solving a problem, to take decisions based on pros and cons”
“I would like to appreciate the fact that I was given the room to think in my own space. It helped me to fork my ideas and explore more paths to generate better code. At a single time, a lot of new ideas creates a slight chaos and sometimes prevents us from reaching mandatory goals.”
“1. Datta was very approachable during the training and i appreciate the time and effort he has put in to give insights into project, he helped us realize other aspects of project as well .Also,he empowered us to to think in more than one way and gave us complete flexibility to choose between the options”
“our mentor is always full of ideas and ready with alternatives , encouraged us to explore different aspects”
“I appreciate the choices Datta gave us on each level. To discuss on the pros and cons on each option and select the best viable option.”
“Liked how he introduces many different approach with pros and cons and still make us think and choose the approach instead of straight away telling the best possible solution and refraining us to think other ways”
“Appreciate:: Approachable, Ability to resolve problems”
“In all our discussions, Datta would always stop and make sure we were understanding and would clear the doubts we had.”
“1) Consistently reviewing the work and suggesting better solution alternatives making learning for us interesting and challenging 2)Treating all of us as equal in the team and encouraging each of us 3)Taught team etiquettes”
“He gave us the Ownership and choices to choose to do the Task”
Ratings about Datta
from the Dattas_Dot_Connects recordFeedback to Datta - interaction feedback form (Oct 2019)
3 respondents Recorded
| Item | Answers | Mean | Scale |
|---|---|---|---|
| Helpfulness of interaction | 3 | 9.33 | 1-10 |
| Philips behaviour item 1 of 5 (name not in export) | 1 | 5 | 1-5 |
| Philips behaviour item 2 of 5 (name not in export) | 2 | 5 | 1-5 |
| Philips behaviour item 3 of 5 (name not in export) | 1 | 5 | 1-5 |
| Philips behaviour item 4 of 5 (name not in export) | 3 | 5 | 1-5 |
| Philips behaviour item 5 of 5 (name not in export) | 1 | 5 | 1-5 |
| Likelihood to recommend Datta | 3 | 9.67 |
Session feedback
93 responses, average 8.91, NPS 67Every comment is on the page, by series.
Viva Engage
every post and comment from the all-activity page, 2019seen 988 times across communities Recorded
seen 486 times; not added to my own posts' figure
on 13 threads
My posts
A post shared to several communities is one row; its views are the sum across them
| Date | Post | Actions | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|---|
| 2 Aug 2019 | Hello Philips Open Source Software Team, I was going through the yammer and landed here. The link to… | Philips Open Source Software | 80 | 1 | ||
| 2 Aug 2019 | Hey guys! | Philips InnerSource | 54 | 4 | 1 | |
| 7 Aug 2019 | Came across this article when I was reading through my feed content:… | the engineering group Software Engineering… | 207 | 2 | 9 | |
| 16 Sept 2019 | Is innersource down? I am not able to access the portal via link:… | Philips InnerSource | 53 | 1 | ||
| 19 Sept 2019 | Nicely articulated Kiran! | Everyone at Philips | 306 | 1 | 1 | |
| 18 Oct 2019 | Hello Everyone, | the engineering group Software Engineering… | 129 | |||
| 3 Dec 2019 | A non-tech post for a change. | the engineering group Software Engineering… | 159 | 2 |
Posts by others that feature the work
| Date | Post | Actions | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|---|
| 9 Aug 2019 | Kiran: I feel that my Friday morning was energized after attending Datta's session on meaning and interpretation of… | the engineering group Software Engineering… | 133 | 4 | 2 | |
| 20 Aug 2019 | Meghana: We make heavy use of PowerMock in many of our JUnit tests. However , For the code that is unit tested with… | the engineering group Software Engineering… | 184 | 4 | 4 | |
| 3 Oct 2019 | Rajeshwar: JavaScript Copy Paste Detector Tool & My Experience | the engineering group Software Engineering… | 169 | 4 | 3 |
Posts by others where I commented
| Date | Post | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|
| 6 May 2019 | Sundaresan: Philips SW Center of Excellence organized the | PIC Bangalore + 1 more | 24 | 4 | 2 |
| 6 May 2019 | Andrea: Hi all | Multi-Factor Authentication… | 6 | 3 | |
| 13 Aug 2019 | Rodolfo: https://martinfowler.com/books/refactoring.html | the engineering group Software Engineering… | 217 | 9 | |
| 4 Nov 2019 | Rodolfo: Does your team have an Observability strategy? | the engineering group Software Engineering… | 277 | 2 | 3 |
| 29 Nov 2019 | David: Is anybody out there using SonarQube for C++ in production? I have references for Java, C# or JavaScript but… | the engineering group Software Engineering… | 306 | 9 | |
| 9 Dec 2019 | Chuck: Can anyone share their experience using TIOBE's TICS IDE plugins? My primary interest would be C/C++… | the engineering group Software Engineering… | 279 | 1 | 2 |
Capacity & Time Investment
Summary
Where meeting time with colleagues went in 2019, from Datta's own monthly exports: 327 hours of meetings, which leadership actions they served and how the weeks were shaped. The exports are meetings with colleagues, not the whole calendar.
Key insights
Meetings with colleagues in numbers
1 Jan 2019 to 31 Dec 2019 · from my own monthly exports233 meetings, 1.3 h per weekday across 261 weekdays Recorded
15 days had 6 h or more; hours are summed, overlaps are not removed
Meeting time by leadership action
each meeting counted once, under its strongest actionHours by action
From the meeting title and kind; 65 h in 72 meetings carry no action Estimate
Month by month
Meeting hours per month, by action
Every weekday
hours of meetings per dayBy kind of meeting
Hours by kind, grouped by words in the title Estimate
Month by month
Meeting hours per month, by kind
By weekday
Hours of meetings, Monday to Friday
Largest recurring meetings
Meetings that came back three or more times; individual and small-group meetings are not listed
| Meeting | Times | Hours |
|---|---|---|
| 2019 Q4 : .craft year end assessment - Minimum - MR | 7 | 10.5 |
| Knowledge sharing session | 6 | 6.0 |
How this was counted
meetings with colleagues, not the whole calendarSource: Datta's own monthly exports of meetings with colleagues (dot-connects, plus other meetings listed in the 2021 exports). They are not the whole calendar.
The exports hold a date and a length but no start time, so there is no hour-of-day, overlap or time-zone analysis; booked hours are the sum of the meetings' lengths.
A meeting is one date and subject. Days are weekdays; leave and holidays are not known, so working days are all weekdays of the year.
January to June 2019 come from a combined workbook and hold far fewer meetings per month (4 to 11) than July to December (24 to 39) from the monthly exports; read the first half as partial.
Participants' names, emails and managers are not kept; the exports' organiser is reduced to me, the team account or someone else.
Project Details
Summary
The projects and areas of work in 2019 whose folders show what Datta did: what each one is, when it ran, the leadership actions it shows, and a page for each with facts and figures taken from the documents.
Key insights
The year, project by project
18 projectsEach project
Project pages
choose a project to open its pageCode Live technical-challenge clinics (Jul and Sep 2019) and the mutation testing session with RadOnc (Oct 2019)
Jul 2019 to Oct 2019Code Live is a SWCoE format where a team brings a technical challenge from its own code and experts work on it with them. The July folder holds the challenge submission template; the September folder holds feedback from a session. The October folder holds a survey from a mutation testing exercise with a RadOnc Python team, where Datta and a colleague mentored.
What Datta did
- The mutation-testing survey names Datta (with Brijesh) as the mentors for the session.
- A RadOnc participant writes that Datta and Brijesh gave support and guidance throughout the session.
- The Code Live challenge template carries a worked example filled in under Datta's name as team member (a template example, not a real submission).
Figures
Facts from the documents
- The Code Live template asks for the challenge description, category, pain points, how they are measured, expected outcome, business value, solutions tried and a suggested expert.
- The template's worked example is a monolith file with crucial business logic that is prone to bugs, with measures such as line count, coverage, regression time and compiler warnings.
- A Do's and Don'ts sheet says tool development, library development, third-party tool problems and regular programme backlog are outside the Code Live scope.
- The Sept Code Live feedback came from participants in HSDP, PSI2M, ICAP and PM business units using C#, Java and others.
- Participants named takeaways such as a strategy for unit testing static methods and increasing unit test coverage of legacy code.
- Improvement requests for Code Live: make it more organised and interactive, and give better information on each workshop so people can choose.
- The mutation testing survey recorded a Python library run with Mutmut: install under 2 minutes, run about 20 minutes, 90 test cases, 955 mutants of which 824 were killed and 131 escaped.
- After a commit the participant killed 2 more mutants, leaving 129, and said the tool added effectiveness to the unit tests.
- The participant answered Yes to using mutation testing again and rated the mentoring 10 out of 10 on recommending it.
In colleagues' words
“Dutta and Brijesh provided support and guidance throughout the session.”