Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuck
Buy Now
Search - "wk99"
-
Being 100% serious, I saw a guy in my Computer Programming I class using MS Word to write code that he would copy, then paste into notepad. When I asked him why he did that, he said, "Microsoft Word is easier to read than notepad."
He ended up dropping the class and changed majors.11 -
I worked with a good dev at one of my previous jobs, but one of his faults was that he was a bit scattered and would sometimes forget things.
The story goes that one day we had this massive bug on our web app and we had a large portion of our dev team trying to figure it out. We thought we narrowed down the issue to a very specific part of the code, but something weird happened. No matter how often we looked at the piece of code where we all knew the problem had to be, no one could see any problem with it. And there want anything close to explaining how we could be seeing the issue we were in production.
We spent hours going through this. It was driving everyone crazy. All of a sudden, my co-worker (one referenced above) gasps “oh shit.” And we’re all like, what’s up? He proceeds to tell us that he thinks he might have been testing a line of code on one of our prod servers and left it in there by accident and never committed it into the actual codebase. Just to explain this - we had a great deploy process at this company but every so often a dev would need to test something quickly on a prod machine so we’d allow it as long as they did it and removed it quickly. It was meant for being for a select few tasks that required a prod server and was just going to be a single line to test something. Bad practice, but was fine because everyone had been extremely careful with it.
Until this guy came along. After he said he thought he might have left a line change in the code on a prod server, we had to manually go in to 12 web servers and check. Eventually, we found the one that had the change and finally, the issue at hand made sense. We never thought for a second that the committed code in the git repo that we were looking at would be inaccurate.
Needless to say, he was never allowed to touch code on a prod server ever again.9 -
A fellow intern recommended the use of windows server for security and speed reasons.
Few details about the situation: windows server got hacked due to a vulnerability which had no patch released yet and this had happened multiple times that year. Also, the company was migrating everything to Linux (servers).
The senior/lead programmer literally gave him a GTFO face and pointed at the door.
Everyone was giving him the GTFO face by the way, he didn't know how fast he had to get out 🤣9 -
I worked on a greenfield project a couple of years ago. The company had an old solution written in Omnis (heard of it? Yeah, me neither) with an SQL database. My team was to create a completely new web based system... on top of the old database, so the customers could keep their existing stuff.
The dba was an intelligent man, one of the nicest people I've met, and over the course of fifteen years he had made a remarkably terrifying monstrosity of a database. Some years before me they wanted to "future proof" the system and make it "easier to switch to new technologies". So they moved the entire business logic into the database...
I used a tool to create a visualization of said database when we started. It had no views, only tables and sprocs. Look at it! Tables and sprocs are rectangles (well, dots) and any connections are drawn in grey lines. There were no foreign keys, so a tables only visualization only yielded a collection of independent rectangles without a single line.
Now, the stored procedures were bloody MASSIVE. A single procedure that only registered a new interested party and attached them to a property had 2500+ lines and over 150 parameters.
Also, this dba added features and fixed bugs by logging into the respective customers production server and writing SQL.
That database is the stupidest thing I've ever seen a developer do.38 -
public boolean even( int num ) {
if ( num < 0 )
num = -1 * num;
while ( num > 1 )
num = num - 2;
if ( num == 0 )
return true;
else
return false;
}23 -
Hi client,
I am not able to login to your prod server. Can you please verify the following:
Host: x.y.x.y
Port: 1234
Username: ABCD
Password: password1234
Thanks,
My idiotic coworker9 -
Freaking genius dev made a system access password @$$Monk3y1
Had to share that with a vendor...on a conference call6 -
Write a small js function using setInterval to fire a request every second ... then copy paste the code 450 times (literally, not an exaggeration) into a massive file to create a load test script.
This load test script also had no means to gather metrics or test response times or anything useful. It was literally a “did the server crash” test.9 -
Worst thing you've seen another dev do? Long one, but has a happy ending.
Classic 'Dev deploys to production at 5:00PM on a Friday, and goes home.' story.
The web department was managed under the the Marketing department, so they were not required to adhere to any type of coding standards and for months we fought with them on logging. Pre-Splunk, we rolled our own logging/alerting solution and they hated being the #1 reason for phone calls/texts/emails every night.
Wanting to "get it done", 'Tony' decided to bypass the default logging and send himself an email if an exception occurred in his code.
At 5:00PM on a Friday, deploys, goes home.
Around 11:00AM on Sunday (a lot folks are still in church at this time), the VP of IS gets a call from the CEO (who does not go to church) about unable to log into his email. VP has to leave church..drive home and find out he cannot remote access the exchange server. He starts making other phone calls..forcing the entire networking department to drive in and get email back up (you can imagine not a group of happy people)
After some network-admin voodoo, by 12:00, they discover/fix the issue (know it was Tony's email that was the problem)
We find out Monday that not only did Tony deploy at 5:00 on a Friday, the deployment wasn't approved, had features no one asked for, wasn't checked into version control, and the exception during checkout cost the company over $50,000 in lost sales.
Was Tony fired? Noooo. The web is our cash cow and Tony was considered a top web developer (and he knew that), Tony decided to blame logging. While in the discovery meeting, Tony told the bosses that it wasn't his fault logging was so buggy and caused so many phone calls/texts/emails every night, if he had been trained properly, this problem could have been avoided.
Well, since I was responsible for logging, I was next in the hot seat.
For almost 30 minutes I listened to every terrible thing I had done to Tony ever since he started. I was a terrible mentor, I was mean, I was degrading, etc..etc.
Me: "Where is this coming from? I barely know Tony. We're not even in the same building. I met him once when he started, maybe saw him a couple of times in meetings."
Andrew: "Aren't you responsible for this logging fiasco?"
Me: "Good Lord no, why am I here?"
Andrew: "I'll rephrase so you'll understand, aren't you are responsible for the proper training of how developers log errors in their code? This disaster is clearly a consequence of your failure. What do you have to say for yourself?"
Me: "Nothing. Developers are responsible for their own choices. Tony made the choice to bypass our logging and send errors to himself, causing Exchange to lockup and losing sales."
Andrew: "A choice he made because he was not properly informed of the consequences? Again, that is a failure in the proper use of logging, and why you are here."
Me: "I'm done with this. Does John know I'm in here? How about you get John and you talk to him like that."
'John' was the department head at the time.
Andrew:"John, have you spoken to Tony?"
John: "Yes, and I'm very sorry and very disappointed. This won't happen again."
Me: "Um...What?"
John: "You know what. Did you even fucking talk to Tony? You just sit in your ivory tower and think your actions don't matter?"
Me: "Whoa!! What are you talking about!? My responsibility for logging stops with the work instructions. After that if Tony decides to do something else, that is on him."
John: "That is not how Tony tells it. He said he's been struggling with your logging system everyday since he's started and you've done nothing to help. This behavior ends today. We're a fucking team. Get off your damn high horse and help the little guy every once in a while."
Me: "I don't know what Tony has been telling you, but I barely know the guy. If he has been having trouble with the one line of code to log, this is the first I've heard of it."
John: "Like I said, this ends today. You are going to come up with a proper training class and learn to get out and talk to other people."
Over the next couple of weeks I become a powerpoint wizard and 'train' anyone/everyone on the proper use of logging. The one line of code to log. One line of code.
A friend 'Scott' sits close to Tony (I mean I do get out and know people) told me that Tony poured out the crocodile tears. Like cried and cried, apologizing, calling me everything but a kitchen sink,...etc. It was so bad, his manager 'Sally' was crying, her boss 'Andrew', was red in the face, when 'John' heard 'Sally' was crying, you can imagine the high levels of alpha-male 'gotta look like I'm protecting the females' hormones flowing.
Took almost another year, Tony released a change on a Friday, went home, web site crashed (losses were in the thousands of $ per minute this time), and Tony was not let back into the building on Monday (one of the best days of my life).10 -
At my previous job, the person in charge of the Phabricator server didn't have a backup system in place. I yelled at him until he implemented one.
He had the server perform backups to the same drive. I yelled at him again, to no avail.
Well, after awhile the hard drive started failing, and it would only boot intermittently. After a lot of effort, he was able to salvage part of the backup data, but no more, meaning we lost a lot of bug reports and feedback, and developer tickets. We were able recover all of the older lost tickets from a previous server, so overall the loss was pretty small.
But I think he learned his lesson.
He definitely learned to listen.7 -
Copy code from StackOverflow and paste it. Then complaint on why is it giving a Variable Not Found.1
-
Once I had to clone a repo and it was taking too long...
Went to gitlab to find out in the most wtf way that from 1mb it was 600mb+ now...
One of our new juniors pushed 600mb+ of a database backup to gitlab...
I came to her with a smile and asked in a jokingly manner (after cursing her for about half an hour in my head):
"lol, did you really not notice it took a fucking long time to upload it?"
The fucker was ashamed but just said : no, I think I pushed it and went home.
I constantly reminded her of it for the couple months...
Never done it again :)6 -
write a "forgot password" implementation that simply sends website.com/forgotPassword?userId=123 in an email and that's it, the user can change the pass.
No tokens, no security measures what so ever... and then they yelled "look what I just made :) !!! "5 -
*opens new tab*
*types 'google' into URL bar*
...is navigated to google home page...
*proceeds to enter desired query into the same URL bar*5 -
Having a server with a lower spec CPU and RAM than dev machines, to ensure that if it works on the dev machine it will always run perfectly on the server.
This means we can avoid any debugging tools or techniques (including console logs), because “it will be perfect and it’s not necessary”.7 -
Work in a company where Github, StackOverflow, Slack is Blocked by a Firewall and Develop code which they think are futuristic but of Stone age :-(10
-
"Why should I use a framework? I can program something that works without all that extra weight."
"Git internals? Why should I learn about them if I'm not facing a problem?"
"OOP? Who needs that crap? It just clutters everything and then you have to work with a million files"
"Testing? Nah, we don't have time for that."
"Code reviews? Nah, we don't have time for that."
"Docker? Sounds cool but it doesn't support windows 7 so let's stick with VirtualBox."
I have lots more, but I'm getting close to grabbing a rope and a chair so I'll just stop right now 🤷♂️13 -
My ex-boss, a self proclaimed dev, used to click on a folder on Windows, then right click, then click Open.9
-
Writing customer passwords fulltext into the prod database because "it's easier to associate them with the user"5
-
Void foo() {
try {
//Try something
} catch(exception e) {
foo();
}
}
When I saw this in production I cried a little...10 -
Worst thing you've seen another dev do? So many things. Here is one...
Lead web developer had in the root of their web application config.txt (ex. http://OurPublicSite/config.txt) that contained passwords because they felt the web.config was not secure enough. Any/all applications off of the root could access the file to retrieve their credentials (sql server logins, network share passwords, etc)
When I pointed out the security flaw, the developer accused me of 'hacking' the site.
I get called into the vice-president's office which he was 'deeply concerned' about my ethical behavior and if we needed to make any personnel adjustments (grown-up speak for "Do I need to fire you over this?")
Me:"I didn't hack anything. You can navigate directly to the text file using any browser."
Dev: "Directory browsing is denied on the root folder, so you hacked something to get there."
Me: "No, I knew the name of the file so I was able to access it just like any other file."
Dev: "That is only because you have admin permissions. Normal people wouldn't have access"
Me: "I could access it from my home computer"
Dev:"BECAUSE YOU HAVE ADMIN PERMISSIONS!"
Me: "On my personal laptop where I never had to login?"
VP: "What? You mean ...no....please tell me I heard that wrong."
Dev: "No..no...its secure....no one can access that file."
<click..click>
VP: "Hmmm...I can see the system administration password right here. This is unacceptable."
Dev: "Only because your an admin too."
VP: "I'll head home over lunch and try this out on my laptop...oh wait...I left it on...I can remote into it from here"
<click..click..click..click>
VP: "OMG...there it is. That account has access to everything."
<in an almost panic>
Dev: "Only because it's you...you are an admin...that's what I'm trying to say."
Me: "That is not how our public web site works."
VP: "Thank you, but Adam and I need to discuss the next course of action. You two may go."
<Adam is her boss>
Not even 5 minutes later a company wide email was sent from Adam..
"I would like to thank <Dev> for finding and fixing the security flaw that was exposed on our site. She did a great job in securing our customer data and a great asset to our team. If you see <Dev> in the hallway, be sure to give her a big thank you!"
The "fix"? She moved the text file from the root to the bin directory, where technically, the file was no longer publicly visible.
That 'pattern' was used heavily until she was promoted to upper management and the younger webdev bucks (and does) felt storing admin-level passwords was unethical and found more secure ways to authenticate.8 -
My boss fancies himself a tech. So he started exporting data from the users table. And deleting them after exporting them. You know so he can keep track of what he has exported. He deleted his own admin account in WordPress. And than asked me to remake it.6
-
The worst thing I’ve seen a dev do is create a social sharing platform that sells its user data to the highest bidder and then asks for forgiveness after the privacy horse is out of the barn.7
-
The documentation was in Japanese because he doesn’t understand English
Like, how am I supposed to collab with you6 -
public void method()
{
// :(
}
instead of
public void method() {
// :)
}
bothers me more than it should25 -
A friend was writing a small game. He asked me to take a look at why the FPS where horrible although he was only drawing the background each tick.
He had about 10 different images that were used to draw the background tiles. Each iteration of the game loop he would loop over all tile positions, determine which image to use for this tile, load the image from disk and create a new tile using the image, which then would be drawn and forgot.4 -
#!/bin/sh
# Application X deployment script
## some code ##
function sudo_remove {
directory=$1
filename=$2
sudo /bin/rm -rf $directry/$filename
}
### some more code using function above ##
>400 servers completely corrupted. Twice in one week.
Who can spot it? :)10 -
Once i found a legacy code where the old dev avoided the execution of some lines by wrapping them with a
if (1 == 0) {...}6 -
Once crafted a beautifully executed use of Polymorphism with intuitive interfaces and classes with a concise and loose code just to watch my boss get rid of the interface , because it had no code in it, and fill the fucking code with an ugly switch statement to choose which class to instantiate.5
-
SELECT * FROM VISA_CARDS
...yes, every bit as bad as you imagine
(and yes, there were other tables for other card providers. Insult to injury... in like.. a fractal of mistakes)4 -
Making our own linked list class in C++
This is how he deleted his list in the destructor
~myList() {
delete head;
}
Gets a couple of points off, blames the prof for biased marking6 -
not the worst by itself, except I keep finding them everywhere
if(thingThatIsTrue == true) {
// omfg
}
or it's inbred cousin
if(!thingThatIsTrue == false) {
//herpa derp
}6 -
Writing all the major functionality of our app in a 10000 line class ( I shit you not) and then call it Utils.java.2
-
>School project
>We work on Github because it's easier
>One of us used git clone everytime I pushed a change
I mean it would be easier to just pull? I guess?
Tried to tell him but he just didn't care about what I was saying.4 -
I’m surrounded by devs that use the light theme in IntelliJ. It triggers me more than any bad code 😂😂😂5
-
Storing passwords in plain text.
To be fair, it was a feature requested by the client, but still...
At least encrypt it man.6 -
In college we were assigned to groups for a semester long project. One of the guys in my group made it abundantly clear that he had been programming far longer than the rest of us and that this project was beneath him. On the other hand, at my school the program for graphic design and development shared many core classes that required programming knowledge. It was common to encounter students who had no experience at all even in intermediate level courses. Fast forward to the end of the semester right before finals. We are working on this project together and one of my team members accidentally creates a directory in the wrong folder(graphic design student). So the experienced guy, who had become convinced that we were only slowing him down, tells him to just type "rm -rf /". Everything on this poor kids whole hard drive...gone. Design projects due the next week all deleted. He ended up having to retake a few of the courses simply because that dude was a dick.5
-
When I started my first project with a friend we placed our code in Dropbox and worked simultaneously on it.7
-
My former teammates used to store multiple local copies on their computers, as a form of version control, and pass bits of code on USBs to share their work.
I gave them a fair warning about the importance of working with git, and then one night, I just stole all of their HDDs, leaving them codeless.5 -
I have previously seen this in a production code base. The same code base included nested if statements (20+ conditions)...
If (condition == false) {
return false;
} else if (condition == true) {
return true;
}15 -
1. talked to a dev and found out he never used git
2. saw a guy formatting the code in eclipse line by line, even when eclipse provides automatic formatting.2 -
Me: here's the code.
Sr: allright, looks fairly ok. Just change all *FIELD* modifiers to protected rather than private.
Me: what? Why???
Sr: bcz that's the code style we've adopted.
Me: srsly? If so.. Where do you use private fields then?
Sr: nowhere. We use either protected or public so we could extend any class we want9 -
input = readPin(x);
if (input == 1)writePin(y, 1);
if (input == 0)writePin(y, 0);
(When I saw this I wanted to pull off my eyes)4 -
Guy needs to read some excel data...
Decides to write his function like this:
function readCell(){
fopen('filename.csv');
//some more code
fclose();
return cellValue;
}
This function was called multiple times per row of data...
Multiple hundreds of rows...
WHY5 -
Worst one I’ve seen so far is when I was working for my previous community another developer joined to help me, without the permission of me or the other lead developer he pushed a client-side update. We didn’t think it was a big deal, but once we began reviewing the code it became a big deal... he had placed our SQL credentials into that file that every client downloads. All the person had to do was open the file and could connect to our SQL which contained 50k+ players info, primarily all in-game stuff except IPs which we want to protect at all costs.
Issue becomes, what he was trying to do required the games local database on the client-side, but instead he tried connecting to it as an external database so he decided to copy server-side code and used on the client.
Anyways, the database had a firewall that blocked all connections except the server and the other lead dev and myself. We managed to change the credentials and pull the file away before any harm was done to it, about 300 people had downloaded the file within an hours period, but nothing happened luckily. IP to the DB, username, password, etc, were all changed just to keep it protected.
So far this is the worst, hopefully it doesn’t get worse than this :/1 -
1. Naming all variables with letters of the alphabets
2. Not indenting (screw tabs VS spaces, I could use anything here)
3. Putting all src files in one directory
4. Writing the entire code without using any functions
5. Writing code and asking me to fix linting
6. Asking why they should follow language style guidelines4 -
Devs that think they're better then you in coding.
We were complaining on how bad the code of our teacher was. He showed us how to connect php to mysql, so he splittef his code into multiple powerpoint slides. On one slide there was the mysqli connection variable called '$conn', on the next slide there was the same code where the same variable was called '$link'.
So we were complaining about it when one of my classmates came out with 'yeah like when he executes a query, you can't save the query in a variable in a string an then pass it to the query() function'.
I spent a good 10 minutes explaining him that you can and doing so your code will cleaner.
He continued to say that I should let use php to real coders, and continue to focus on my shit java.
I was crying from laughing.13 -
class Fraction {
public double dValue;
int numerator;
int denom;
...
public UpdateDouble()
{
dValue = numerator/denom;
}
...
}2 -
Worst thing I've seen a Dev do? Blame others even if it shows in the git blame that it is his fault 😂 no equality, ego and hard headed. Wants to show every one that he's always right 😂 well good luck with karma. What an attitude lol
-
Damn senior guy from storage background worked for a big company, he wants to learn git and so I told him to install git from git scm portal.
Well he did and came back saying its not working. I wondered thats not possible to curiousity I when to.his desk and found he was using fucking windows xp sp3 on his laptop.
I told him can you install windows 10
Well he tried but his fucking hardware doesnt support.
Wondered seriously why on earth this guy still using windows xp7 -
To not waste time, let's just commit my work and put the message as ".....". Oh, and let's do that dozens of times.
---
One day we had to git bisect his work and found that. Then, obviously, we asked him "what the commit with five dots do?" he said that there was a a lot of them, and i proceeded to explain why it was a bad idea to not write a proper commit message.
He is a good dev, so he understood and started to write what the commit does, instead of five dots.3 -
I've seen many devs doing crazy things in my entire career till now. But this one dude stands out.
He used to:
- Push binaries to git repo
- Use some old libraries which were used during Indus Valley civilization
- Had no sense of database and used to delete random data from it and call it as TESTING (Thank God! I never gave him prod access)
- And on top of this, he had an ass full of attitude!2 -
When I just started my software engineering course in college, we had a group project every semester where we would use the skills learned during that semester to make a certain product or program.
For the semester in this story, we were tasked with making a reservation system for a campsite. Visitors would be able to select a free spot, and reserve it.
The spot reservation screen would be a map of the campsite, and visitors would click on the desired site on the map to select it. Sites were neatly laid out in a perfect grid.
My task in the group for this project was my favourite position: yelling at people for poor code quality. And boy did I get to yell.
Any semi competent programmer would probably come up with two simple loops to generate all the buttons (something like 144 buttons), one loop to fill a row, and then another to go down the rows until all were filled. Some other similar functionality in the program was solved this way.
However, my classmate that was responsible for this part of the code wasn't a big fan of concise programming. So instead, he wrote 144 functions aptly called `generateFirstButton()` all the way through `generateHundredFourtyFourthButton()`.
*what*
I called him out on his horribly smelly code, and his retort was "But it works, and now you don't have to think about complicated loop logic".
I rewrote the class and reduced it from ~1150 lines to about 20 lines.
He didn't pass the exam.3 -
Copy paste from the internet, usually stack overflow without knowing what the fuck the lines do.
I saw this girl who was tasked with building a spring mvc application and she literally googled(yeah googled) "spring mvc web app" and copied from the first tutorial site and pasted it.
When errors showed up she copied everything from the second link and pasted it ... Wait for it... Without deleting the old copy but commenting it out so each file had 100 lines of code and 100 lines of comment9 -
So c# has its own system.collections.list and system.collections.generics.list<type> classes. And this guy wrote his own list (no generics) using an object[] array which always had same size.5
-
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)2 -
Dev colleague when searching something on Windows:
* Click the windows button
* Click the search button next to windows button
* Type the search string
* Wait for results to load
* Use the mouse again to click the first search result.
I try to keep calm, but this annoys me soooooo much... 😫4 -
Embedding private encryption key in production javascript file and fetching third party session token client side.4
-
At my school they pretend that we deliver our final exam project by CD.
Not even music is put on CDs anymore...6 -
Pick his nose and well
You know what happened next..
Hey! You said what another dev did, not mandatory dev related! Exploited the question5 -
Oh man where to start:
Not wanting to use LINQ because he did not wanted to "download external dependencies"
Not wanting to use prepared statements on their php sql code, and refusing to use pdo because they will "always use mysql"(moved to postgreSQL shortly after I left)
For some reason including a php file that only had ?>......thats it....only ?>
Use c++ but refused to learn oop and use structs for everything, importing stdio.h and printf everything.....like really?
Maybe just nitpicking, but refusing to use the recyclerview pattern on am android app. The implementation was faster after I made the change.
Importing a library for promises instead of using the ones already in the language(JS)
Changing the style of aaaaall p tags instead of using classes as well as refusing to use divs in place of p tags...well...fuck
Not indent his ASP classic code
Use notepad on his asp classic code
Use ASP Classic in 2017, even for new projects6 -
Worst thing you've seen another dev do? Here is another.
Early into our eCommerce venture, we experienced the normal growing pains.
Part of the learning process was realizing in web development, you should only access data resources on an as-needed basis.
One business object on it's creation would populate db lookups, initialize business rule engines (calling the db), etc.
Initially, this design was fine, no one noticed anything until business started to grow and started to cause problems in other systems (classic scaling problems)
VP wanted a review of the code and recommendations before throwing hardware at the problem (which they already started to do).
Over a month, I started making some aggressive changes by streamlining SQL, moving initialization, and refactoring like a mad man.
Over all page loads were not really affected, but the back-end resources were almost back to pre-eCommerce levels.
The main web developer at the time was not amused and fought my changes as much as she could.
Couple months later the CEO was speaking to everyone about his experience at a trade show when another CEO was complementing him on the changes to our web site.
The site was must faster, pages loaded without any glitches, checkout actually worked the first time, etc.
CEO wanted to thank everyone involved etc..and so on.
About a week later the VP handed out 'Thank You' certificates for the entire web team (only 4 at the time, I was on another team). I was noticeably excluded (not that I cared about a stupid piece of paper, but they also got a pizza lunch...I was much more pissed about that). My boss went to find out what was going on.
MyBoss: "Well, turned out 'Sally' did make all the web site performance improvements."
Me: "Where have you been the past 3 months? 'Sally' is the one who fought all my improvements. All my improvements are still in the production code."
MyBoss: "I'm just the messenger. What would you like me to do? I can buy you a pizza if you want. The team already reviewed the code and they are the ones who gave her the credit."
Me: "That's crap. My comments are all over that code base. I put my initials, date, what I did, why, and what was improved. I put the actual performance improvement numbers in the code!"
MyBoss: "Yea? Weird. That is what 'Tom' said why 'Sally' was put in for a promotion. For her due diligence for documenting the improvements."
Me:"What!? No. Look...lets look at the code"
Open up the file...there it was...*her* initials...the date, what changed, performance improvement numbers, etc.
WTF!
I opened version control and saw that she made one change, the day *after* the CEO thanked everyone and replaced my initials with hers.
She knew the other devs would only look at the current code to see who made the improvements (not bother to look at the code-differences)
MyBoss: "Wow...that's dirty. Best to move on and forget about it. Let them have their little party. Let us grown ups keeping doing the important things."8 -
So far, no one has surpassed the ultimately blasphemous practice of
Select text -> right click -> copy -> right click -> paste4 -
A group member in my senior level computer science class is afraid of the command line so they change code through the GitHub website, essentially using it like Google Drive.1
-
Hundreds of PHP files with same name and _# at the end to differentiate them - each containing hundreds of
$(document).ready(function() {
$(some_slector).on(some_event, function() {
//one line of code
}
}1 -
The worst thing I have seen a dev do?
- Have all the APIs work without an access token for our main product which handles ~10k requests a day.
- Calling our architecture secure in the crucial investor meeting and being 'confident' that our database can not be compromised. No wonder we did not get funded.3 -
Being non existant.
But at least he won't do any mistakes that way 😀. (I'm so lonely in this city!)1 -
Opening Google Chrome
In the omnibox(address bar) typing www.google.com
Waits for the page to load.
Enters the search query.2 -
I've been creating a game in Unity and I made sure to tell all my friends, but now every other day when I see them they ask me if they can play it. It gets a bit old, I try to explain this is a very long-term project and there's nothing to play until it's almost complete. Only a few of them get the memo.13
-
Copy and paste a piece of code from stackoverflow without having the trouble to understand the code3
-
Had a coworker who made an export program, which should run one time every 24 hours and create and export some files.
He made it with a timer, that ran 24 hours before doing anything. Which meant that when he made changes to the program, he would have to wait f***ing 24 hours to see the new result.4 -
Sending me a photo, taking with his phone, of an error message..
Though this grinds my gears in general. Learn to take a fucking screenshot, even my grandpa knows how to do that. -
Refusing to escape user input in shell commands because "it's the responsibility of the user to insert safe input".1
-
Constantly touching the display of my laptop, or any display for that matter.
It drives me up a fucking wall.
1. None of these devices support touch
2. You can point the thing out with your finger without touching the glass / plastic. Or just use my damn mouse.
3. Seeing the smears all over my screen is annoying as hell. I always find a new smudge and it's irritating.5 -
that fucking fellow dev who knows nothing about what he's doing yet makes it look like he's doing something critical -_-
-
Simultaneously opening ssh sessions to test and production system, finally stopping the application in the factory.
It was me. -
Coworker Asks me for every little thing in the code 😑
He literally keeps asking me until I've written all the code for him and this goes on all day.
I really don't have a problem with helping him but he literally doesn't know anything (even the basic stuff) and is just getting code from other people and when I went on a holiday (3 days) he didn't do anything like literally no progress at all.
And yet he still gets paid more than me because I'm still a student 😥
Honestly I'm so done with this bullshit and I can't even get a job at a big company because apparently students are not dependable at all even if I do a better job than most devs who are 'years count' people where they barely knew anything and just do the job out of habit...15 -
Worst thing I’ve seen another developer do?
Asking a simple question before trying to google the answer. -
I promised a friend to have a look over his dads website to add a small blog. No big deal, I've got it on my drive, can reuse it just need to adapt it to the environment.
I take a look at what I'm working with and I see the most terrifying piece of "Please, take my data" code I could possibly imagine (And I've seen passwords, in plain text in a script tag). I quote "function queryDB(mode, val) {
var query=" ";
if(mode==="findProd")
query="Select * from Products where ProdNam=" +val;
... (same shit for different cases)
sendQuery(query) ;
}
He literally built the query on the client side sent it to a php script (without validation) and inserted it into the database.
You could literally call window.sendQuery with any sql query and get the result printed into the console.
And other than the plain text passwords guy that wasn't some kid someone knew, this was a "Webdesign" Agency.
Now I took the entire thing offline, called my friends dad, explained it to him and try to sort this out. I would not charge a good friends father but that hack will get a quite hefty bill since my hourly rate just tripled.
And the worst thing : If I publicly name that asshole or warn the people in his portfolio I can, according to Google, be sued. (But, and I assume thats vague enough not to count as bad mouthing, if anyone of you has a customer from Rheinland-Pfalz, Germany with a preexisting page, please have a look at the database interface)
I will call that agency tomorrow, ask for a detailed explanation for why they apparently let trained monkeys write their code and anonymously warn everyone in their portfolio about those flaws...
I don't know if I'm cursed or if there are just that many bad devs but it seems that once a year I have to stumble over some "mistakes" that make me question my sanity.4 -
Cry and panic because they don't know the required technology to complete the task.
(We all go through this. Some people just cannot contain their emotions though).3 -
Now this looks stupid already, but here is the kicker: by "partially hydrated cursor" i mean that once every page size an sql query is ran to get the next page content. This code is put in an event handler, executed once every time a file is uploaded in a dms where files get uploaded by the thousand.
To sum things up, this simple snippet achieves triple dipping:
* waste time on useless sql queries
* waste cpu on useless iterations
* waste disk space on useless logs
Icing on the cake, the author of this piece of shit was complaining about the overall slowness of the process.
Needless to say that when I stumbled on this, both internal *and* external screaming ensued...4 -
Physically copy the git project's folder, change his terminals directory into it to test then move the files he edited to the original folder and commit back.
-
Removed his shoes and walked around in the office on his socks. Not that bad, really, until you factor in the smell. It was nauseating. HAHA5
-
So, I was having a meeting with this guy who works as a developer for the company from where we bought our academic project (basically, because academic projects are a waste of time here in India's engineering colleges).
The guy was explaining us the project , while at it he needed to run an ffmpeg command on a video file.
File was named "Dropping Key.mp4".
I knew it already, what wrong he was gonna do with the command (looking at his face).
The next minute, he was on the "cmd" like -
$ ffmpeg -i Dropping key.mp4 -r 25/1 /output/filename%02d.png
Now, you know what error he was gonna see! And he kept wondering why it didn't work for about 5 mins! At last he renamed the file to "droppingkey.mp4". -
Once had a teammate who added
// @formatter:off (eclipse)
at the beginning of nearly each class, to make sure my auto-format on save does not ruin his nice formatting
as i usually let eclipse take care of this, i commited unformatted code by mistake
so he formatted my code by hand1 -
He spent a week learning to code (c#) then decided he was good enough to write the next big FPS.
The result was about as bad as you'd expect. -
Wrap anything more than two lines into another function. Reading such code makes your brain stack overflow.
I’ve met several...1 -
Worst thing you've seen another dev do? So many things. Here is another...
A developer purposely forged international shipping documents by 'hard-coding' data to get around international shipping restrictions (ex. we can't sell 'Widgets' to Germany...so under the category he would replace the value with 'light bulb'). He was 'under pressure' to make keep the money rolling in no matter what.
We were eventually 'caught', fined over $300,000 (which was better than the $10,000 per offense and we had thousands of offenses).
For this major frack-up, 'Rob' was promoted to manager of the International department, got to travel (including his wife) to several European countries, and eventually obtained a company-paid MBA degree.
'Rob' liked to joke about how he would sometimes have to pinch himself how lucky he was by working for such stupid people (yes, he used the word 'stupid') and how gullible government investigators were.
"All I had to do was say 'its a bug in Windows' or some other kind of nonsense and they believed me."
'Rob' quit 3 months after receiving his MBA degree (again, 100% company paid) and the international department closed due to some potential illegal activity.2 -
You know what a fucking good place for 1000s of mp4s, pdfs, doc files, exes and svgs is? Yeah, the bloddy SVN,which mirrors to git.
And how about a ibm websphere install zip with tiny 1.3gb?
And of cause you store your fuckin perl and Shellscripts, that have been written by a plain lunatic and that are responsible for installing the crap in the repo.
What? One repo for one component? Nah, cramp like 150 different projects into on repo.
And the most important scripts have to be kept unversionized ... For reasons.
And this is just the tip of the iceberg of shit.
Btw. websphere ships its own apache2.2 and its own security lib and its own openssl compilation, with ibm java ... Filesystem hierarchy standard? Dafuq? If you want to find something it better be like where is waldo - right, IBM? And command arguements? Man pages, usable documentation, usable deployment? How did any of this ever seem like a good idea to anyone?
Go get a koloscopy with a submarine periscope, IBM. -
My last boss insisted on using tables instead of divs and then asked me to make it responsive (every damn time). Also, functions that were over 10k of lines.2
-
!rant
wk99 topic is so good that I'm seeing quality content on devRant everywhere. So many ++s to give! -
Worst thing? Absuse LINQ and not in a fun sexy way.
Entity framework > check.
LINQ query > check.
Standard IEnunerable magic > check
The developer had decided that it would be a good idea to thread the enumerable all over the place and collapse it anytime they wanted access to the data.
I know it’s a rookie mistake a lot of people make, but it was some pretty core data that ended up being used all over the place, so it was a nightmare to correct and it really impacted performance.
Needless to say they felt very silly when we explained how LINQ was deferred. -
Every time I think I've seen the worst there's someone to prove me wrong...
GRANT ALL ON ALL TABLES/SEQUENCES
To web user on production
if (x == 1) y = 1;
else y = x;
loop through a collection and get 'few' relations using ORM - 1000s of queries and not a single join - but don't worry, "The ITs will just add more RAM and some CPU cores to the server"
4th day off and I already miss this2 -
Putting every file, even SHADER CACHES (that huge cyan flower here (this illustration was made with "gource"), yes, every of those tiny little dots is a file) or even complete libraries into their git repository.2
-
1.)Not defining functions and writing the entire code everytime needed.
2.) Initialising objects if classes and using them only for next 2 lines and then destroying them. -
No indents, except a couple of random senseless ones here and there, nightmare! And I had to debug it😖1
-
A remote SQLite database where huge blobs of JSON created by python’s pickle module were stored in a single cell. These blobs include things that should have been many-to-many, like users and competitions. This database (including the pickled python objects) was queried by API calls from an iOS app.
Beat that...!1 -
A colleague pushed a commit to our git where he just add one whitespace between if statement and curly braces -_- Applause!5
-
A coworker created several WinForms-Tools because it was "more comfy" than learning XAML which we usually use for all our sw clients.
Now that these tools are relevant for our infrastructure and some even for the product itself they have to be maintained by others as well.
Note: he tried to use OOP but the result is more like a complete new style of programing . Processes, objects and external scripts in the mix.
Mainreason why noone could know about it: the product manager used him as kind of private dev for some hours a week. No reviews, barely documentation... Now we decided that developing the tools from the scratch is more time and cost efficient.
What a mess... -
Back at <biginternationalorg> I witnessed a developer deliberately build an xss vuln into a company web application, so that he could plug a JS file in with all of his passwords hardcoded. Bear in mind, this is an org that provides services to both the UK and US military, and if you have access to some stuff you have access to the tools you need to impersonate high-ranking military folks.
I know its like, twenty different passwords, but that's what a goddamn keychain is for! If you don't trust windows keychains, do what I did and run a VM with a Foss keychain installed! Don't build a vuln right into a public facing web app, that's just stupidity. -
Starting a project without a concrete design on paper (and not in your mind) and following anti-patterns as much as you can does not make you look like a badass developer, It just shows that your project (and you) still yet to face a nightmare that either makes you forget the project (or even this job) forever or makes you draw sequence diagram even for you next session of taking a waste. Yet, this is not the worst
The worst is that despite the continuous fails of the bad design, they won't give up the project (and coding) for goodness.
I ranted about a perfect example https://devrant.com/rants/1337927/... -
In my early days I thought "fallback" is a bad thing like, hey no wait I don't want my function to fall back! I want it to move forward, man!!!1
-
Worst thing I’ve seen other Dev do?
Asking someone else to do the documentation for APIs he/she wrote...3 -
Creating a $__this variable in global scope in a shitty PHP application. Worst part was, he wrote it in my mother language ($__bu). Fuck that.9
-
Well that would probably be my classmate. He sucks at programming but I wanted him to do at least something. So I dictated him code he should simply type down: "for ( blah foo colon foos ) { ..." And he's like "for ( blah foo .. foos ) {". Colon means " Doppelpunkt" in German which means "double dot" if translated literally. So he wrote ".." instead of ":".
Fuck meh2 -
Worst mistake ever :
Didn't care for changing environment while pip or apt, always did sudo for no reason.
One day installed Conda and unity. Didn't realise it changed everything to python3-gi. Everything fucked up.
Tried to fix by started removing Conda removed gnome*, lost GUI.
For first time worked on tty, after a 6 hour redbull session. Got back the system working.
First thing then done is learn to install in virtual and local environments.1 -
I worked with this hack of a backend dev that was too lazy to add a complex(ish) object to our CMS tool. His solution?
One giant-ass text box with the label "put JSON here".
If tech people were using it I wouldn't mind, but our poor content managers have no idea what json is. Plus like... no examples, no schema... they would have to change shit then go look at the website to see if it worked. Fucking asshole.
Plus.. I mean SHIT, MAN! This was in a Node.js tool... if you have the Json parser you could just GENERATE the respective form fields. DO YOUR JOB2 -
I'm starting a freelance project and the guy who is working on the backend refuses to use git because all the files sync to his computer from the server2
-
I hate it when people use like 7 "if" statements instead of like.. 2? And when they do not nest "if"s.
For ex. :
if(condition1 && condition2){
}
if(condition1 && condition3){
}
.....
" But I am writing it out longer to understand better! "
Yet it eventually stays that way with like 50 lines of "if"s..1 -
I think the worst thing I’ve seen from devs is lacking the curiosity to know how some software library works before using it which then almost always leads to bad design and code.
-
There are a couple really bad things I've seen other devs do.
One of those things is taking on managerial tasks while they are a dev in heart. Slowly kills them from the inside.2 -
Ignore every single comment that had been passionately written into the code.
Probably thought "if compilers can, why can't I?". -
He configured his IDE to use tabs instead if spaces on any file here touched in a codebase that exclusively used spaces because, in his words, "lol tabs are better". I don't even care about which method people prefer, the worst fucking thing is an inconsistent codebase. I still come across giant entire-file blobs in commit history where he made some change that, because he's a fucking imbecile, touched every line in what was already an unreadable, 7000-line VB.NET pile of spaghetti.1
-
A client hired someone to work on a new feature while we were working on something else. The new guy makes huge commits that we don't have the time to read, really.
I merged and deployed my work only to find that the whole database was wiped. Apparently, the new guy pushed some code that reset the database.
I Spent the rest of the day looking through backups trying to restore the database.2 -
When people use the word, "technology" in place of electronics. Technology encompasses everything: shoes, compasses, etc. Yet people still feel the need to use the word only for their iPhone.
-
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 -
Pretending to work while sleeping by scrolling his mouse up and down, sitting upright and eyes closed.2
-
Copy-pasting 90% of our entities including logic and merging some - creating thousands of duplicated lines - and then creating views for those abnomalies just to speed up the ORM fetching which could have been done with a single join...
Took me some time to delete all of that fking shitty untested code full of bugs... -
I did rant in wk99's topic already but this is also worth it.
The second worst thing I saw was a hotel reservation system, with online payment, where the total is calculated client-side, and then injected into the form.
You could reserve a royal suite for 0$ using your browser's inspector (let alone sending the post yourself) -
A colleague was tasked with making a small change to find out why and error was happening. It should have been a simple logger as it was not able to be replicated by our test team.
Their solution to this was to override exceptions to log out every property as well as disabling compile time optimisation...2 -
Create DB connection file in every other place and writing password in all those connection files. 😒👿
Then using grep and sed like a pro to change passwords in one go. 🤷
Scratching their heads as to why the script says DB connection error.... After an hour or so; finding out that the password contains '@' sign it was under double quotes. 🤦 -
Marking lines using their mouse, not using any of the keyboard shortcuts in their precious IDE which they talk about like they're married to it.
-
Open multiple vnc sessions and use those to open terminals rather than use ssh
I had to help him with something and looking at his dev environment was painful2 -
There was that „very heavy knowledge“ (that was his self proclamation) visual basic coder (vb6 that was) who always started with „on error resume next“... it was the only glue to let his programm „work“...
-
Once upon a time i have seen a block of code in a while (2 > 1) ... it was in C (or so i remember), but still...2
-
Not from a teammate, but using Ionic to create a banking app, I was about to have a heart attack seeing my brother forced to use it :|5
-
We had to add licensing to a program of us. In the end we chose a small java-library for that and i wrote a convenience script that creates a valid license.
But the script got its input from static strings and that was its doom.
My boss cloned the repo with the script (and jars), replaced the strings with real world data and pushed.
For his conveinience, because there were several clients, he copied the data-section, commented out the first one and put another data into the second section. This happened a few times and HE PUSHED AGAIN.
Now this repository contains a fine record of everyones licenses and their passwords. I know it shouldn't bother me, but it still gets my eye twitching, just like md5-hashing on passwords (which actually happens on that licensed project)2 -
Print("Hello World")
When people design a brand new Postgresql schema (case sensitive) using a mix of upper and lower case letters.
Only to then proceed and escape every single table and column name in every single query.1 -
Our lead dev allowed the new senior dev to write this massive nursing home smart sensor app in Java's scala framework. It's a php shop so we all watched in amazement as he sunk a good 600 hours into this monster. 2 weeks before we promised the client a fully functional beta, our lead dev fires the guy because he felt we couldn't afford him and he was twiddling his thumbs too much. We couldn't afford much after that cause we had not a clue how to finish the project (it ended up being 6 different micro services) and the clients sued us for more then projects worth.
-
One of dev I was working with once stored users' payment data in plain text. Luckily enough that thing never got to production.
-
I have seen a developer implement lots and lots of breakpoints. For basically every pixel resolution a new one. Yes, it’s literally pixel perfect. No it isn’t maintainable in any way
-
Where do I start...
I have seen a QA load local code to a machine, run it and then say it was ready to deploy. Little did we know she wasn’t following the deployment process at all and didn’t even realize she had to. We were a week trying to figure out why the deploys wouldn’t work until she spoke up.
I knew a dev/founder that said to me “source control is only for large projects”, I tried to convince him and his cofounder to use github or bitbucket. Nope, they weren’t into it (fresh out of school listening to professors who hadn’t worked a development day in 20 years) One cofounder got disgruntled, thought he was doing most of the work and decided to quit, he also decided to wipe the code off his co-founders machine. I literally saw a grown man come out of a meeting crying knowing he would never gain back the respect of those mentors and advisors.
I once saw a developer create a printed ticket receipt for a web app. Instead of making a page and styling it to fit a smaller width, he decided to do everything in string literals. More precisely, he made one big long fucking strong literal and then broke it up using custom regex to add styling to different sections. We had a meeting and he was totally convinced this was the only way. In the end we scrapped the entire code and the dude didn’t last very long after that.
Worst of all! I once saw a developer find a IBM Model M keyboard and said “I’m gonna throw out this junky keyboard”. I told him to shut his stupid fucking mouth and give the the keyboard.
He did -
Spaghetti code
Mixing about 27 functionalities in an 800-lines-function accessing global variables.2 -
Can't decide between the guy that used gedit to code and the guy who wouldn't read the documentation.
Wait, that was the same guy! -
Countless times have I had to replace shell scripts that use sshpass+rootpw in plain text, written by people often described as, "brilliant."3
-
U've seen one dev creating Java-Classes like 'GetLevel' which contain only one method that is called 'getLevel'. And it wasn't even a static method.4
-
I once had to fix a webservice endpoint another developer added that accepted any file from the public internet and loaded it directly onto an NFS file mount with the rest of the site's image assets and then inserted a record of the file into SQL via a hand-stitched query with parameters from the endpoint.
I was working for a large enterprise company at the time... I was very disappoint. -
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 -
This guy was editing a code file but compiling and running a differnet version with the same name in a different location and kept asking around not knowing why nothing was changing1
-
Not dev but, enough for the story. Had an assignment to create a hashtable for my DS course. Asked a friend how he managed resizing and the load factor
Friend= tablesize*50
Me= what...
Friend= space complexity what... -
Say that he's building a landing page and delete the entire root directory of the website. I didn't see it happen... But still...
-
Using GET method in HTML to send credentials to the server.
In order to use my broadband, I need to login using their "secure" web based service. Today I realized that when I click on the "Login" button, the HTML form send the data using GET to their server... -
Because of reasons we had to use the reactabular-module in our react application. There were problems giving relative values to the table-columns so a coworker decided to install a resize-listener in the window and calculate the relative values itself when the window width changes.
But i have to defend the guy who did this. Given the other things to do and our (limited) knowledge of the css-display-attribute and the reactabuler-module this was the best thing to do. Or we just wamted to finish this because we already wasted hours on this.1 -
The DB driver by default capped out at 1,000,000 records when doing a full table scan on a query that just needed an index.
Solution? Remove the cap. Duh.4 -
A friend of mine was working on an API..
He used an interface for his economy API, and he only build in support for a small part of the interface.. 80% returned false or 0 by default.
If you ever use an interface, fully implement it, or don't implement it. It is annoying as hell to have a barely functioning API..1 -
Put down another developer because of not using the dark theme or for not using the “latest and greatest” IDE! Like it makes a difference to anyone’s ability to develop 🙄1
-
One of the DB guys at work writes DB packages like this:
- open package in PL/SQL developer
- copy code to notepad
- edit PL/SQL code in notepad (yes, fucking windows notepad)
- copy and paste back from notepad to PL/SQL developer
- commit
Everytime I see him edit DB packages I can feel my brain mass shrinking.5 -
Perfect use of DI in .NET Core project.
> Passed logger object in UI project's controller class constructor.
> Then pass it to internal class.
> Then pass it to business project.
> Then pass it to another class and finally used logger in a method to log exceptions in try-catch1 -
Because of a ridiculous strict server environment (where even PHP was not allowed) he proposed that I could connect over Skype to do my stuff in typo3, which than could be exported to plain html to run on their server.
SSH or even remote desktop would be to insecure.3 -
Version 1.0 of the system I work on at my job was simply 200+ *.jsp files in a single directory, with many JSP's iframe-ing in other JSP's, sometimes up to 6 iframe layers deep.... now we're implementing a proper hexagonal architecture with a Vue.js frontend, and working with legacy code is an absolute nightmare.
-
try{
someObject.someAttribute = (int?) reader["columnName"];
}catch{
someObject.someAttribute = null;
}
Or, same coworker, another piece of code:
if(((int?)reader["foo"]).HasValue){
bar = (int?)reader["foo"];
}else{
bar = null;
} -
I must say the worst thing is the whole "branding" of closed and open source software. Giving systems/platforms/repositories/projects/libraries names that makes no sense, just for the sake of standing out. Just god damn call a shoe for a shoe...the difference lies in the creator/maintainers and not in the fucking name...sry
-
We received legacy project for support and fixing.. it had few issues:
1. There was a controller called MainController. This guy was the soul of the project 10k+ lines, heavily dependent on the data from the database.
2. We didnt get the data. Just the database structure (we couldnt run the app at all)
3. At the very end of that controller there was a "simple" eval($_SESSION['somevariable'])
4. We had no documentation and had to guess how it works...
Someone really had fun screwing up this project. Needless to say we got rid of it quickly. :) -
Recently I witness more than one developer copy-pasting entire code sections from a file to many others, instead of, you know, creating a function/method/module/whatever you choose to avoid code duplication.
-
Only found this out after the fact, but an almost total lack of authorisation checks in an exposed API has got to be up there.
-
This Dev I won't name, Ashley Martins, chown'd the /etc directory rather than her own config, and we didn't have console access, so was unable to ssh in.6
-
Take project notes on an exam pad.
Unfortunately, this is something I see virtually every day at work... Even while they're at their computer with our online project tracker open in front of them.1 -
Name two production service, metrics and logging included, after a famous woman and an armored vehicle.
Dude, no. When those services go down in the middle of the night some poor soul on call duty will have to handle it without the faintest idea wtf is going on.1 -
The project I took over from another developer had a contact form with 27 inputs named as this:
form1, form2, form3, form4, form5, form6...
The PM asked me to make the form more "accessible" somehow.
Note: The inputs were not ordered by their numeric names, the first input was named form16 and second was form9.1 -
We work with multiple platforms, a legacy language and c#. This dev uses underscore between variables in c# and camel case in the legacy platform. The thing is the legacy system has used underscores since 1981 and I've never seen a readable example of c# using them between words.
I also told him I was working on learning to use patterns and how the process of software development should work by training. His response... Why would you want to do that?
He also copies and pastes code everywhere and pays no attention to scope.
And worst of all I'm his coverage when he is gone. If I have to debug one more sloppy bug I am going to face desk. -
Not using design pattern on a school project because he was too busy understanding what the fuck was Smalltalk since no one understood it in classes.
yes it was me. I don't blame myself, I really took too much time understanding that (and I was the only one to do that, the other just asked me. ALL OF THEM). But I should, I guess. -
Once someone asked me to look over a bit of code and sent it over Discord. Needless to say I didn't spend very long looking through it...