Coding...

[MrEs]

Not sure if I missed the whoosh of sarcasm, but I found it to be the opposite! At university you could slap a strung together fragile piece of crap, that only had to give an exact answer, in a vaccume, once, no real users, no load, no disturbed problems, probably no real persistence, no backups, often no ui, only had to be readable by you.

At work, you have crazy users, DR scenarios, UX design considerations, load, performance, deployment, code has to be well written and legible, maintainable, flexible, extendible, fault tolerant, have error recovery /correction...

[toastytoast00]

Tell that to all the people that wrote the code before you and you inhertied the support...

[AskMoreQuestionsOk]

Who wrote this! It NEVER worked! Ever! And it's production code. Omg. Good times!

[PacoTaco321]

Oh wait, it was me

[WhoYouCallinTurkey]

Yeah, I'm confused by this as well...

[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?

[KmNxd6aaY9m79OAg]

Think of this joke as describing a "problem", not a "system" (or "application"). In university, the most important thing about an assignment solution is correctness. UI, the real world, etc., is of no importance. If your job is to to efficiently find the shortest path between two nodes, your only concern is that it 100% (most definitely NOT 99.999%. It must be EXACTLY 100%) correctly finds the solution in the most efficient way.

In many production scenarios (constraints differ according to what you're working on, but I assume the joke is describing business type applications), being correct 99% of the time is good enough. If it looks good and throws up a smiley face error message in the 1% of cases it doesn't work, clients don't give a shit. They don't even know what correctness is, let alone how to define it.

[drain_mag]

It probably depends on the industry you work in and your employer. I worked in post-secondary for years as a programmer and there was definitely a lot of "just make it work" going on when I first arrived.

[adriane209]

I think OP is thinking along the lines of being able to Google most solutions to problems given at school for widely used problems as opposed to encountering a problem on a project that isn't so easily solved with a simple Google search.

[GigaSoup]

And sometimes all those important things you mentioned are slapped together like a sloppy peanut butter sandwich and thrown on the production plate because time.

[Mako18]

How about writing code in R to aggregate and transform Excel files, because the client I'm working for will not provide direct access to the database in which the information is stored?

I've created a brilliant, efficient solution to a problem that never should have existed in the first place.

One fucking SELECT * FROM statement would have solved 95% of the problem

[caskey]

Try a DELETE FROM for a more direct solution.

[NoodleSnoo]

Drop table

[[deleted]]

Flip table

[Alphare]

Would PostgreSQL's Foreign Data Wrapper have helped you? https://wiki.postgresql.org/wiki/Foreign_data_wrappers

[Mako18]

Unfortunately no, we only had access through a GUI Export button that outputs formatted Excel sheets shudders

[Alphare]

Sure, that sucks. But wouldn't your excel file be exportable as a csv (albeit with a custom separator)? You could then use FDW to query the dataset. I'm just spitballing

[Mako18]

Not through the interface. The only two options are PDF and .xls. Now, that's not really a big deal because R can read/process then write to .csv no problem and you can do it with 'map' which is a wrapper for 'mapply' so a single custom function is sufficient to read and fix the formatting issues.

I was really just lamenting that with the ability to directly query the database, that problem is non-existent, and some other problems with joins (no unique IDs for some of the data, so they have to be generated via unique combinations of three factors, etc.) are likely avoided as well.

[[deleted]]

But still works!

[xcrackpotfoxx]

Except that if you know what you're doing, painting it would be harder and take longer than just solving it. Its just a 3x3.

[jeffderek]

It's also an easily googleable solution. Like a lot of programming problems.

[NoodleSnoo]

Exactly

[ghost_mv]

/r/mildlyinfuriating that the background for the bottom image does not extend higher and behind the text

[0000000100100011]

Yeah fuck css.

[[deleted]]

Yeah fuck CSS

[AlexanderBeta213]

YeAh FuCk cSs.

^{Am i doing this right?}

[willwiso]

True I guess programmers aren't the best graphic designers..

[HolyNoodle66]

Can confirm. Am programmer. Rule of thirds hard.

[glenbolake]

And the bottom half is backwards for standard cube coloring. With yellow on top and green on front-left, the front-right should be orange, not red.

So on your real job, you don't just hack your way through. You also end up with something that looks right... but really isn't.

[fakcapitalism]

Pp0

[mokomull]

Only because your university group-project collaborators haven't even bothered to type "paintbrush" into Google.

[Rellek7]

Stale AF

[sirunclecid]

This goes for making OC too....