3 ms·

Why use kubernetes and the cloud when you can FTP or rsync your code onto a box? Simpler times.

by ljm 3y ago

spinningslate 3y ago
2nd law of Thermodynamics: Entropy increases over time. Quoting[0]: "The entropy of a system can in fact be shown to be a measure of its disorder and of the unavailability of energy to do work." I rather like that - where "work" is the time spent solving first order business problems, and "disorder" is a measure of the energy spent not directly solving the business problem. AKA dealing with accidental complexity. [0] https://www.coursehero.com/study-guides/physics/15-6-entropy-and-the-second-law-of-thermodynamics-disorder-and-the-unavailability-of-energy/ https://www.coursehero.com/study-guides/physics/15-6-entropy...
danuker 3y ago
I deploy my static blog via rsync. I also have Isso [0] on it. No need for a back-end web framework or anything. [0] - https://isso-comments.de/ https://isso-comments.de/
Scarblac 3y ago
I just ssh to the server and edit the code there, I never understood why people need to have two whole environments that they keep in sync. (though seriously, in my dorm room in the 90s, my pentium 90 desktop at the end of my bed had a fixed IP address and was the server...)
- phist_mcgee 3y ago
  Now add 5 people doing that at the same time and report back on how scaleable that solution is.
  - yumraj 3y ago
    You need Kubernetes for a product which has a 5 people team?
    - baq 3y ago
      Resume/CV won't pad by itself
  - ljm 3y ago
    That's how we did it at my first gig with PHP and Drupal. I'm not going to say it was great or even particularly good, but given our work was split across different modules, you could easily have multiple people either uploading changes over FTP or doing some quick hacks over SSH. After all, you only needed to copy over your changes and not re-deploy the entire project. The server was a little Dell box sat under the desk of the 'CTO' in his office. There were some cowboy-level engineering practices for sure, to the point that I'm not sure you could call it 'software engineering', but there was definitely some beauty in the simplicity of that setup compared to what we typically have to do these days. At least after you set up the box and the access to it, anyway.

Why use kubernetes and the cloud when you can FTP or rsync your code onto a box? Simpler times.

by ljm 3y ago

Why use kubernetes and the cloud when you can FTP or rsync your code onto a box? Simpler times.

2nd law of Thermodynamics: Entropy increases over time. Quoting[0]: "The entropy of a system can in fact be shown to be a measure of its disorder and of the unavailability of energy to do work." I rather like that - where "work" is the time spent solving first order business problems, and "disorder" is a measure of the energy spent not directly solving the business problem. AKA dealing with accidental complexity. [0] https://www.coursehero.com/study-guides/physics/15-6-entropy-and-the-second-law-of-thermodynamics-disorder-and-the-unavailability-of-energy/ https://www.coursehero.com/study-guides/physics/15-6-entropy...

danuker 3y ago

I deploy my static blog via rsync. I also have Isso [0] on it. No need for a back-end web framework or anything. [0] - https://isso-comments.de/ https://isso-comments.de/

Scarblac 3y ago

I just ssh to the server and edit the code there, I never understood why people need to have two whole environments that they keep in sync. (though seriously, in my dorm room in the 90s, my pentium 90 desktop at the end of my bed had a fixed IP address and was the server...)

phist_mcgee 3y ago
Now add 5 people doing that at the same time and report back on how scaleable that solution is.
- yumraj 3y ago
  You need Kubernetes for a product which has a 5 people team?
  - baq 3y ago
    Resume/CV won't pad by itself
- ljm 3y ago
  That's how we did it at my first gig with PHP and Drupal. I'm not going to say it was great or even particularly good, but given our work was split across different modules, you could easily have multiple people either uploading changes over FTP or doing some quick hacks over SSH. After all, you only needed to copy over your changes and not re-deploy the entire project. The server was a little Dell box sat under the desk of the 'CTO' in his office. There were some cowboy-level engineering practices for sure, to the point that I'm not sure you could call it 'software engineering', but there was definitely some beauty in the simplicity of that setup compared to what we typically have to do these days. At least after you set up the box and the access to it, anyway.