I like 1-index because its what I learned first, and you like 0-index because that's what you learned first
Programming
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
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
My hot take: There is no such thing as 0-index. If you start with 1 it's an index, of you start with 0 it's an offset.
If you can't find where you missed a closed parentheses, just add a bunch of them to the end of your project like this...
)))))))))
... until your editor's syntax helper tells you it's good. I am very good at coding.
The only thing a GUI text editor can be better at than a terminal editor is making it easier to use the mouse.
My experience with people from university is that they have extremely strong opinions about things they don't know very much how they work outside theory. There is this syndrome that you have to do everything from scratch with low level languages and keep shitting on anything that uses abstraction to make your life easier.
I don't know why people in this industry have this need of feeling that they're better than others.
DRY means Do Repeat Yourself, when the alternative is cooking up some awful OOP abstraction
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 actually hard af to do for any extended period of time (more than half an hour)
It requires such a specific mind that's drawn to all the detail oriented specific robotic parts of coding but almost all coders say coding is easy because the people whose mind don't fit coding already quit long ago
Yes I find coding hard and no I'm not coping
Actually programming being difficult might not be correct but more like programming is largely unbearable
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.