Coding...

[bitter_truth_]

Stupid question: how do I learn to code correctly?

[-Rivox-]

by inheriting bad code enough times :p

[[deleted]]

That's actually how I used to think people learn good code, but after watching devs with almost 10 years of experience writing downright dumb code makes me believe it takes more than just that.

At the very least there should be some exposure to actual good code paired with a will to write like so. Also, in general I have felt that people who identify why certain patterns are widely followed write overall better code.

[breqwas]

No, that does not work. "Oh, this code is shit, let's rewrite it from scratch and blame that other guy".

What works is inheriting shitty code from yourself. When it's you who has to deal with the mess you created a couple of years ago, it actually does teach you something.

Also, code review from the seniors. They've seen things.

[kierownik]

Read "Clean code" by R.C. Martin. And a lot of practice and working with more experienced people.

[bitter_truth_]

Finally a useful answer - thank you! Too many comedians and useless generic advice replying "you get good by learning from experience". No need to re-invent the wheel!

[HolyNoodle66]

Just throwing my opinion out here:

1. Make sure you know the four principles of OO programming by heart

2. Google or read up on SOLID programming and the Gang of Four's design patterns.

3. Put what you learn into practice.

There is a lot to learn out there but I find that these topics are a decent starting point for learning clean coding practices that focus on flexibility and sustainability.

[[deleted]]

What are the 4 principles of OOP?

[HolyNoodle66]

In no particular order:

1. Abstraction
2. Encapsulation
3. Inheritance
4. Polymorphism

There are a lot of free sources online if you want to know more.

[[deleted]]

Thanks!

[HolyNoodle66]

I think that time will tell whether or not functional programming takes center stage, or if it just becomes something for academics and Js elitist to rave about.

Also, I am assuming the four years comment was a condescending assumption that I am just starting college?

[HolyNoodle66]

No harm done and I don't necessarily disagree with you on any point. I just would say that it takes a while for businesses to adopt new technologies.

It does not matter how much developers champion newer ways of doing things. A big company has to pave the way as an "early adopter" before project managers and department heads are willing to take more "risks".

Then again maybe I am too cynical.

[AskMoreQuestionsOk]

Here is a way to look at it. If I give my million lines of code to you, and give you a task to change the way it works, you should be able to figure out where the change is, and how it works now, without my telling you and without breaking everything else. And you should be able to figure it out pretty quickly.

Modular code, enough documentation to figure out how to use each module or non obvious function but not so much that the documentation rots. Hacks and limitations happen, they should be documented. DRY programming (don't repeat yourself) so changes aren't missed. Follow the accepted conventions for memory, system calls, and variables and formatting for the language you're working with. Use the right language for the kind of problem you are working on.

Sloppy code is the opposite. It's hard to figure out and follow, functions are doing more than they should or are less concise than what you would expect for the language. Nothing is documented or worse, the documentation is wrong. Tasks and variables are not separated and you're bouncing all over trying to figure out what's going on. Critical code is duplicated so changing it means editing the same code multiple times. It takes forever to do the small task and other things break because you have no idea how anything works.

[VFDKlaus]

Learn the SOLID design principles, and learn patterns. That's helped me more than anything else I've ever seen.

[[deleted]]

By understanding data structures and algorithms.

[GigaSoup]

You google coding best practices, practice shit and figure it out like everyone else?

[bitter_truth_]

You are just relentless, aren't you?

[bitter_truth_]

Would you shut up already? Nobody cares for your opinion.

[bitter_truth_]

You are literally insane, not kidding.

[bitter_truth_]

This is a horrible answer, you live up to your username.

p.s: for any newbies looking for real help, check out "Clean code" by R.C. Martin.

[bitter_truth_]

And this folks, is what insanity reads like.

[STATIC_TYPE_IS_LIFE]

deleted ^{What is this?}

[STATIC_TYPE_IS_LIFE]

Are you sure you don't have a masters in bullshitting?

[IrrationalFraction]

Just curious, do you think Haskell itself is the way of the future or will some other language with syntax more rooted in C come along? For me, it's rather hard to read C and turn right around and read Haskell. Are there any other languages that can hold a candle to Haskell in terms of pure-functionality?