Modern programming - crazy nonsense

AutoVideoFreak

Registered Member
Joined
Jun 6, 2024
Messages
50
Reaction score
52
What is all this for? More suffering? Maybe that's the point.



Take a random keyword, e.g. "microservices", "containerization", "serverless"

Fuck some trendy framework, React, Vue, whatever

Throw in something about CI/CD, because that always sounds smart

Don't forget some shit from Google or Amazon to make it enterprise

Fuck Agile and Scrum there, because without it you won't get anywhere

Finally, fuck something about scalability and performance

And voila! You have a ready-made "good practice" that you can push to junior devs. They will swallow like young pelicans.

Example:

"Microservices based on React with a serverless backend, implemented via CI/CD pipeline in Google Cloud, managed in Scrum sprints, ensuring high scalability and performance."

What the fuck does that mean? But hey, it sounds professional! Next ones:

"Event-driven architecture with Kafka, implemented in Golang, hosted on Kubernetes, with Prometheus and Grafana monitoring."

"Serverless functions in AWS Lambda, connected to GraphQL API, using DynamoDB, with CI/CD via GitLab pipelines."

"Microfrontends in Vue.js, integrated by Web Components, with backend in Node.js and MongoDB, implemented by Docker Swarm."

"Progressive Web App with an offline-first approach, using Service Workers and IndexedDB, hosted on Firebase, with A/B testing."

"Edge computing with Cloudflare Workers, integrated with CDN, using WASM for high-performance computing, with TensorFlow.js for ML on the front end."

"Reactive programming with RxJS, backpressure handling via Akka streams, with event sourcing and CQRS patterns, hosted on DigitalOcean."

"Blockchain-based smart contracts with Solidity, frontend in React Native, backend in Rust, with sharding for better scalability."

"Serverless architecture with Azure Functions, real-time communication via SignalR, CI/CD via Azure DevOps, with blue-green deployments."

"Microservices in Spring Boot, communication via gRPC, service mesh with Istio, observability via OpenTelemetry, hosted on GKE."

"Jamstack architecture with Next.js and Netlify, headless CMS, server-side rendering, with feature flagging and canary releases."

Independent thinking is a lost art nowadays. And that's a pity, because it is what leads to real innovations.
 
Trending framerwork sounds good. Other than that, everything else is just fancy words for those big corporations. Small organizations use them to fancy themselves or something, I don't really know lol
 
Trending framerwork sounds good. Other than that, everything else is just fancy words for those big corporations. Small organizations use them to fancy themselves or something, I don't really know lol
The problem is even freelancers can't see through it.

Entrepreneurs have to think on their own, but that's probably the only group that can speak of success in software development as they just get this done instead of slowing everything down with "future in mind". The problem is, money doesn't flow... developers get lost in all of this.
 
Some of the technology you mention is extremely useful. It's all about using the right tool to fit your needs. Pick a trch stack that you are good at, and can deploy quickly.

Containerization technologies and microservice architecture happen to work well for a lot of people, but can be a massive headache if used wrong. At the end of the day, the customers don't see what the backend is made from, its abojt making something that meets the specifications at the necessary scale
 
Some of the technology you mention is extremely useful. It's all about using the right tool to fit your needs. Pick a trch stack that you are good at, and can deploy quickly.

Containerization technologies and microservice architecture happen to work well for a lot of people, but can be a massive headache if used wrong. At the end of the day, the customers don't see what the backend is made from, its abojt making something that meets the specifications at the necessary scale
Said tiktok crap seller.
 
I don't get the point of this post.

You mentioned some common design patterns and technologies, what's the problem with them? Do you reinvent the wheel each time you make a new car?

To me, seems you are getting crazy or overwhelmed trying to understand them.

Take a break from coding bro
 
All of your examples are specific technology stacks for specific solutions. You know exactly how they were built just by reading them.
Maybe ask your Senior for help, if you don't know what some of those funny words mean.
 
What is all this for? More suffering? Maybe that's the point.



Take a random keyword, e.g. "microservices", "containerization", "serverless"

Fuck some trendy framework, React, Vue, whatever

Throw in something about CI/CD, because that always sounds smart

Don't forget some shit from Google or Amazon to make it enterprise

Fuck Agile and Scrum there, because without it you won't get anywhere

Finally, fuck something about scalability and performance

And voila! You have a ready-made "good practice" that you can push to junior devs. They will swallow like young pelicans.

Example:

"Microservices based on React with a serverless backend, implemented via CI/CD pipeline in Google Cloud, managed in Scrum sprints, ensuring high scalability and performance."

What the fuck does that mean? But hey, it sounds professional! Next ones:

"Event-driven architecture with Kafka, implemented in Golang, hosted on Kubernetes, with Prometheus and Grafana monitoring."

"Serverless functions in AWS Lambda, connected to GraphQL API, using DynamoDB, with CI/CD via GitLab pipelines."

"Microfrontends in Vue.js, integrated by Web Components, with backend in Node.js and MongoDB, implemented by Docker Swarm."

"Progressive Web App with an offline-first approach, using Service Workers and IndexedDB, hosted on Firebase, with A/B testing."

"Edge computing with Cloudflare Workers, integrated with CDN, using WASM for high-performance computing, with TensorFlow.js for ML on the front end."

"Reactive programming with RxJS, backpressure handling via Akka streams, with event sourcing and CQRS patterns, hosted on DigitalOcean."

"Blockchain-based smart contracts with Solidity, frontend in React Native, backend in Rust, with sharding for better scalability."

"Serverless architecture with Azure Functions, real-time communication via SignalR, CI/CD via Azure DevOps, with blue-green deployments."

"Microservices in Spring Boot, communication via gRPC, service mesh with Istio, observability via OpenTelemetry, hosted on GKE."

"Jamstack architecture with Next.js and Netlify, headless CMS, server-side rendering, with feature flagging and canary releases."

Independent thinking is a lost art nowadays. And that's a pity, because it is what leads to real innovations.

Reeaski?
 
I don't get the point of this post.

You mentioned some common design patterns and technologies, what's the problem with them? Do you reinvent the wheel each time you make a new car?

To me, seems you are getting crazy or overwhelmed trying to understand them.

Take a break from coding bro
If you just use templates, perhaps you're not making new inventions.

All wheels have only one thing in common. However that doesn't mean you should make all of your wheels grouped into one class of shapes and then from shapes make wheels and then each new wheel would inherit from a wheel.

1721196530994.png

To me personal comments like your aren't very professional. That's why this forum sucks so much and the internet in general. People act like it's kindergarten meanwhile they're talking about delicate stuff requiring precision.
 
React is fantastic. I wasn’t really around the days of jquery but I got to use it a couple times and omg was it worse than what we have now. Installing packages was awful. Writing a big app meant a huge file of spaghetti code. React is actually readable and maintainable.
 
React is fantastic. I wasn’t really around the days of jquery but I got to use it a couple times and omg was it worse than what we have now. Installing packages was awful. Writing a big app meant a huge file of spaghetti code. React is actually readable and maintainable.
Jquery is fantastic. I wasn’t really around the days of react but I got to use it a couple times and omg is it worse than what we had before. Installing random package based off random unverified packages is awful. Writing a big app means a huge file of spaghetti code. Jquery is actually readable and maintainable.
 
people rely too much on frameworks instead of writing their own code... then when there is an issue they don't even understand whats wrong or have to wait for the developers to update the framework in case of a bug. also it makes things bloated, some projects use a ton of different frameworks for just a few functions they would need from it. its just because they are lazy...
 
If you just use templates, perhaps you're not making new inventions.

All wheels have only one thing in common. However that doesn't mean you should make all of your wheels grouped into one class of shapes and then from shapes make wheels and then each new wheel would inherit from a wheel.

View attachment 360832
To me personal comments like your aren't very professional. That's why this forum sucks so much and the internet in general. People act like it's kindergarten meanwhile they're talking about delicate stuff requiring precision.

Why dont you explain what you're trying to build and what technology are you using?
Also, my comment was not meant to be professional, this is not a "professional" software discussion and there is nothing "professional" on a weird comment on technology names lol (:

Anyway back to wheels, I'm not using any template or anything as I dont make abstractions or encapsulation when its not needed.
Most of technologies mentioned are products first of all, companies and individuals compete in making better solutions to common problems so that's why there are multiple similar technology with those "strange" names.
 
people rely too much on frameworks instead of writing their own code... then when there is an issue they don't even understand whats wrong or have to wait for the developers to update the framework in case of a bug. also it makes things bloated, some projects use a ton of different frameworks for just a few functions they would need from it. its just because they are lazy...
They should check old school programmers who really made creative programs and knew how to deploy independent instances without oop. You can do that with procedural or anything else without all the bloat and complication while having control of what you would like to have. Guru programmers can make you successful too but not in terms of understanding.
then when there is an issue they don't even understand whats wrong or have to wait for the developers to update the framework in case of a bug.
I remember when I did that and I was blaming OS developers for that. That was about 15 years ago.
 
Micropenis based on serverless glans, implemented via prostate pipeline, managed in urethra sprints, ensuring high scalability and performance.
At the end of it you want to add some AI, so it becomes blurred.
 
Oh f**k, here we go again! Let's go back to ENIAC and punch cards, please. Abacus, why not?
Mods, please unban @reaaski , it's easier to track a single username.
 
Back
Top