DEV Community: Armando Rogério Brandão Guimarães Junior

Drinking straight from the source with DX.

Armando Rogério Brandão Guimarães Junior — Mon, 28 Aug 2023 11:30:00 +0000

Hey guys! Are you all right?

Today I’m going to write about an important aspect, but often overlooked, to have a good DX for internal collaborators: direct feedback from customers.
Customer feedback is essential to understanding the needs, problems, and expectations of end users of the products and services we develop. It helps us validate our hypotheses, prioritize features, fix bugs, and improve the quality of our work.
But how to get that feedback efficiently and effectively? There are several ways to do this, but I’ll highlight three that I find especially useful:

Satisfaction surveys: these are questionnaires that we may periodically send to customers to measure their level of satisfaction with our products and services. We may use tools such as Microsoft Forms, Google Forms, or SurveyMonkey to create and analyze these surveys. They allow us to obtain quantitative and qualitative data on customer perceptions.
Customer interviews: these are individual or group conversations that we can conduct with customers to explore their opinions, feelings, and experiences with our products and services in more depth. We can use tools like Teams, Zoom, or Google Meetings to conduct these interviews. They allow us to gain deeper and more detailed insights into customer needs and issues.
Usability tests: these are sessions in which we observe customers using our products and services in real or simulated scenarios. We can use tools like UserTesting or Lookback to record and analyze these tests. They allow us to evaluate the usability, accessibility, and functionality of our products and services.

These are some of the ways to get direct feedback from customers to have a good DX for internal collaborators. I hope you enjoyed this article and that you can apply these tips in your daily life.
Do you have more tips on how we can bring the development team closer to end users to get direct feedback from the source? Comment below. 😉

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

DX ❤️ Error Culture

Armando Rogério Brandão Guimarães Junior — Mon, 21 Aug 2023 11:30:00 +0000

Hey guys! Are you all right?

Today I’m going to talk about a very (perhaps the most) important aspect of having a good DX for internal collaborators: the freedom to fail and experiment.
When we are developing a product or service, it is natural that not everything goes as planned. Sometimes we make mistakes, encounter bugs, experience technical difficulties, or simply fail to achieve the expected results. This is part of the continuous learning and improvement process.
But how do we deal with these failures? Do they discourage us or motivate us to try again? Do they make us feel guilty or curious? Do they stop us from innovating or encourage us to explore new possibilities?
The answer to these questions depends a lot on the culture of the company and the team in which we work. If we have a culture that values experimentation, creativity, and constructive feedback, we can view mistakes as opportunities for growth and learning. We can test innovative ideas, tools, and methodologies without fear of being judged or punished. We can share our experiences with colleagues and learn from each other.
On the other hand, if we have a culture that prioritizes perfection, conformity, and control, we may be afraid of making mistakes and stepping out of our comfort zone. We can get stuck with old and outdated solutions for fear of risking something new. We may hide our problems and difficulties from others out of shame or pride.
This cultural difference can have a big impact on the Developer Experience of internal collaborators. If we want to have an engaged, productive, and innovative team, we need to create an environment that encourages the freedom to fail and experiment. We need to trust our developers’ ability to solve problems and overcome challenges. We need to recognize their efforts and celebrate their successes.
And you? What is your company culture like regarding error and experimentation? Are you free to fail and experiment? Tell me in the comments!
Hope you enjoyed this article.

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

Even in DX self-service is good!

Armando Rogério Brandão Guimarães Junior — Mon, 14 Aug 2023 11:30:00 +0000

Hey guys! Are you all right?

Today I’m going to write about an especially important topic to have a good DX for internal collaborators: Self-service DevOps workflows.
What are Self-Service DevOps Workflows? These are automated processes that allow developers to build, test, and deploy their own applications without relying on external teams or complex tools. This means more autonomy, agility, and quality for projects.
Why are Self-Service DevOps Workflows Important for DX? Because they reduce lead time, rework, and human errors. They also increase satisfaction, trust, and collaboration across teams. With self-service DevOps Workflows, developers can focus on what they do best: creating amazing solutions for end users.
How to implement self-service DevOps Workflows in your company? There are some best practices that can help with this task:

Define clear standards and requirements for applications.
Create reusable templates and templates to make it easy to get started on projects.
Use integrated and automated tools to manage the application lifecycle.
Establish continuous feedback and monitoring of results.
Foster a culture of learning and continuous improvement. Hope you enjoyed this article. If you want to know more about Developer Experience and how to improve it in your company, stay tuned for the next articles.

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

Focus time on DX is VIP!

Armando Rogério Brandão Guimarães Junior — Mon, 07 Aug 2023 11:30:00 +0000

Hey guys! Are you all right?

Today I want to talk about a particularly important aspect of having a good DX for internal collaborators: having focus time to get the job done.
Do you ever feel overwhelmed with so many meetings, emails, messages, and other distractions that keep you from focusing on your code? I know I already. And this repeatedly negatively affected my productivity, creativity, and satisfaction with my work.
That’s why I think it’s essential to create dedicated development time slots where you can isolate yourself from interruptions and immerse yourself in your task. This will help you solve more complex problems, write better code, and deliver value faster.
But how to do this in practice? Here are some tips I use and recommend:

Plan your week and day in advance and block out periods of at least an hour for coding. AVOID scheduling meetings or appointments at these times.
Communicate to your colleagues and managers that you are in focus mode and ask not to be interrupted. You can use tools like Slack, Teams, or Meet to flag your status and mute notifications.
Choose a quiet and comfortable environment to work in. If possible, use noise-canceling headphones or music (which focuses you) to drown out outside sounds.
Set a clear and specific goal for each focus session. For example: “Implement feature X” or “Fix bug Y”. This will give you a sense of direction and motivation.
Take regular breaks between focus sessions. Take the opportunity to stretch your body, drink water, breathe fresh air, or talk to someone. This will help you relax and recharge. I hope these tips are useful for you. I guarantee having focus time to get the job done is one of the best things you can do for your DX. And you, how do you focus on your code? Share in the comments!

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

Challenges and Opportunities with DX

Armando Rogério Brandão Guimarães Junior — Mon, 31 Jul 2023 11:30:00 +0000

Hey guys! Are you all right?

I am happy to share with you another article about DX (Developer Experience). In this article, I’m going to talk about the technical challenges and growth opportunities that can be faced in delivering good DX to internal collaborators.
As you know, DX is the way development teams interact with the company’s tools, processes, and culture, and I’ve said it before, but it bears repeating, DX is not only important for end users of products and services but also for the development teams themselves! Good internal DX means that development teams can work efficiently, creatively, and collaboratively, using the best tools and practices available. It can increase the productivity, quality, and satisfaction of development teams so they can solve their problems quickly, easily, and in a fun way. But how can we achieve good DX for internal collaborators?
But what are the technical challenges that need to be overcome to achieve good indoor DX? Well, the ones I remember now are:

Maintain consistency and compatibility between the different systems and platforms that exist
Ensure that our code is readable, testable, and following good programming practices.
Keep documentation up-to-date and accessible
Ensuring code and data quality and security
Integrate different systems and technologies, using automation and monitoring tools
Automate and streamline development, deployment, and monitoring processes
Resolve bugs and issues quickly
Scale infrastructure and resources
Facilitate communication and feedback between the development team and other stakeholders

To overcome these challenges, we must seek opportunities for personal and professional growth, which is why it is necessary to:

A culture of collaboration, feedback, and ideas
An agile and flexible methodology
A modular and scalable architecture
A diverse and qualified team
A continuous learning mindset
Learn innovative technologies and methodologies
Improve our communication and collaboration skills
Solve complex and creative problems
Participate in online courses, workshops, and events
Seek mentorship and coaching from more experienced professionals
Ask my internal collaborators for feedback and suggestions

These are also some of the growth opportunities we must improve our internal DX. By doing this, we not only benefit our internal employees but also our external customers.
I hope you enjoyed this article on DX. If you have any questions or comments, please leave them below.

Hope you enjoyed this article.

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

Recognition and Reward

Armando Rogério Brandão Guimarães Junior — Mon, 24 Jul 2023 11:30:00 +0000

Hey guys! Are you all right?

Here I am with another article about DX, that is, the digital transformation that allows organizations to become more innovative and competitive. Today I want to talk about an especially important aspect of DX: the recognition and reward for having a good Developer Experience (DX) for internal contributors.
Did you know that the people involved in the development team are the main agents of DX? They are responsible for creating digital solutions that meet customer and business needs. Therefore, it is essential that they feel motivated, valued, and engaged with the company’s culture.
But how to do it? How to recognize and reward developers effectively and cost-effectively? Write it down because here are some tips:

Give frequent and constructive feedback. People on the development team need to know if they are doing a good job, what their strengths and weaknesses are, and how they can improve. In addition, positive feedback increases the professionals’ self-esteem and confidence, but whenever necessary, also give constructive feedback!
Provide opportunities for learning and growth. People on the development team are curious and like to update themselves on innovative technologies and market trends. Therefore, encourage them to participate in courses, events, webinars, podcasts, and other sources of knowledge. Also, create spaces for them to share their ideas and experiences with other colleagues.
Recognize efforts and results. People on the development team work hard to deliver quality projects, often under pressure and tight deadlines. Therefore, it is important to recognize the value of your work, whether through public or private praise, symbolic or financial awards, or simply a SINCERE thank you.
Create a pleasant and fun work environment. People on the development team spend many hours in front of the computer, which can lead to stress and fatigue. Therefore, it is important to create a work environment that favors the physical and mental well-being of professionals. Some ideas are: offering regular breaks, providing healthy snacks, promoting playful or social activities (such as games or happy hours), and decorating the space with vibrant colors or creative elements.

These are some simple but effective ways to recognize and reward your company’s in-house developers. Remember: good DX doesn’t depend only on technology, but also on the people who make it happen!

Hope you enjoyed this article.

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

DX, responsible autonomy!

Armando Rogério Brandão Guimarães Junior — Mon, 17 Jul 2023 11:30:00 +0000

Hey guys! Are you all right?

Today I’m going to talk about an important aspect of having a good DX for internal employees: autonomy and responsibility.
Autonomy means being free to choose the tools, methodologies, and processes that best suit your needs and preferences. Responsibility means assuming the consequences of your choices and delivering quality results.
Having autonomy and responsibility is essential to having a good DX because it allows you to work with more efficiency, creativity, and satisfaction. You don’t have to rely on bureaucracy, approvals, or restrictions that can disrupt your workflow. You can use the most appropriate technologies to solve the problems you face. You can try innovative solutions and learn from your mistakes. You can feel more motivated and engaged with your work.
But how to achieve autonomy and responsibility in your company without creating chaos? Write it down so you don’t forget:

Communicate with your team and your managers about your expectations, goals, and challenges. Align your priorities and goals with those of the organization.
Seek constant feedback on your performance and that of your projects. Take advantage of opportunities for improvement and recognition.
Demonstrate proactivity, initiative, and commitment to your work. Show that you can make sound decisions and solving problems independently.
Respect deadlines, quality standards, and good development practices. Make sure your code is readable, testable, and documented.
Collaborate with your colleagues, share knowledge, and contribute to team growth. Learn from the experiences of others and offer help when needed.

By following these tips, you can gain more autonomy and responsibility in your company and have a better DX for internal employees.

Hope you enjoyed this article!

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

DX executed correctly Continuous Learning

Armando Rogério Brandão Guimarães Junior — Mon, 10 Jul 2023 11:30:00 +0000

Hey guys! Are you all right?

Today I want to share with you a little about the culture of continuous learning (you may have heard it called Lifelong Learning) and knowledge sharing that DX proposes. This culture is essential for creating innovative and high-quality solutions for customers and users.
What is continuous learning? It is the ability to always be looking for new knowledge and skills, whether through courses, books, podcasts, articles, or other sources. It is also being open to receiving feedback and learning from mistakes and successes.
What is knowledge sharing? It is the practice of disseminating what we have learned with our colleagues, whether through lectures, workshops, mentoring, or other ways. It is also being willing to help others and clear up doubts.
Why are these two things important to Developer Experience? Because they allow us to keep up with market changes and trends, adopt best practices and tools, solve complex and challenging problems, and deliver value to our stakeholders.
How do we cultivate this culture in Sinqia? We have some rituals and initiatives that encourage us to constantly learn and share. For example:

We have channels on Teams where we share interesting links about software development, design, UX/UI, accessibility, etc.
We have periodic meetings (Guilds) on various technology topics, where a team member presents a topic relevant to our work or a personal project.
We have an internal mentoring program, where the more experienced team members help the younger ones with technical or behavioral issues.
We have a Corporate University, SinqiaUP, with several courses, for example: technical, business, and soft skills leadership. All related to our work.
We participate in external events such as conferences, meetups, and hackathons to update ourselves and expand our network of contacts.

These are some of the ways we’ve found to maintain a culture of continuous learning and knowledge sharing within our team. And you? How do you learn and share your knowledge in your work? Leave your comment below!
Hope you enjoyed this article.

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

DX and diverse collaboration!

Armando Rogério Brandão Guimarães Junior — Mon, 03 Jul 2023 11:30:00 +0000

Hey guys! Are you all right?

If you’ve read my first few articles on Developer Experience (DX), you already know what it is and why it’s important for every organization that wants to ensure the speed, quality, and retention of a good engineering team. If you haven’t read it, I recommend you do it now! 😉
In this article, I want to talk about how having a collaborative and diverse work environment can improve your DX and that of the people you have on your team. Developing software is not a solitary activity, but a team effort involving communication, feedback, and learning.
A collaborative work environment is one where development team members can share ideas, knowledge, and experiences without fear of judgment or criticism. It’s an environment where everyone feels comfortable asking for help, offering help, and learning from each other. It’s an environment where the tools and processes make it easy to work together and don’t get in the way.
A diverse work environment is one where people on the development team have diverse backgrounds, perspectives, and skills. It is an environment where everyone respects each other and values differences as sources of creativity and innovation. It is an environment where opportunities are equal for all and no one is discriminated against due to age, gender, race, sexual orientation, or any other characteristic.
Having a collaborative and diverse work environment can bring many benefits to the DX development team. For example:

It increases team motivation and satisfaction, as people feel part of a community that supports and recognizes them.
It improves code quality as people can review each other, find bugs faster, and avoid common mistakes.
It accelerates people’s learning, as they can exchange tips, recommendations, and best practices with each other.
Stimulates people’s innovation, as they can explore innovative ideas, technologies, and solutions with the support of the team.

As you can see, having a collaborative and diverse work environment can make all the difference in your DX. But how to create this environment? Well, there is no magic formula for this, but there are some practices that can help. For example:

Promote a culture of constant and constructive feedback among the development team.
Use tools that facilitate communication, documentation, and collaboration between the team.
Encourage the participation of developers in internal or external events.
Support initiatives that promote diversity and inclusion in the engineering team.

These are just a few suggestions to improve your working environment for the development team. If you have other ideas or experiences to share about this important topic for DX, please leave your comment below! I would love to hear more about your point of view!
Hope you enjoyed this article!

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

How to improve the hiring process with DX

Armando Rogério Brandão Guimarães Junior — Mon, 26 Jun 2023 11:30:00 +0000

Hey, guys! Are you all right?

In my first article, I talked about what Developer Experience (DX) is and why it is important for organizations that want to develop quality software with agility and satisfaction.
I was a little unsure where to start after that, and I remembered the story of Alice in Wonderland, when the king said, “Start at the beginning”.
And what is the beginning of the relationship between a person involved with the development and the company where he works? The hiring processes! So today, I want to share with you some ways to apply DX principles to improve your hiring process.
We know that hiring good developers is not an easy task. In addition to evaluating the candidates’ technical skills, we also need to check if they fit the company’s culture, if they have excellent communication skills, and if they are aligned with the project’s objectives and with the company’s culture. But how to do this efficiently and attractively?
One way is to use DX techniques to create a hiring process that is simple, intuitive, and fun for candidates. Thus, you can show that your company cares about the experience of developers and that it offers a favorable environment for their professional growth.
Some tips for creating a hiring process with DX are:

Use modern and popular tools among developers like Draw.io, Slack, Google Meeting, Discord, Google Jamboard etc.
Create challenges that are practical and relevant to the project, but not too long or complex.
Use whiteboards to discuss possible architectural solutions but make it clear that the person isn’t solving a problem for free for you. 😉
Avoid asking test questions, for example: Explain OOP concepts to me. Here at Sinqia we use the S.T.A.R.
Give constructive and quick feedback to candidates, showing the strengths and weaknesses of your solution.
Provide opportunities for candidates to interact with the team and learn more about the company’s product and culture.
Be transparent about the process steps, evaluation criteria and job expectations.
Put your champions, specialists, or whatever their name is, to participate in this process of assembling the technical interview and the interview itself. If you need to give them a face-lift so they can be interviewers, DO it. Technical people LOVE talking to technical people!

By following these tips, you can create a hiring process that is more effective and enjoyable for both you and candidates. In addition, you can increase the chances of finding talented and engaged developers who will add value to your project.
Hope you enjoyed this article! If you have any questions or suggestions about DX or the hiring process, please leave a comment below.

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

One step 🔙

Armando Rogério Brandão Guimarães Junior — Mon, 19 Jun 2023 11:30:00 +0000

Hey, guys! Are you all right?

Today I need to step back and clarify one thing: Developer Experience is not just about developers, but all the technical people involved with software development. This includes UX, analysts, testers, architects, designers, and others. Why is it important? Because all these professionals are part of the process of creating and delivering value to customers and end users. And if they don’t have a good experience working with the company’s tools, processes, and culture, it can negatively affect the quality, productivity, and satisfaction of the team.
As I explained in a previous post, Developer Experience for internal employees is the perception that technical professionals have when interacting with the company’s internal resources, such as systems, infrastructure, documentation, communication, and feedback. This perception can be positive or negative, depending on several factors, such as usability, performance, security, reliability, and support. The goal is to create a positive experience that makes the work of technical professionals easier and helps them deliver high-quality solutions to customers and end users.
By applying DX principles and practices, you will create a positive experience for all technical professionals involved with software development in your company. And that will bring benefits not only to them but also to customers and end users, who will receive faster, better solutions that are more in line with their needs.
I hope you enjoyed this post and that it inspired you to think about how to improve the Developer Experience for internal employees at your company. If you have any questions or suggestions, leave a comment below.

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑

Ever heard the term "Developer Experience" ?

Armando Rogério Brandão Guimarães Junior — Mon, 12 Jun 2023 20:57:52 +0000

Hey, guys! Are you all right?
In this newsletter, I will talk weekly about an especially important subject for me and for all people involved with software development: the Developer Experience (DX).
Ever heard of it? Do you know what this is?
DX (I’ll just use the acronym to make it easier 😉) is the experience that people involved with software development have when using a tool, a platform, or an API. It’s how they feel when interacting with the code, the documentation, the examples, the tests, and the support. This is how problems, doubts, and needs are resolved. This is how you learn and evolve.
DX is critical to creating quality, innovative, and scalable products. DX makes the difference between code that works and code that delights. DX is what attracts and retains top talent.
I really care a lot about the internal DX, that is, the experience of the developers themselves. I want them to feel motivated, valued, and happy. That’s why I’m sure the best companies should dedicate themselves to consistently delivering:

Collaborative and diverse work environment
Culture of continuous learning and knowledge sharing
Autonomy and responsibility
Recognition and reward
Technical challenges and growth opportunities

I believe that DX is essential for the success of any business involving application development.
And you? How’s your DX? Are you satisfied with the tools you use? Do you feel like part of an amazing team? Are you proud of your work?
Contact me if you want to know more about DX. I would love to talk to you about it!

Thank you for your attention and see you later!

Armando Guimarães Junior 🥑