Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities [email protected]
Composition over inheritance has become a meme that people repeat without understanding. Both have their uses, but if composition is all you use, then you're using a hammer on everything. There is no silver bullet in life and most undeniably not in programming.
Also, electron has a reason for existing. If it didn't have a use, it wouldn't have the number of users it has. You can't tell me in all seriousness that Qt, Gtk, Swing, Tkinter is easier to use than electron for the common developer.
While I completely agree with you about electron, I still don't have to enjoy the fact that companies are outsourcing their lack of development in native tech to my wallet in terms of wasting resources on my device. Now perhaps the cost of the associated services would be higher if they had a native app which is a fair response. I still don't have to like it.
Written as a user (and occasionally enjoyer) of electron based software.
It's especially infuriating when you have a giant like Microsoft rolling Electron on their flagship applications (Teams), and then deprecating support for some platforms (Linux). What's the point of your nice, memory-gobbling, platform-agnostic app framework if you're not even going to use it to provide cross platform support?
Oh I have some!
Computer science is still a hobby and has a lot to go through before it is an actual industry.
Developers are too often bad engineers.
Short development cycles are a bad thing.
POO is trash. It's a manager tool, not an engineering one.
My mantra has always been to bring solutions not problems. Applying that to code reviews makes for a far more productive experience.
Rather than just pointing out errors in code help the developer with prompts towards the solution.
Or, if you're too lazy to explain why something shouldn't be done then why should another developer have to act on your criticism?
Abstraction will be the death of traditional software development as we know it
Write the whole thing, and only then, scrap it and rewrite it. This way you actually have a good understanding of the entire implementation when you are rewriting. When I refractor while writing my draft I will slow myself down and trip over myself, I'll be way more likely to rewrite something I've already rewritten.
Sure there is a limit to the size of projects this can work for, but even for massive projects they can still be broken into decently sized chunks. I'm just advocating for not rewriting function A as soon as you finish function B.
Programming is the easy part, and a useless skill on its own.
If you can only program in one language, you can't program.
C++ is the single best language to learn programming.
Stupid mistakes you make are not bugs, at least not for you.
Doing this is a hot take, but "clean architecture" is a joke.
My company is obsessed with it.
If you're not a programming superstar you can probably make more money writing nothing but Terraform code for hapless enterprises.
Front end and back end are different enough that you can really specialize in one or the other. They take very different mindsets. I know how to make css obey, I don't know how to make sql performant. Its possible to have both, but not as well.
For every front-end dev, you need 3 back-end guys and a designer.
Programmers are not bad at our jobs, its just not a mature disclipline yet.
