<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Domenico Rizzo</title>
    <description>The latest articles on DEV Community by Domenico Rizzo (@willypuzzle).</description>
    <link>https://dev.to/willypuzzle</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F865954%2Fcf8caaf2-cb94-4a81-b605-355f5e95805e.jpeg</url>
      <title>DEV Community: Domenico Rizzo</title>
      <link>https://dev.to/willypuzzle</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/willypuzzle"/>
    <language>en</language>
    <item>
      <title>[HELP] Spring Boot: field is not set in request</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Thu, 09 Jun 2022 20:52:55 +0000</pubDate>
      <link>https://dev.to/willypuzzle/help-spring-boot-field-is-not-set-in-request-399p</link>
      <guid>https://dev.to/willypuzzle/help-spring-boot-field-is-not-set-in-request-399p</guid>
      <description>&lt;p&gt;I'm learning Spring Boot. My learning project is in this &lt;a href="https://github.com/willypuzzle/to-do-spring-application"&gt;repository github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I have &lt;a href="https://github.com/willypuzzle/to-do-spring-application/blob/main/src/main/java/com/willypuzzle/todospringapplication/controllers/todo/ToDoController.java"&gt;this controller&lt;/a&gt; where in the method createTodo I have as RequestBody &lt;a href="https://github.com/willypuzzle/to-do-spring-application/blob/main/src/main/java/com/willypuzzle/todospringapplication/dto/todo/TodoDto.java"&gt;this dto&lt;/a&gt; where I have the problem that only the field "when" is not filled properly when I make a post on that controller route.&lt;br&gt;
I tried to insert a log but I didn't succeed. I don't know why all the other field are filled and only "when" not.&lt;br&gt;
This is an example of the body to the call at such route:&lt;br&gt;
&lt;code&gt;&lt;br&gt;
{&lt;br&gt;
    "what": "Buy bread",&lt;br&gt;
    "when": "2022-06-01 19:00:00",&lt;br&gt;
    "where": "To the grocery store"&lt;br&gt;
}&lt;br&gt;
&lt;/code&gt;&lt;/p&gt;

</description>
      <category>spring</category>
      <category>learning</category>
      <category>tdo</category>
      <category>request</category>
    </item>
    <item>
      <title>Teamwork</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Fri, 27 May 2022 07:32:11 +0000</pubDate>
      <link>https://dev.to/willypuzzle/teamwork-1pp3</link>
      <guid>https://dev.to/willypuzzle/teamwork-1pp3</guid>
      <description>&lt;p&gt;There are people that think that developing is a standalone job and every developer should figure out everything on their own. But, from my point of view, these people miss an important part of a developer’s job: teamwork. In fact, when you experience real and inclusive teamwork what you learn is that teamwork is made up of continuous debating that leads to learning a lot from each other every day.&lt;/p&gt;

&lt;p&gt;Besides, there are many other aspects we should consider and learn when we come to teamwork:&lt;/p&gt;

&lt;p&gt;First, succeeding to be kind is always a good achievement and it’s not easy at all, but human relationships are very important inside teams and the price to pay for a rude contact is to ruin such kinds of relationships. Besides, there are people that say that speaking the truth can ruin relationships, but this is not totally correct. The fact is that it depends on the way you say the truth. Many times, what we lack is the ability to speak and truth (a to be assertive) in a clear and respectful way. Instead often when we come to speak the truth we became nervous and so we appear unrespectful. This is an important skill that should be learned.&lt;/p&gt;

&lt;p&gt;Second (but related to the first point), the ability to succeed inside a team lies in the ability to build strong and deep connections and relationships. And in order to reach such a goal, we need to communicate. Speaking could be a good means to communicate but it’s not the only one. What we really need in order to communicate (even though it could seem unrelated) is a sincere desire to contribute to the general wellness of the person, company, community, or institution we want to connect with. And in order to achieve such a goal we need to engage in a personal development path.&lt;/p&gt;

&lt;p&gt;At last but not least, surely teams where we land are not perfect, surely they could have a lot of flames but we should think we’re not helpless. We can give a great contribution to improving the team. I know, it’s not easy but what a team needs is dreamers and people with purpose, and if you are one of them even though you could encounter a lot of issues (they could be fixed with patience, humility, and kindness) you will succeed. On the rest, every single step, even if the smallest, is however a step towards improvement.&lt;/p&gt;

&lt;p&gt;However, we should keep in mind, that if the team doesn’t fit with us, we could leave and find another team that better fits with us. We should have always cleared our purpose and checked them against the team’s purpose but this doesn’t mean we shouldn’t give our contribution to the team we are now.&lt;/p&gt;

&lt;p&gt;Teams are made of people, and people are, in the last instance, what we should care about.&lt;/p&gt;

</description>
      <category>team</category>
      <category>people</category>
      <category>improvement</category>
    </item>
    <item>
      <title>Building a Complete Testing Framework</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Thu, 26 May 2022 11:06:27 +0000</pubDate>
      <link>https://dev.to/willypuzzle/building-a-complete-testing-framework-2bk9</link>
      <guid>https://dev.to/willypuzzle/building-a-complete-testing-framework-2bk9</guid>
      <description>&lt;p&gt;In the software lifecycle, building a test is an essential framework to enable trust in our system. It allows to pop errors out before the product goes into production.&lt;/p&gt;

&lt;p&gt;So if you have extensive coverage of your code you can be assured with certain reliability that your code is flawless.&lt;/p&gt;

&lt;p&gt;But an automatic testing framework is not enough alone. Before we put things in production we need to test manually in a staging environment. So automatic tests are necessary but are not enough.&lt;/p&gt;

&lt;p&gt;Surely, we can rely on End-to-end tests but they are hard to write and not so easy to maintain and, in the end, nothing can substitute a good human eye that makes an overall test about the new feature and checks if the system still works properly in staging and production environment.&lt;/p&gt;

&lt;p&gt;Besides, collecting the issues from the final users is the best test an application could have, because only when the application is used by whom is supposed to be used that we can check if, overall, we have done good work. And at the final instance, if our product satisfied end-user expectations and needs.&lt;/p&gt;

</description>
      <category>software</category>
      <category>testing</category>
      <category>softwarelifecycle</category>
    </item>
    <item>
      <title>Building Deep Relationships</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Thu, 26 May 2022 07:34:50 +0000</pubDate>
      <link>https://dev.to/willypuzzle/building-deep-relationships-2cop</link>
      <guid>https://dev.to/willypuzzle/building-deep-relationships-2cop</guid>
      <description>&lt;p&gt;It’s pretty fast to build relationships that stay on the surface. But surface-laying relationships are not satisfactory and leave us with a deep sense of loneliness. Besides, in order to feel connected and in order to feel that you belong to a community you have to build deep relationships. It’s not easy for many reasons and two of them are: first when you try to build a deep relationship you need to get involved, and this involvement means you have to engage with people in some way; second, when you try to build a deep relationship many people try to take advantage of you so this makes every one of us staying on the defensive, on both sides.&lt;/p&gt;

&lt;p&gt;How can we overcome such difficulties? They are very challenging.&lt;/p&gt;

&lt;p&gt;Surely, they don’t fade away overnight. We need time to build such kinds of relationships. Surely, we need to find a reason because, as formerly said, you have to get involved (and so engaged), this means you cannot build a deep relationship with everybody. The problem with this second point is that usually, you know if you would deep connection with someone only after you have just started the process (because you need some interaction time to know someone better).&lt;/p&gt;

&lt;p&gt;I don’t have a solution, everyone faces this challenge as they wish or can. On my side, the only thing I can do is to be as honest and sincere as possible. And even if this can seem simplistic in reality this is a big challenge. Because many people don’t deserve or/and aren’t able to deal with my sincerity. And I need to understand to which people I can be sincere.&lt;/p&gt;

&lt;p&gt;But when you succeed to build such kinds of relationships, it’s a great goal. Not only because great communities are deep-relationship-based communities, but mainly because that connections are very meaningful for you and you can count on them.&lt;/p&gt;

</description>
      <category>relationships</category>
      <category>community</category>
      <category>connections</category>
    </item>
    <item>
      <title>Changing is possible</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Wed, 25 May 2022 12:45:26 +0000</pubDate>
      <link>https://dev.to/willypuzzle/changing-is-possible-4e7p</link>
      <guid>https://dev.to/willypuzzle/changing-is-possible-4e7p</guid>
      <description>&lt;p&gt;Many people complain about the fact that they don’t love their job instead they hate it.&lt;/p&gt;

&lt;p&gt;I think that doing what you love is fundamental to having a happy life because we spend most of our time working. Surely, a job has ups and downs but what definitely matters is the way how you do things. If you leave space for improvement and provide the necessary rest when needed, you should have a more enjoyable experience at work.&lt;/p&gt;

&lt;p&gt;So, instead of complaining, let’s begin to actively change, remembering that every goal is reached by the smallest steps, with a combination of “should’s” and “could’s”. Changing is a long process, awareness and engagement are key values to reach it. But don’t forget to rest!&lt;/p&gt;

</description>
      <category>lifestyle</category>
    </item>
    <item>
      <title>Hard Work doesn't matter</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Tue, 24 May 2022 15:35:52 +0000</pubDate>
      <link>https://dev.to/willypuzzle/hard-work-doesnt-matter-297n</link>
      <guid>https://dev.to/willypuzzle/hard-work-doesnt-matter-297n</guid>
      <description>&lt;p&gt;When you try to build something is no matter how much time you consume to do that thing. But the matter is how efficaciously and efficiently you implement such a feature. It doesn't matter if you spend more or less time. What you build should work fastly and well. In order to achieve such a result, you don't need (necessarily) hard work but &lt;strong&gt;innovation&lt;/strong&gt; and &lt;strong&gt;creativity&lt;/strong&gt;. If you spend too much time working and so little time innovating there is something that doesn't work in your job. So innovate first, and after you will find solutions more rapidly and with less effort. Yes, of course, innovation requires time but on my own, I find more pleasure in studying new technologies and solutions than staying stuck in the old and obsolete ones.&lt;/p&gt;

&lt;p&gt;On the other hand, if you don't experiment, creatively, with other solutions, you never discover new possibilities. Besides, using creativity is a strong pusher on motivation and makes the job more enjoyable.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;In such a way you work less, with more joy and with more productivity, even though is still a job.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>innovation</category>
      <category>creativity</category>
    </item>
    <item>
      <title>To Be too harsh with yourself</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Mon, 23 May 2022 08:43:38 +0000</pubDate>
      <link>https://dev.to/willypuzzle/to-be-too-harsh-with-yourself-3j62</link>
      <guid>https://dev.to/willypuzzle/to-be-too-harsh-with-yourself-3j62</guid>
      <description>&lt;p&gt;Sometimes, I get involved in activities for not pure honest reasons. I do them because of my ego, my success, or my earnings.&lt;/p&gt;

&lt;p&gt;So, meanwhile, I declare to want to improve the world, in the fact, I'm pursuing my own interests.&lt;/p&gt;

&lt;p&gt;So, when I become aware of this aspect of my behavior then I feel unmotivated, I see myself as a liar. &lt;/p&gt;

&lt;p&gt;Then, I promise to not do it anymore but inevitably I fall into the same mistakes again and have the same unmotivate liar-base process.&lt;/p&gt;

&lt;p&gt;Does this mean I'm not improving? Of course, not. Only that the path toward improvements is not linear. We have ups and downs, We have to repeat mistakes, and above all, we have to not give up.&lt;/p&gt;

&lt;p&gt;Our genuine desires should emerge in the future and we will be revealed for what we are. And this time we should decide if to change or not and how.&lt;/p&gt;

</description>
      <category>improvement</category>
      <category>liar</category>
      <category>awareness</category>
    </item>
    <item>
      <title>Why do I like to learn?</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Mon, 23 May 2022 08:18:14 +0000</pubDate>
      <link>https://dev.to/willypuzzle/why-do-i-like-to-learn-10ph</link>
      <guid>https://dev.to/willypuzzle/why-do-i-like-to-learn-10ph</guid>
      <description>&lt;p&gt;I think I can't stop improving my knowledge. But why?&lt;/p&gt;

&lt;p&gt;Why do I need to improve, more and more if this, in fact, leads me to dissatisfaction?&lt;/p&gt;

&lt;p&gt;When do I feel satisfaction about what I know?&lt;/p&gt;

&lt;p&gt;The problem is that I always feel as if I'm at the beginning. Even though I have covered a lot of roads: it's such as my knowledge is just a little. &lt;/p&gt;

&lt;p&gt;I don't have a clear understanding of what I'm doing and the environment surrounding me.&lt;/p&gt;

&lt;p&gt;This is the problem. Is it such clearness reachable or am I confined always in the field of approximation?&lt;/p&gt;

&lt;p&gt;I think the last is the correct one.&lt;/p&gt;

&lt;p&gt;What I know is always an approximation of reality and I have to make peace with this.&lt;/p&gt;

&lt;p&gt;Improvement is always necessary but it alone is not enough. What I miss are meaningful connections. And If I don't achieve this, I will be always dissatisfied and improvement won't save me.&lt;/p&gt;

</description>
      <category>develop</category>
      <category>relationships</category>
      <category>improvement</category>
    </item>
    <item>
      <title>Why we need to discover ourselves?</title>
      <dc:creator>Domenico Rizzo</dc:creator>
      <pubDate>Sun, 22 May 2022 19:26:26 +0000</pubDate>
      <link>https://dev.to/willypuzzle/why-we-need-to-discover-ourselves-36d9</link>
      <guid>https://dev.to/willypuzzle/why-we-need-to-discover-ourselves-36d9</guid>
      <description>&lt;p&gt;Becoming a software developer means facing a lot of challenges. I think that in order to face these challenges we need motivation. Where can we find it?&lt;/p&gt;

&lt;p&gt;To have a salary is a great pusher but after years of developing is not enough: because in order to produce code we need inspiration and salary fades inspiration away after years of developing. Definitely, we need more.&lt;/p&gt;

&lt;p&gt;In order to find this "more", we need to discover ourselves, our real passion, our real motivation, and at this point understand if there is something to change in us or in our life.&lt;/p&gt;

&lt;p&gt;To proceed in the path of a software developer you should love changes, challenges, learning, problem-solving, and more but above all you need to be able to build trusting relationships. The last is not as easy as it appears. It requires a lot of soft skills that, in order to acquire them, you need to shake your being since the fundamentals. So in order to have an effective improvement, it's required to know yourself. Because if you don't know yourself, you aren't able to have an effective change of yourself. In order to change awareness of ourselves and the environment is required.&lt;/p&gt;

</description>
      <category>awareness</category>
      <category>softskills</category>
      <category>lifestyle</category>
    </item>
  </channel>
</rss>
