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
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Me: I need a Windows PC to test my code on.
Server dude: We don't have any free, but I can setup an old server for you.
Me: 🤔 .. I'll take it!
18 -
Yeeeeeeeee! My granddaughter yelled up to me, "Grandpa, I'm programming!" She was doing some kid code game thing. Ten years old. I can hope, can't I? 😁14
-
A guy on another team who is regarded by non-programmers as a genius wrote a python script that goes out to thousands of our appliances, collects information, compiles it, and presents it in a kinda sorta readable, but completely non-transferable format. It takes about 25 minutes to run, and he runs it himself every morning. He comes in early to run it before his team's standup.
I wanted to use that data for apps I wrote, but his impossible format made that impractical, so I took apart his code, rewrote it in perl, replaced all the outrageous hard-coded root passwords with public keys, and added concurrency features. My script dumps the data into a memory-resident backend, and my filterable, sortable, taggable web "frontend"(very generous nomenclature) presents the data in html, csv, and json. Compared to the genius's 25 minute script that he runs himself in the morning, mine runs in about 45 seconds, and runs automatically in cron every two hours.
Optimized!22 -
Was going through some old gadgets n found this fossil.
Give me the fucken code Blackberry and I'll catch it for you.
4 -
This code looks pretty old, I wonder if I can delete th.... what the...
(src: twitter/@iammerrick)
4 -
Your app works.
You do some changes.
It doesn't work anymore...
You restore the old code.
It still doesn't work... WHY?4 -
At my old company one of my colleagues introduced async / await into our csharp code. He created interfaces and showed us a great structuring of his code. Sadly a few weeks later he left the company, because of personal reasons and a bug appeared in his written service. Our senior developer took the issue and complained for like 1 week. That you can't find anything, that interfaces are useless, that async / await is slow and sucks and that we should stop trying to bring new structures into the code base and do things the old way. In the end he deleted all the great things that my colleague introduced and wrote bad and smelly code.9
-
Seen at work in code:
<!-- DO NOT REMOVE CONTENTS PLACED HERE //TODO: Would have loved if some one also had said why we should not remove this -->
Lol1 -
Started learning C++, coming from Python.
Just spent ~25 minutes searching for a problem - My code wasn't working like I expected.
Problem: Didn't compiled the program, kept running old code, didn't noticed8 -
Improving an old JS code, replaced all 'var's with 'let's. Previous guy wrote a comment above his variables, which is now saying:
"letiabes"17 -
Me: Why is there such a delay between the app and the hardware device?
Colleague: Ah, same old same old, TCP is just an inefficient protocol. We should stop development and build our own replacement to TCP.
(PS. The actual problem was his code)9 -
Crawling through some old code and asking myself:
-Who wrote it?
-When did he write it?
-What did he think then?
-Me
-Last week
-I have no idea -
My dad said if I fix his old car then I can have it once I pass my driving test. I can't seem to find the source code...18
-
All these people talking about learning to code at school makes me feel old. There wasn't even an option to learn programming when I was at school. Had to teach myself!4
-
Give me a 10 year old application with no comments, layers of spaghetti code, global variables, embedded SQL, and a text editor with no debugging; just don’t make me write Excel formulas.6
-
Just found an EPROM (Erasable Programmable ROM) from my dad's old stuff.
Yeah, there's a window for UV light, if you wish to erase your existing code/data!
Thought you people can relate.....
11 -
When you touch your code that was written 2 years ago. It's like looking on pictures of young yourself, naive and ambitious ;)1
-
When your code changes don't give different results and after an hour you realize that you're still editing the old version....7
-
Holy shit i've found my father's old books back from the 80's for basic and comodore 64. He learnt from thoose and used to code a lot of games and office softwares on that old beast. 😮
1 -
Me when I'm updating my projects:
"I put some new code in,
I took some old code out,
I put some new code in and I tested it all out, I fixed some major bugs and I pushed the update out. That's what it's all about!"5 -
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 -
Decided to update an old project. Turns out I wasn't stupid 6 years ago and my code still makes sense :)))4
-
I love coming back to old code from when I was learning a new language and cleaning it up/making it better. It confirms that’s I’ve learned something :)4
-
Love reading through old code and seeing things like this
var hasFailed = (errors.length > 0)?true:false;
Makes you wonder what their thought process was when writing it :D5 -
I’m reading through the Apollo 11 source code like a 13 year old that just found out what porn hub is.13
-
Found this gem in some old piece of code:
public static void printStackTrace(Exception e){
e.printStackTrace();
}3 -
when your co-worker instead of commenting a piece of old code wraps it in:
if (false) {
...
}
Took me 2 hours to figure out why my changes weren't working.3 -
I don't really drink alcohol, but every time I look at my (old) code, it looks like I was drunk when writing it.
-
Keeping old and unused code blocks commented out and not deleting them immediately is the equivalent of leaving that bottle of soy sauce in the fridge even though you know very well that you won't use them ever again.7
-
Do you know what i hate most?
... commented old code!
What is the fucking purpose to comment old code IF YOU ARE USING A VERSION CONTROL SYSTEM?????
Commented old code is shit, because it fucks the readibility! I saw entire class full of this shit!
DELETE IT, YOU DON'T LOSE IT YOU MORON!!!!5 -
I took my old project and I was like "Why don't fix it and open source it?". So from 2785 lines of code in main class, I've cut it to 1662 lines of code while keeping same functionality plus some more...4
-
So he is in the “elite” team as a “Sr” dev and i’m in the normal team as a ssr dev.
He: Hey look, the ‘F’ case is empty and doesn’t return anything, can you help me? This is some old code and we have to add some features.
Code:
Switch(string) {
case “J”:
case “F”:
cade “D”:
// some code
break;
// more code
}
I’m crying9 -
Was forced to code like this:
if(condition)
{
//code
}
Instead of this
if(condition){
//code
}
Also I should mention that this happened 4 years ago and my mentor (27 years old economy major at the time) did not know how to use git, we stored projects on a shared networking folder.15 -
I dont like it when i have to edit an old code made by a previous developer, i dont want to touch that spaghet.
1 -
You know you learned a lot in the last year when you try to change something on a website you made 1 year ago and it is almost impossible.
The code is not well structured. PHP mixed with HTML, functions that should be organized as a class etc.
I really, really, need to refactor the entire site!4 -
When reading your old code, there are two feelings you may have:
1. I was such a dumbass back then
2. I was so thoughtful back then
If its #2, seek a position outside development, like product management, your coding career is probably over.3 -
When you watch the new Jason Bourne and see people from CIA hacking a laptop from an Old cellular with a "shell code", or other people saying "use SQL to hack the database"3
-
At my current project we use SVN, but today I noticed a colleague of mine uses another version of version control as well.
Example:
V1:
console.log('Hello, world!');
V2:
//console.log('Hello, world!');
document.write('Hello, World!');
V3:
//console.log('Hello, world!');
window.alert('Hello, world!');
//document.write('Hello, World!');
Every singletime Ive to remove 40 lines of comments before Im able to follow the code and refactor it.2 -
I recently came across my old interview assignment code which I had written while I was still in college. Oh my God, it was cringy! It was such crappy code 😂
My coworker (who had interviewed me) saw it too. He was surprisingly very chill about it, saying that the code is not bad, it just shows a lack of experience. I think I will choose to believe him 🙃4 -
Programming commandment: Thou shall, from time to time look at your old code, introspect and improve!
-
Just finished recovering all deleted files from my old hard disks I found in the attic, just for fun.
I was hoping to find some old photos or something. Instead I found my awful old Qt code.
Back when I started the recovery it was sunny and perfectly clear outside. As soon as I found the code the skies went dark and now it’s raining like hell and lightnings are blasting.
Wtf i just summoned
2 -
!rant
To the Devs at OnePlus,
Who ever wrote the code that lets me swap the 'back' and 'show recent apps' buttons so they're like my old phone.... You're a fucking god1 -
I just did a code review on an old project of mine. 10k lines altogether. 5.7k TODO's. I can't even.4
-
Everyone is on their vacation and I am in good mood so time to refactor some 3 year old frontend, angular, javascript code. After 5 minutes of looking, some great quality of code snippet on the image below.
10 -
Me in front of an year old code snippet:
1) "omg, wtf did i write that time?"
2) "i'm going to fix it"
3) after 2 hours lost trying to get new code working... reset from git
4) look around feeling guilty -
Found my old code.
You gotta admit, that's some clean code there, considering I learned C# only for a year at that time.
But those comments....
VeRy WeLl WrItTeN, vErY dEtAiLeD, vErY gOoD
8 -
Engineering managers will say things like -
- "I'll let the team decide what's best for them" & "code quality is our primary goal" -
but then they'll shoot down any & all requests to go back to some old piece of code and refactor/clean it, because of "deadlines".
Hypocrites, all of them.3 -
I came to this company. I saw spaghetti code. I told myself to write clean code and also clean the existing code. I took too much pressure for too little return. I am done with this shit. I will now write clean code but fuck the old spaghetti code!2
-
Why did I volunteer to this shit...
I am supposed to maintain 4 old websites (like they were written 10+ years ago..). It's written in PHP, before mysqli, so all the calls to the DB is with mysql functions.. Now the server is to be updated and run PHP7.... guess what? those functions don't exist any more.... Now I have to patch several thousand files to use the mysqli functions... And no, there is no reason to rewrite it more than that, as I'm also developing the new versions om the sites, but those are so far from done and the new server needs the update as soon as possible, so bodging the shit out of this one...
Oh god the amount of repetitive labor 😫☹😭
And I'm not getting paid, because I'm doing it for my scout group... Tho they pay some of the Pizza 😜10 -
That fealing when someone that picked from the graves an old project that you've started when you were just a noob developer... and then you look at the code... and then the shame.2
-
So basically, we're all just constantly writing legacy code of the future. RIP programmer kids of today.4
-
older clients are returning with my old projects and asking for improvements, I did buy a few very shitty scripts from the internet/ and used one of my friends custom php cms for the other client because I REALLY needed money and they needed the projects yesterday.
Now I'm looking at the code and can't start working because of how messy it all is, I want to remake it all with a good framework and system, but it would take too much time (and they want it fast) and they wouldn't want to pay for the improvements because what they have now works..
I guess the shit you throw out when you're younger does come flying back like a boomerang..3 -
The design process.
Call me old fashioned - but clean-code/clean-architecture/SOLID is not as important as simplicity and coherence.
I JUST NEED FUNCTION THAT DOES STUFF! But noooooo better overly design EVERYTHING!4 -
900 lines to build an HTML select list which displayed the months from January until the current month, for picking which months data to display seems a tad excessive... probably good the guy who did it doesn't work anymore.4
-
Rereading old code I wrote and asking myself questions while reading it...then reading the next line, a comment, answering those very questions.
Past self. Thank you very much. 😎 -
Working on a damn old Android app's source code so it's usable in more recent versions (back when 2.2 Froyo was new). So much has changed in the Android SDK...1
-
Several months ago, I wrote the most beautiful Java code of my life. It was shelved and never merged because it added minimal overhead to every call on the system (I'm talking super small relative to the functionality it provided). I've been asked to resurrect it, but master is too different, so I'll have to rewrite it all. 😭 Since that code, I've been doing research and prototypes - nothing production, and looking back on this old code nearly brings me to tears. I might actually get back to writing code that people will use.
I'm just really emotional about it, and I don't know why. -
How about you started off with programming?
I'll start with a veery old picture of my first Java-Code I've written (if you can call it eben that). At that time I tried to code using a JS-Designer. Just hilarious. 😂😂😂
9 -
Sometimes I look at my old code and just keep asking myself...
Were I drunk when writing it .. or am I too sober too understand it... -
Note to self:
Fucking comment your fucking code
So I finally got time to work on an old project and now I can't figure out what does what.6 -
So I'm tasked with rewriting the old software my employer uses to track basically anything in his company. They want to stick quite close to the old workflow as much as possible, I get that.
"Why exactly do you need access to the system? No you don't need to look at it just recreate the flow. I'll give you the sql structure is that OK? Oh and this won't take long, you can copy from the old code can't you? Wait why do you need access to the code? No. "
🙄7 -
That moment when code reuse makes you reuse reused code and you actually reuse a BUG.
You decide to go for code reusing when your boss asks: "Can you add an edit popup besides that 'add customer' popup button?". You do some little tweaks to the "new customer" code and it allows that to save over an existing entry, cool.
However, after a lot of time spent on reviewing the resulting PR, turns out there was a dormant bug on the code you reused, and it woke up with its new use.
That code was a bad copy-pasta from another, bigger form, which included a whole bunch of optional fields. As it was only used to save new entries, those now missing fields were simply being saved as empty. But as you reused that to save existing entries, you were now cleaning up all those optional fields without noticing.1 -
Me.
Because every time when I see my old code, I begin to criticize it and think how can I improve it. -
Fine don't take my suggestion during refactoring old code. Keep the python code over 100 lines of code...we could have cut it in half, but whatever
-
Boss: Why are you trying to build the old program?
Me: Because I need to determine behavior of why old program works with data that new program does not.
Boss: Does it affect the output?
Me: No, but...
Boss: STOP! Just filter it.
Me: Okay.
Boss: Go write new fun code, not work on old shit.
Me: Thank you for saving me from myself.
In reference to:
https://devrant.com/rants/4666401/...2 -
*senior dev comes over to my desk*
"Your code is so wrong I didn't even bother to comment on the review." He proceeds to lecture me about why the code that I modified (a 2 year old file I included a tiny helper module in) needs to be rewritten. -
When you look through two year old code and have to make it conform with your new and shiny code.😀1
-
My biggest fear about publishing open source code is people looking at it and having the same reaction a have when I get back at my old code.2
-
Ahhhh.. the great feeling of starting a new project at work after the stresses and health deterioration of maintaining old code bases.
-
The happy moment you start a new project a Find that you can use your old code, then realizing you don't remember how it worked but use it anyway.1
-
Anyone else feel that the main code base they work on is so old and clusterfucked it could do with a rewrite?5
-
Nothing more depressing than a response like "No, no, no, we can't remove this old code. It doesn't matter that there's 0 references as of 3 years ago"3
-
That moment when you go to your web development lab, write ES6 JS and your teacher tells you you are doing it wrong.
"That's not going to work in JS!"
You know something? SCREW YOU OLD MAN! 😕😠😑2 -
Refactoring a method of a 5 year old system. Probably one of the ugliest code I have ever seen. This is just a little piece of the ugliness
6 -
When someone copy and pastes code, repurposes it and leaves in the old comments that just confuse the hell out of the next dev.1
-
*opens the code of an old project still running today*
*see the horror spaghetti code*
*decide to modernize it with good code and practices learned by the years*
*can fucking decide where to start *
*réalise it is impossible *
*rewrite it from scratch in a few hours*
*be proud*
It's really rewarding to go back to old projects and give them a good hug. You réalise then you really got better5 -
Having to use Xcode 4 alongside the new 8 to support old iOS versions. I almost wrote the code twice, once in Swift and once in Obj-C.
-
I'm looking at old code that I wrote around half a year ago, and noticed that my coding style changed over time (relying more on arguments to pass messages between commands and functions, rather than sourcing the result of a command). I feel like this old code isn't truly mine anymore. It's thousands upon thousands of lines of code though... Given that, would you rewrite it or just move along with the existing design? I mean in my opinion the current code really sucks.4
-
...
Person me = new Person();
me.setAge(20);
int newAge = me.getAge();
System.out.println("Happy birthday! " +me.getName+ "You are now " newAge+ " years old!");
Happy birthday to me!😎🎊🎉🍻
(Probably stupid code 😂)10 -
One of my favorite things to do in Secondary School was to go around telling people I had written a program that uses the 'Doomsday Algorithm' which sounded really cool and always scared those who didn't understand it.
Truth is, the 'Doomsday Algorithm' is just an Algorithm that used to determine the Day of the Week of a given date.
I wrote this when I was 13/14 years old and I'm still super proud of it today.... well I mean I probably would be if I could read my own code.1 -
Right now I need to fix 10 years old php code handling data sets coming from a database. Normally I work mostly on C#.
God, do I miss LINQ!8 -
When you find a new use for an old app I wrote and still have the source code...
And now I'm late to work...
-
When you look into the code of old developers with nice comments such as "What a fucking retard he is trying to book in the past". Just laught .1
-
A colleague is walking me trough some of the source code because we try to fix an issue.
colleague: Oh we don't use this anymore
Me: ...
LATER
colleague: This part we should refactor someday
Me: ...
LATER
colleague: Oh I think this is old code and does not exist anymore.
Me: .. .. ...
Great Colleague BTW :)
PS: fix will be posted Later.3 -
I have a friend which have a hoarding disorder when it comes to coding. Here are some of the things he does:
1: If he rewrites, remove, or in any other way refactor a function, then he keeps the old one in the file commented out.
2: If he deletes a class then he takes the code and paste it into a class that he have just for old code. AN ACTUAL CLASS! Not just some random text file somewhere. Even though it is commented out, he leaves it so that you can initiate his garbage.
3: In point 1, the code is not pasted on the end. It inside all the other actual code.
So if you try to help him with something, then you have to dig through a mountain of shit just to find some code.5 -
Every month I re-evaluate the code I had written previously to compare my progress in coding standards...
Turns out I need a time machine to go back in time and slap myself1 -
A legacy custom made WordPress Theme.
Old developer made main styling sheet with 8000+ lines of code with no component separation. -
One of the best feelings is when you're hip deep in code refactoing and you're delezing old code with your new and shiny code.
-
Porting a very old program I wrote from Console to WPF app... looking at the source code, I'm amazed that it has been working all these years...1
-
Because almost all the answers from stackoverflow are still optimum, even if it's 7 year old code, all it needs is some good ol' spit shine refactoring
-
Reading through old post-it notes and found a TODO that says "fix code" with no indication of a project it refers to lol1
-
!RANT
Bet the diff between a beginner developer and an intermediate developer is where to get code snippets either from old codebases or remote resources. -
Sometimes when I read old code of mine I'm ashamed. But more often when I read others I just feel better.
(I'm talking about other webdev freelancers, not OS projects or so...) -
When I teach/help someone with code without telling them explicitly what to type and their solution works and they get hyped af. Never gets old. I like helping people.3
-
> mmmmh this old code I wrote for my previous job could be handy now, lemme just git pull the thing real quick
> clone the repository in my new pc
> can't deploy because I intentionally didn't commit any of my old credentials, no env files other than the example, and everything is smooth clean to prevent some dumb fuck like me from just grabbing the project and do whatever
There's an old IHateForALiving giving me the middle finger. -
Last year I wrote a sudoku program which did solve easy sudokus but messed up on harder ones. I had got bored after a bit and forgot about it until today I thought I'd rewrite it using new stuff I've learned since and make it work properly.
So I opened it up and look and I'm like 'WHAT!?' because I don't understand what I wrote. After a bit I start to get the idea and see that it was kind of smart even if long and complicated.
If anything, it shows how much my documentation skills have improved.
Now I just have to work out how to redo it in a way I understand.7 -
At my old company one of our directors referred to a QR code as "heiroglyphics"... That struck me as pretty incompetent for the director of a tech company
-
Any code should be simple and easy to read / understand.
I just reworked an old stored SQL proc.
Went from 102 lines to ... 10.
More I code, more I realize that maintainability, readability, comments and unit tests are more important than actual code. (And performances ofc. But if 1 line code does it in 1 second and 500 lines code in 0.2 seconds, I’ll take one line solution every time)5 -
ticket sized small: figure out why this thing is failing, get the old MR to work, test it
month old MR, over 8000 lines of code changes
FML5 -
There was a "Snake" game on an old windows machine that came with the source code. I was able to tweak the code enough to add interesting twists to the game. From then on I was hooked.
-
Would there ever be a day when I would look up some old project's code and won't say "WTF was I thinking!"8
-
It has been over 5 years developing C#. Every time wanna do events and subscription I get lost and open my old code and relearn it again 😐😑3
-
My work day lately:
5% new code
95% figuring out how the old shi...code worked so I don't break everything4 -
My code works.
Well, it should, but not like this.
I've set some datas to a nested form, saved by a variable named 'stat1', however the code won't work unless I use a variable named 'fields'. Not 'stat1'. I'm only 24 years old and I already feel too old for this shit.3 -
I fucking hate shit/incomplete code tutorials, especially ones that reference old/unmanaged libraries. Fucking waste of time!!!!9
-
So, I like refactoring old shits.
Now I want to exterminate this over thousand lines of code class. I have to be witty about it and do it within couple of PR, or they will find out I'm not doing anything productive but making their code cute again!3 -
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 -
Want to get last value of a list?
value = 0
for value in list:
pass
working with 10 year old code :/2 -
Do you ever look at old code from years ago a think “god that was bad”? I’m so embarrassed by something I wrote on 2010, it’s shockingly bad!
I actually feel a little low and think maybe I’m not very good! Of course now my code is so much better but think to myself, is what I’m writing now gonna be the same down the line?2 -
Starting the Monday with a good old heap corruption in a c# project that uses only managed code.
Occurs on 2/3 PCs.
Today is going to productive :/ -
Have some downtime today, so since I lucked out and found some old backups (from before I used Git) of a project I was planning on revisiting, I decided to fire it up and see what I can do to get that going again.
And discovering just how much my coding style has changed since then...
[Code is in PHP, for reference]
* Virtually no documentation (whereas my current style is near-obsessive with PHPdoc blocks)
* Where comments exist, they only use // and are a full tab after the end of the line
* All assignment operators are dutifully aligned on tabs
* Have to update the entire codebase because it relies on deprecated `mysql_*` calls
* Have to flip all of the quotes throughout the codebase because I used double-quotes as my primary at the time instead of single quotes.
* Also relied on magic quotes for injecting variable content into strings
* Associative array practices varied; sometimes the names are encased in double quotes, but I just hit a block where it's all leaving it to the compiler to interpret unquoted string literals
And perhaps the most egregious so far...
* Any time we get database results back the process for cycling through them is to do `$count = mysql_num_rows($result);` (or $count2, etc.), then do a `for ($i = 0; $i < $count; $i++)` (again, or $j, $k, etc.), instead of just a simple `while ($data = $result->fetch_assoc())`2 -
New year old me
Fucking Windows
"You have written a lot of code lately it would be ashame if I just crash"
*Bluescreen*
"Configuring updates"
Fuuuuuuuuuccccckkkkkkk
Luckily I saved my code5 -
I’m thinking of replacing my dev duck with baby yoda.
Btw he’s 50 years old, and I bet his psychic abilities could help me run my code better.
5 -
I've been infcted with writing awful, sinful, obscure code, so others can't read or change it.
Recently i got my first full time job as a programmer (yay). It's with a company with 15+ year old system and they are currently upgrading it. But it's driving me crazy with the massive mess of old and new code. However it only gets worse! Instead of making it simple and nice to read, they want it over complex, just to get something from the database i have create at least 5 fucking classes and endless SQL code, the old system didn't requier any SQL or the creation og new classes, WTF. I've become a sinner, of corse i use the old system, but i do it secretly, and i obscurify my code so others can't understand. It's shameful, but i'm afraid to confront the older programmers, they've spend too much time in the system and they've been in the business for a lot longer than me.3 -
#define AUDIOLB_EXIT_ON_ERROR(hres) \
if (FAILED(hres)) { goto Exit; }
#define AUDIOLB_SAFE_RELEASE(punk) \
if ((punk) != NULL) \
{ (punk)->Release(); (punk) = NULL; }
Looking through old audio code I wrote. Found these macros. Will most likely reuse for a new project. It works damnit!
Do you feel lucky?!7 -
Please don't try to decipher your code from 5 years ago, it's a mistake. Thought it would be a great idea to bring an old project back to life. Turns out it is not. Not when I can't understand my own code...3
-
Never realize how much you hate yourself until you dive into code on an old project.
Damn comments that mean nothing 😣2 -
!rant
When you get the go ahead to scrap the old legacy code and design it from the ground up
feels_good.jpg -
6 weeks of working on some crackpot bull shirt half ashed code just to end up using a pre built theme that works like a charm... Wish I had thrown this old code out 6 weeks ago.
-
After 12 hours I've managed to delete old and obsolete code from my project... Well, from part of it... Okay, small part... From 10% of it...1
-
Transferring our website from (outdated) SAPUI5 to VueJS.
It's so painful to look at 6 years old code... And at least 10 different coding styles.3 -
"I don't think anyone will mind if we update and make all old code incompatible."
- every reat/soap service the day after you finish development. -
Refactoring code that I've wrote like a year ago, made me realise how much I've grown in the past year, do you guys ever go back to old code that you've wrote?3
-
I can't delete old useless code, I am afraid of deleting it and I always end up commenting it as if I am giving it a chance to prove itself. #rant3
-
2 seconds after I checked in some work on a web page, co-worker runs to me, freaking out because "This is not how I wanted it to look!" and waving a printed mock-up in my face.
I inherited a shitty, bloated, broken, 10-year-old site with dumbass CSS, but I did my best to work with it. I'm not surprised it's broken, so calm the fuck down and let's talk about what you're seeing and I'll happily fix it. It will be okay! -
New piece of code which should work perfectly and solve your problem but it is not working just because you forgot to remove an old piece of code you were trying to fix the same problem! Fuck my life!1
-
Anyone else get really infuriated when Flutter keeps deploying an old version of your code!? It drives me absolutely nuts and I wish to kick Flutter in the non-existing balls!2
-
Is there actually any frontend framework or boilerplate to just code and avoid messing around with old libraries, missing dependencies, no documentation? I'm seriously moving to plain ES6, it feels more flexible :/1
-
> trying to make project using old version of specialized toolchain, exposes toolchain issue
> fix toolchain issue
> fix small typo issue in code
> linking spews ALL the errors at me and fails
-
Update to my last rant*:
I got to know what my colleague did as he "rewrote" my code:
He just searched some GitHub-Projects and used the good old copy+paste method.
Awesome bro, "rewriting" code until nobody's understanding it is the best method to improve code.
*https://devrant.io/rants/735762/...2 -
Some hint on how to take an php 3 old code and transform it to php 7.3 without rewrite all the class ...
Like an auto converters or i dont know ?10 -
Every time I read "IDGAF", I can't help but parse it as a Doom cheat code, trying for a moment to recall what effect it had.
Boy I feel old1 -
I've been spending the last few days reorganizing css, js files, removing old code and rename directories. Yep its that kind of week at work...
-
First contact with code was about 10 years ago, trying to customize my own server of the old Tibia (pre historic mmo game) with lua language
-
So actually on the note of my last rant. What music does everyone code to? I code to EDM, JPop, Vocaloid, old video game battle themes and Heavy Metal.
One Punch Man opening is a favorite when deadlines draw near.9 -
Damn it's hard to alter code, on a big (side)project, that is pretty shitty... And it too big to start over.. :/
I'm just gonna run with it and rewrite the damn app piece by piece as I am writing new features..
It's by the way a project I kinda quit half a year ago or so. Now it's coming back., but better. :)1 -
Update to Doomsday !rant which can be found here: https://devrant.com/rants/1000628
Hey Everyone I'd like to let everyone know that I finally found the original file for my Doomsday Algorithm and thought it would be fun to show you the dirtiest code I've ever written (I was 12 when I wrote it).
here is the github link, https://github.com/LiamHolmesEPD/... , and I'll likely update it will more cleaner languages in the future.2 -
At the place where I am interning right now, most QAs that file bugs are running code that is nearly 6 months old. 95% of the bugs they file don't exist anymore in the current code -_-
This is in spite of testing environments available with the latest code deployed :/ They just refuse to use them!1 -
What's your favorite editor for Web development? Using Coda on the Mac and good old UltraEdit when on Windows (with custom theme). Tried Sublime and MS Visual Studio Code but they never stuck.17
-
A dev today tried to tell me that a full copy of a VM in XenServer copies all of the data but magically pulls old code. Long story short, he was wrong.
-
So the project I'm working on atm and ranted about a couple of days ago... There is absolutely no documentation and the code is at least ten years old.
At least I can contact the old dev, but he's slower at replying, than reading the code through and figuring it out 😐1 -
I just had to re-run some old scripts written in python, after a year and a half without using the language. Much spaghetti code, but strangely inebriating. 😯
-
This Old Fart looks at webpack prod ver of my code and be like change the way you write code because I can't read it.1
-
Spent the day refactoring old copy-pasted astronomical code with minimal commentary, cryptic variable names and missing mathematical symbols. Self documenting code my ass.1
-
Aaaaaaaarg GCC! Stop caching my failures. I do correct my code, stop pulling the old copy from /tmp you bloated piece of C3
-
Sometimes, when I look back at old code, I fell like when naruto is getting his ass kicked by sasuke while remembering the...Almost good times they had
-
The confusion, regret and self loathing I feel looking through old code is only comparable to how I feel seeing pictures of a gangly, 15 year old me on Facebook.
-
Occam's Razor. When you think you're investigating a hack but it's actually your old neglected code causing trouble..
-
Apparently I just realized we've been migrating our system in the wrong order....
The cross systems dependencies are like spaghetti code....
Data Flow: Old -> Upstream (that i need) -> Old -> New
So in order to migrate a feature to the new system... I still need our old system... indirectly...
WTF?!?!?!
I thought Topological Sort was a topic taught in CS... and everyone but me were CS graduates....
How the fuck did they screw this up?!?!?! -
I only prefer { on same lines if not used for class constructors & try catch blocks..
Other than that, I adapt to the existing codebase styles, to not fuck up things further, even if it makes no effing sense (old project, styles & best practises changed 'a bit')..
So I guess I'm being influenced most by the old code and pass devs on the projects..1 -
Got a full stack job in a really large org. They write shit code and refuse to comment on code saying the code should explain itself.
And I’m like yeah but if you’re writing spaghetti code at least fucking comment why.
The new job’s pay is like 2x my old job so it’s really fucking good pay but my brain is melting from frustrations with these devs.4 -
Is it just me or do people sometimes do major refactoring not because it needs to, but purely because they are inheriting old code and can't be bothered to understand it5
-
When you a find a phantom function that looks important that doesnt get referenced, but the application is so big your not sure so you leave it.
-
Having to change the data type of a column in the database of an app is just the worst! I always forget to code the migration of the old data :(
-
Cleaning up some old. NET code and found this gem. At least it might be readable once it is rendered to the browser.
1 -
Looking back at the VBA code I wrote for work about 10 months ago makes me realize how much reading the Clean Code book by Robert C. Martin did for me, because holy shit my old code is unreadable...2
-
Tomorrows meeting couldn't be more messed up
•boss(we are kind a thing now)and her ex sitting at the same table while she tries not to kill him
•me sitting there with someone else's shitty website with 20 day old code to show as a back end (previous dev was a cunt and deleted all copies from everywhere)
•them expecting a junior dev to build a whole accounting package on the 20day old code
•deadline 3weeks
• crying on the inside 😱😱😱5 -
Bricked my old Galaxy Tab 10.1 after trying to install Marshmallow on it.
// Sticking with code from now on1 -
Started a new contract, nearly end of first week without access to code repository. Spent all day helping on old contract and looking up Archer gifs for our internal messaging app.
-
WTF ! Spent the whole day yesterday refactoring an old code and today a new requirement came, which adds a new functionality changing the entire code again.
-
What is the preferred learn to code book for a 10 year old. I only have some python and Pascal experience to draw on to help with any debugging.5
-
Started a new job. Saas solution 10 years old. Not a single page of documentation....... Spent last three days trying to find code connections. #nodocumentation #y-u-no-doc2
-
I was trying to complete some computer science coursework on an old school computer running Netbeans...
It took 10 minutes and lots of freezing to write one line of code which doesn't even work. -
Code base is full of /*bug fix - XXXX */ coments, sometimes it feels the software is a Bugenstein's Monster!!
Not sure if this kind of comments serve any real purpose...
Commented old code is a more familiar monster; but that's a tale for another day. -
Still working on this oldass project. Casting enums to different enums.. longass methods call another longass methods at the end...
-
[GIF] This code looks pretty old, I wonder if I can delete th.... what the... https://twitter.com/iammerrick/...
(Sorry, I was not able to download the GIF from Twitter's app) -
Going through old code
And it's beautiful
Probably my best code ever
And it feels good
I am not that bad actually -
Usually I write code in Rails and usually what I happen to rails are vanilla PHP systems, I think I have some super natural knack for finding very old systems that do strange things.2
Top Tags
Weekly Rant
View