<?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: Hassan Pezeshk</title>
    <description>The latest articles on DEV Community by Hassan Pezeshk (@hpez).</description>
    <link>https://dev.to/hpez</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%2F26295%2Ff14c2b8d-80c1-40cb-bbc1-daaa6a7c181a.jpg</url>
      <title>DEV Community: Hassan Pezeshk</title>
      <link>https://dev.to/hpez</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hpez"/>
    <language>en</language>
    <item>
      <title>Laravel .env backup generator</title>
      <dc:creator>Hassan Pezeshk</dc:creator>
      <pubDate>Wed, 27 Nov 2019 10:45:23 +0000</pubDate>
      <link>https://dev.to/hpez/laravel-env-backup-generator-19fp</link>
      <guid>https://dev.to/hpez/laravel-env-backup-generator-19fp</guid>
      <description>&lt;p&gt;I've been using Laravel for a couple of years now and I thought it's time to give something back to the community! So I tried to tackle an issue I have stumbled upon lately, that is, creating backups of the .env file. My main problem was due to the fact that multiple people have access to the file and may change it anytime in our company, having backups is always a good thing in case of any failures or even edits that you forgot and want to go back and check. &lt;br&gt;
So I developed a package to satisfy that need and here it is!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/hpez/DotEnvBackup"&gt;hpez/DotEnvBackup&lt;/a&gt;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--JMmW-olG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/1fmetlr487ave8y9b8ym.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--JMmW-olG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/1fmetlr487ave8y9b8ym.png" alt="hpez/DotEnvBackup"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>laravel</category>
      <category>env</category>
      <category>backup</category>
    </item>
    <item>
      <title>Turning audio into pictures!</title>
      <dc:creator>Hassan Pezeshk</dc:creator>
      <pubDate>Sat, 20 Jul 2019 16:43:09 +0000</pubDate>
      <link>https://dev.to/hpez/turning-audio-into-pictures-290l</link>
      <guid>https://dev.to/hpez/turning-audio-into-pictures-290l</guid>
      <description>&lt;p&gt;I've started a project and recently made public with the goal of turning audio into pictures, meaning, I want to create an accurate visual representation of an audio file, especially music tracks.&lt;/p&gt;

&lt;p&gt;Here's the link: &lt;a href="https://github.com/hpez/tunegraphy"&gt;https://github.com/hpez/tunegraphy&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Check it out and let me know if you like it or have any ideas! Also any contribution is more than welcome!&lt;/p&gt;

</description>
      <category>audio</category>
      <category>pictures</category>
      <category>python</category>
      <category>creative</category>
    </item>
    <item>
      <title>Be careful who you work for!</title>
      <dc:creator>Hassan Pezeshk</dc:creator>
      <pubDate>Sat, 26 Jan 2019 08:37:58 +0000</pubDate>
      <link>https://dev.to/hpez/be-careful-who-you-work-for-1o7c</link>
      <guid>https://dev.to/hpez/be-careful-who-you-work-for-1o7c</guid>
      <description>

&lt;p&gt;This is my first post here! And here it goes:&lt;/p&gt;

&lt;p&gt;I was working for a company for 4 months last year and there was one big mistake that made those couple of months really hard for me and that was not paying attention to what/who I was working with. &lt;/p&gt;

&lt;h3&gt;
  
  
  The interviewer
&lt;/h3&gt;

&lt;p&gt;First off, don't trust what you hear in the interview, which can mean two things: &lt;br&gt;
1- The interviewer may not be that honest with you or, &lt;br&gt;
2- He/she may not see the job as you should (In a technical view).&lt;/p&gt;

&lt;h3&gt;
  
  
  When you should start looking for more
&lt;/h3&gt;

&lt;p&gt;When you get to the stage that you know what you're doing,  there are a couple of things beside salary and co-working experience and other obvious things that you should make sure about:&lt;br&gt;
        1.  What software stack they're using and how suitable it is for you to work with that stack&lt;br&gt;
        2.  How experienced they are in managing the position they're hiring you for&lt;/p&gt;

&lt;h3&gt;
  
  
  What it can cause
&lt;/h3&gt;

&lt;p&gt;Not knowing the above may lead to the experience that I had, a bad software stack led to losing my coding passion and therefore not delivering with the quality that I should have. And the second part led to not being able to manage the tasks and not knowing what to expect from the developer; which, in a rather small team, messes up the whole developing team and puts a lot of pressure on the developer.&lt;/p&gt;

&lt;p&gt;So all in all, &lt;strong&gt;be careful who you work for!&lt;/strong&gt;&lt;/p&gt;


</description>
      <category>job</category>
      <category>softwarestack</category>
      <category>employer</category>
      <category>interview</category>
    </item>
  </channel>
</rss>
