<?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: Ibon</title>
    <description>The latest articles on DEV Community by Ibon (@ibonkonesa).</description>
    <link>https://dev.to/ibonkonesa</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%2F498083%2F8177bef3-063f-4ea8-b3f7-0a2fd3354a0f.jpeg</url>
      <title>DEV Community: Ibon</title>
      <link>https://dev.to/ibonkonesa</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ibonkonesa"/>
    <language>en</language>
    <item>
      <title>What ports are I serving?</title>
      <dc:creator>Ibon</dc:creator>
      <pubDate>Sun, 21 Mar 2021 23:39:13 +0000</pubDate>
      <link>https://dev.to/ibonkonesa/what-ports-are-i-serving-76n</link>
      <guid>https://dev.to/ibonkonesa/what-ports-are-i-serving-76n</guid>
      <description>&lt;p&gt;Sometimes we need to know what ports are our server/pc serving.&lt;/p&gt;

&lt;p&gt;Few years ago netstat was the command that have us a clue about the ports a machine was listening to. I usually launch &lt;/p&gt;

&lt;p&gt;$ netstat -putona&lt;/p&gt;

&lt;p&gt;And we got the ports our machine is listening to. &lt;/p&gt;

&lt;p&gt;But nowadays Linux servers don't install the net-tools package and we have to use another tools. This case suggest us using ss command. ss is a tool that allow us knowing what ports are listening in our system. ss is netstat replacement and we can do many operations with this command:&lt;/p&gt;

&lt;p&gt;ss -a&lt;/p&gt;

&lt;p&gt;This command list all ports our system has opened&lt;/p&gt;

&lt;p&gt;ss -l&lt;/p&gt;

&lt;p&gt;Only returns listening ports&lt;/p&gt;

&lt;p&gt;ss -p&lt;/p&gt;

&lt;p&gt;Returns the PID of the process running a networking activity.&lt;/p&gt;

&lt;p&gt;I use ss -lt | grep "*:" to get current listening ports and check what is happening in my network.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>fullstack</category>
      <category>server</category>
    </item>
    <item>
      <title>The separation of back and front</title>
      <dc:creator>Ibon</dc:creator>
      <pubDate>Sun, 21 Mar 2021 21:31:43 +0000</pubDate>
      <link>https://dev.to/ibonkonesa/the-separation-of-back-and-front-1pnp</link>
      <guid>https://dev.to/ibonkonesa/the-separation-of-back-and-front-1pnp</guid>
      <description>&lt;p&gt;I have been reading a lot of post about PHP and wich framework is the best nowadays. Many developers said that Laravel is the winner. Other prefer Symfony or Drupal. There are a lot of reason to decide using one despite another. But I have not read nothing about the separation of backend and frontend. &lt;/p&gt;

&lt;p&gt;When I started my career we used to mix the back and the front in the same project. In my case (using Symfony) I developed a lot of webapps using the TWIG template system. Mixing backend and frontend code in the same file. That was the way we get used to be. It worked and there was no reason to change.&lt;/p&gt;

&lt;p&gt;After a couple of years I decided to separate a little bit the responsability and I started using frontend frameworks (Angular, jQuery) to call the backend service and returning just json data from the back. In the end the frontend was server by the backend that was serving data to the frontend (booom). It was a step to be closer to my new setup.&lt;/p&gt;

&lt;p&gt;After a few projects injecting Vue in the frontend side, we decide to separate completely the front from the back. This was a natural step because the projects we developed were usually based on a native mobile/web experience and the same API develop for the smartphone apps could be consumed by the web side. This decision was a point in our organization. &lt;/p&gt;

&lt;p&gt;Now we are able to undestand the scope of a project and we can separate and distribute the develop flow more efficiently than the time we mixed front and back at the same time&lt;/p&gt;

</description>
      <category>php</category>
      <category>backend</category>
      <category>fullstack</category>
    </item>
    <item>
      <title>Hacktoberfest finished!</title>
      <dc:creator>Ibon</dc:creator>
      <pubDate>Sat, 24 Oct 2020 17:24:44 +0000</pubDate>
      <link>https://dev.to/ibonkonesa/hacktoberfest-finished-3e45</link>
      <guid>https://dev.to/ibonkonesa/hacktoberfest-finished-3e45</guid>
      <description>&lt;p&gt;I have needed more time I expected, but I finally finished the challenge. This experience has been enriching. I have met people, I have learned how to contribute with an open source project. I realized all the work behind many tools we usually used without keeping in mind who is doing our work easier.&lt;/p&gt;

&lt;p&gt;I tried to do the challenge last year, but I wasn't confident, and finally I left. I regret that, but now I have compensated.&lt;/p&gt;

&lt;p&gt;Haven't you done this challenge? You have still 1 week! Don't doubt and try it, because these events are funny and constructive&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
