Prioritize Performance post
TitanE
8 months ago
parent
0da800d610
commit
f4b4891844
@ -0,0 +1,57 @@
|
|||||||
|
<!DOCTYPE html>
|
||||||
|
<html lang="en">
|
||||||
|
<head>
|
||||||
|
<title>(POST) Prioritize Performance</title>
|
||||||
|
<link rel="icon" type="image/x-icon" href="../images/favicon.webp">
|
||||||
|
<link rel='stylesheet' type='text/css' href="../style.css">
|
||||||
|
<meta charset="utf-8"/>
|
||||||
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||||
|
</head>
|
||||||
|
<body>
|
||||||
|
<a style="text-decoration: none;" href="../">
|
||||||
|
<pre class="main-header">
|
||||||
|
_______ _ _ _______ __ __ _______ _______ __ _
|
||||||
|
|______ | | |______ \_/ |_____| |_____| | \ |
|
||||||
|
______| |_____| | | | | | | | \_|
|
||||||
|
</pre>
|
||||||
|
</a>
|
||||||
|
|
||||||
|
<hr/><p><a href="../">sf.me</a> > <a style="color:#bd93f9" href="../blog/">Blog</a> > <a style="color:#bd93f9" href=".">Prioritize Performance</a></p>
|
||||||
|
<h1>Prioritize Performance</h1>
|
||||||
|
<p style="font-size:110%">Posted on: <strong>07 April 2024</strong></p>
|
||||||
|
<p style="font-size:110%">Reading time: <strong><strong>2 min</strong>
|
||||||
|
<p style="font-size:110%"></strong>Category: <a style="color:#ff79c6" href="../blog/software/"><strong>Software</strong></a></p>
|
||||||
|
<p>In various software teams, inexperienced developers prefer to add features in the current moment and plan to optimize for performance later.
|
||||||
|
They forget to do so in <em>many</em> cases.
|
||||||
|
This is a horrible habit that needs to be stopped.</p>
|
||||||
|
<p>These are the reasons this may happen:</p>
|
||||||
|
<ol>
|
||||||
|
<li>Companies prefer new features over speed</li>
|
||||||
|
<li>Companies pay their employees on the basis of the amount of lines of code</li>
|
||||||
|
<li>Employees find it easier to write low-quality code that just works</li>
|
||||||
|
</ol>
|
||||||
|
<h2 id="why-">Why?</h2>
|
||||||
|
<p>By not optimizing for performance, <strong>you are not respecting your users.</strong>
|
||||||
|
Over the years, the required specifications and hardware for each piece of software has been going up.
|
||||||
|
This leads to old devices being obsolete quickly and provides a bad experience for users on low-end hardware.</p>
|
||||||
|
<p>A widespread counter to this argument is that most people upgrade their hardware regularly.
|
||||||
|
<strong>They don't.</strong>
|
||||||
|
Look at your acquaintances and you will find a few people who use their devices for as long as you can.
|
||||||
|
<a href="https://www.sellcell.com/blog/how-often-do-people-upgrade-their-phone-2023-statistics/">A survey says that 39% of people don't upgrade their smartphones before 4 years of ownership.</a>
|
||||||
|
That is a whole lot of people to give a bad software experience.</p>
|
||||||
|
<p>Another reason to prioritize performance is because it's simpler to make swift software when it's in its early stages.
|
||||||
|
By following good conventions and proper practices, it becomes trivial to make software run fast.</p>
|
||||||
|
<p>Lastly, fast software allows people to use their devices longer.
|
||||||
|
Your software will be indirectly making a positive impact to the climate.</p>
|
||||||
|
<h2 id="conclusion">Conclusion</h2>
|
||||||
|
<p>Software teams should take the initiative to make sure their software performs fast from the get-go.
|
||||||
|
This is because of user respect, simplicity and the climate.</p>
|
||||||
|
<p><a href="mailto:sf@sufyaan.me?subject=Prioritize%20Performance">>>> Reply To Me</a></p>
|
||||||
|
<p><a href="p.pdf">>>> Download PDF</a></p>
|
||||||
|
<p style="text-align:center;"><a href="../secure/" style="color:#bd93f9"><svg class="footer-posts" xmlns="http://www.w3.org/2000/svg" width="48" height="48" viewBox="0 0 48 48"><mask id="ipSLeftOne0"><path fill="#fff" stroke="#fff" stroke-linejoin="round" stroke-width="4" d="M30 36L18 24l12-12v24Z"/></mask><path fill="#bd93f9" d="M0 0h48v48H0z" mask="url(#ipSLeftOne0)"/></svg>Previous Post</a> - <a style="color:#bd93f9" href="../terminal/">First Post</a> <svg class="footer-posts" xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20"><path fill="#bd93f9" fill-rule="evenodd" d="M2.232 12.207a.75.75 0 0 1 1.06.025l3.958 4.146V6.375a5.375 5.375 0 0 1 10.75 0V9.25a.75.75 0 0 1-1.5 0V6.375a3.875 3.875 0 0 0-7.75 0v10.003l3.957-4.146a.75.75 0 0 1 1.085 1.036l-5.25 5.5a.75.75 0 0 1-1.085 0l-5.25-5.5a.75.75 0 0 1 .025-1.06Z" clip-rule="evenodd"/></svg></p>
|
||||||
|
<hr/>
|
||||||
|
<footer>
|
||||||
|
<p class="footer-text"><a style="color:#bd93f9" href="../blog">blog</a> - <a style="color:#ffb86c" href="../about">about</a> - <a style="color:#f1fa8c" href="../portfolio">portfolio</a> - <a style="color:#ff5555" href="../links">links</a></p>
|
||||||
|
<p class="footer-text" style="font-size:80%"><a href="../">sufyaan.me</a></p><p class="footer-text" style="font-size:65%"><a style="color:#aaaaaa" href="../sitemap">Site Map</a></p>
|
||||||
|
</footer>
|
||||||
|
|
||||||
Loading…
Reference in New Issue