I have to say that I may be a bit ignorant, because I’m mostly engaged in greenfield projects with very tiny devteams and I always keep my dependencies count low as possible
Thank you for pointing this out, that’s very valuable to keep in mind
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?
I don’t get it
Stop saying that, it has it’s uses /;_;\
Just use the paint, internet person
This is what that indian kid would write on facebook after his first programming course lesson, to show off career choice
Actually they’ve all been replaced by 🤡
It’s the opposite, everything is passed by reference but primitives are also addresses and therefore passed by value
You can’t pass objects or functions as value
This is an authentic message for when you open a php project
It may not be the fastest solution, or the most reliable, or the most maintainable, but it certainly would best accommodate our investors’ needs!
Been there, done that. Everyday would start with a 2 hour session of meetings. Daily for 30mins and then 1.5h of refinement. Day by day, for 2 years of me being there.
It, without an ounce of irony, leaves a fucking scar on you and makes you despise having meeting for the rest of your life.
Because it doesn’t seem like a useful feature. The only occasion I imagine this could be helpful is with logging to the console to track when the function breaks, but even then - still trivial to replace.
I had tried to use debugger with React so many times and each time I’d drop it soon after. Not useful at all.
Does much better job on the backend though
Good, OOP can suck my balls
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.
https://lemmy.world/comment/13098712
dis 'bout you?
You seem to enjoy overengineering your code, don’t you?