Programming

The only thing a GUI text editor can be better at than a terminal editor is making it easier to use the mouse.

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.

I like C# and Visual Studio

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

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.

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

A lot of programmers need to work on their soft skills.

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.

learn Haskell, write better code

Doing this is a hot take, but "clean architecture" is a joke.

My company is obsessed with it.

C# is fine

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.

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.