(public).sospep.subjects ~ view article ~ confessions-of-an-intermediate-programmer

<h1 style="text-align: center;">confessions of an intermediate programmer</h1>
<h2>[WHAT]</h2>
<ol>
<li>] by Michael Bromley&nbsp;@michaelbromley.com -&nbsp; Bromley tells the story of how he went from being an "advanced programmer" to being an "intermediate programmer" by learning more about programming and working&nbsp;more with other programmers.</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li><strong>] READ THE FULL ARTICLE</strong></li>
<ol>
<li>]&nbsp;<a href="http://www.michaelbromley.co.uk/blog/65/confessions-of-an-intermediate-programmer" target="_blank">http://www.michaelbromley.co.uk/blog/65/confessions-of-an-intermediate-programmer</a>&nbsp;</li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2016-06-22</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>] started programming as a kid, not all kids had computers, most who did, didnt know how to use them well</li>
<li>] after getting borland compiler on PC magazine CD, discovered programing and&nbsp;wrote the program 'no fucks' while his friends played on their PS3's</li>
<li>] built an ecommerce system for his client&nbsp;with PHP + mySql&nbsp;, in the early days of the web, it worked, in production, for several years, but ...</li>
<li>] it was massive, functional (non object oriented),</li>
<li>] got harder and harder to work on, unexplained errors, trouble finding code that was source of errors</li>
<li>] contd for years, was only PT work, developed 'awareness' the certain choices were not optimal</li>
<li>] example - using mysql functions was risky</li>
<li>] one day, got an urgent call - website was down, the victim of an exotic sql injections, the likes of which he had never seen before</li>
<li>] maybe, time to swap to this new&nbsp;"PDO" thing ( the right way to access databases in PHP)</li>
<li>] epiphany - realized it was going to be hard and realized why it was going to be hard - functions scattered all over the place, no way of knowing if changing 1 thing was going to break something else, code was 'inconsistent' and code was 'tightly coupled'. it was going to be tough because of all the bad practices and lack of understanding that had informed the creation of this sprawling mess that only now revealed itself to me.</li>
<li>] I was not the sublimely gifted programmer I had suspected myself to be. I was a fake who had somehow gotten away with it for this long!</li>
<li>]&nbsp; I learned first-hand &ndash; and painfully &ndash; why there is a right way and a wrong way to do things. It&rsquo;s not just a matter of taste or fad. It&rsquo;s not a matter of who has the cleverest arguments. The right way has real-world ramifications which will make your life (and the lives of others who touch your code) better. The wrong way leads to frustration and wasted time.</li>
<li>] &ldquo;It&rsquo;s no sin to be a beginner or an intermediate. It&rsquo;s no sin to be a competent programmer instead of a leader. The sin is in how long you remain a beginner or an intermediate after you know what you have to do to improve.&rdquo;</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>] SRC = HN, (238) <a href="https://news.ycombinator.com/item?id=7337278" target="_blank">comments</a> (117)</li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] index FROM [ Book] analysis IN [ libraries] careers