Is there any coding behaviors from your colleagues that make you angry?
spaces for indentation
inconsistencies in their style or stupidly fucking complex styling where you have to read their whole program before you understand which style of commenting to use where, especially in C89 code
Not really my colleagues but co-eds in university
>work on group project with three others
>poorly structured code
>no comments at all
>horrible use of libraries
>poorly designed classes and OOP approaches
I have a colleague that insists on leaving a blank line between every 2 lines of code. He literally presses Enter twice after every line.
He once made a git commit that was literally nothing but inserting whitespace lines in all the existing code. Someone higher up later reverted that, adding the comment "removed unnecessary whitespace", I loled.
everything they write.
committing code once a week into source control
using legacy frameworks (ASP.NET 1.1)
never heard of MVC
they don't know what an API is
button1, button2, button3 for GUI applications
they don't know how to use the console, so everything needs a GUI
no unit tests, not even knowing what it is
no testing at all, it goes from developer computer straight into productions
The only reason I'm still with this company is I can browse 4chan almost all day and get a huge paycheck at the end of the month doing so.
That's the fuckin problem: it isn't fucking readable.
Barely anything fits on your screen and the entire visual structure of the code is gone. It's fucking retarded to write your code like that, and even more fucking annoying when the dickwad inserts blank lines into the code assigned to other people.
I swear, there is not a single person in our company who cares about things like mixed tabs and spaces in the leading indentation, trailing whitespace, consistent line endings, consistent code style, any sort of readability or any sane maximum line length. Visual Studio does not encourage people to care about those things because it doesn't do things like showing whitespace by default or normalizing line endings on save, and they're just not things that normie programmers seem to care about. Also, C# is so fucking verbose that you can easy clear 200 characters on every other line if you don't care about that sort of thing.
They also don't care about descriptive commit messages, line length in the commit message or properly separating the title and body of the message. It drives me up the wall.
I'm so sorry
I've just recently started Uni after programming by myself for the past four years and barely going near normie code (I was mainly writing in C with a text editor my friend and I wrote) and these fucking normies with their fucking notepad++ and vim on the uni servers pump out the most disgusting shit. Oh boy do I miss just working with my own code and libraries
It's like they don't give a shit it all, there's no consistency anywhere and why would they have any when the fucking lecturer has the most retarded and hard to follow styling which is inconsistent as fuck as well
>no order of functions
>500 line behemoths
>direct copy paste from SO without understanding what it does
>100 outside library dependencies, half of which are not used, occupy space in unused functions
not using comments while typing shitty variables like:
I am already looking a way out of the company.
Or should I stay to have a safe job as a debugger?
Itis not like I call a girl to relieve my stress in her every weekend.
Yeah, Uni code is even worse. I've seen programs with 20-ish global variables per file, programs where 50% of the code is in the main method, the most bizarre and error-prone data structures and pointer manipulation, and of course, pretty much everything has inconsistent whitespace and code style. You even see that shit from most third year students, and almost no one knows how to use Git or any other VCS.
I wish they had a course, or at least part of a course, that focused on code style and readability. I feel like you can get through a whole CS degree without learning that the ends don't justify the means when it comes to writing code and you actually have to do more than just write good comments to make your code readable. The only times I remember lecturers talking about code style is when they're a OOP or structured programming weenie and they're trying to push their religion on you, explaining that conditionals are evil, or continue, break and early return statements are evil (the phrase "as bad as goto" is often used.)
Also, nobody at university or school can develop software, no exception.
Those who think are the worst wannabe smart skiddos that break stuff when it matters.
What's worse, even lecturers are shit, well most of them anyway.
>Hey anons, in this project we create a node/mongoloid based web epp; I suggest you use Sublime, an editor whose creator apparently died so it's endless beta or two browser based editor that are known to be pieces of shit.
>Also, I have this wacky idea that is borderline retarded, have fun creating.