ivan/site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

change philosophy html

Browse Source
This commit is contained in:
Rawley Fowler
2022-11-28 16:05:50 -06:00
parent 0bf65d32b5
commit 75046ba14c
1 changed files with 65 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
html/philosophy.html
View File

@@ -42,13 +42,13 @@
</header>
<main>
<h3>Philosophy</h3>
<h4>The Problem with Modern Computing</h4>
<h4>Modern computing and the modern mindset</h4>
<p>
As computers get faster get faster, code quality and performance get's worse. The tragectory of the software world
(particularily in the web dev sector) is to produce solutions to problems, without considering
performance, optimization, and availability. How many billions of CPU cycles have been
lost rendering SPA's and PWA's? In reality, computers are limited tools for communication, mathematics,
and entertainment, not for loading 2MB JavaScript payloads, that in turn render the page.
and entertainment, not for loading 2MB JavaScript payloads, that in turn render the page. This way of computing is almost synonymous with the world views of most "modern" people.
</p>
<h4>Solve Your Own Problems</h4>
<p>
@@ -59,11 +59,10 @@
potential security vulnerabilities, and inturn reducing bloat. Some developers will argue
"why do it yourself when I can get a premade solution, that I know works!" Sure, download that dependency, link that
project to yours, but know this. You will <b>never</b> develop anything truly unique if the solutions to <u>your</u>
problems are solved by people smarter than you. Simply put, how do you think the library creators made it to the level
they're at today?
problems are solved by people smarter than you. Simply put, how do you think the library creators made it to the level they're at today? Heck, even most library code isn't particularly smart, so what's the excuse?
</p>
<p>
Packages also, can make us feel very productive. This is something that Jonathan Blow points out in one of his talks,
Packages make us feel very productive. This is something that Jonathan Blow (a very critical and influential programmer) points out in his talk about developer productivity.
Blow mentions that high-level languages, and libraries make us feel like we're doing a lot more than we really are.
Ken Thompson and company wrote most of Unix in 3 weeks; an entire operating system, kernel and all. Compare this to
the most "productive" day of a web developer. Blow demonstrates in his talk that as companies progress they hire more
@@ -85,8 +84,15 @@
causing software to be developed in a more intimate way, focusing optimizations rather than features.
Machines were fair, but not powerful. Think, Intel Core 2 Duo, 2-4gb of DDR2. This hardware is actually very good,
and in my opinion as much as an average person needs (even today).
If you write software (outside of graphics programming, games, etc), and it can't run on a Intel Core 2 Duo, you need to seriously
re-think what you're doing, and how you're doing it.
If you write software, and it can't run on a Intel Core 2 Duo, you need to seriously
re-think what you're doing, and how you're doing it. This for obvious reasons does not take into account GPU bound tasks.
</p>
<p>
I believe that the hardware limitations of the pre 2010's were what drove the software quality gold rush of the time.
Most software released during those times is still around, sure there may have been some un-forseeable security issues,
but that software was really good. BSD's, Linux, Unix, Emacs, etc, staples of the software world, beautifully hand crafted
by developers who actually care (because they had too!). If they didn't care about their software and took shortcuts, their software
would suffer as a result. A stark contrast to today, where most developers are most concerned with their "industry standards", and "design patterns".
</p>
<h4>Conclusion</h4>
<p>
@@ -94,11 +100,11 @@
</p>
<p>
It's really a beautiful and unique way to approach software, and to an extent, your life.
I find much more gratification and self purpose when I solve my own problems indepdent of pre-existing solutions
(obviously you can still take inspiration from others).
I find much more gratification and self purpose when I solve my own problems indepdent of pre-existing solutions. This isn't meant to scare people from taking inspiration or even copying existing solutions. But rather meant to inspire a sort of creative, and exploratory spark. Even if you were to copy an algorithm or program from an existing one,
I still bet you'll know it far better than anyone who simply installs it.
The world would be a much better place if we focused more on what we need vs. what we want. This is especially powerful
in software, but can also be applied to how your own happiness. Finally, taking ownership and responsibility of your
work will make you better at the work, and also, a more pragmatic person overall.
in software, but can also be applied to how you view the world. Finally, taking ownership and responsibility of your
work will make you better at the work, and also, a more pragmatic person overall. Putting it all together, you can find the undeniable power of self-sufficieny and proficiency.
</p>
</main>
<footer>