Programming in a tree. I usually climb up here and read, but I decided to code, and I didn't drop my laptop :D

I covered the screen with my hand because my code's ugly, and I don't want anyone to see it lol.

Being 100% serious, I saw a guy in my Computer Programming I class using MS Word to write code that he would copy, then paste into notepad. When I asked him why he did that, he said, "Microsoft Word is easier to read than notepad."

He ended up dropping the class and changed majors.

Yesterday I had to modify a python script that was written by the previous dev,
There was no documentation to understand the code, I had to read 10 files almost 900 line each, after a looooooooooong 7 hours, at the top of one of the scripts, the author name was same as mine
😂😂😂😂😂😂😂😂😂

"there's a problem with your API"
Me: "why?"
"I get no data"
Me: "what response code are you getting?"
"405 - Method not allowed. But only on the /version endpoint"
Me: "Soo... What request are you sending?"
"POST"

WHY THE FUCK WOULD YOU SEND A POST REQUEST TO AN ENDPOINT THAT **GETS** THE VERSION OF MY API???!!!!

Me: "Read the documentation. It's there for a reason"

When you start reading someone else's code and all you do is properly indent for the first 30 mins so you can actually read it.

The story of how humans evolved to an asshole.

Code-reviewer: please change 'if a==b' to 'if b==a' as it is easier to read so I can approve.

Code-owner: -_-

How I feel when I read the code I wrote when I started to learn c++

Who said I can't read my own code after 2 months?
*Opens code*
.
.
.
.
.
*Cries in a corner*
*The world hates me*

I woke up today with my power off, dad forgot to pay the bill

WTF.jpg

I get home from work all stoked to code to learn that he didn't get it straightened out

Phones on 10% so i cant even read pdfs or surf Kodi

And im spending the last bit of electricity i own to bitch about it

Pay your bills devs

Yesterday I was updating the code in a linux server at 23:00.
My 6 year son look the terminal while i was typing and said:
"Dad, why you always write in block letters? I can read and write also in italics."
"Dear son, you are smarter than my PC."

Stackoverflow

When I was just starting with programming I used to google a lot (more) of my problems. But just just copying them made me feel guilty, since I could not handle the problem myself. So I decided to analyse a code to the point where i understand exactly how it works. Sometimes it took me a couple of hours to understand a method, which was written 1 or 2 levels over my current level, but it was totally worth it. I learned a lot about Java, how to write cleaner code in general and how to read and understand code quickly.

Just downloaded some big ass codebase and the first line i read is:

"// The source code is not well documented, but every advanced programmer will be able to understand it after some time."

Well... let's find out about your definition of "some time", Dickhead!

People on Stack Overflow are SUCH FUCKING ASSHOLES

"You didn't show us where you declared this unimportant array, please review this article for how to ask questions"

My question doesn't concern the array, my question concerns how the system works, all code I provided was only for clarity. Read my fucking question you arrogant asshole. You have lots of points, fine, go tell your mother, but you assume I don't know how to ask a question which you clearly did not read.

To all the C++ programmers who haven't read "Modern C++ Design" by Andrei Alexandrescu yet, READ IT! Its great. To me, it opened up an entirely new approach to designing classes with a whole new dimension of possibilities. And it reads really well! Sometimes I got shivers because the code was so sexy 😅😂😂

Attack problems you've never solved.

Don't fear projects which you're not familiar with the technology.

Read books, blogs, and code.

Refactor every opportunity you have.

Don't always be the smartest developer in the room.

Be flexible. Tools are tools, don't fall in love with any one till and neglect others.

1. You don't code to add a feature or whatever. You do it to solve Users' problems. It's a User-centric system.
2. You read more code than you write. So help yourself and write code intended to be read.
3. If people don't know you did something, you did nothing!
4. Never answer a call at 3 am if you're not paid to be on night call-duty. You'll become the guy who answers at 3 am.
5. Remember the big difference between you and me is that I failed to do stuff more times than you have tried to do.
6. When you start shaving the yak, stop!

Fuck me. I just posted a huge post on StackOverflow with images and huge puddles of code everywhere because I had been stuck since yesterday and five FUCKING minutes after asking, I read the code on the website (Pretending to be an outsider solving my own problem) and find the FUCKING TYPO.

Everyone should learn to code" is a movement to flood the market with Software Engineers so that salaries can be reduced.

Conspiracy theory that I just read on reddit and sounds about right.
Would you feel the same?

Fucking developers putting emojis in their code!

My terminal (st) doesn't support displaying emojis and it crashes immediately once it read an emoji. I have been chasing crashing bugs for weeks and I just found out where the issue is.

(As a CS student in University)
Teacher 1: I am a new teacher and have an electrical subject and I know you guys hate this and love coding so we will code whatever we study in python so you can actually understand what we are studying

Teacher 2: I am a senior teacher and have an super important computer science subject , I will fuck everything up come to lectures read a ppt that I didn't even make and read the ppt in the most monotonous manner humanly possible and fuck everything up and steal your work if your research with me

i really hate when i have to read someone else's shity code ... I'd rather write the entire code from scratch -_- !

When Its 4PM and you're trying to read the Code you wrote at 3AM.

Spoke to a programmering student who insists on writing his Java and python code in PARAGRAPH format, like an essay (the teachers do not teach this). Tried to explain why this is a bad idea. He explains to me that if others can't read his code that it is their problem and that he would never make a silly syntax error like missing a semicolon or a bracket. Called me stupid and walked off.

Life will be hard for him.

First day of work,
team lead asked me to study and read the source code.
Opened one file...

Sometimes, you'll be tempted to copy-paste some piece of code from somewhere (stack overflow, w3schools, etc). But instead, read the code there and re-type it. Will help you to understand it better.

The rants I read here make me want to be a better developer. I started writing tests, linting code and ensuring 'quality code' because of the devrant community. Being a self taught developer, you never really have anyone to thank. But today I would like to appriciate you all for the rants, comments and advice that make us developers become better at our craft.

I’m happiest about code I deleted.

Deleted code is easy to maintain, easy to read and it makes applications run faster.
Moreover applications take less disk space and are faster to download.

The more happy than about deleted code I’m about deleted software or destroyed computers.

If you're gonna comment a lot or a little, at least be consistent. I just read some code like this:

//prints "are you ready?"
printf("are you ready?");

//get the value
int findVal(int x) {
/* some fucking complex algorithm with no comments whatsoever that seems to have an error messing everything up */
}

Worst code review experience?

Hard to pick just one, but most were in a big meeting room with 4+ other developers not related to the project and with some playing Monday-Morning-Quarterback instead of offering productive feedback.

In one code review, the department mgr reviewed the code from a third party component library.

<brings up the code on the big screen>
Mgr: "I can't read any of this, its a mix of English and something else."
Me: "Its German."
Mgr: "Then why is 'Button' in English? This code is a mess."
Me: "I'm not exactly sure how I should respond, I mean, I didn't write any of this code."
Mgr: "Yes, but you are using it, so it's fair game for a code review."
Me: "Its not really open source, but we can make requests if you found something that needs to be addressed."
Mgr: "Oh yes, all this...whatever this is..<pointing again to the German>"
Me: "I don't think they will change their code to English just so you can read it."
Mgr: "We paid good money, you bet your ass they'll change it!"
Me: "I think the components were like $30 for the unlimited license. They'll tell us to go to hell first. Is there something about my code you want to talk about?"
Mgr: "<Ugggh>...I guess not, I couldn't get past all that German. Why didn't we go with an American company? Hell, why didn't we just write these components ourselves!?"
Me: "Because you gave a directive that if we found components that saved us time, to put in a request, and you approved the request. The company is American, they probably outsourced or hired German developers. I don't know and not sure why we care."
Mgr: "Security! What if they are sending keystrokes back to their servers!"
Me: "Did you see any http or any network access?"
Mgr: "How could I? The code is in German!"
Monday-Morning-Quarterback1: "If it were me, I would have written the components myself and moved on"
Me: "No, I don't think you could for less than $30"
Monday-Morning-Quarterback2: "Meh...we get paid anyway. Just add the time to the estimate."
Mgr: "Exactly! Why do we even have developers who can't read this mess."
Me: "Oh good Lord! Did anyone review or even look at my code for this review!?"
<silence>
Mgr: "Oh...ok...I guess we're done here. Thanks everyone."
<everyone starts to leave>
Me: "Whoa!...wait a sec..am I supposed to do something?"
Mgr: "Get that company to write their code in English so we can read it. You have their number, call em'...no...wait...give me their number. You keep working, I'll take care of this personally"

In they nicest way possible, the company did tell him to go to hell.

I'm real tired of my coworkers always trying to one up me and being elitist about their code. Like I get it, you think PHP is shit, C is so much better than Java. Wow, you must be so knowledgeable! /s

Just because you're bashing on bad languages and talking shit doesn't mean you write good code, and in fact your code isn't top quality, I've read it. All you're going to accomplish with an elitist mindset is close yourself off to improving, and that's probably the worst thing you can do as a developer.

During code review:

Guy (also the same guy who pushes code without making unit tests): "Hey, this thing you added is unnecessary. Remove it."
Me: "Have you read the rest of the changes? It isn't unnecessary."
Guy: "Not yet"

StackOverfllow -> Copy Code -> Doesn't work -> Study its working -> Read related info on other websites -> Code starts to make sense -> Do the required changes in code as per the understanding -> Got it working.
I only learn if the initial 2 steps fail. Else I skip the latter.

Told the new hire that for the first week they can just familiarise themselves with the JS framework, do the tutorials, and read through the code / docs.

Boss comes by Tuesday morning "you should be finished with all the tutorials by the end of the day"

Looks like we're throwing him in the deep end!

Context: new dev has Java and 3d games background. Our app is full stack JS

Read Clean Code and came to the realization that I'm a terrible person to everyone who had to read my work.

"There’s a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. […] The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming: It’s harder to read code than to write it." - Joel Spolsky

From the guy who wrote all the Programming Microsoft books and the Annotated Turing book. Comes this book.

This book is great for beginners great for people who don’t know a lot about software and how computers work, simple read. I like it because it also gives a different prospective, beginning at Morse code and works up from there all the way up to high level languages.

The book gives snippets of code to discuss it not really a tutorial book. It’s a different type of book that all people could understand.

Good read

Once a day, take some time to read your colleagues' commits.

You will see how they work, you will learn how they solve problems, you will understand their flow and you will know more and more parts of the code base.

When the last dev wrote code and you dared to read it....switch on a Boolean, what even is your life legacy dev?

"read the code" he said
"all the requirements and business process is in there"

Knok knok...who is there...................
VB6

CR: "Add x here (to y) so it fits our code standards"
> No other Y has an X. None.

CR: "Don't ever use .html_safe"
> ... Can't render html without it. Also, it's already been sanitized, literally by sanitize(), written by the security team.

CR: "Haven't seen the code yet; does X change when resetting the password?"
> The feature doesn't have or reference passwords. It doesn't touch anything even tangentially related to passwords.
> Also: GO READ THE CODE! THAT'S YOUR BLOODY JOB!

CR: "Add an 'expired?' method that returns '!active'?"
> Inactive doesn't mean expired. Yellow doesn't mean sour. There's already an 'is_expired?' method.

CR: "For logging, always use json so we can parse it. Doesn't matter if we can't read it; tools can."
CR: "For logging, never link log entries to user-readable code references; it's a security concern."
CR: "Make sure logging is human-readable and text-searchable and points back to the code."
> Confused asian guy, his hands raised.

CR: "Move this data formatting from the view into the model."
> No. Views are for formatting.

CR: "Use .html() here since you're working with html"
> .html() does not support html. It converts arrays into html.

NONE OF THIS IS USEFUL! WHY ARE YOU WASTING MY TIME IF YOU HAVEN'T EVEN READ MY CODE!?

dfjasklfagjklewrjakfljasdf

Me : I should start building user authentication system.
inner self : there are enough free and secure ones out there, just go read the documentation.
Me : fuck I'm not reading 10000 pages of documentation written in alien language.
inner self : well then you better start building
Me : **writes code
Inner self : you better add the data validation and security while coding
Me : I just want it to work !
Me after a few days trying not to suicide : the site is hacked, the code is bugged, hello darkness my friend

Why in the flying motherfuck can't people remember the fact that other people might have to read their code?! If you're not gonna name things properly, and mess everything up with utterly useless and garbage comments (all comments are useless and garbage), then the least you can do is fucking format and indent it properly!! GAWD FAKKIN' DAMNIT!!

After 9 months of my course that involved much fear, anxiety and depression, last night I had a great moment.
Learning about scrapers for my dissertation - watched 10 minutes of a tutorial video then thought of an idea and went away and an hour later had built a little program to read a restaurants menu on their website then read back what they had in the form of a poem - all in a language I hadn't used before that night.
The reason I learnt coding was that I idolised the idea of thinking of a problem and then just solving it with your own code. Last night was the first time I felt like I might be getting there.
:).
p.s. Sorry this isn't very ranty.

Random thought of the day: I'm afraid of posting any picture of my screen/setup where you could read my code because I'm scared that people would zoom in and discover how incompetent I am. Does this make any sense?

Just read this in a blog post by Jon Arundel, I think he's spot on:

"Programmers are incurable optimists: we always think our code will work, despite much evidence to the contrary."

Franz is his name, he is our new programmer. He got task to made a calendar to display ongoing ads with javascript, and damn good he done it fast. Until today, he not coming because he got ill and i have to edit his calendar code because there's a change request.I look at his code and thinking how he read this code? no indentation, bracket everywhere, etc. Then I call him:

Me: Franz, can you explain your code to me?
Franz: Sure, but.. umm.. I forgot to bookmark the stackoverflow link.
Me: ...

/**
* Do not read before New Year.
**/

Happy coding to all of you guys! My very best wishes for this 2018. May your code be free of bugs the whole year.

P.S. Fuck you testers (just kidding, we need you)

When it's dark outside all the time and the sun suddenly comes around.

Everyone's going crazy about it and walking outside.

Me: FUCK. How am I supposed to read my freakin code like that?!

*Me standing up and closing the shutter*

I've been looking at the shittiest code today. Hundreds of lines saying

this.thing.otherThing.EvenAnotherThing[this.someFuckingIndexThatShouldntBeAField].theOnlyBitThatsDifferentPerLine.AlsoNoneOfTheNamesWereThisMeaningful

Over and over. They're all wider than the editor window. Clearly copy pasted. Just make a fucking variable Jesus Christ how do you expect anyone to read that

When the source code of a library that you depend upon is easier to read than its official shitty documentation...

I think Clean Code: A Handbook of Agile Software Craftsmanship by Robert Martin should be a must to read.
In school no teacher puts emphasis on code quality.
They should learn how to name variables and functions the right way at an early stage in order to better perfect their craft :)

When your sysadmins can't script a file compare and so you do the code for them.
"Sorry but we can't run unknown code on the server"
Read the code then you vile troglodytes!

As a resident of Québec (Canada) who has been training for the Google Code Jam for a while, I was sad to read this while filling my application this morning 😑😔

What?... really?... You read my code? ...*wipes away tears*

THANK YOU SO FUCKING MUCH!!! You sir/madam/undefined are a true gentleman and scholar! (even if you are just a troll picking random shit apart to flash around your superior knowledge of design patterns).

Any time I receive a code review, that is bearing that is an actual review, born of free will and not a mandatory report - I feel flattered beyond words.

> Think its shit? - GREAT FINALLY FEEDBACK!
> Have an idea? - I'm all ears.
> Trying to sound smart? - You still read/used my shit.
> Want to understand my approach? - Grab a drink and get comfy son.

In a world where I am usually the only person in the world that knows WHAT MY ACTUAL WORK IS and there being only a select few people on the planet able to understand it, I am always grateful for developer feedback.

Seriously... out of your own volition you used my code, read it, made an effort to understand my thinking and THEN REACHED OUT TO ME with ideas!!??

I could kiss you... you beautiful binary saint.

Scenario 1
Friend 1:"Hey, you're good at computers right?"
Me:"Erm yup."
Friend 1:"Can you hack Instagram? I've lost my password."
Me:"Oh My God."

Scenario 2
Me looking at a friend's unity C# code
Me:"You know there's an enter key right? Why is your code horizontal not vertical?"
(Means that after a semi-colon he continues his code)
Friend 2:"I like to read my code in horizontal, that feels natural to me"
Me:"What ever, as long as it works. But why do you have so many if function inside another if function?"
Friend 2:"Cuz I want the player to do this while moving"
Me:".........."

Management: Create [totally idiotic and complicated feature, near to impossible to create]
Me: that's close to impossible and could probably destroy some other parts of the application.
Management: well, then your application is poorly programmed.

DAFUQ? HOW DARE TO JUDGE THE QUALITY OF MY CODE WITHOUT EVEN ABLE TO READ 2 LINES OF CSS? WHAT THE FUCKING FUCK IS THIS?

I'm really not easily offended but this sentence hit really hard.

This stupid crap is pissing me off.

I write a quick blob of code that performs an http request with custom headers and writes the response to a file. easy squeezy. Everything works.

I abstract it into a class and add request building and stages (enjoayble!), and have one method make the response, read its body, and write to a file. I literally copy/pasted most of my existing code into the method and indented it. The only changes were updating var names to instance vars.

But now? It's complaining something is trying to read the request body twice, and it's throwing a fit. What? How? You were just working!

asfklasjdf;l

The more I play with C, the more I realize why many people hate C++.
I like the amount of control and the simplicity. No unnecessary syntax sugar, and the code is very straightforward to read.

Self documenting code is a fucking myth you bloody sheep.

Write “self documenting code” then add a fucking comment or two explaining why the fuck the code deserves should be there because nobody can see what the fuck it is doing or understands how the whole collection of microservices works. I’m sick of spaghetti code bullshit full of accidental redundancy because it is impossible for anyone to realize why something is there at a glance.

I renamed different “Contract” classes today by adding numbers before code review.
Contract
Contract1
Contract2
Contract3
All of these classes are supposed to be the same but somehow they aren’t and you self documenting dumbasses missed it. Don’t gripe about the numbered classes in the repo… fix the fucking code and collapse the classes so we don’t have four sections of code describing the same fucking structure from a http get with different interfaces because four people couldn’t read the whole like some fucking computer.

Code reviewer keeps removing my comments saying, "This will only be read by other programmers, the code should speak for itself".

<hyperbole>
This is the exact opposite to back in uni where for every line of code they demanded 2 lines of comments!
</hyperbole>

I hardcoded credentials into source code because I was too lazy to write the method to read them from the database properly.

Recently for a project I needed to read/write ID3 tags from MP3 files. And after a long search, I found this bloated, monolithic but quite stable library, "getID3".

So, I was looking through the code-base and I found this. This guy literally storing the key value based data embedded as comments within the class file. Then wrote a method to parse the data and even used caching to ensure maximum speed! And such usage is repeated all over the code-base.

So, this is what people used do before arrays were invented :3

WTF is the point a
of auto-generated documentation. Some dude litterally thought it was a good idea to read the code and write the exact same shit differently. WTF IS THE POINT!?

Documentation takes work, sorry, stop being lazy.

Hard-code a security key. It's a read-only website, only the admin needs to have a key to publish, right...

What's wrong with this code?

std::pair<float, float> foo() { return { 0, 0 }; }

"Nothing," would you say.

That's because you're normal.

But the most stupid C++ compiler ever (M$ VS)
issues an ERROR that converting 0 to float incurs possible "loss of data". So you have to write "0.f".

BTW, "0." is a double, so you really have to write "0.f". Or "static_cast<float>(0)" if you like ugly, impossible-to-read code.

I wish all newbies would read clean code. I feel if you understand the concepts you can more easily join an established team and contribute more quickly with less do overs. I realize writing elegant, testable code is like making good whiskey. It takes time.

ERROR MESSAGE:
<I am written in plain english>
<Here is the line number of the error>
<Here is the possible reason for the error>

Developer: What the heck is wrong with my code now. (looking at source)

ERROR MESSAGE:
<You incompetent piece of s**t, READ ME. F'n READ ME. Please READ ME. I promise, I be helpful.>
<Nope. You aren't gonna. Fine!>

Read source code and unit tests. Don’t bother documentation cause it’s outdated. Dig into the core, look where data goes in and where it gets out. Everything else is just a wrapper.

Sometimes I write so many comments that it's hard for me to read the code :/

Today a tester asked me to make a modal smaller. I read the code and saw modal size was explicitly set to "large". So I was about to set its size to default but I asked myself "what if I enter a random string there?" and I set it to "not-so-big". UI framework handled it well and actually set its size to default. I'm keeping the code that way for future laughters.

The best comment I ever read in the production...

/*
* You may think you know what the following code does.
* But you dont. Trust me.
* Fiddle with it, and youll spend many a sleepless
* night cursing the moment you thought youd be clever
* enough to "optimize" the code below.
* Now close this file and go play with something else.
*/

Programmers nowadays have to...
… write 100%-covering unit tests;
… set up continuous integration, linters, hinters, style checkers, …;
… follow style guides for every language;
… meet impossible deadlines;
… meet impossible management/customer/end user expectations;
… read through terrible code others made;
… read through terrible documentation others made;
… make terrible documentation themselves;
… fight with the IDE;
… fight with the build tools;
… deal with unreproducible crash reports coming in from everywhere;
… debug code written at 2am (by themselves AND others);
…
…
…
… KNOW HOW TO PROGRAM.

!rant

My colleague saw this code of mine and said it is annoying conditions are not on the same line, since it is a shared project I can't go "that's my style!"

What do you think should I convince him why we need to follow this approach (at least it can be easily read rather than reading a screen wide line)

Siemens Step7 code block protection (PLC's).. It was designed to lock code that you don't want others to be able to read. All blocks are in a dbf file, so you just need to find the block record and uncomment one line, voila - source code available.

Given the massive use of Siemens PLC's on plants all over the world, and the simplicity of hacking via S7 protocol, usually Internet connected, it's a breeze to steal or modify the controllers code with possible critical implications.

Enter Stuxnet.

I don't seem to understand why so many developers nowadays are focused on learning newer frameworks rather than focusing on best practices and learning how to code better.

"Hey I learnt React today, we should totally switch to it because it's so amazing"

> mfw the same guy doesn't even know how to follow coding styles, write good code that scales or document his code.

I think some people need to take a step back and focus on the more vital tasks of writing good code to begin with rather than getting so excited about every new thing that surfaces. It's annoying as fuck to deal with some of these people who you have to work alongside and be able to read their loopy shit code and all they are doing in their time is refreshing hackernews.

Do you wanna be a software engineer at Google?

Go to AlgoExpert.io. Pick a question. Read the prompt. Write some code…

JUST FUCKING STOP

Fucking shitty ad popping up every time I watch anything even remotely related to tech or science.

The senior dev in my team wants me to convert all the lambda expressions I have written to anonymous inner classes. He says it will increase the code readability.
IT IS NOT MY FAULT THAT YOU CAN'T READ LAMDA EXPRESSIONS!!!!

It's like the dev has something against the new features of Java8

When in internship you have to read 150000 lines of code to make changes and the code does not have any comments, no indentation, no documentation, no wiki. You'll be like fuck this shit. I'm outta here.

One thing you learn after a few years in IT and some languages is that there is no problem with most languages.

BUT

Ugly code is ugly code! Has half of the devs I have been working with never heard of a style guide? Is it so long of a read that they just skip it.

I have flashback of variables being called "a", "b", "c" and/or methods being called "method_alfa" in production code.

In my opinion, repeatedly sh*ting all over a style guide is a reason for getting fired.

I think it will be very odd to ask a girl to wait so that I can read the code on her skirt, with no wrong intentions.

I guess she won't understand how attractive source codes are.

Don't hire monkeys that write shitty code that cause production issues.

Just spent the entire morning with our global team (10+ ppl) looking into the cause of a production issue.

Root cause: shitty code that anyone that has read an algorithm book (array resizing costs) and understanding how DB functions should be used and why (bulk inserts vs one at a time) would never write.

Even the code itself is a mess...

The performance is based on how much code you wrote that day.

Not mine though, i heard/read it from somewhere else.

But that’s fucked up, right?

Serously I just recoverd from being overworked and senior developers are complaining to me that their code does not work???

DUDE just read the fucking error and start googling!

How the fuck do you think I learned software development?

It's a fucking matter of trail 'n error!

Man nothing quite like reworking some code to make it 'better' so that nobody has to read it top to bottom to make a change.

And then months later get a request and think "Oh crap that code".... and you go in and find the little hooks you added made a 3 or 4 hour (or more) change into a 15 minute task.

I just started commenting my code. I know, its horrible i havent done this earlier..
I actually enjoy it now, i can express rage, write small jokes for myself to read next time i gotta edit the code, or just remind myself how fucking stupid i used to be

My internship company does not believe in the concept of 'commenting'. They just tell me: "Ahh just write readable code!
Yeah that's cool until I need to read out thousands of lines of javascript without a single comment!

This isn't a rant. This is a brag on my team.
I asked the team what exactly a feature did. They read me the test code.
I may get a little weepy. So proud.

After noticing 4 operations in a single line, I comment a pr stating the line is not simple to read as there are many operations which can be, especially in the eyes of a junior, hard to read.
I proceed to suggest a better solution.

Colleague: “what??? How is this not readable??? Is it [op1], [op2], [op3] or [op4]? 🤷‍♂️”

I kindly explain this person that it’s not about the single operations, but the fact they are all on a line. Inside an object assignment.

Colleague: “you should learn stuff! (4 links to websites giving that snippet of code”

Ah yes, the oldie: “but other people are jumping off a cliff, why don’t WE do it???”

I was deaf but now i'm half blinded ! :/
(Glad i know the place of the keys)

So boered cuz i cant code or even read a book!
FUUUUUCK !!!!

Looking at some legacy code and I was like wtf, later read the author name and it was me.
How people were tolerating me than! Man😂

Sometimes, rewriting a project can be faster, more time efficient and better to read than trying to fix the single inefficiencies in parts of the code.

Programming on paper (any benefits?)

For the programming exams we have at our university we have to write code on paper (like full code, not pseudo).

I feel that writing code on paper really limits my ability to express my programming knowledge, in comparison to writing code on the computer.

However, I cannot think of a real benefit of doing so. I mean most programmers (if I may generalize) have bad handwriting. Which is a loss-loss situation for both the examinees and professors (who have to read the exams).

Are there any benefits for writing code on paper?

The ability to look at uncommented legacy code and read the thoughts of the developer when he wrote it
(seriously, comment your shit!)

Several months of work got deployed and suddenly the app stops displaying user submitted images. No new changes that looks related went live and the images seem to be stored and read by the code. Nothing looks odd about it other than images not displaying. 4 hours of frustrated developers later an accidental newline at the top of a routing file is removed and all is fine.

Hey Visual Studio, WHY THE FUCK DO YOU THINK MY CODE IS SUDDENLY READ ONLY YOU BLOATED PIECE OF SHIT

Every time I read some code of the rust standard libraries or code of other popular rust crates, I feel ashamed of the code I produce ... their level of documentation is just outstanding, mine is ... hardly existing?

Guess a rant about myself :D

"damn bro, you made that? how can i get into coding?"

shut the fuck up. you can get into programming like anyone who wants to can. by googling how to code. it's not the question itself that bothers me, it's the fact that if you actually wanted to code so bad, you already would've googled it. stop projecting your lack of passion on me.

this is most common with programming, but it happens so often with so many other things.

if you want to learn about biology and chemistry, there's free courses online and papers from nih.

if you want to learn about forsenics read a book about it and read about cases and how they were solved.

i could go on and on. the internet gives you access to so much that if you actually wanted to learn something, you would've already have.

I'm a junior dev less than 1 year into my first job out of college. I'm halfway done reading Clean Code (my first software book out of college) and I'm really enjoying it!

What should I read next? I was thinking something about design patterns. Should I go for the classic GoF book or continue with Robert C Martin and read "Agile Software Development, Principles, Patterns, and Practices"?

Apache Tomcat vulnerability "GHOSTCAT" allows read conduct files and implant web shells. All versions in the last 13 years vulnerable.

According to Security Researcher of Chaitin Tech : Due to a flaw in the Tomcat AJP protocol (the channel for Tomcat to connect to the outside, pass them to the corresponding web application for processing and return the response result of the request), an attacker can read or include any files in the webapp directories of Tomcat.

For example, An attacker can read the web-app configuration files or source code. In addition, if the target web application has a file upload function, the attacker may execute malicious code on the target host by exploiting file inclusion through "GHOSTCAT" vulnerability.

Apache Tomcat has officially released versions 9.0.31, 8.5.51, and 7.0.100 to fix this vulnerability.

Does anyone practise code reading and comprehension? If so, are you able to share your idea?

I try to find how to read code faster with retention and comprehension. It is much like speed reading, but I am reading code.

Here is my journey so far:
Stage 1:
When reading code, I literally each word in line as comment. I though it will help me to understand better. It did, but the retention was not strong enough.

Stage 2:
After reading each line, I will close my eyes for 1-2 seconds and do a reflection what I just read. Better understanding, but comprehension still not good.

Stage 3:
After reading each line, I use my own words to describe what it does and write down as comment. I found that I have better comprehension

Stage 4:
Constantly, remind myself to describe with my own words. this speeds up the reading and understanding.

To be honest, I am still trying.

Code = play games
Watch a tutorial = watch a movie
Read docs = read a novel

So I end up being scolded for never studying for my academics and just having fun all the time

debug hell

senior: i'm going to read the code changes of the PR that caused this bug, many files , lots of lines of code to see if i can suss out this issue

me: skimmed the PR, i give up, unga bunga time, time to compare the variables in the debugger between the different implementations, found the difference

due credit, the unga bunga approach worked this time, might nto always work

Has anyone here read the book "clean code" by Robert C. Martin and can recommend it?

90% of beginner questions are so damn annoying. I get it, some people are new and still learning but for the love of God, I just want to tell these kids to shut the fuck up, sit their ass down and WRITE SOME DAMN CODE, instead of bitching and moaning about what they best language is or how to magically read a tutorial and become a ninja in a day.

Fuck.

QMS admin: you only finished the code review, you didn't complete it!

Me: opens review clicks complete

QMS: you didn't export the code review comments!

Me: opens code review again. Clicks Export. Attaches *.txt

QMS: you exported the comments in the wrong format, I can't read them

Me: what is the right format?

QMS: SOP document <random alphanumeric> clearly states the format

Me: spends 20 minutes navigating the piece of crap QMS software with no search function folder by folder.

Finds document.

It's 120 pages and 4 years old.

On page 68, I find "template to be implemented"

Reply to QMS, that document doesn't actually give a reference to a template

QMS: Email my line manager "Please teach your staff how to do a code review"

So this is what a test looks like here in my school...
I really like my teacher but his test are... uhh... fucking awful.

I mean the code isn't even indented ffs! Like wtf?!? How should one be able to read this bullshit?
The questions are shitty too.
Also please add line numbers so it is easier to describe how things work in the code.
AND USE FUCKING A4 PAPERS FFS!!!

Thanks,
an experienced student

I appreciate Ruby so much more now after writing a tiny Assembly + C Grub-compatible kernel and being forced to read libc source code.
The lower levels truly are a dark place.

I just read this great line in the Google SRE book which I have experienced myself:

"Some of the most satisfying coding I’ve ever done was deleting thousands of lines of code at a time when it was no longer useful."

I know people have mixed feelings about Uncle Bob and I really never followed the guy at all, but back in college I found his book Clean Code on a shelf and read it cover to cover. A lot of it really stuck with me. In fact, I might dig it up again now that I'm thinking about it.

When your project partner is an absolute coding genius.

But writes spaghetti code with methods named function1, function2, ... function20.

How the fk am I supposed to read that code?!?!?!

But I’ll give him credit, the program is works and is amazing. It’s just not possible for anybody other than him to understand.

It's embarassing and you guys will find it either rude or annoying but I have readied myself and here goes my confession;

Whenever I see the abbreviation for Command line interface I cringe. You know because cli ? And I read it in my head as 'Kli' which is like the shortened form of a female part ?
I can't just read it as "See, el, ai" or think 'Command line interface' directly.
My brain's first thought is it must be an acronym so you should read it like how you would read NASA which is also an acronym and not like 'cmd' which is not an acronym but just an abbreviation.
Thus whenever I see it I feel a mixture of embarassment, self-loathing and physical discomfort.

I wonder how can I not be embarassed and cringing whenever I see Something-CLI.
I just noticed when it's in uppercase I don't cringe as much. I should code a chrome extension to change all CLI abbreviations to upper case.

Does anyone else have a major problem with over thinking debugging or like the code to write in general?

I spent 10 minutes the other day reading over 6 lines of code only to realize 2 words were capitalized when they shouldn't have been.

Wednesday night, i was doing my CS homework. The question wanted me to swap variable values using a third variable. I stared at it for 30 minutes scratching my head. (I did Google it and read the notes I took.) And when I saw the solution, it was so simple that I face palmed really hard.

By taking one 30 minute dump in the toilet per day to relax and read other people's code on my phone

Around 6 years ago I started at this company. I was really excited, I read all their docs then I started coding. At every code review, I noticed something was a little off. I seemed to get lots of weird nitpicking about code styling. It was strange, I was using a linter, I read their rules but basically every review was filled with random comments. About 3 months in I noticed, "oh! there aren't actually any rules, people are debating them in my code reviews!" A few more reviews went by and then I commented, "ya I'm not doing any of this, code review isn't a place to have philosophical debates." All hell broke loose! I got a few pissed off developers, and I said, listen I don't care what the rules are, you just need to clearly fucking articulate them and if you want to introduce one, I don't care about that either just don't do it in the middle of my review. I pissed off 1 dev real bad. Me and this dev were working together, the QA person on the team stood up and said "hey! you know what I love about your code reviews?!" The other dev and myself looked at each other kind of nervously, "I love that you're both right, these are all problems!"... 1 year later (and until now) me and the other dev are still friends. Leave it to QA to properly identify the bug.

Code Simplicity by Max Kanat-Alexander, a very short but inspiring book I've read two or three weeks into learning programming. I can only highly recommend it to beginners and probably even people who already have some experience in the field.

Posted a question on Stack Overflow today for the first time in as long time... Have lost faith, what shit some suggestions people have.

- Clear the cache, check again...🤨
- Your code is wrong, I tested it my way, you need to change.😒

Read the fucking post properly and gauge some level of expertise... I clearly wrote that it WAS working, the bull shit your detailing is completely irrelevant.

Fucking idiots...

I think this is the first time ever on my team where I read someone else's source code and actually went "wow... This is pretty well written and structured". No god methods or classes.

Read the fucking code! Stop asking questions that could be answered if you spent 5 minutes reading the code.

If it weren't for poor documentation I'd be retired by now.

We didn't all write your library. In fact, only you did. So, some helpful documentation would really help us all out. Can't believe the number of times I need to read source code to figure out what the hell you are doing.

I find it way easier to read code than ordinary text.

Am I the only one? Do I have a problem?
After the first sentence my I eyes can't focus to keep reading text. This also happens to my native language except from English.

read this somewhere on the internet

e=(mc)²

error = (more code)²

guess it's true

Anyone read the book "clean code "? Want feedbacks! Thanks!

After I read clean code I talked to a fellow developer about some concepts. Later I reviewed some code of him and he clearly got the concept (not)

Java
...
If (isTrue(someValue))...

public boolean isTrue(boolean value){
if(value == true)
return true;
else
return false;
}

In my experience object oriented is very good for composing high level abstractions into a complete system. Functional is awesome for validation, parsing and massaging data in any way and imperative is tithe most useful paradigm to handle side effect dependent code that either manipulate the computers state ( read/write) or communicate with external systems.

The people acting as if one of them is the one true way are misleading you.

The pain of using third-party library with unclear documentation.

"Oh just read the code"

well it would've helped IF THE CODECLIMATE RATING ISN'T 0.4. D:

Sitting here reading Clean Code and read the heading, "How Would You Build a City" at the beginning of chapter eleven. Damn it now I just have the urge to put the book away and play SimCity.

I've been writing Java the last few days. Really makes me remember why I enjoy writing objective c / swift so much. It's not necessarily the crazy syntax of objective c. It's the conventions behind the languages. It's very easy to make your code read like prose. Which when you become used to this it's very hard to jump back into spaghetti code with abbreviated variable names and such.

Everywhere I go I see these "Become senior in 3 weeks" courses
That's good and all
But when the fuck will you teach your students to debug and search your errors on google/stackoverflow
This is so fucking ridiculous
Them guys can't even read git push/pull errors and wonder why they make changes to the code but nothing happens

I'm using Meteor for the first time, and it's fantastic. I never felt so comforted by a language. Then I saw the source of served html pages and it's puzzling and unintelligible and I don't like it. I'm afraid that someone goes in my website, read the source code and judge me 😞

A client hired someone to work on a new feature while we were working on something else. The new guy makes huge commits that we don't have the time to read, really.
I merged and deployed my work only to find that the whole database was wiped. Apparently, the new guy pushed some code that reset the database.
I Spent the rest of the day looking through backups trying to restore the database.

People who literally ask "How to I translate this code to this programming language/framework" without even attempting to read the documentation should burn in a fire.

Not actually solving the problem in an error and instead implementing a workaround thinking "no one's going to read this code anyway" when I'm actually just condemning my future self to a lot of hell.

Are you planning on entering politics?

Because your documentation is dishonest, doesn't mention side effects and is not meant to be read humans workout a law degree.
Your code on the other hand makes me question whether you try to troll us or whether you are actually unable to understand what you were supposed to do.

!rant

Just read an article about a blind sofftware developer, who is proficient in way more technologies then me, for example.

He can use certain screen reader and code edor combo to read out the text, and also something called refreshable braille display.

This is so insiprational and only goes to show that there is no excuse whatsoever for a person NOT to learn software developing...

This is how my coworker does code reviews... imagine comment on a line of code:

"Oh why does this not do this and that.
Edit: Oh I've read few lines below, now I understand. But this may break when this and that.
Edit: Nevermind I realized, that never happens, forget about it."

Let me just emphasise, that this is single comment, so it's basically editted multiple times, before submition.

Like wtf, just delete the comment then?!

Is it just me or are there others who like programming and enjoy the work but just can't do it all day. After 10 hours I don't even want to look at a screen much less code more or read about it.

Guess fullstack is now the trending thing. Read a book on javascript and code examples in the book, do same thing with python or any other backend.
As soon as you are done, add fullstack to your bio.

So many newbies following this path. Coding up alot of examples with no real depth in any particular language.

A company I work with are reluctant to change their hosting provider until the end of their hosting term. (Which may be a perfect reason as it's paid for)

The website goes down everyday!!!! Not to forget it's a popular magazine website!

Here are the new relic emails at 1 minute intervals:
- HTTP 500 Response Code
- HTTP 508 Response Code
- NetworkError: Read timed out
- Connect to domain:80 failed: connection timed out

The University Struggle: when you want to actually code and learn your major but you have an English essay, a Spanish project, chemistry homework, and a book to read all within two days.
.
.
.
Not to mention my actual computer science classes don't teach anything useful in terms of programming

On a shitty day where your brain doesn't work, have you ever looked at some code you wrote, and actually get intimidated by whatever version of you wrote that? After stumbling around most of the day, read some beautiful code, I admired it, then realized, holy shit, I wrote this?

"Yeah, I don't know who that was, it looks great, how the fuck did I do that, and will I ever be able to do it again"

Like, I don't think I can, definitely not today, write anything even close to that.

bleh.

Had to explain for 30 minutes to a consultant why:
1. registering a the container in the container.
2. writing abstraction for the container to use the abstraction of the container internally.
3. doing service locator thus hiding dependences.
4. having your business logic code know about DI.
5. writing log4net in a massively over complicated manner just because you didn't read the fucking manual.
6. coping code from github into our source.

are just wrong.

I read this rant on Quora. Is this true ?

“The IT industry has devolved into a gigantic ponzi scam built on exploitation and BS. Quality of solution and quality of work was replaced with a ‘Does it work now?’ approach with zero contingency.
And the fact that geeks and nerds are naive only helps the white collar crooks to exploit them as code monkeys.”

Load a medium post. Wait for the entire junk to download. Or stop the loading if you just want to read the text content

But Medium has other ideas. Hook to the cancel event, show a useless page which only has the reload link. And why would it trigger the HTTP 500 status code to be sent? 🤔

joined blind today...

i don't see smart engineers...

all i see is a bunch of scared sheep blathering around and complaining and wondering why a job in a capitalist society isn't 100% secure all the time...

get off leet code for once and read a damn history book

🤡🤡🤡🤡🤡🤡

Been trying to update some really old C++ piece of code.
And all the comments and variable names are in FR*NCH.
Apparently they didn't had accents in the keyboards back then, because they used stars instead.
Makes it really hard to tell commented code from French comments.

Obs: I don't speak nor can read French. Neither does anyone in my team.

I hate the overuse of arrow function everywhere even for super long expression. that `function` should fit to them more comfortably .

writer of code should aware that it take three time more to read expiration with arrow function inside

So, today I've read a study that says that chocolate '' improves brain function ". Bullshit. What improves brain function is having a glass of scotch while programming. Damn, I even write code faster. The problem is the morning after when I re-read my programm. I really didn't thought I knew mandarin.

When having to fix parts from an other programmer's code, do NOT concentrate on the small code expected to be wrong, instead read and understand the whole program around it!

Best practice:
1) Why is this code here
2) What does this code do
3) How does the code solve the problem

(just happened to me 😅)

Anyone else get called cute nicknames working in IT?

My favourite is one of the VPs at my company calls me a warlock, because I can read code that he calls "archaic scribble"

If you read some react tutorials, weaseled your way through the interview and think your code now is waka flocka flame, I’m gonna waka flocka fire you. Here’s an autograph for your next employer, I wrote it on a starter cap.

So I wrote the script for the GAL in WinCupl for our project. I used the operators: ! for NOT, * for AND, + for OR

me: *writes code*
me: *compiles it*
compiler: error, unknown operation.
me: wtf but thats how its done, isnt it?
friend: u used the wrong operators. didnt u read the manual?
me: smh i didnt, i invented the syntax xD

lesson learned: always read manual first before writing it directly without knowing the syntax

The catharsis of deleting code that is difficult to read, clashing with the agony of deleting code that was difficult to write.

So this is the case I have not coded in a long while and was actually starting to miss it. I was LITRALLY considiring starting to code again, then i went on devrant and read about two rants and you know what? Im good i dont wanna start code again

Classmate: I'm done with this

I read his code

Me: Good. But could you make that a little bit more.. readable?

Classmate: Eh..what?

Me: Or use one or two lists less.. and the naming

Classmate: But I need them all!

It's a square around a coordinate within given borders, not rocket science.

I came to a point where I expect the computer can read my mind and suggest keyword accordingly, be it in code editor, terminal or word editor. That level of laziness. 😂

It's a Monday, I've been trying to fix a bug since the morning, I cannot read or write any code. I tried to review a PR, still cannot read the code. Getting frustrated by the slightest problem.

When your 'business-minded' friend tells you that you'll never be able to understand and see the future and the power of [buzzword] because you only know how to code...

... and then comes to you an hour later telling you that Bitcoin and blockchain is the same thing & will change the world because he read it somewhere on techcrunch

USING FUNCTIONS MMAKES MY CODE EASER TO READ BUT FOR THE SAKE OF EVREYTHING IBM AND LINUX DOING NETWORKING FUNCTIONS WITH MORE THAN ONE JOB FEELS LIKE RIPPING YOUR TOENAILS OFF!

Ffs, idiot comes to my PR, that didn’t have anything to do with him (he’s not even part of the team) trying to lecture me without bothering to understand the changes and the context.

I wish I could have replied “next time, I’d recommend you to take your head out of your ass first, and read the goddamn code. It will be a better use of your time than writing this nonsense.”

*Task too simple but says "discuss about it"*

*I'm weary of its simplicity, it seems deceptive*

Me: hey, about this thing to discuss, what about it? Is there something I need to know about that I don't?

Boss: read the code

*I'm now even more weary of the task*

I find dynamically typed language a lot easier to read and understand than statically typed language.

What's up with all these interfaces, types and abstractions, its just too much!

I do want structure when writing code, but also the flexibility to test things without the f*** interface/type errors!!!

Got asked by a coworker for some help, looked at the code and told him it could be written better and show him the example.
His reply : "It's not easy to read for me"
That was ok but then, now here's the kicker, he asked another coworker to come and see which was easier to read.
You did what mate?
So of course i got pissed and went out for a smoke just to return to see my version being used.
WHY THE FUCK DID YOU ARGUE ABOUT READABILITY IF YOU"RE GOING TO USE IT ANYWAY???
Fuken fuk, never again am i going to offer optimization support to people.

Two things actually bad I do :
* Put some printing lines everywhere to debug, and then, debug.

* A syntax than can be pretty bad if not handled properly :

if (your test)
do_something();

I actually always put a tabulation to see the hierarchy and break lines, which is not optimized AT ALL but help me to read, and I hope helps other to read too.
But that's a bad habit tho if you have bad presentation of your code (which I don't have, given how people compliments my code presentation)

Another small update on my games modding stuff...

Currently building a command line tool to pack the game data, currently have a working sprite packer and am able to actually read data from the packed file and export all images byte for byte... Holy shit I might be able to actually do this!

Let me know if anyone might be interested in seeing a demo or some very unclean source code!

The day I read The Simulation Argument, by Nick Bostrom, a thought popped into my mind: "if we are made of code, maybe there are ways to hack life as you would hack some random program", I started thinking privilege escalation over the simulation, buffer overflow, picking signals as if I was eavesdropping... it was an epiphany and also fun

Stating the obvious when writing comments. 🙈

I used to this when I was starting to learn how to code and let someone read it, 'cause it's better to have comments than nothing, right? 😂 I was wrong.

But that led me to improve writing informative comments and self-documenting codes.

I read the source code of a guy who decided to name his variables, functions, and comments in Spanish which is not a language I'm familiar with. So I need to first translate the code into English and then understand what it does.

Can't decide between the guy that used gedit to code and the guy who wouldn't read the documentation.
Wait, that was the same guy!

Someone at work asks boss something stupid. He gets mad and says "omg don't they teach you anything at school?" and proceeds to give us all a pop quiz... On paper... Then tries to read all the code pieces like a lecturer.

Anyone else notice that the error checking in Visual Studio sucks sometimes? I'll see the error pop up in the editor, read what it's complaining about, double check all the code, think for a minute, get confused about it, comment out some stuff - wait no, it wasn't that, uncomment it....

then save the file and it rescans. Boom, error gone. It was just a phantom error wasting my time.

music, and ranting against youtube for their weird autoplay features. How in the world can they go from Korn - Twisted transistor to Bonjovi ????

Beer at night, that really helps me, except after the 4th, i start to make shit code, and read devrant even more xD

If I had a dev superpower, it'd be to put myself in the exact mindset of the author of the code I read, at will, so even the comments that never got written would be understood.

I would learn so much, about code && people!

When you can't read your own code the day after you write it

After a few months of working in an actually well coded project, I'm back in the one where I find abominations like this every day:
boolean result=false;
<do stuff>
if(<condition>){
<do stuff>
return true;
}
<do stuff>
return result;

Do they even read their code before submitting?

Finally got my first dev job. I am looking at the code base for my company. And it’s like I know how to code in this language. But I don’t know half of the advanced shit they’re doing. I understand they have more experience than me. But I’m just not sure how to catch up to them. Or be even on the same level as them? I guess just more out of office learning?

I can read what they’re putting in the code and understand how it works. But like how they came up with it I have no clue. I guess I’ll learn over time and have to put in some extra man hours.

nested ternary operators

like/dislike?

I used to hate them cuz I would have to break them apart just to understand them, but now I use ternary operators so much, nesting at least one level is ok for me.

but i'm the only person that reads my code, what's the concensus.. nesting one level bad?

I wouldn't want someone reviewing my code if they couldn't wrap their head around a simple ternary, so if only myself or people more experienced than myself will ever read them, then fuck it, i'm using them

Reading code takes time!

Everytime I read:
"var" or "auto" Add: 10s
- Just use the type

Everytime I read:
if(Expression1 && Expression() ? GetNumber() : 0 > 0) Add: 30s
- Just write two if statements or create two bools the line above.

Everytime I read:
delegate = () => {} Add another 5 minutes of reading time.
- Just write a separate function for it. It helps with searching and understand what it does

Please code like the person that needs to check your code or change it just knows basic coding skills and logics.

I do know all these concepts I just never use them because it makes the code unreadable. hard to follow, mistakes that can happen everywhere. difficult to search.

And it frustrates that I need to read 10 extra lines to understand code flow or hover my mouse in an IDE to figure out what type object it is.

It's properly just me... I just like clean readable code. that is logical and failsafe and strict and deterministic with its behavior

>Working on code
>Shit works as intended first try, nice
>Goes to play strange bootleg Gameboy Color ROM sent by a friend
>ROM immediately fucking dies
wtf.svg
>Pop emulator's debugger
we're executing from VRAM, stack's firmly embedded in ROM
>why
>Add execution breakpoint to entrypoint of game, restart emulated system (because i'm actually using the legit bios i hacked so it allows null/corrupted games to run)
>Step through everything, everything goes well until all of a sudden we call a function and shit hits the goddamn fan
well we have the culprit
>step through subroutine
if <unused_byte_in_HRAM> != 0 then stackPointer+=32;tryAgain();else return
>***y***
>Realize this is using a bootleg Memory Bank Controller with hard-backed encryption so none of the bytes executed or read as data are the right byte
>Find emulator that'll handle the jank MBC
>read code to try and figure out how it works
if checksumExtendedLogoBlob == some_number then set MBC_Bootleg1 else if checksumExtendedLogoBlob == some_other_number then set MBC_Bootleg2 else if...
>of course
>Spend 10 minutes finding the right bootleg MBC
>code shows 8 possible tables for real bit order based on some value in the cart header
>look for code that gets this value
>not in the header
>not in ANY header in this 1000+ file emulator
>not in any related cpp files???
>get desperate
>email author
>"Delivery failed: email doesn't exist"

fuck me i guess

I'm thinking of designing a programming language.

I want it to have easy to read syntax like python. Inheritance and interfaces like java. More advanced concepts like pointers and memory management like c++.

I was originally going to write my own compiler but I figured it's not worth reinventing the wheel. So the current plan is to basically just create a parser that turns a source file into c++ code and then that is compiled with g++. The only problem I can think of with that is catching runtime errors.

How does this language sound?

My purpose is to have a language that is as easy to read as python but with the speed of a compiled program and the ability to use it for embedded projects. I feel like reading larger C++ projects can be quite time consuming. So I figure the trade off of taking a little longer to write the code to make it more obvious what is going on is better than having a lot of syntax that can be tough to walk though the logic of (I find this often with c and c++, not like I don't figure it out but It definitely takes longer than it does to read and understand python)

I hate arrow functions in ES6! Whenever I see them, I get acute code dyslexia and can't read shit. What the fuck is wrong with writing function, why change it for some unreadable series of symbols?

I just read about the 'Learn to Code' nonsense. It seems some journalists told coal miners to learn coding for a living. Wtf.. As a person doing formal CS education after 1 year of work, i take offense for that comment. Coding jobs are dragged to the ground by these comments which imply that coding is a no skill, for everyone job. Opinions ?