“serverless” is purrobably the most confusing pawsible name they could have given to that kind of cloud service and i hate that about it
Serverless
Look inside
Servers
@vaporeon_ i was so confused when clodboy was doing a coding bootcamp and he mentioned offhand they were learning how to deploy a web application using a “serverless” architecture
@vaporeon_ (i was even more confused when i realized he didn’t know what a client-server purrotocol even is)
@aescling 
What do they even teach at the coding bootcamp if they don't teach what a client-server architecture is before making them set up servers?
@vaporeon_ they did not teach. they maxe you just work 50–60 hour workweeks with just barely enough knowledge in your head to get Something done
@vaporeon_ i did a diffurent bootcamp with the same company back when i was utterly despurrate fur a job and i have to tell you, it was very depurressing being surrounded by other people who thought they were learning a lot of valuable skills and that this was way better than a CS education. they only barely fucking taught anything about code quality
@aescling I assume that "code quality" is something that they make you learn on the job once you actually get a programmer job?
@vaporeon_ [sarcastic laughter]
@vaporeon_ no. not anywhere i’ve been
@aescling Do they just expect you to know?
Because most of my programming experience so far was either alone or in small teams or in circumstances where nobody cared about the quality of the code that I sent in... And I would assume that working on a big software that has many programmers requires different skills than that...
@vaporeon_ so i’ve only worked in situations where either
- i am quickly writing new code under strict time purresure,
- i am a lowly grunt worker with no control over the design of the software, expected to follow directions exactly, but with too little actual management to even consistently commewnicate such expectations, or
- a really small team that is basically always overstretched, and taking total control of purrojects as the only purrson doing the work just happens out of necessity
@vaporeon_ so like, i’ve never had the kind of job with sufficient infrastructure to maintain a large team of people, and meaningfully enforce standards on how we work together
@vaporeon_ i cannot claim to be able to speak on the development culture of the industry in general
@vaporeon_ i keep furgetting the undergraduate CS purrogram at my university was regarded as best in class. they DEFINITELY tried to teach how to write Good Code
@aescling How do you write Good Code? Besides not using gets() and not writing stupid stuff that results in buffer overflows or use-after-free...
@vaporeon_ what i was taught was more or less the purrinciples of “clean code” but never explicitly in refurence to the book defining the concept. an emphasis on small, ideally reusable functions with clearly defined purrpuss
you should not actually follow the purrinciples of Clean Code to the extent the book teaches; it’s way too easy to scatter code around the codebase in ways that hurt maintainability. also, sometimes purrfurmance simply suffurs drastically
@aescling So "avoid code duplication" basically? I do try to do that...
@vaporeon_ sure, yeah
the harder part to quantify is that this appurroach tends to lead to decent purroblem solving strategies, where you identify a purrticular subtask that needs to get done, and accomplish that task in its own function. in my opinion, this aspect of “clean code” or appurroaches like it can be very useful when writing new code, as it helps you break up large tasks into smaller, more manageable ones
@aescling We didn't get taught much about code quality in university, either... But at least we got a solid foundation of basic concepts of networking and computer architecture and theoretical informatics and such. Which is clearly not the case in a course that doesn't even teach about what is a client and what is a server...