I find it hard to trust code school's courses when they use green as the color for error.

Person: I want to learn to code neural networks and cool AI stuff.

Me: Look into Python or Lua.

Person: Those are too hard, I'm going to use HTML instead.

I got out of there as fast as I could. 😅

Real programmers don't comment their code. It was hard to write, it should be hard to understand.

Reading devRant feed is so fucking hard nowadays. Every other rant is about Windows rebooting, Google being evil, Quantum beating Chrome, M$ users being cunts and all these fanboy shits.

Fucking hell. Write some actual code and rant about some solid problems rather than being a stupid fanboy.

Whenever I'm starting to think that my job is hard, I always recall that someone somewhere had to ensure their code compatibility with Nintendo 3DS browser

A wise man once said:

Real programmers don't comment their code. If it was hard to write, it should be hard to understand.

😂😁

Why is it so hard to code when you bleed. T_T
I just can't.

So my brother had a school project for which he got an 9. I looked at this code and saw this comment. I laughed so hard. 😂

Wtf Microsoft...

Found out the hard way that copying a line of code from Teams chat will sometimes convert the spaces into unrecognized ASCII char.

Spent a few hours yesterday to fix the bad chars.
🤡👍

I suck at maths. Hard. But i can still write proper code. There, i said it.

Was watching a Chinese movie and there's a scene where someone is getting hacked, and this is the fucking code that they are show as the "hacking code". How hard would it have been to find something more legitimate than this?

If I hadn't had a few $0.69 hamburgers from McDonald's today, I would be more upset.

Everyone generally agrees code reviews are a good idea right? And some form of testing is kinda a requirement before releasing.

Nope not my boss at the moment. None of my work has been checked in any way but is going out to thousands of users.

If I take the heat for bugs I'm gonna hit back so hard

How do you salvage a really hard question on a whiteboard interview?

Ans: "I'm sorry, I don't code on light theme"!

Via reddit user csquestions5583292

For all those who hard coded 2017 in their code don't forget to update it 😋

PS. I actually know people who have

My first dev job was to code a minecraft plugin that was so simple but I made it sound super hard. The guy who bought it from me thought I was some professinal plugin maker so he paid me 100 swedish kronor for a plugin he could get for free ☺️

I am officially a retard.

I was DOing hard refresh multiple time and making changes on the code.

nothing seems to happen.

after quite a while, I realized I was refreshing the deployed site and not the local one.

kill me.

!rant

My girlfriend brought me her laptop at the hospital so I could code. Hello self project.

Rant

It is fucking hard to type while being plugged from fucking everywhere!

Client: Hi Johny, we finnaly finished design of our eshop. Half of year of hard work. Can you code it in week? We have deadline. :(
I: Sure, i can code in speed of light.
Client: How about money?
I: Tripple of sallary.
Client: What?
I: My sallary also grow in speed of light.

Some clients can not understand they can't throw shits on my head. Take it, hire someone else or stop giving mi impossible conditions.

My colleagues broke down our AWS account by hard coding the AWS access API keys and pushing the same code to a public repository. This took down our system for nearly 3 days.

IF YOU HARD CODE URLS INTO YOUR CODE I WILL HARD CODE MY FIST INTO YOUR FACE

Him: You can code, right?
Me: Of course,why
Him: I want to start promoting my (very crappy) music, I need you to –
Me: No!
Him: But, I just –
Me: I already said No.Never gonna happen.
Him: I get it.You really can't code,you just pretend to.A simple website can't be that hard for you if you knew.
Me:(Pushing him out) Nice try.

Manager: Hi, here is component X with 200k lines of code. Can you go through the code and see if you can implement component Y using component X?

Me: What does component X do?

Manager: I don't know.

Me: Is there a design docs for it?

Manager: I don't know. Can you check? Let me know when it is done.

*Wondering if I should joke and say "Oh management, hard job huh?"*

*Remembering how life is fucked up unfair and I need food to survive and house to live in and follow the society's rules and work hard to make the rich richer and shove money into their fat belly of greed...*

Me: OK.

Hunted a bug for 8 hours, thinking it was a problem in my code....

Found out it was someone else's code generator that injected the bug...

Contacted the concerned dev... Had to convince him for another 3 hours that it was his change to the code that caused the issue. He is still sure that his change can't break the code...... What the fuck are you..? A fucking God programmer who never makes mistakes??

I mean how hard is it to just accept when I just proved it to you??

Me: Taking online course for programming. Think it's not that hard.

PC: Coded programm runs good like in the tutorial.

Me: Wow I can code now.

Just printed "Hello World"

Shit code. I've done it, you've done it, we've all done it. Just keep working hard and improving. Eventually, you'll be writing better... shit code.

Sometimes it works... :)

1. Refactor shitty code because it is hard to maintain
2. Rant about how can someone write a code like that
3. Check commit log to see who is the person to blame
4. Found out that's me

Code with syntax coloring fascinates my young nephew, so after I commit and push, I let him do his thing then later I do a
git reset HEAD --hard

I dont date

I code

Hard

Being different is not a crime, and people who tell you it is are jealous that you've picked up a skill they never in their wildest dreams could acquire.

You can code. They cannot. That is pretty damn cool.

-learn python the hard way

Lately I've been losing sleep dreaming about how to fix my code, but client I have been praying hard to make you happy 😜😜

Hands.
Imagine how hard typing could be without hands.
"Look Mom!! No hands"
*bashing head on memeboard to code*
*best tool ever*

Pastebin, I know my code really sucks sometimes, but did you have to go *that* hard on me?

Is good code the same as clean code?

Clean code is hard to follow all the way through

Making a Package Manager from Scratch is hard.

Making a Scratch-like education coding software in XAML is hard.

Setting up a server with zero knowledge is hard.

Creating a new file extension for my project and making it work is hard.

But, as a student,

studying and coding is the hardest thing.

Same 24 hours for everyone, and I should code as well as study.

Time.

The most precious thing in Earth.

==========================================

NASA dislikes this rant.

clean_air_rocks dislikes this rant.

no_suicide dislikes this rant.

students_who_study_and_code_and_wants_to_do_everything loves this rant.

Submitted my last pull request, said farewell to my team today... *weeping*... haven't realized it would be so hard. Oh, well, best of luck my friends, and keep my code running ;)

In an interview, when you throw a simple piece of code to a candidate...

Candidate: ...

ME: (maybe I'm too hard on them)

Candidate: ...

ME: (ok, I definitively have to simplify this little pattern example)

Candidate: ...

ME: ...explaining the short piece of code and give'm the answer

Candidate: haaaaa that's what I was thinking but I used that long time ago...

ME: (Yeah... nice try)

Non-dev colleague: "You won't understand how hard is my job until you walk in my shoes."
Me thinks: "I don't think so, but my code probably will."

I just wrote this piece of code. Without googling. Call me regex king!
But in fact regex is not that hard, you just have to learn the syntax 😄

17 minutes without single break. That was longest nightmare for me. I had to write 6 lines of code... You know how that feels. My fingers were bleeding and my eyes were burning. Oh maan, I don't even want to remember that hard days.

Wrote a cpp semester project where i had to develop school management system.
The code was spaghetti and horrible with frightening OOP implementation but it was beautifully written with comments and 🐫 Casing.
Submitted the program and examiner rejected it while saying that i had copied it from else where and i could never write a beauty code like that .

You dumb 💩! Don't you know other basis to reject a person's hard-work

My previous manager: "Your code should hard to read, so our work is cant stolen by everyone".
Me: "Why?"
My previous manager: "Just do it"
Me: "Okay"

So, anyone can answer my 'Why?' question?

P.S: My previous Manager is PHP Programmer

Isn't it lovely when someone wants feature X and Y and one is five minutes (and mostly CSS) and the other one is hundreds of hours of backend code.

"I don't want to know, just make it happen. Jeez how hard can it be, it's just a new button"

Sad. Got a new job. Apparently, readable code is not a priority. My suggestions were being ignored. Does the benefits of condensing an if-else to a simple one-line return statement really that hard to understand? Does making clean and readable code should be an optional thing to consider? It doesn't help that I'm the youngest, they felt like I don't have enough street cred. I'm starting to hate my job.

Am I the only one? When you pushing hard in the night, to finish some code; after you done, thinking to sleep, then your stomach reminds you - there's something called eating.

When I saw hard coded credentials in the code repo.

C : Cool (for me)

Java : Just A Variety Available (uhm.. no hard feelings java lovers)

Python : Please .. You THink On Nothing (You literally think on nothing xD )

JavaScript : Join A Very Attractive , Sophisticated Code , Reactive In Particular Time (hmm...that took a lotta time)

"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian Kernighan

IS IT REALLY SO FUCKING HARD TO CARE ABOUT CODE QUALITY AND READABILITY FFS

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. :)

One of our senior dev enjoys berating the other devs because they don't check-in code according to his schedule (once a day, once an hour..he flip-flops a lot), then when they do, he 'reviews' their code, beating them up because of incomplete features, commented out code..petty..petty nonsense.
Ex. (this occurred couple of weeks ago).

Ralph: "The button click code in this event isn't complete"
Dev: "No, its not, the code in my development branch. You said it was best practice to check in code daily whether the code worked or not. I didn't finish the event last night and ..."
Ralph: "Exactly. Before you check any code into source control, it has to work and be 100% complete. What if someone moved that code into production? What happens if that code got deployed? I'm not even going talk about the lack of unit tests."
Dev: "Uh..well..the code is on the development channel, and I branched the project in my folder ...I didn't think it mattered.."
Ralph: "Ha ha...you see what happens when you don't think...listen..."
- blah blah blah for 10 minutes of hyperbole nonsense of source control check-in 'best practice'

This morning Ralph's computer's hard-drive crashed.
Ralph: "F-k! ..F-k! ... my f-king computer hard drive crashed!"
Me: "Ouch...did you loose anything important?"
Ralph: "A f-king week of code changes."
Me: "You checked everything into source control on Friday ...didn't you?"
Ralph: "F-k no!...I got busy...and...f-k!"
Me: "Look at the bright side, you'll have a good story to tell about the importance of daily check-ins"

Oh...if looks could kill. Karma...you're the best.

every once in a while i put something useless on my code, like an invisible button that randomizes the colors or a stupid message that's hard to find

"Hard code it"

When you have to repeatedly explain that typing out the code is the easy part and deciding on the correct lines of code is the hard part.

I hate it when my classmates don't fucking indent their code properly.
IS IT THAT HARD?

Trying to hire more good devs... it's surprisingly hard. Guy with supposed decade of JavaScript experience fails code test, "I don't really use map function so I don't know it."

R U kidding me

...and yet my "maybe we should consider remote devs" idea isn't getting any traction :/

I rewrote something in clean 20 lines of code, while my coworker had worked hard and ended up with like 80-100 lines. I did not talk to him before I did it, but asked him to review what I did. I still had to learn how to properly work together..

FUCK DJANGO CSRF FRAMEWORK.
THE PERSON THAT BROKE csrf_exempt DECORATOR SHOULD BE PUNISHED BY YEARS OF HARD WORK IN BITCOIN MINE. I DONT KNOW WHO YOU ARE BUT FUCK YOU AND ALL YOUR CODE, I WISH YOU SLOW AND PAINFUL DEBUGGING OF LEGACY, UNDOCUMENTED, PRE-JQUERY IE-FUCKING-6 CODE YOU FUCKITY FUCK!!!

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

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

While working I was munching from a bowl of candy, suddenly realized my face hurt and hard to breathe. Emergency room....
I apparently ate something I'm allergic to while in a code fog.
No idea what it was yet.
Must have been bad code.

Quote of the day
"Writing code without thinking of its architecture is useless in the same way as dreaming about your desires without a plan of achieving them."

That literally hit me hard

Just finished recovering all deleted files from my old hard disks I found in the attic, just for fun.

I was hoping to find some old photos or something. Instead I found my awful old Qt code.

Back when I started the recovery it was sunny and perfectly clear outside. As soon as I found the code the skies went dark and now it’s raining like hell and lightnings are blasting.

Wtf i just summoned

If you search hard enough you’ll find where they copied the code from.

Clicks "Exploitation and Enumeration" category.
Clicks "Python (HARD)" challenge.

"What is a key that passes the code?"

Opens Python file and sees one line of nested lambda expressions spanning 1,846 characters (no spaces)
*Cries*

Today I stop smoking. It's really hard to code... 😡😡😠

While working on generic enterprise code: querying databases, calling third-party APIs and just passing data around, I'm thinking: "PLEASE LET ME DO SOME THINKING, LET ME WORK ON SOME HARD ALGORITHM OR SOMETHING!"

When finally working on 'some hard algorithm or something', I'm thinking: "ARGH! MY HEAD ACHES! GIVE ME RELEASE! LET ME WORK ON SOME MINDLESS ENTERPRISE CODE!"

So.... yeah, making a Scratch clone (with more features) is frustrating and super hard.

Major problems include
- Drag&Drop from listbox to usercontrol - stress level : 3/10
- connect blocks when two blocks are close to each other - stress level : 10/10
- generate live code when there was a change in blocks editor - stress level : 9/10
- write a compiler or some interpreter that converts block code to real c# code - stress level : 10/10
- generate output by calling csc.exe - stress level : 1/10
- make code at least readable - stress level : 7/10

I have a lab at uni where my lab group have to refactor some code from an open source project. We got assigned some Apache project and jfc that code is a mess. Little to no documentation, hard to navigate, tests that you have no idea what it's testing, and so on. On top of that the teacher expects us to spend more time than we have on it. I'll be glad when this course is over :))

TL;DR;

Idiot hard coded database host on the app... Pushed to prod and suddenly shit wasn't working... Took me 10 minutes to figure out what was going on...

Wrote a passive aggressive git message and commited.
Before updating prod my boss turns around to me and the following took place:

Boss: is there any problem with the server?

Me: yes, someone (i know who was ) hard coded the test db IP and it broke the backend.

Boss: oh, but will it affect the mobile app?

Me: well, it won't work but I'm already pushing the fix.

Boss: no..err.. I mean... Will I have to make any change to the mobile app?

Me inside: wtf dude... For real?! Get your shit together...

Me: no. It good, I already fixed it.

Boss: OK. Thanks

TL;DR;

Moron hard coded dB's host and stupid boss can't get shit together nor ask who did it to take precautions...

Anyone else experiencing moments like 'you sit behind a computer all day, how hard can your job be?' or is it just me?? 🤔
I'm getting tired of this shit... Especially when it's comming from a person who relies ob tonns of apps to do their goddamn job.. :/
I'd get it if it was comming from a farmer who actually has to work hard to produce the food for us.. or any of the blue collars..but from white collars?!? Dafuck?! Yeah, I may not be the person writing the code for your precious little apps, but they're written by people just like me, who sit behind a computer all day & code.. :/
Show some respect ya cunts!!

Just noticed my boss turned a nice and beautiful polymorphic code into a fucking hard to maintain switch case that now this mother fucker here has to maintain just because he probably thought it was too hard to understand.

I bet he finds it hard to fuck his wife in any way other than the one she needs to wear a strap on and tear his ass apart...

Why do so many online resources still change quote characters in the code for the curly ones? It's 2023, how hard is it to add a fucking rule to skip conversion inside the <code> blocks?

When you're trying really hard to figure out a problem with your code, but then just realize you've been sitting there for 40 minutes staring at the screen.

So before the Age of JavaScript, when programming was trying to be an engineering discipline, I felt like we were getting close to figuring out what worked and what didn't. We had rules of thumb (more general than Patterns) and code smells.
Then JavaScript came in and no one had time to think about "engineering" anymore. I'm fine with MVP and small iterations, but the disdain I see for making code clean and extendable and improvable is baffling (and annoying). First-time coders might never have had to fix someone else's code, but two weeks in a chair should have fixed that.
It's not that understanding code is so hard (although it can be); understanding the _intent_ is hard. This MVP is great, but when no one had time to document what is actually supposed to happen, programmers have to reverse-engineer the *design*.

Everytime I don't sit in front of my code (and go for a walk or something), I immediately find bugs or things to improve from all the code I've written, IN MY HEAD. If you have a hard time finding bugs, try this, maybe. Might help.

Took me awhile, and 3 reinstalls but I finally got my second hard drive on Linux, Kubuntu with most of the things I use to code here and zsh on powerlevel9k. Yey!

Hey guys.
Do you find it hard to code when depressed or it's only me?

When someone is presenting their code for aspects of a terribly made page.

They know you are proficient in 6 different languages, and then still ask "is it too hard for you".
Holding back my comments, just sitting down and smiling inside.

Until you have written ethereum vm hex code by hand, dont talk to me about hard tasks

When its hard to code, just 'hard code'

My loop checked a variable, then the next 5 nested loops checked it again, then started over. It was a hard coded variable I forgot about.

I just made my code OCD

ask about his game code logic he will rage, ask about how his front end code doing he will rage, talk to him about my server so that his front end code can follow he will rage.. and the end of final project which I merge my code and his code (I need to refactor nearly everything) he said you are very hard communicate. _. fml

Mixing lazy loading with event-based code == events won't be handled because the class won't subscribe to events until it's initialized hours after startup

Thank you, my dear lazy-loading lover, who keeps introducing hard-to-spot bugs everywhere. I wish your hand was as lazy as your code, that would have saved hours of debugging time.

It's hard training fresh grads at work when their minds are already full of themselves. Code written for production is always different from those written for projects.

I see this in code:

bool status;
status = true;

It makes me want to hit things. INLINE THAT SHIT! bool status = true; It's not hard. JFC. And of course I don't have the authority to change it.

Do you think refactoring code adds value?

Pick one:

1. Hard No (Only refactor when there is a dollar value associated with it, i.e new feature depends on it).
2. Somewhat Yes (Futureproof your code, anticipate easiness to build feature requested in future).
3. Yes (Developer happiness, retention and for point 2)

Well create a Googleing machine and infuse it with code words which it automatically searches till the Google AI thinks I am a ( ) programmer and gives me a job offer.this was my last night's dream . How Hard Can it Be?!!!

REAL Programmers Don't //COMMENT their </CODE>.

If it was HARD to WRITE
It Should be HARD to UNDERSTAND

Comment if you "Agreed"

when BFs delete wrong lines of code.

$ gitreset--hard

Most difficult part of a programmer?
-> Naming variable

/** It takes me 2-5 mins to think

When a client tells you to hard code the root creds to their server.

Last day of internship:
"You will not become a developer, at best you will be a code writter".

That struck hard at the time.

Oh my god my brain is hard wired to write c++ in snake case. Spent 4 years doing it. This code base uses camel case.

Damn! Almost three years it must me really hard to code a delete button.

❤️ Swift ❤️
Compiling fails due to many inter-dependent errors (think database deadlocks).
1 - Comment the code that produces the "locking" error.
=> Code compiles.
2 - Uncomment the code that produces the "locking" error.
=> Code compiles.

My peepee hard

a lesson that I learned the hard way: Don't test a code or a library on your master branche, in other words: don't shit where you eat.

I was assigned to maintain the website as full stack dev but the code from backend is horrible previous devs didn't use SOLID principle, DRY, KISS, or Design patterns. I had to adjust from OOP mindset to Procedural its hard to debug in this state.

Never write at the limit of your talents! Remember: debugging is always twice as hard as writing code. And if you write as cleverly as you can, you won't be able to debug it anymore.🧠

Fairly new to Linux, read that vim is a neat editor but hard to learn, good for script editing and such, but why use it over a language specific editor or something like VS Code?

Fucken Designers - Have you ever heard of fucken consistency?

Different looks and feels for the same thing in every single page? Wat the fuck man - I am trying to write clean and modular code for components and you guys are making hard -

Bomb Alert:
Fuck Designers *middle finger*

At first my dad was against it, I'm studying electronics engineering and he didn't want me to code because he is a software developer and he know that in my country it's really hard to make a living out of it. But since he realized that there is not much he can do about it he became really supportive and always review my code to help me improve it.

The frustration that comes to each developer when he tries to write the code structured by thinking through each situations, and your team lead comes and tells you why r you doing so much validations just hard code them we need to release it today client is waiting. After 3-4 months the same team lead goes through the code and shouts at you telling why the he'll you hard coded all these, can't you write the code correctly by thinking through.

I was just commiting some code on GitHub for school tomorrow and I kinda got lost in the commit description..

Ah, it just hit me so hard I had the urge to get it out.. Helped, tho, love you Git

[worst hypothetical dev job]

You know how theres a dedicated person in porn whos job is blowing the actors so they are hard? That, but with writing all the boilerplate code and nothing else.

I literally only wrote one line of code today. Don't ever start your day off by saying, "I think I'll make a quick backup of my primary hard drive."

Legacy code is like overgrown bangs 😋 It's very hard to decide if you have to let it grow out or trim it.

The developer who thinks they are so elite because they make their code hard for anyone else on the team to understand. Especially when they have access to operator overloading.

self <- ~~~cgr

pushing code at 3 AM, so that my manager knows am working late and hard.

Saturdays I like to code and have some beers.

Learned the hard way to wait until the next day to push my changes... 😂

Why has programming become dependency management and third party paid libraries implementation?

I hate it.

I want to code some real hard stuff but everything is already made!

Code of developer's life

int f = 1;
If( life == "smooth")
problems();
else if( life =="hard")
{
problems();
breakup();
}
else
{
while (f = 1)
{
bugs();😣
}
}

Programming when sad...

My dad is acutely ill, and trying to focus on code is so hard! This has happened before, and makes me realize that our normal day job is really taxing mentally...

Already using PhpStorm for 2 years now. Just discovered there was an auto-formatting tool for your code. Could have saved me hours of work. Why is life so hard with me

Chuck Norris writes code reorganizing electrons on his hard drive

I do not understand people who critique Python for using indentation to mark code blcoks. I've seen multiple posts being like "Uhh in Python a missing space breaks everything and it's so hard to find it". Yeah so hard when the interpreter throws a parse error and tells you exactly which line it's on. Let me go back to a bracefest language, misplace a brace halfway through the file, and get told there's a syntax error at the end, and spend a whole two minutes finding it.

FUCKING PROMISE WONT FUCKING RESOLVE SO MY FUCKING CODE KEEPS FUCKING RETURNING A FUCKING NULL VALUE FOR FUCKING FUCKS SAKE IT REALLY SHOULDNT BE THIS FUCKING HARD TO RESOLVE A FUCKING PROMISE WITHOUT FUCKING CRASHING MY GODDAMN SERVER

Best : Finally getting my first internship after teaching myself how to code.

Worst : Was a preeeeeeetty shitty internship. I know you'll say all internships are hard BUT, this one was on another level.

We code hard in these cubicles

My style’s nerd-chic, I’m a programmin’ freak

We code hard in these cubicles

Only two hours to your deadline?

Don’t sweat my technique.

Sippin’ morning coffee with that JAVA swirl.

Born to code; my first words were “Hello World”

Since 95, been JAVA codin’ stayin’ proud

Started on floppy disks, now we take it to the cloud.

On my desktop, JAVA’s what’s bobbin’ and weavin’

We got another winning app before I get to OddEven.

Blazin’ code like a forest fire, climbin’ a tree

Setting standards like I Triple E….
Boot it on up, I use the force like Luke,

Got so much love for my homeboy Duke.

GNU Public Licensed, it’s open source,

Stop by my desk when you need a crash course

Written once and my script runs anywhere,

Straight thuggin’, mean muggin’ in my Aeron chair.

All the best lines of code, you know I wrote ‘em

I’ll run you out of town on your dial-up modem.

Cause…
We code hard in these cubicles

Me and my crew code hyphy hardcore

We code hard in these cubicles

It’s been more than 10 years since I’ve seen the 404.

Inheriting a project can make me go beeee-serk

Ain’t got four hours to transfer their Framework.

The cleaners killed the lights, Man, that ain’t nice,

Gonna knock this program out, just like Kimbo Slice

I program all night, just like a champ,

Look alive under this IKEA lamp.

I code HARDER in the midnight hour,

E7 on the vending machine fuels my power.

Ps3 to Smartphones, our code use never ends,

JAVA’s there when I beat you in “Words with Friends”.

My developing skills are so fresh please discuss,

You better step your game up on that C++.

We know better than to use Dot N-E-T,

Even Dan Brown can’t code as hard as me.

You know JAVA’s gettin’ bigger, that’s a promise not a threat,

Let me code it on your brain

We code hard in these cubicles,

it’s the core component…of what we implement.

We code hard in these cubicles,
Straight to your JAVA Runtime Environment.

We code hard in these cubicles,
Keep the syntax light and the algorithm tight.

We code hard in these cubicles,

Gotta use JAVA if it’s gonna run right.

We code hard in these cubicles

JAVA keeps adapting, you know it’s built to last.

We code hard in these cubicles,

Robust and secure, so our swag’s on blast

CODE HARD

Trying to get an app written on my home pc running on a different one... Without the source code...

Fixed a config issue but then run into a hard coded path I forgot to put into the configs...

Just going through some old code from git repo's and code examples and I have a message to every dev out there after seeing some of the code quality...

Never... ever... ever fucking give variables with names like vx, tr and sq.

Give your variables names that explain what they are, it is so fucking hard trying to follow code that has 2 letter variable names and there is a special place in hell for you :-)

Spent ten plus years professionally coding, used c, go , python, openwhisk ,docker, kubernetes and God know what else. Now I have to convince those team members who coded so far in their free time that write fucking clean code, avoid dependency on distributed and hard coded configuration, how to build a product
Fuck my life

Being 26 learning to code with intention to do it for a living is hard, I wish I never gave up the first time I attempted to learn a programming language when I was 16 I'd probably be making a shit ton of money...

> do you feel sorry for freelancing contractors
> whose previous client abandoned them
> they ask you to help them fix some trivial bugs in the shitty code
> you believe you can change the world by going overboard by also improving the code quality, along with fixing the bugs
> initialize an empty file where you'll translate the shitty code into a more organized one
> start creating variables and generic functions which can be used in a modular and organized fashion
> meticulously document the first function you write
> realize this is not worth your time
> insert some glue code into the original code which fixes the trivial bugs
> glue code has hard coded values so it adds to the shittiness of the code
> submit the work
> get $$$

Pulled an all nighter for a project, the next thing i know i am demonstrating my code with the error message i forgot to change which was houston we got a problem, i felt so weird and i was laughing very hard after the project presentation

Just had to debug a piece of code for the 5th time today and I'm starting to lose my mind. Why do programmers insist on using single-letter variable names?! Is it really that hard to come up with something more descriptive? I mean, I get it, "x" is easy to type, but so is "counter" or "iterations". Does anyone else feel like they're just constantly fighting a losing battle against the entropy of poorly written code?

Need a C++ partner..

I'm self taught developer and it's kinda hard to understand the code of your own.. since c++ is not an easy language to master I need partner whom I can easily discuss code and topics of c++. I'm in slack too and it's great community .. has people who always willing to help you out.. but the thing is it's really weird to ask simple question there again and again.. so i wanna have some partner to discuss C++ code easily..

Worst is when you lost your mojo and you wanting really hard to code something

code is emotional because it represents ideas, collaboration, and hard work. On the other hand, code is completely cold, instructional, and meaningless.

I think both of these are true.

Experienced programmer:
Code works in head; code almost works in computer; code never works with client.
Beginner programmer:
Code almost works in head; code never works in computer; code will never work with client.
Long story short: it's hard to begin but when you let the code flow, you became a programmer

Machine learning is hard! Spent a whole day with Weka and it's Neural Networks. God my brain. There is too much to know before being really equipped to use this tool... especially from code.

"It was hard to code so it should be hard to understand."

- my former boss who did never document any code

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.

What the fuck did I drunk code last night.. git reset --hard to the rescue.

Why are you trying to multithreaded c++ file i/o? If you can't write c++ code that's faster than your hard drive, please just don't write c++.

Literally no complex calculations, just some insane string formatting.

Is it so hard for other people to write code as if there will be other eyes watching? When will people learn that a programming language is what bridges the communication gap between humans and machines? If I can't follow your code, you wrote it poorly. Period. At least document what the hell is going on. Be considerate of the next person. Unbelievable.

Code reviewer tried as hard as possible to find issues in my commits.

After timereportimg 3 hours extra in a small ticket, he concluded we needed to try a different approach, even if code was OK? Why?

Simply because it was his idea and his idea is better. The reviewer needs to feel his superiority by any means.

Title: The problem with "good enough" code

Body:

I'm a software developer, and I've seen my fair share of "good enough" code. You know the kind of code I'm talking about: it works, but it's not pretty, and it's not very maintainable.

The problem with "good enough" code is that it's a slippery slope. Once you start writing "good enough" code, it's easy to fall into the trap of always taking the easy way out.

Before you know it, your code is a mess of hacks and workarounds. It's hard to understand, it's hard to maintain, and it's a nightmare to debug.

I've seen projects go down in flames because of "good enough" code. The code was so bad that it was impossible to fix, and the project had to be scrapped.

I'm not saying that you should never write "good enough" code. Sometimes, you just need to get something working, and you don't have the time or resources to do it perfectly.

But if you're going to write "good enough" code, you need to be aware of the risks. And you need to make sure that you're only writing "good enough" code for a short period of time.

Once you have a working prototype, you need to start refactoring your code and making it better. You need to make it more readable, more maintainable, and more testable.

If you don't, you'll eventually regret it. Your code will become a liability, and it will hold you back.

So next time you're tempted to write "good enough" code, think twice. It might save you some time in the short term, but it will cost you in the long run.

1. start up my monitors, have one monitor streaming news while the other one is browsing devRant.

2. drink an ungodly amount of caffeine

3. crash so hard that I have an excuse not to code and go back to bed.

that BS thing you do when your too lazy to code and just copied a code from an existing class and renamed the vars even if it does not work or not being used just to show your boss that your working hard as f*

Can you force yourself to code? I have a hard time doing that. I kind of have to feel like it.

i always assume that my code is right so when the compiler gives an error, its hard for me to find out why it gives an error and why it doesnt work. my mind is too convinced that it is correct.

i guess i have to sleep it off 😴 maybe tomorrow it will be easier to fix

As I mentioned in previous rants
The company that I work for is very loud and noisy, making it really hard to code.

First day in new office, bigger space in the same building....PEOPLE HAVE COMPLAINED ABOUT THE NOISE AND LOUDNESS

FIRST. DAY.

Sorry guys, I have complained too they dont care.

the two code review personality types

review activity:

- dev A: requests code review, sets dev B and dev c (myself) as reviewers

 - dev C comments: this review is marked with a complexity > 9000, touches > 20 files and has zero comments... also there's a lot of refactoring going on, making it hard for me to tell what the actual relevant changes are. can you please add more comments to this review?

 - dev B (10 mins later): approved review

I'm doing a code review on a huge feature, basically touching every part of our authorization logic, and man... It's like my colleague writes his code to be as hard to read as possible. He's 60+ and you'd think he'd have learned how to write good and clear code, but nope. "Let's make it cool cool and I look like I'm a genius. And if I can spend 3 keystrokes less on a function I'm happy". Fuck me.

My biggest influence on coding style is:
"If code make reviewer puke, code bad."

In all seriousness though, I think the biggest influence is seeing messy code and not trying to replicate that.
I think every code file, however ugly it is, tells you a story. Maybe the coder was less experienced, maybe it was written during crunch or the coder is an enterprise software engineer who has to make a factory for everything and everything is generic.
In my opinion there is no perfect code style. You do what's required and hopefully in your best ability, and, as a bonus, think of the person who has to look at your code next...

For me it's kind of hard to tell whether my code is good. I have no reviewer in the company, which brings the risk of writing code so only you understand it... but so far it has worked and I've definitely seen worse than my 1 year old files. 😄

I am already tired before even looking at this code.

Looking at your code makes me cry.

I can insult myself whole day but it won’t be enough to survive looking at your coding style.

If cpu could talk it would ask for heater removal because your code depresses it so much.

Looking at your code makes my monitor burn out.

Downloading your code makes my hard drive stop.

And my favorite:
You’re already good developer so now stop writing and appoint as manager / tester.

I'm burned out and yet I'm trying hard to do anything useful that I push uncompleted code in different new projects without a README file or description of any kind.

When programmers try too hard to reuse everything that already exists on their code.

All code and no tests makes a software buggy, hard to maintain and a pain in the ass to work with.

I seriously hate ppl that write vague variables name. It makes so hard for me to understand ur code !

How hard can it be to refactor this 170 lines file?

- a single “data” variable used to store everything
- arrays inside arrays inside arrays (see prev point)
- operations with a lot of obscure sideEffects
- $data[] = something (which in magic php land means $data.enqueue()

Why is such… biological matter… even allowed to code? Fucker’s pretending they are a senior for four years: how in hell didn’t they learn to code in this timeframe?

I feel so fucking proud after finally finishing what i started coding

I delayed so many days and procrastinated because it seemed way too fucking hard to code it

But i sat down and forced myself to do it despite it being hard

Yes i broke my fucking head trying to figure it out but i somehow figured it out

And it is finally fucking done

Fucking good Lord thank you

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 really fucked up thinking I had all the time in the world.
I also wrote very shitty code but I know that would've been hard to avoid, so it's cool.

I really just hate Apple development. Xcode blows hard ass and if you are a person like me who has 0 Apple devices and has to go to the fucking school labs to code then why wouldn't you hate apple development. It's really the lack of being able to code outside a fucking Mac cause its just pointlessly limiting, fuck you Apple.

You know you're going to have a great day when your transpiler is spitting out an error that you hard coded to ignore and don't have access to its source code for a couple days .-.

Hey everyone!

Me and my team have been working very hard to create this programming language which people thought impossible to make. After years of work/research and hard-work we are now announcing the first beta release of this programming language. This programming language which we call "English_Code" is going to be revolutionary since it understands any English sentences. Now the programmers can finally code in English without learning the if-else, loops and other syntax keywords. Errors will be shown in pure English and your managers can now understand your code.

Anyway, let us know what you think, and we hope you enjoy!

You will get far more rejections than acceptance. A lot of the time it has more to do with the interviewer and not the candidate (assuming the candidate is a genuine hard worker). The job search process is similar in this regard to finding a mate or compiling your code.

Keep moving forward!

Every week since I started the company:

Boss "We need a special feed of resources for this customer."
We say "Great let's build support for custom feeds."
Boss says "Could we just hard code that resource in really quickly?"

This week:
Boss says "Could you make a system that dynamically let's me know what resources has been hard-coded in all special feeds, and that alerts me when a resource goes offline".

Now what should we respond?
Help us out! Best suggestion might turn in to an email to boss..

How hard it is percieved by management to do something in code is proportional to whether or not it's a task that sales or the CEO wants, versus what the developers need. Developers want to rewrite something, or fix infrastructure? Too much work can't justify it. Sales wants to clone Google Search? We'll expect it by next month.

I want to spend about 10 minutes a day in to small code brain teasors.

I know there are apps like SoloLearn. I don't want to learn hard new concepts but rather just maintain the basic ones. I am looking for an app that gives me quizes, not just informational text

What would u recommend?

I have a really slow machine and it's running Ubuntu, so annoying. I launch VS Code and Chrome, 30mins in and it fkn hangs, then I have to hard reboot.

I'm so tired of eating spaghetti everyday, sometimes i wish i could just solo the projects, iI would rather have a hard time writing my code rather than fixing others.

Who else shouts at their code when you are trial and erroring it? And by shout I mean hard core yell at, insult and maybe even spit at the screen.

Ladder to success - everytime you write a successfull code and it doesn't compile slap yourself so hard that your hand debugs that code automatically. I am red.

When asking for help:
Sending screenshots or worse, use their phone to take a photo of their screens instead of copy pasting the code.

As if reading their code isn't hard enough already. Ugh

I have a really hard time staying focused reading through legacy code. As a result, I often miss many subtle details about how a given system is currently functioning.

How do I become good with functional features(map,reduce,filter,zip,flatmap) in Javascript and Python?

It feels so alien. I'm so used to writing plain old loops.
Reading and undersranding this kind of style in other people's code is really hard for me, especially if all this is happeining on the same line.

Network code is hard. Events come all the time and it's really difficult to account for all orderings and uncanny timings. Have you got any advice, book or paper about it that I should read?
I'm using node and websockets btw.

Run it again,Even if you didn't change anything !

My first job as a student was at the institute. I was working realy hard. Doing my best. Closing issues lika a boss. All my code was reviewed by senior.
Two other student has this simple program to make (gui for some functions and some graphs). They have no idea how to make it. Their code was worst than spageti and in four mounths then didn't even come close to the end. Noone even looked at theri code.

We were paid the same money!

If you ever try to learn C++, give C Primer Plus 6th edition book a try. This is one of the best books that are prepared to teach, not tell about C++.

I tried Bjarne's boooks, but damn they are hard to understand, with badly formatted non-monnospace font code examples and terrible technique to teach.

Accidentally ran

$ git reset --hard

On my 2 weeks worth of uncommited code.
Thankfully Intellij has a local history. 😥

Quick question...
Can you guys code without any reference?
I find very hard to memorize all the functions and etc...

Any other devs with PTSD here? Since the trauma I find it hard to focus on programming. Before the trauma I would code on the job, get home and code personal projects for fun. After the trauma I can barely focus on programming for work.
How do you focus?

Brian Kernighan once said that "debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."

Hello devs. This happens to be my first rant. And I got a question to start off.

I'm looking for an existing public/open-source React project which is not too hard to understand and has a good folder/file structure and code structure. Something that gives me an idea of how a good production level code and project should be.

Any recommendation is appreciated. Can be your own project too.
Thank you 😊.

almost end of working day... jobless...

me : *running `uptime` on a server*
*for no reason* : runs `uptime --pretty`

interesting output... ( that I have seen so many times on my personal machine because I have `uptime` aliased to `uptime --pretty` )

*thinks to self* : didn't we create that program that computed a similar output? Wonder if the code is similar...

*brain gets excited about the source code of `uptime`*

goes hunting for the source code of `uptime`... finds it... ( wasn't too hard anyway )

now here I am comparing my code with the source code of `uptime`

what a way to end the day... 🤦‍ FML!

Do you believe that code is inherently hard to read?

Do the hard stuff first. Then everything else looks easy. Make a mess of the code, then fix it and make it efficient.

When your colleagues keep asking you questions about how to code this and that through messenger, and you keep replying them with lmgtfy links. "Was that so hard?"

Life Bugs
====================

What would you define code that's not "Hard coding ?" ---"Soft-coding" ?
Any suggestions?
-_-

I find it really hard to accept that a non-iOS developer rates my performance based on source code he doesn't clearly understand

I downloaded Hive from Vault 8 and got latest thinking I would find some neat things; here’s what I have learned so far:
# Reading others people code is hard
# Code you don’t understand looks “normal”
# No one comments
# If you want to do something cool it has to be in C++ with Python make scripts

Has anyone else looked at it?

We should teach people early on how to collaborate with others in a team atmosphere. It’s hard to get code into production on your own, and once it’s in production it’s not your code anymore, it’s everyone’s. Everyone should have a say.

So android devs dont have a brain to just code the fucking game or app to just flip the screen upside down because its so hard to fap or play when there is a bloody earpiece jack on the bottom right of your phone.

It's​ so hard to find open source contributors, especially for large projects. Lots of people might use what you create, but getting them to contribute code is like pulling teeth sometimes. 😤

When you pick up a codebase from 4 years ago of utter dissaray and static/hard coded in nature.
Then later meet said original developer presenting at a conference on re-useable code.

There is a feeling akin to meeting someone whom you have seen naked...

A new year, a new job.

After a years hard graft learning front end code I finally landed my first dev job!

Even though the job is a while away, there will be nothing stopping me getting there and learning all I can in this industry.

#bosh