HAHA! SEXPRESSION! GET IT?

We know it bro, we have it all over our feeds, involuntarily

Look down bro

I hope none of you have a habit of commenting on porn threads, because that would surely be an uncanny way of finding out eachother’s kinks

Honestly at this point you’re just being obnoxious

It’s literally a meme. And in no way is it even attempting to hide it.

You seem to enjoy overengineering your code, don’t you?

It does take a lot of space for devs, but personally I find that absolutely irrelevant, because it’s your end user’s experience that really matters, and - as a dev - you are most likely to have a much better rig and internet connection than your average Joe.

Which is of very little importance in most cases, because modern bundlers incorporate treeshaking in order to filter out all the unused code when you’re building a production application

Edit: okay well appearently that’s controversial for some reason

When I was a junior, I was given an entire front-end app to develop entirely on my own with very little guidance from the team-lead. It was some ridiculously bad code, especially since it was my first time working with React with basically zero preparation.

Few months later, project is delivered, I get some time to read docs and guides before starting the next one. Since I was learning theory on what I would practise earlier, I was digesting it extremely fast and it helped me patch up all the holes in my thinking and learn how things should actually be done.

Soon after the next project came and it was definitely much more of a smooth ride. The code was alright and even the early decisions I made were pretty sustainable much later. It was another project I was working all alone, then some people joined in and I was teaching them, but I would always guide them too much and they weren’t growing very fast.

Even after a few months, these people were not ready or willing to work independently, which was my personal failure as a mentor. That’s what really assured me that people should be given a lot of space to properly grow.

My whole career is me working on increasingly larger projects with decreasing assistance. And it’s extremely effective. 4 years in the field and I just became a software architect.

Is that even a joke or a fact statement at this point?

To me, there are two classifications of DRY - one I find harmful, the other very useful.

First one resembles mathematical extractions, essentially you never allow a single chunk of code to be written twice and you create massive amounts of global util junk. This also creates some bad tight coupling.

The other is more logical, where you only extract logic in places you want to always change together. Simple and effective.

This sounds just extremely dumb to me, as in “do something manually for 2 minutes or spend 2 days automating it”

Also, DRY in 90% of the cases is a sham