Always

TL;DR: Clients are dumb.

Client IT Lead: "Your code isn't working on our website."

Me: "Because you didn't load our code into your website. Do that, and everything works."

CIL: <proposes terrible alternative>

M: "No fix on my end will matter if you don't load our code into your website."

CIL: <more disagreement>

M: "Let me discuss with my team and I'll get back to you."

... later that day, in a follow up meeting with client's team ...

M: "Load our code into your website as was initially intended and everything works fine."

CIL's Boss: "That makes complete sense, and I'm not sure why we weren't doing that from the beginning. Let's make that happen, CIL."

CIL: "Okay."

——

👨🏽‍💻🤷🏽‍♂️🤦🏽‍♂️

Code not working.
Comment out code.
Slowly rewrite it bit by bit till it works again.
Check against commented code.
They're the same.
Wtf.

Seven hours wasted on this shit :/

CS Teacher: *provides shitty code written in (I kid you FUCKING NOT) Microsoft Word, sans font*

Me: *Submits beautiful, fully working and commented code*

Half a point off because I didnt write how many points the assignment was worth at the very top of the code.

ARE YOU FUCKING KIDDING ME YOU CUNT GOBBLER?! YOU JUST **HAD** TO TAKE THAT HALF A POINT OFF, DIDNT YOU? MAYBE YOU'RE INTIMIDATED BY THE FACT I DONT USE MICROSOFT WORD TO WRITE C++?? God, I hope you take a nail gun to the eye.

At customer site with my boss.

Boss: let's check this code which is not working

Me: ok (starting the debugging session)

I found this code, which was failing during the writing on disk for some reasons.

try
{
....
writer.writeline(some data);
....
}
catch(Exception ex)
{
....
}

Boss: ok it fails to write data but we need to, let's manage it like this:

try
{
....
writer.writeline(some data);
....
}
catch(Exception ex)
{
writer.writeline(some data);
....
}

Our company got attacked last month by what i believe was a code time bomb from a ex employee. And it was brutal, website hacked, email server not responding, locked out from database servers. The IT department asked for my help and I was more than happy to do it. Long story short I got every thing back working smoothly. The IT guys ask for a favor to not include this in my monthly progress report. Fine by me. But then they went out and tokd the top management that they are teaching me about the networks and servers so thats why I was working with them last month. Fucking assholes. Not going to help them any more.

Wife - my site is not working, everything in the code looks correct. But it is only throwing me 404 all over

Me - "blaming the teacher for giving bad shit"

Wife after googling - I fixed it, you have forgot to enable .htaccess in the virtualhost

FFS how long have I been this stupid?

So, I'm programming a control system for a prototype aerospace vehicle. You know, the stuff that needs to work to prevent falling out of the sky.

Anyway, test day was today (was -- not anymore). Wiring all the electronics, everything is actuating and works well. Except for one part, a little thruster for stability.

I spent hours - literally, fucking hours - trying to fix the problem. Wrong address? Wrong syntax? I had absolutely no clue what was wrong. Queue the hardware guy, $stupid:

$stupid: "How have you not got it working yet?!"

$me: "I don't know, everything I'm trying isn't working. I've spent hours digging through this code and nothing is fucking working."

$stupid: "Well have you set it up for the new thruster?"

$me: "What...What new thruster?"

$stupid: "Oh, the one we installed this morning, did noone tell you?"

WHY WOULDN'T YOU TELL ME THIS?! COMMUNICATION 101!

Sister comes into my room

"Can you look at moms laptop, it stopped working I'm scared I broke it"

Ask why

"Idk it just stopped working, all I did was install adobe flash player I dont think that could do it could it?"

Top kek

Take a look

"EFI IPV4 0 (error code) failed to boot"

Weird. Enter bios

"Hard drive: [Not detected]"

Well, that's no bueno

Pop open back, hard drive is loose

Pfft, push that fucker back in

Boot -> works

"Mom is going to kill me I broke it im so worried" -> relieved laughter

Adobeflashplayerkilledmyharddrive.jpg

Shook.exe

I was asked to present a code I wrote previously. This was not planned. I shared my screen and presented. Things went well.

One employee asked me to search a particular term which was possibly related to an advance topic in the domain we were working on.

I opened Chrome and the first page had a Quora post: "Why my dull co-workers try to act smart and are not yet fired?".

[silence]

Just last month we finished a big project for a client. The company had their lawyers make a contract to transfer ownership for the website to them.

One of the requirements was to deliver all code in a word file. And just that. In the whole contract was not a word about transfering the production environment to their servers. Or supplying a working version. The files and database. No just the word file.

As of today still wondering what they where planning to do with a word file with hunderds of pages of code.

Offcourse we deliverd a working version to their servers. But why are there people making decisions about things they understand nothing at all.

The recruiter in call today is a spoilt brat .

I answer him wether am I know PHP. So I show him my code in PHP (oop) I show should him how I build a restful API and connect to MySql etc.

He told me that's not PHP , PHP don't use define and class , and that's not how you connect to MySql (I'm using PDO) he confused that pdo is something from Java. He told my code is not working because it is java syntax (actually not even closed)

Then I asked him then show me the proper way , he showed me his code in PHP which is started by <PHP instead of <?php (this is fucked up)

And I told him that (after looking at his code), he yelled at me that "there's no mistake, do you really understand PHP? " And he ended the meeting

All this happen in a zoom meeting.

void main ()
{
//Not working code
Also not working code
}

Friend :- Dude i made some changes and the code is not working now.
Me:- Bro, Do you even GIT it?
Friend :- No i don't GET it how it happened and how to restore it.
Me :- You destroyed my pun and my faith in your development skills -_-.

When the code is not working:

I have failed my parents, my job and everyone. I shouldn't have taken Software Engineering as my profession. All I'm doing is giving pain and frustration to everyone. *thinks about a clean way of suicide*

Then after a while the code works:

I am probably the best engineer to live on these planet.

Do you agree to this rule given by my company ?

"Employees are not allowed to create any sort of library for any language after or during working hours, whether for personal or company projects. As they might somehow expose companies code to the open-source world."

Personally, I created quite much (not that much) of library , I created for fun, today I was told to delete ALL , so those who use my package , Im sorry :(

> make a change
> PR gets rejected
> IHATEFORALIVING! YOUR CHANGE IS NOT WORKING! EVERYTHING BREAKS!
> 3 hours long debugging session
> We find out a whole bunch of bugs
> Suddenly, everything works
> None of the bugs had ANYTHING to do with my change. In the instances where the app broke, my code wasn't even being called at all.
> My change was literally the one and only working thing

I wish life was like in The Office, when you just stop what you're doing and you drop the Jim stare at some camera

I've a recently joined developer hired from campus sitting next to me.

She: I'm printing an array in Java but it's not working. Could you please check what's wrong?

I see this piece of code:

printArray(arr);

Me: Where is the printArray method?

She: (With a puzzled look) Oh, do I have to declare that?

Me: 😶😶😶 (lowered my head, walked away slowly praying for the company)

How I feel working with code that's been worked on by at least three different teams at three different companies over the past couple of years and not a single person has left any comments or documentation.

My computer science teacher is very sly: while you are working he stands right behind you for some time, so you start writing good code, functions for everything, perfect indentation... But you don't know if he is still behind you, and you're not brave enough to look back, so you write good code for the rest of the lesson.
What a good prof

So the CSS code I'm working on has a terrible vertical alignment problem on every browser except IE11. Using `display: flex` =_=

I'm not joking this alignment glitch is driving me nuts! Deadline tomorrow.

Manager: How’s the progress coming along?

Dev: The section of code I’m working with is one of the more difficult ones so it’s a little slow

Manager: Ok well I didn’t write that section of the code

Dev: I’m not saying you did I’m just giving you the status update that you asked for

Manager: Ok well I can’t really do anything about that so how about you tell me something I can do something about instead of just complaining about code THAT I DIDN’T EVEN WRITE!! *Marks self as offline*

Dev: …

piece of code: *not working*
me: okay, i can try this again later
me: *comments it out*

4 hours later

me: omfg why are there so many comments??? :(

The music I hear while coding can describe my current mood:

Dubstep and other electronic music -> chilled and focused
Movie soundtracks -> everything I do today is working fine
Anime Openings/JPop -> in desperate need for motivation
Metal -> why is that son of a code not working?!

What kind of music do you listen to while coding?

Senior Engineer -
Hey. I have a code that hits API to get details and multithreading is implemented. Can you just change the URL formed to hit Api?

Me
Yeah sure why not.

Me
After some time I discover that the initial code itself wasn't working 😐
I realise i need to fix code, fix multithreading and then make the URL changes.

Just finished......Realised had to rant....

App nearing completion. Code tested, everything's working fine. Ready for release.

The client just calls me and tells me that they have decided to turn the app into two separate ones. Should not be a problem, you developers must have some tricks for that, according to the client. Of course, the release date remains unchanged.

Clients!, finally understand that there's no secret button for turning an app into two separate ones.

Turns out the small company I'm working for is depending almost completely on the new SaaS system I'm building, to appease investors and not go belly up.

I just wanted to move to another country and code some stuff, this is too much pressure.

"I strive for code quality and maintainability. I actually do. And i will not work for a company that does not care about it and just wants something done as fast as possible.
The only time i will do something quick and dirty is if it's actually urgent. And even then with one condition - my next task will be to fix it properly.

I do not care about your deadlines. I will do my best to meet them, but not at the expense of code quality. I've seen too many projects fall into technical debt, where productivity is so low, that the only way to move forward is hire more people and start working on a project 2.0

And please do not lie about how great your company is, if it's not. These kind of things surface very soon, and you will have wasted both of our time, because as i said - i will not work for a company that does not care about code quality."

you think i'll ever get a job again if i put this on my CV ? :D

Me, going on a vacation
"Fuck yeah, finally a break, beach, grill, nice. Im not bringing my laptop, theres no way im touching any code."

Me, 10 minutes after i got on the bus
"Oh, i figured out whys that one thing not working, let me just get my lapt...shit"

I working on Twitter Cilent for android as school project, and I made code getting the logged in user own tweets, but it not returned anything, and after one hour trying I realized I never post tweet with example account....

Those developers working under non-technical bosses, i understand your pain.

1. Pain when they don't realise that output != number of hours put in. Aaaaaaand that acting busy doesn't mean someone's working.
2. Pain when chilling out in office is necessary, because mind jobs don't work same as other jobs. Wherein if you don't vent it out you're gonna screw up the code. Them not getting that.
3. Pain of "meetings".
4. Pain of changing the feature when you're done, and them acting as if its a minor change.
5. Pain of vague requirements.
6. Pain of a product not thought through, and them trying to blame the implementation.

Wordpress :(

Here is another piece of garbage from a previous Wordpress "developer".

This is NOT the generated HTML, it's the actual source code within a custom category template.

The client has said their archives stopped working this year.

*** MASSIVE FACE PALM ***

Spent 2 years slaving for a “start up” building not only the core framework but also handling clients, operations and logistics while being yelled at constantly for not delivering even though I was clearly over worked.

Once it finally hit my head that none of this was my mistake, quit, took a few months off and started working as a freelancer for no code development platforms.

Have been working with multiple amazing clients for more than a year now who understand and appreciate the work I do.

Working code is not a clean code

MY CODE IS NOT WORKING 😬

Yes! you made a difference.[image]
P.S.
started working at a startup as an intern(android app developer), Most of my work is like debugging the code, new feature implementations.
And the codebase is full of this kind of shit(even worse) plus literally zero documentation(not even for API's), not even a single line of comment in complete project(40K-50K), not any unit test/ UI test.
The funniest thing is when I ask for documentation he(boss | *) said: I am documentation.

For my school project that was due awhile back my group ran into the problem of a certain feature not working on a site we made. I had a test version of the site and it was working perfectly. Both the test version and the project site had the exact same code. We couldn't figure out why it wasn't working and so we just turned it in and took the point hit.

Today I was thinking about it because I was still annoyed/upset that the site feature didn't work. I started talking it through with a friend and in the middle of it stopped-I figured out why it didn't work. My teammate didn't actually update the database, he just downloaded the code to the database and was using an outdated version of it. I suddenly stood up and screamed, "F***!" At the top of my lungs.

I startled my friend so bad that she spilt beer all over herself.

In india

Teachers teach students to code, without any field experience

These students learns things tht they dont need in their life and becomes teachers

The cycle continues...

From my genius analysis, we can see that these students need not go to a company to work like a horse,

Why are we in a company working like a horse?

Fixing someone else's code who left the job.
Production suddenly not working, cannot debug locally, cannot deploy to a test environment because it does not exists anymore.
There should be a contract clause that developer need to support his project for 2 years after he leaves his job.

My code is not working correctly but there are 0 errors on the console.

Hmmmmmmmmmm😑😑😑😑😑😑

Dev: My VM is not working. Something is wrong with VM.
Me: Have you made any changes to the code?
Dev: It shouldn't matter my VM is not working.
[I go and check the Dev's VM.]
Me: ಠ_ಠ The build output literally states your unit tests failed

A senior engineer with about 8 experience in my team and company for almost a year now. Believe it or not, still hasn't setup local dev environment.

Every time we ask this person to set it up / refer to guide in Confluence / or just use the docker image the person says ok.

Starts sending code for pull request. The code would not even compile in most cases just from a quick scan. When questioned how was this tested, answer would be more or less 'oh my local setup not working, could you test it out for me.'

Doesn't know how to write tests. Fairly recently instead of storing string values in a list, (I swear am not kidding) decided to come up with 20 string variables.

8 years plus experience! I think this is retarded even for a fresh grad.

FRIENDLY REMINDER: Fucking save your goddamn work. Thanks.

- Your friendly neighborhood dumbass who just lost 14 hours of his life because his computer crashed.

P.S. Normally not a problem when working on code because I'm forced to save and commit with Git. Unfortunately I was balls deep in Adobe motherfucking illustrator working on wireframes, and didn't have doc recovery turned on.

So a company I'm working at has this internal product. I just got employed and was put into that team.

"First task: refactor some of the code"

Alright, I start refactoring. Oh I may need to write a small class for this one. And then rewrite this a bit. And then rewrite that a bit. And then rewrite everything.

"Why are you rewriting most of my code?"

oh i would not have needed to do so if your code was not COMING OUT OF YOUR ASS and if all the teams had FREAKING PROPER API DOCUMENTATION

*working on a programming assignment for a graduate-level course*

"We will provide you code that implements the protocol in the server. You do not need to touch this code."

*provided file has syntax errors, including a block comment which doesn't close before EOF*

My code is not working, why?

The time when we were not aware with advance features of IDE and version control.
(3-4 days before the project demo)

Me: This code was working fine last time. Now it is not compiling. Has anyone did some changes?

Team member: I corrected some spellings. So that our teachers don't correct us at the time of demo.

Me: (shocked, expression less ) We demo the application not the code. And you have not corrected on all the places.

Team member: You should do the rest.

(Based on true story)

While I was working with my Android project that is written on Kotlin. One of my on non-tech colleague came and saw my screen and

said "Why are you overriding fun"

I replied him that we just not override fun we also have private fun and public fun.

Is it not funny translating code to real English 😂😂😂

Guess what's even worse than reading the code of someone else?
Reading your own code after not working on it for a couple of days.

Self rant!

Looked at a code snippet I wrote last year and I thought to myself: am I geting stupid for not understanding my own code ?

Tried to re build it from scratch...

Failed and had to reuse it without understanding how it's working.

I guess I am getting stupid!

It's about a guy that knows better.

I was working as a subcontractor on a bigger system. We (subs) were not allowed to deploy code, we had to wait for contractor to deploy.

One day I got an email that my code is bugged and that my feature is not working on production. I checked it on test env, everything was fine. Then I checked if the code I wrote was deployed. It was not.

I send an email explaining that if they deployed my code it would be working. Then I got a response. There was a bug in my code.

Another email. I asked how would they know? Do they have a test on their environment that failed?

No. There is one guy that READ my code and he said it should not work, so he will not deploy it. He was not a programmer, he was a business consultant responsible for the documentation.

His issue was that I used a function that was not in a class. So if the function is not declared it's obvious it will not work. I had to explain to him in another email, that you can use object of another class inside your class and then call a function, that is not in your class. It was the last time this guy blocked my deploy.

TL;DR, I had to explain a non-dev how object composition works in order to have my code deployed. Took four emails.

So this one time me and my teammates had just started working on react (please note that we all were backend developers and no one has the basic understanding of javascript) and things were looking quite exciting..

But towards the end of the deadline we were sitting and refactoring each others code since we had not decided on the coding standards and practises and random code had been written left right and center.. It once happened that the same piece of code was refactored multiple times by only 2 people..

And it is obvious that we couldnt make it to the deadline and that code is sitting there like a mixture of weird things..

WTF is with the entire Angular2 eco system and "half instructions". Started learning it and every inch is a struggle, out dated docs and code samples and then this style of shit:

Google: "Angular2 and bootstrap"
Result: "Install ng-bootstrap to get native bootstrap components written in Angular by the Angular UI team"
Me: Install != work

Google: "ng-bootstrap not working"
Result: "You also need to install bootstrap css, heres how"
Me: Install, plus try component
Error: "Bootstrap requires jQuery"

Google: "Installing jQuery in Angular 2"
Result: <Instructions>
Me: Install, still not working

Google "Angular2 ng-bootstrap bootstrap jQuery"
Result: "Don't forget to also include Tether"

WHY DID THE FUCKING "ANGULAR-UI" TEAM NOT MENTION ANY OF THIS

I guess I'm not the only one who sometimes code in my dreams while sleeping. Maybe it's because working as a programmer is like a dream come true.

So I just wanted to log back into windows. Typed in the password. Wrong password...
Then I tried being super accurate while typing and also checked keyboard layout, etc. Still, wrong password.
Then I noticed that the letter p is not working. Shit, keyboard seems to be broken.
On screen keyboard -> p is not working...

What the hell? What kind of error is this?

NT Kernel code has to be something like this:
if(timeSinceLastError > someValue)
keyboard.p.enable = false;

I guess you could also replace the keyboard error with some random error.

If you encounter this, restart Windows.

We were in a meeting today and it came my turn to talk.

me: "I am working on something not fun. I am tracking down a bug in X software that a customer has issues with."
boss: "It is like an easter egg hunt."
me: "Yes, but instead of eggs I am going to find a pile of crap."
boss: "Laughs..."
me: "Its not chocolate..."
boss: "next..."

The original code I am wading through is very likely my boss' code.

We do infra as a code, and one of my coworker worked on the project alone. Few months down the road, when shit hits the fan, he just message me this is not working.

First of all, I did not write that shit, and also I was never part of the conversation during the decision making. So when shit hits the fan what do you expect me to do? Do some black magic and fix it magically???

My manager thinks I am Superman! and he is so confident that can do any shit he wants me to do.

Yesterday he asked me to merge an ancient code hotfix (literally ancient) with latest branch of changes.

1. Hotfix is really old, most of the things are hardcoded, very specific to a stone age client.

2. Code documentation does not exist.

3. Developers of that code are probably dead.

4. Many Libraries which code uses are deprecated.

5. It's a legacy code, so no one has fucking idea what a particular clumsy block of code do, or what will happen if you remove it.

'if it runs don't touch it' policy by management.

Despite all this shit I successfully merged the the hotfix, refactored outdated code so as to run the application.

Showed this to my manager in full swag!

He was surprised at first, and asked me to show the code changes.

'Code review' was done by comparing files 😅

Manager: Dude, you have changed these lines, why? Explain.😧

Me: those lines won't work with new build, with new libs.☺️

Manager: then why can't you do old build with new changes?🙄

Me: umm.. wait... what???🤔

Manager: the code was working previously, it must be working even today without these changes.😡

Me: it was not working hence I made changes and now it's working fine see! ☺️

Manager: you have removed this, this and this!!! 😡

Me: but I also added that, that and that!😔

Manager: "don't touch it' if it works!"😡

Me: ... Idk what to say!
(In the back of my mind: "Don't touch it even it doesn't works!")😌

When you're training a new guy who thinks hes better than you and completely overwrites all the code you've been working on because he thinks UX designed it wrong and it should look "correct". Thats not how corporate business works buddy...

Often I look at my seemingly perfect code 30cm away from screen, mumble "WTF", while asking me why it is not working.
My boss might think I'm retarded...

Shit Project Managers say.. to my coworker when I'm not there :
"Hey do you think she's working hard enough ?..I don't know, she has only made 2 commits in the past week so.. "

Fortunately my coworker defended me and told me after but yeah.. As if you could measure efforts and work in development by counting lines of code, fuck-tard.

i'm here because my code is not working 😂

Writing a super extensive project in php. Twice so far, I have had weird problems of codes not working.

But everytime I copy/paste the SAME code from another file, IT MIRACULOUSLY WORKS!!!!

WHAT THE ACTUAL FUCK!!!

Both apps I'm working on have legacy code:

iOS app has 100's and 1000's of lines of code with no documentation, no proper naming conventions and cut and pasted code off the net.

Android app has skeleton code from a Spanish taxi app + remnants of a funeral webcasting app, there's also the same no documentation, bad naming conventions and cut and paste code off the net.

The server is also as bad, it had methods that we're never used, I for one don't fully understand the server but from what I can see it's a mess.

I had a hard time understanding both apps and gladly majority of the modifications I made we're not including existing stuff, so I guess I just basically pilled my code onto of the already existing software.

I would have gladly started from scratch given the chance.

Monday morning: The last straw.

After talking about in a previous rant about how my client wants to fix bugs that keeps popping out after bug fix.

Today I discovered, that all C-levels, worked all Saturday to "fix my code" because it "didn't work" and we "needed bug fixes not pretty things".

The app version I was working on for the last week is gone. Without mentioning that their "CTO" wrote a fucking crappy code to disable features that I added, breaking the build step.

This shit is enough for me, I'm done!

Don't you just love it when the lead developer/project manager comes in and totally revamps your code even though it does the same exact thing as it was written before? And then when it's not working he blames you because it's in GIT as your commit...

When you work hard for something and you are sure that you gonna get it, but some ass licking guy who doesn't even know how to code gets it. Yes, it happened to me. I was working for an open source organization called PROBOT. I was working my ass off to get into GSoC with that organization. I created PR(pull request) after PR and solved most of their issues. But later on, I came to know they didn't even saw my single PR. Life surely teaches you some hard lessons but it's you who should not give up I would say. I do not regret working my ass off and writing those code and not getting into GSoC but I cherish those moments where I learnt many new things. And as for that organization, I would say they don't even know how to manage. This was my exact reaction when the result came

10 PM (after a very busy working day), CTO calls me and tells me: "We decided to hand in the new version to [random client] one week earlier, so they can test it."
Me: "I don't think is a good idea, the app is still unstable, we started working in it yesterday, it *will* crash"
CTO: "Don't you worry, at least they know we are working on it"
20 minutes later
CTO: "WTF why did you make my app crash?! I can't send this to a client!"

Told you. That is why that code is on develop and not on master.

Damn stupid me...
One of our customers told us, mails are not working with SMTP. They send us a working code example, which looked very similar to our implementation... I was not able to find out what was wrong for hours.

A colleague checked the code later. After 5 minutes: you forgot a ! before checkin the string if it is null or empty...

Shame on me ..

it is really frustrating not to be able to actually maintain and improve the code you're working with. i'd be happy to completely dig in and live in the code and get it all - not so much fucked up - , or, totally spitballing here, do some research on how we could improve the functionality and performance in general (which is not "nice to have", but rather ongoing customer pain points), but I'm not allowed to, because management hates having maintainable code or even an adequate number of devs. it rather has me doing hippity hoppity between different projects to make sure nothing gets my full attention. -.-

the only thing i can do is to clean it up a bit during bug fixes, but even heavy polishing won't fix this giant pile of garbage that is called our code base.

A Bad and Sad Day

Hello Monday,

Client : on weekend site went down for 7 hours? Why ?
Me : Let me check the logs
Client : bla bla bla
boss : check ur code bla bla bla
Reason : Some PHP service stopped on server

Client2 : I have purchased this software and you have to made minor changes
Me : Payment Integrations are not working?
Client : Whataa nonsense is this.. you are supposed to do this
Me : We are supposed to do minor changes. They do not have proper payment integrations. If you want we have to write complete code
Client : bla bla.. I gave you working software

:( Why don't you just fuck off .. liars

started converting VB code to JS.
* lets refactor it when we are on it *
After 3 hours, with refactored code not working, uses the old logic.

Knockout JS.
I am not sure if the library itself is so bad or the code which I was working on was ugly. But since then I avoid anything that is related to knockout js.

I started a project at high school 7 years ago, I had no idea what's clean code or design pattern, just learn while keep coding. I eventually stopped because my code is so terrible I cannot understand it anymore.

Now, after 1 year of working, I look back those dirty codes and think it is actually not that bad. Within hours I even fixed a bug with concurrency.

I start to think, instead of learning to how to write good code, maybe I should learn how to read bad code. That's just much more practical.

First Rant here.

So I was working on some integration test issues when I found this by accident made by a professional level SW engineer:

@Test
public void testMethod() throws ApiException {
Response res = null;
try {
res = serviceToTest.callMethod();
} catch(Exception e) {
assertNull(res);
}
}

Was wondering why tests were being green after some code changes I've made cuz tests could have not been green afterwards.

Together with a senior (I'm also professional only) I've tried to explain him for a good 1-2hrs why this code is useless and he still did it. Good thing there are no errors in the real implementation from him after fixing the tests as it's code freeze here and we are having go live in a few days 🙃

Also luckily he isn't working on our code anymore and has only been doing so for a few weeks.

Wasted a day with it and gonna check all of his code now before I run in the next surprise.

There was an android project that I got from my senior.

he told me that another developer already completed most the project and all I have to do is minor changes...

Well when i saw, i was amazed that the code he commented is more than the actual working code without any structure.
He copied most of code from internet.

If it's not working, put in comment else use it.

It took me a whole month to figure out what's going on.

And another 2 months to fix the issues.

Well in last my senior told me that the developer took 1 year to write this code
(to be honest any normal developer can complete that project in less than 3 month)

Quick rant!!

Deadline in 2 days, working with a team.

Me: yo ! , How's the xyz feature? Is it working now?

Teammate: yah, made it work yesterday.

Me: epic! Can you present it to me?

Teammate: wtf, it's not working today!!

Me: no worries, you can sort it out!

Teammate: the latest release you worked on doesn't work properly.

Me: yah, merged code fucked up, I'm fixing that, I'll push a fix today.

And the cycle continues...

FUCK FIREBASE, FUCK CLOUD MESSAGING, FUCK GOOGLE, FUCK APPLE, FUCK PUSH NOTIFICATIONS, FUCK PROGRAMMING AND FUCK MY LIFE. JUST TELL ME MOTHERFUCKERS WHY NOTIFICATIONS IS NOT WORKING ANYMORE, I SWEAR I DIDN'T CHANGE A SINGLE LINE OF THE FUCKING CODE. AND IT'S BEEN ONLY ONE WEEK SINCE THE LAST TIME I TESTED IT.

So I’m working on a project right and I don’t run it after writing 104 lines of untested code and it doesn’t work.

Which is expected but then I do some stuff and fix that, I get a new error which is great cause I’m getting closer.

Cut to tonight. I’m trying to hunt and kill this bug. And after doing nothing but copying the code to another text file so I can upload that copy and get help.

I decide to run it with a little just print statement in it to make sure it’s definitely broken and I’m not asking online for no reason.

And.. it works.. WHAT???

I uncomment the rest of the function and get rid of the print statement and scream because ITS WORKING!!

I MEAN IT HAS BUGS BUT THEYRE BUGS I CAN FIX AND FOCUS ON AFTER I FREAK OUT ABOUT IT WORKING AFTER ME CHANGING FUCKING NOTHING.

Pro Tip: If you spent all day debugging and shit's still not working, go get yourself an oversized, fully functional enter-key-pillow. Your code will probably still not work, but now you can at least spare your keyboard and smash that enter-key with all your built up rage

Boss only likes stuff he can see and that looks pretty. Doesn't understand code, servers, containers, DBs, etc. Praise is attributed by something looking nice in the frontend, whether or not it does crazy stuff behind the scenes.

Spent a week working on a project whilst boss was away. Got to about Thursday and thought, oh poop, I've built all this API stuff, but not much frontend. So I panic built frontend screens with no functionality just so I had something to show.

Wish I had another dev to share backend progress with (and code review)...

Lels

Before I was unceremoniously laid off by a shit company in which they tried to blame shit on me I was working on a opencv implementation of a proprietary document scanner.

I finished the Android prototype and was working on the ios implementation. It was left unfinished in the ios version because I was building it in swift and obj c to compare code bases.

They launched a shit unfinished Android app of their product without the scanner (they could not add the scanner lels) and have not been able to do shit on the ios version.

I did not give them the Android prototype. There was no binding contract that specified that what I developed was theirs. There is no record of anything.

The scanner? Is still in my phone and I still have the built project in my mac.
Unless them cheap assholes decide to pay another engineer for the opencv implementation, their vbscript php non theory knowing shit lead will have to figure out the required mat obj c swift java cpp code needed to build it.

Top kek

Our (new job) dress code policy is "that's what the CEO wears, so you have to wear a shirt too", but not enforced while working remotely.

So, I'll never be in the office.

Doing a python code review after working in Scala is all:

"Why the loop? Can you just put a function here and... oh yeah, right... python does not allow it. I could have written these 20 lines in 4 if was Scala"

Scala, stop spoiling me!!

Context:
Me, Front-end Developer, Javascript stuff
---

Junior Dev: Hey xxzer0, could you help me with this? I spent the entire day on it and at this point, I think I just broke Chrome.

xxzer0: *---* Okay, let me see.

Junior Dev: Do you see it? I am updating the Javascript code but it's not working at all. The browser is not even loading it... Literally, the code I just wrote is not there.

**
Now be me, be the fucking idiot I was and I have been my whole life, I already knew what was going on because I lost a fucking day on it as this guy.
**

xxzer0: Well, let me see just one thing...

'Open Chrome Dev Tools' -> 'Network' -> 'Disable Cache'.

xxzer0: Now try again...

Junior Dev: What are you..doi........ IT'S WORKING! O.O

Chrome, I love you but sometimes I wish you could make this more "accessible" to newcomers.

When i sit down and code, its like a conversation with women.
Im not sure whats going on, but it appears to be working.

My coworker is... something else. He's "coded in Java for six years", bear in mind and this is a bit of .py code he's written. First a doNothing() function (probably didn't hear about pass) and then there's about 400 lines of creating values. No iteration whatsoever. I have no idea how he's got the job. Not to mention that whenever he talks about anything technical it's like listening to Gertrude from Accounting talking about 'mouse not working'.

I have been trying to understand why my student's code isn't working just to find this piece of code. Checking out code early in the morning is definitely not my thing.

A rant about people in general:

I am sick of people not caring, not giving a fuck, not valuing others.

Studying CS this is something I noticed the past year: people tend to not acknowledge that there are other human beings around them.

Some are just focused on getting their degree done and dusted as fast as possible, which is fine.
Some are working to pay the rent or student loans, which is fine.
Others just do their thing, code their stuff, criticize other's code... which is also fine.

But nobody's realizing they're interacting with other people! Other living, feeling human beings. For them it's just about getting it done.

And not just at university.
I've started seeing it everywhere.

At the job I'm working, people in the shops and on the streets.

I don't get it. We are all human on this rocky sphere in space. Why do so many not care for each other?

It makes me sad.

My biggest distraction at coding are my parents.

I still live in there house and it's really comfy.

But whenever I code the always come into my room with something random like "my phone is not working" or "how can I delete this?"

I love my parents and Im glad that I can help but always get off where I was after 😂

Reviewing code for applications after not working on it for six months.

Client: so what is the first step to adding our new feature.

Me: I really think we need to redo the entire architecture from the ground up. It won't work any differently than it does now, but the code will be cleaner.

Client:😓

Me:😅

!rant

Goodbye Java I will not miss you at all! I swear ...

I do like it when making web services (especially that I can use Java8) but for Android you have been a torture. Hello sweet Kotlin! I shall embrace you and treat you like my newly born baby!!

Story is:
Working on a new project where I need to talk to a web service (also made by me).
Started writing in Java, all is cool and unit tests pass.
Downloaded Android Studio 3 Beta 1 and converted my Java code to Kotlin, That AsyncTask did not look nice in kotlin, converted it to async & await feature and I must admit lots of code removed, no more need to create a new fucking AsyncTask every time the app sneezes for data!

I feel like I'm working with C# but with difference in syntax.
My life is now complete :)

Spent 5 hours working on a solution for a hash difficulty comparison/scaling algorithm. after a bunch of different iterations and approaches, I find that my problem can be solved by the attached equation. Its such a simple answer but no way in hell would you be able to discern the amount of time and brainpower that was put into it. The git commit is literally 10 lines of code total, but I guess its not about the amount of code, but the time spent thinking about it thay counts?

Forgot to change code in my api for rate limiting, after development. No unit tests.. because who really needs that right? 🤦‍♂️🙅‍♂️🤷‍♂️lolololol

Long story short, API went to production eventually, and stopped working almost immediately. Rate limiting was set for 2000 requests in a 1 hour time period. Not my finest moment.. fml 🤦‍♂️

-Writes a function that I'm going to schedule for django.
-works in development.
-adds it to production cron using django-crontab
-not working.
-spends 3 hours editing code, searching for similar problems and reading documentations but find nothing wrong and it's still not working.
-maybe it's django-crontab so I decide to just write a custom management command and call it through cron.
-still not working.
-calls function using what I'm telling cron to do.
-everything works.
-?????????
-adds logs to cron command (sorry for not making it earlier)
-mfw the code is not working because I imported 'patterns' in urls.py which has been deprecated since django 1.8

Write a piece of code that works just fine and it's fairly extensible in 20 minutes.

Then proceed to spend the rest of your night rethinking and replacing said piece of code numerous times, with slightly more elegant code.

7 hours later and I'm still not done. Although a fine way to improve your skills, I seriously need to stop doing that for every single thing I write and start managing my time better. Got lots of other stuff I need to be working on...

Surely I can't be the only one doing this

The scrum master for the project I'm working on decided to help out with changing some code (I'll add he's got a master's in software engineering and very proud about it..aka..big ego). It took him two days...yes two days to write the attached code.
I reviewed his code and sent back a response (code took about 15 seconds to write) including the link to the logging documentation explaining what fields were and were not necessary. Not sure how will look in devrant ...

var data = new InformationalDataPoint
{
Properties =
{
["RMANumber"] = rma,
["InvoiceID"] = invoiceId
}
};
Logger.Log(data);

He's stopped talking to me. Our next scrum meeting with the product owner should be ...um...awkward.

I've got a confession to make. I.. I just love hand-obfuscating JS-Code. Not because, i would prefer working with obfuscated code.. I just find it extremely satisfying watching the code shrink and being the only one being able to understand it..

It's out. I feel better now.

Thought I would only do frontend-stuff when I started working. Boy I was wrong. I thought it would be easy coding in a real company and not just in schoolprojects, boy I was way out in the blue. But when your code works and is actually used by people, I never could've imagined that would feel so good!

We receive an email from Splunk when errors go above a certain threshold, and a particular service has been especially problematic this week (throwing hundreds of exceptions). Email response from the team mgr responsible for the service.

"We are working to address these errors. We don’t currently have a way to prevent a user who’s account is locked from logging into the service and performing work."

The exception? NullReferenceException: Object reference not set to an instance of an object.

The code? (paraphrasing)

var user = GetUser(request.Login);
if (user.CanPerformWork) ...

<facepalm>

I'm doing my best not to reply .."Really? No way? You do realize we can read code, right?"

Let's try this.

In the project I'm working there is an strict rule : NO COMMENTS!!!

I mean wth, the times I've spend hours trying to understand the crappy legacy code in VB.Net that has been there almost decades, that wouldn't happen with comments, I know i know there are some supernatural developers that think in binary and their eyes work as compilers, but I'm not like that, so seriously go to hell.

P.S. Of course I follow that rule, after all, my code is so damn perfect that even a baby can understand it.

jk

After 1 year of working as android dev and coding in java, finally switched to another startup where everything is in Kotlin where I will be the only one maintaining that project.

Me: This code has almost no comments
Senior dev: Code is pretty self explanatory

FML

At least she spent 4 days with me and walked me through the code, so I'm not totally lost which is great!

fuck this!
spent an hour trying get my website working (on a raspberry) ... no errors, dev tools gave nothing, php gives nothing mySQL related... weird.. debugged my code for an hour when it me... db on my pc for testing is not the same one as the "production" server. i am so fucking stupid... i need some sleep

When you hack up some spaghetti code which works right off the bat and you don't even know why but you take it for granted anyways. Week later someone tells you that it's not working anymore and you have to find out why.

Going through legacy or other developers code which don't have documentation or even comments. Plus the author of the code is not working in same organisation anymore to consult. We have to understand the code like deciphering any ancient language. 😥

One thing I learned early on was...

"If the bug is not where you are looking...look somewhere else."

I just spent 2 hours looking at 50 lines of code pulling my hair out why it wasn't working. Guess what...those lines were correct. The bug was somewhere else.

When you can't tell why your code is not working, and you wish to see an error message...

Made a change.
Patched some files.
Ran the app.
App not working as intended.
Freak out.
Check code.
Think of random solution.

Waste an hour.

Realise that files weren't patched properly.
Kick myself in the head.

After being an active developer in the industry for about 5 years, I still have some bad dev habits on which I'm working on:
- Starting off with the code first without a proper design in mind/paper. (Trust me, I'll always regret of not having a proper design later)

- Writing long method bodies and not refactoring them later. (Because sometimes I turn out to be a lazy ass)

- Duplicating code in some places without reusing some.

Why won't you just approve my PR???

Whats wrong with you?!

I don't understand your cryptic one-sentence feedback. I'm not even sure you understand what you're asking yourself.

What the hell does "make it a transaction" mean? Don't give me pseudo-code examples that don't even work fucking asshole!

Its a small change that does NOT need a canary build dammit. Don't go testing the ORM, its a goddamn standard library. Why does working with you make everything so complicated?!?!

The code fucking works! There is no need to make it comply to your specific tastes goddamn it. Working with you is like pulling teeth!

/endrant

Two states of a developer every day:

• Fuck this job. I hate everyone and everything. My code sucks. It's not working. Why did I choose this career?! I am so miserable.

• It works! I'm a programmer god. Oh my goodness I'm smarter than everybody.

IHateForALiving: I created a trigger on the model, every time you perform a save it should fire an event. You're calling the same methods I am, and the trigger is NOT firing. Are you sure we are running in the same process?
TheTeamLeader: I'm manually starting this whole piece of code in your same process, there must be something wrong on your side if it's not working

90 minutes of debugging later

TheTeamLeader: there's the thing! Your hooks are registered in a separate process, of course they are not firing
IHateForALiving:

So now I’m working with this code that is roughly documented because ”variable names are self-explanatory”.

Yeah, you just forgot that FORTRAN does not support utf-8 variable names...

Why utf-8? Because then if I see:

real :: 座標(3)

I would understand that you mean ”zahyō”, the usual 3D position array ”r(3)”, but no, I need to deal with:

real :: zah(3)

yeah...🙃🔫

Product Owner: There is a major bug with your code it's not working.

I then spend hour looking at code to find out.

It's a content problem!

Question: is it a red flag if I'm "not supposed to" blog about tips and tricks I've found at work (not even code level, just organization and general design patterns)? Reason given to me: "we need to be careful about due diligence and intellectual property for our investors to be satisfied". Am I working with idiots?

My baby sister told me she wanted to learn how to code, her reason being; she visited a startup incubation center at her school, my alma mater, and she thought they looked so cool and collected.
Hahaha! I told her to try visit when they are having a deployment or when someone's code is just not working.

!rant
My mother got me a programmagle calculator this year for christmas, a Casio fx9750gII. Needless to say I'm already hooked. Casio BASIC might not be the best language I've ever used, and working with string is pretty much impossible but I'm actually having real fun. Hopefully I'll finish my snake code by this week (will update with pics :P).

<html><body>shit everywhere<meta>more shit</meta></meta><\meta>countles garbage code lines</body><head>[copy&pasted html code that actually works <img ... />]Tons of shitload</body></body></html>

Me: what are you reading?
PM: some email code that doesn't render well in the browser...
Me: let me see... OMFG!!!! who was the author of this garbage?
PM: Oh! it is not that bad! It was working well 'till today...
Me: But... but... this is really bad! you can't send this to customers!
PM: I think that the problem is the "/" at the img's end...

True story.

Note to self, don't fix a minor bug that will not effect the demo right before the live demo. My program that was working great didn't work anymore during the demo because of my quick bug fix I figured I had a few minutes to add to my code.

Not only dev related but remember to constantly backup your important info of your Hard disk constantly... specially if those disk have not only the lastest code you are have been working on but photos of you and high school friends back in the day when the original Iphone was just released that you havent properly printed yet.
I think that is one of the nearest thing I can think of that I regret lately aside from simple being "my life" in itself

Went to bed last night with my code not working. Woke up, ran the app and IT WORKED! I have no clue what I did last night it's all a blur, but apparently I fixed the problem in my sleep. #SleepCoder

Working in a organization that hire people that don't know what they doing and can't ask a question correctly...

HELP WE'RE GETTING AN ERROR IN OUR CODE WHILE TRYING TO GET DATA FROM YOUR DB... PLZ FIX IT

WTF IS NOT WORKING, WHAT ARE YOU QUERYING, WHAT IS THE ERROR?

**Sends a SQL query but with ? for all the parameters**

WTF..... U PPL ARE IDIOTS.... CAN'T EVEN ASK A QUESTION CORRECTLY OR PROVIDE NECESSARY INFORMATION... CLEARLY YOU HAVE NO IDEA WTF UR DOING..

EVEN GOD CAN'T HELP YOU...

Story about my old boss:

I was doing a lot of work in an area that had a data property and a method to build an object. I noticed a reset method that iterated all that objects properties, found the matching data from the data object, passed that data through some logic to format it and then assigned that value to the object property.

As part of my PR I removed that method, since data wasn't changing, and simply called the create method again with data.

The result of tidying the code base and putting it up for review before a merge? I get told I have no respect for my boss's code, that I am undermining him, that I need to be more considerate and respectful of other people's work and that I am no longer allowed to change any code he has written in the code base (half the code base) without talking to him about it first, before it goes up for review. Also if he is working on an area I cannot change anything - not even 1 character (he is working on the core of the app).

Every day there I was so confused :D

Scenario A:
Your code is working. You run again, now it's not working.

Scenario B:
Works on production. Next day it doesn't.

It is nothing you just experienced alternate universe. You probably with your manager temporarily jumped into another timeline where your code is not working.

Next time it happens tell your manager it's not your fault.

Eureka!

How to NOT handle dates!

Do not put the date to "mdy" format, today would be 050217.
Working on an intranet for some multi-billion corporation, and was wondering why events from last year were showing.

Last year's events were 28th of October, 2016, and was showing as upcoming events :)

Checked the code, and saw this. Quick fix, turned dates to UNIX timestamp, and it worked.

code not working?
comment code and try to run
uncomment piece by piece
code back to original
running...

apparently, the code didn't know it was right

Remember about this project of mine? Maybe not because I deleted the rant, but after a long pause I re-started working on it. In -just- 1 hour I wrote this code that picks a random number, goes from 0 to 5 and, if found, it prints the match.
This is my most (useless && senseless) project by far.

GIT LOG VERSION 110
---------------
a9c2934 I don't believe it
fb8d2e6 I am Root. We are Root.
6be9078 FINALLY FIXED THE FUCKING BUG IN THE CODE, DO NOT EVER EVER FUCK ME AGAIN YOU MARON
3d08a88 THIS IS THE FUCKING WORKING VERSION
013faed THIS IS NOT WHAT YOU ARE LOOKING FOR, GO TO A PREVIOUS COMMIT
af5d013 We'll figure it out on Monday
49e238b de-misunderestimating
a40351b happy monday _ bleh _
a5f345d Fixed unnecessary bug.
485a26a pay no attention to the man behind the curtain
c4fcbde s/import/include/

Trump: I pay taxes as little as possible!
Me: I write code as little as possible!

I have written less than 2000 lines of code in production in 5 years(about 2 line per working day)but with my luck, I earn more than average wherever I live. God, I live this profession AND my luck.

Note: I write fewer sloc not because I am lazy but because of my industry.

When its 2am and your code still not working

Not being able to write code only using pen and paper :/
I had one job interview where they ask me to iterate a tree using my preferred language. I felt so uncomfortable.
And my problem is only the pen and paper.
I'm able to write working code without any code completion even without highlighting in any shitty editor. But when it comes to write code by hand on paper it feels like my programmer brain side turns off.

I don't know why my referrel code is not working.. 🤔🤔🤔🤔

Writing my code, go to run it and boom its not working. I pull up stack over flow to get some insight. At this point i was working on my code for countless hours and became a bit annoyed so i decided to copy what someone wrote on stack over flow delete my code where i thought it was flawed. I run it and Blam bugged the hell outa my code. So i undo go back to my original. Turn to a friend and ask what do you thinks going wrong. He resets my browser and there it goes it works. I just kind of gave him a blank stare and thought to myself Im a dumbass!

So today I started working on a code base someone else wrote and stubled across this and thought it was worth sharing.

Why somebody would be doing something like this is beyond my understanding.

Not commenting on the empty catch block keep in mind the whole snippet has nothing to do with rest of the code...

WHY!!!!!?!?!?!?!

I've been working for 6 months now, and the boss tells me he's not satisfied with my work compared to someone that has 15+ years experience. He clearly states that for him - it's more important lines of code, than planning and defining the architecture which he don't like because that doesn't provide anything...

Of course, I can just jump into the code if that is whats important. I've seen the code produced by the other guy, and its shit.

The guy is a talker, and knows how to talk. I'm more like, hey lets create a simple design prototype or do some UML diagrams to get a better visualization of what we need.

Anyway, its just annoying to be compared to someone with many years of experience, its not that I can achieve it overnight...

When it’s 3am and you are working on an exception for more than 2 hours and have optimized your whole code just to be sure and remember you are writing swift not java: some ints have low max value like UInt8.

I know by heart that "premature optimization is the root of all evil" but not when I'm coding, no! I premature optimize the shit out of my code until I get crippled down and then I undo everything and make a working version no matter how terrible it is.

Got rejected from a really nice opportunity today. Irrelevant experience as it seems to the company.

As it turns out I'm an unlucky beginner in the industry who's stuck with a wrong, legacy code project. Doesn't mean I don't know anything and I can't learn new stuff. They were not judging capabilities, just judging people by the project they're working on in their current firm.

Trying to understand other people's code like:
- 6 README, in total 7 lines (that's all there is for documentation)
- 40% of code is commentary like (original code, not altered...)
// if(a = b)
// c = d; // this is not working

*using random JS for website*
*finds stuff not working*
*opens JS file*
(mesh of code)
*select all*
*Format Selection*
I love you, Visual Studio :')

Just opened a project that I'll be working on for work, first thing I notice is C++ like code formatting, which hurts my eyes (keep in mind this is Java)

But then decompiled Hybris classes came at me with not only that, but three newlines between methods.

I fear what I have yet to see...

One good thing about working at a shitty place is you end up knowing what not to do by just pure pain.

I once consulted for a company who had the latest tech - kubernetes, bit bucket, you name it. But it didn't matter. The code was shit. It's not about the tech, it's always about the people that use the tech.

Hmm. Seniors have the half working experience as I do and I am the only not senior one in Dev team.

I adapt code only to "taste" good for code reviewers, but they allow themselves to commit without caring and just saying :"oh unit testing is boring"

Enough with the kindergarten. Time to prepare myself for the next job.

1.Working on a repo's 20 day old version without pulling the changes first
2. Then blaming me to not tell him
3. Ultimately sending me a see screenshot of his code to incorporate in my code ( which he himself didn't write, but asked a coworker to do it)

WTF DUDE. Atleast you could have realised your mistake and not blamed me for it

Just got upset with a coworker due to not understanding the code written, logic, lack of documentation, comments. Nothing!

Other coworker: But Dave, you added that feature last December. Remember?
Me: So what are we working on today?

I feel like a lot of us write code without thinking it through beforehand. I spend more than half my day working everything out via diagrams on paper or lucidchart or with a coworker/previous maintainer (if applicable) before line #1 of code is written. Ideas are to code as source code is to build products - the latter is made (essentially by rote) from the former.

I'm glad I work from home thanks to 'rona, but before that, gah. Everyone else was visibly grinding away, and here I am staring into space thinking about the problem/project I'm working on. I'm not gonna sit there all day debugging code I once rushed. There's a reason the sites I maintain stay up and untouched by hackers (I think, you can never be sure...).

THE TYPESCRIPT DEFINITIONS SAGA CONTINUES

> IHateForALiving: so, I don't really know which field we're supposed to use here, but that's your entity I'm working on, so...
> TeamLeader2: wait, what is this? Why does your code have autocomplete?
> IHateForALiving: Every time I worked on some parts of the code I've been writing some type definitions along the way, and it's adding autocomplete if you type hint your code... but I've been told not to write them anymore, so I stopped
> TeamLeader2: But why tho? It's so fucking handy
> IHateForALiving:

Optimization issue pops out with one of our queries.
> Team leader: You need to do this and that, it's a thing you know NOTHING about but don't worry, the DBA already performed all the preliminary analysis, it's tested and it should work. Just change these 2 lines of code and we're good to go
> ffwd 2 days, ticket gets sent back, it's not working
> Team leader: YOU WERE SUPPOSED TO TEST IT YOUR CHANGE IS NOT WORKING
> IHateForALiving: try it on our production machine and you'll see the exact same error, it's been there for years
> Team leader: BUT YOU WERE SUPPOSED TO TEST IT

Just so we're clear, when I perform a change in the code, I test the changes I made. I don't know in which universe I should be held accountable for tards breaking features 10 years ago, but you can't seriously expect me to test the whole fucking software from scratch every time I add an index to the db.

You do not own your companies code. Of you hate working at your job, don't let the feeling of responsibility for the codebase keep you there. I keep learning that lesson.

Today was a bad dev day working on a shitty React project. Not that React in itself is bad, but it can be hell to work with when the code is a big pile a crap full of anti pattern code. I spent the day refactoring to try to fix a bug, but to no avail. It would take days if not weeks to put some order in this mess and to prevent such bugs.

Got back at work after 2 weeks off

Useless to say I did not remember what to do or where to start…

Today I was working on a feature and while thinking about code organization I found an empty function ready to be filled with the exact name I was about to type.

My 2 weeks ago self prepared it for me… it was so kind of him

Always make your code readable before you stop working on it.
Not just for other people to learn from but also for yourself.

Context: just lost about 3 months of progress because everytime I look at this file I feel like starting over...

I'm in my first internship, they gave me their only company owned product. They always made interns work on that, and it's something I really appreciate (I like when people give to others any possible chance of learning)... But apparently they made a mistake: for the first year they never reviewed interns' code. And now that software is huge and full of bugs.

After two weeks working on that I said to the tech leader and to the PM that we should spent a couple of months rewriting more than half of the code, and surprisingly they listened and agreed (the TL already knew that, and the PM is not a dev and he listened to the TL).

After two days of code rewriting ("refactor" is a too weak word) the boss calls me and orders to stop, telling me basically "I agree on this decision, but not now; let's first make it work and then we make it great!".
Okay I respect that, but what he didn't understand is that the two things are strictly related!

Result: last week we had a first official release (with some client's testers, so they were expecting a few bugs) and nothing was working, so me and the tl started a really hard rewriting work (that didn't finish) and managed to release a very bade made software that works by chance.

After easter we'll keep working on this, and I think at the end it will be great.

First working experience, in two months I learned a lot (not only about code/tech).

Boss asks if the project will be finished today, I reply ‘yes’ and then realised I’d not pushed my code after working from home the previous day! Doh!

The few times i have pushed code to the repo when it's not ready.

Granted it was so i can carry on working on it elsewhere but it wasn't my proudest moment.

Aaaannnd again a failed interview.
Just because I didn't pay enough attention to the question.

Did that ever happen to you guys? Like you just write a huge pile of code, you look at it, you're proud, but it ends up not working because you forgot one little thing that makes it completely incorrect?

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*

Release on Monday === almost 10h of code today... Though it's just an internal release, so not that serious really. Though it's be fun to have something we've been working on for half a year working decently the first time people actually get to try it... Well, well...

I value our most senior developer. His code is certainly clean and structured. He is the ultimate at KISS. However he's not a fan of testing and instead just says, well, did it compile? No matter how much I show him how great testing is, he comes back with how it's pretty unnecessary. Somehow, in the deep dark parts of the web, he finds articles that comply with his standing. I'm okay with him not making tests, I do it myself. But then when working extending or implementing his code, many of my parts are untestable because the parents are. Oye.

Spend nearly a full eight-hour day working on a piece of code that, while not at all trivial, would have taken probably two hours start to finish if not for the constant stream of interruptions bombarding me...

...but then, 10 minutes before quitting time, build and run it for the first time...

...AND IT FREAKING WORKS!

I'm never more scared than when ~1000 lines of code works the very first time it's run. Makes me want to check if I've signed any documents presented as a "deal" by a guy with a fiddle in a southern state :)

I wanted to rant like 10 times today but was on a tight schedule (yes its fucking sunday), so here is everything:

*********
Fuck you, i dont give a shit that you need to present data tomorrow, its weekend, you cant just fucking call me to get things done asap. Im working from the code of a dead guy do you know how fucking hard it is to ask a dead person whats their code do?

*********

I really wish devrant had some kinda longboard/skateboard in the profile pic

*********

Im still not a fucking designer i can make like does-not-make-you-barf tier designs, JUST TELL ME WHAT TO FUCKING CODE JESUS

*********

whys the new rick n morty episode not out yet wtf

*********

Yo i love linux but set the fucking privileges right you dipshit, i cant exrcute my damn code on your crappy ass 2008 xeon server fuck you

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.

0. working PCs
0.0 technically they are working, but they are too slow to even open up eclipse
0.1 maybe this gets better at university
1 coding on paper
2 not using google + usbs + network drives for code sharing
3 if it might be applicable PLEASE ENABLE THE FUCKING CMD! OR LET ME USE ARCH ON MY STICK! C'MON

When you are creating a tool for a direct client that has no idea about development. She asks you to develop a tool to open a log file and format in a specific way inside Excel.

Ok, this is simple. In about 4 hours I can do that. After delivery and the client has tested, they answer: "Oh, it's working fine. You just forgot to include Y".

Of course Y were not in the initial scope. They supposed it was as it would makes sense to them, but at first they just asked a tool open a log. Ok, not a problem, I will implement it.

Weeks after implementation they answered it was not working with another specific file format (from a not industry default tool), but they have this client and my code should work with it too.

Ok, let's implement that. I had to change some functions and with some extra hours I could make it work. Once more, after delivery, they said the tool has to use a specific formatting for this file extension, that was not only different to the others, but I had to rewrite the entire code to make it work.

At least they paid me some extra hours...

The website I'm working on went down because of a 500 HTTP error and halted my company of working

I should not code in production

I've only been working for a about 6 months, so this is the best I got.

I'm working with a software/programming language I've never worked with before this, so sometimes I have to go ask my co-worker if what I did is correct, or ask him where some information is stored.

So sometimes I do someting, and then go ask him if it's ok and I can continue. He looks at my code, starts asking questions and (sometimes, not always) says something like "this is not it, let's do it together". Alright, I understand that, I know I still make a lot of mistakes and I'm still learning how to work with this. It's all still very new to me.

We start looking for stuff, making queries, programming, etc. and then we end up with the exact same code that I had made... But, somehow, now it's correct...

This happens so much, I hate asking him things now!

Hey devs!!

I just can't stop myself from sharing this.

Its been two years now ... my junior is working. and now she is handling standalone WP projects.. but somehow her task got stucked so I was asked to help her.

So I just said check the count of variables and she messaged me with code .. Ma'am this isn't working .. Haha.. I mean come on she better can google out atleast for syntax :(

<?php if(count($content2 == 3) && count($interestt2 == 3))
{
print_r($content2);
print_r($interestt2);
}else{
echo "not checked";
}
?>

I’m either going crazy or someone just dropped a table from a database I’m actively working in. I don’t have a drop script for any tables in my code, not anywhere. One moment it’s right there, the next it’s gone? Luckily it’s pretty much empty, only generic data. On my way to check permissions.

The moment when your code is like,
Yeah I'm working, not throwing errors, but not doing anything closely related to the things I should do.

Fuck this construct, I'll recode the whole thing and stop using any two-year old legacy code, for this project

Colleague (Lead Engineer): Hey, check my code. I'm trying to group a list of Request objects by their id. Something is not working here

Me: * saw his code, had a lot of shitty loops, called all for a quick meet, changed his shitty mess to one liner

list.stream()
.collect(Collectors.groupingBy(Request::getId))

Walked out like a boss*
😎

This just crossed my mind. The company i applied at was working with the freaking Wordpress for webshops and still they think i’m not good enough for them. Next time better check the code i send better. Insane. Bunch of fuckheads

Build pipelines are awesome. What's not awesome is forgetting the 'pipeline' bit.

Sure, let's have each TeamCity job in the 'pipeline' build the deployable from different places! You must manually merge your code from dev to test to release.

What's that? The functionality working in dev isn't there in production? I wonder how that happened.

Today I got bug report on code that I thought was fairly well unit and manually tested by me while I was writing it.

What happened:
Our QA was testing other feature and asked someone to deploy into his env other branch, without these changes, and reported that this feature is just straight up not working at all.

That report was kindda big deal

Spent 2 weeks writing code in different services
Today D-Day for integrating all of it. And guess what, Friday evening and it's not working.

Gonna give up on Advent of code.
I know I'm not really a programmer and while I had fun solving the challenges so far it feels I fail to translate the idea of solution into working code. i.e. I know how it should be working, but when diving into the code I'm losing focus and getting lost in the functionality.
It was also good reality check of my skill level when a task took me 50 min while TOP100 is below 10. Can't really fit the time it takes me to come up with a solution with other activities I should actually be doing.

Thanks I hate it, I hate the fact that typescript will still transpile this. Not an exact copy of the code I'm working with, but close enough. Also this code targets es3, but we generate tsconfigs that say es5 (which don't actually get used) which leads me to believe that we generate them soley for the benefit of ides, and because if they said es3 the ide would show even more errors

For the new/aspiring developers:
1. If you are still looking to learn more, but you don't know where to go, start brainstorming. Make a list of projects you could make and sort them by difficulty. Put the ones you could do now at the top of the list, and the ones you aren't sure how to do yet, at the bottom of the list. As you go through them, if you want to do something but aren't sure how, just hop onto an irc chat and everyone will be glad to help. As you go through the projects, your logic and program design skills should improve, as well as your knowledge of programming.
2. Put comments in your code. Seriously. If you are working on a project and suddenly stop working on it for a week or more, you will go back to look at that code and be extremely confused. If you are making something open source, its even more important. If people can understand the code, they are more likely to contribute to it.
3. Try not to focus on code for too long. The longer you work, the more tired your brain gets. Eventually you get tired and make really stupid decisions in your code.
4. Don't code while tired (look at #3)
5. If you are writing code as an assignment, make sure to rename all variables to proper names before submitting it. The instructor will likely not be pleased to see variable names with the f-bomb in them.