My 9 year old son checks out the source code of every website he visits. If he finds something he doesn't understand, he bounces it off me. I love the snot outta that kid ❤️❤️❤️.

30 year old starting to learn to code. Wish me luck!

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!

Fixed a two year old bug by deleting a bunch of code

Sometimes we scare to delete old code

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? 😁

Was going through some old gadgets n found this fossil.

Give me the fucken code Blackberry and I'll catch it for you.

This code looks pretty old, I wonder if I can delete th.... what the...
(src: twitter/@iammerrick)

I found some old code that I wrote in high school. Young me was fucking smart. Sure, he may have saved his email and password in a text document and committed it, but he also wrote a functioning email client that talked over POP and IMAP. I want to hire old me to work for me.

Whereas new me is like "npm install email-client".

When I come back to my old code and see how I was using that framework

Am I alone? 😅😂😂

Came across a picture of one of my old projects from college. This still sums up my code today...

Credits: devHumor

Your app works.
You do some changes.
It doesn't work anymore...
You restore the old code.
It still doesn't work... WHY?

Me after changing code of an old project

Friend: "Don't all computer science people learn multiple languages so they can use the right one for the job?"

My reply:
We learn multiple languages because some asshat before us had a hard-on for it and now we need to keep that shit running and we don't have time to rewrite it.

Took over an old project. Okay lets look into the code: a method with 17 parameters... 17...

currently working on dusty project

When you find 7 years old website made while you were 14 yo.

So I was looking through my year-old code and found this.

I'm a pretty funny guy.

Having to learn "Modern web technologies" from a 60 year old woman who has never heard of HTML5 and build her website with tables. And we even had to code on paper. Fuck sake, so much time wasted

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 -->

Lol

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 noticed

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"

And sometimes are afraid!!

Trying to extend 15 year old code.

Found

#define private public

at the beginning of a sourcecode file....

Time to go home.

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)

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...

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

Refactoring that old code written by you

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!

Discovered this beauty of code in an old application at work

Refactoring old Js code with Ramda.

Looking at old code is as bad as looking back at what you posted online years ago

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.

Buddy just hit me up on Snapchat after one of his code reviews

Looked at your old code and starts wondering "who the heck wrote this shitty code!"

Me looking at my old code

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.....

When your code changes don't give different results and after an hour you realize that you're still editing the old version....

I'm currently rewriting the heart, foundation, core module of my company, that's written with my own shitty legacy code that is old, is dirty, but somehow worked flawlessy during whole 4 years. I'm afraid.

When you touch your code that was written 2 years ago. It's like looking on pictures of young yourself, naive and ambitious ;)

Just realized I left a console.log in production code at my old job

Once i found a legacy code where the old dev avoided the execution of some lines by wrapping them with a
if (1 == 0) {...}

> Writing some code 😀
> Compile it
> 10 errors 😣😣
> Debugging mode on😎
> Write about 100 print statements to debug the code
> At last found errors and now remove those print statements😅
> Compile code
> 2 out of 30 test cases pass😤😤
> Exhausted and angry😡
> Silicon valley new episode arrives🎉
> Super excited after watching the episode and think like you too can code like Richard Henricks😎😎
> Coming back to the old code and build logic from scratch
> Compile and finally all test cases pass
> Task completed😂😂

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. 😮

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

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!"

Bought a 27" 1080p monitor and decided to use my old monitor besides it in portrait mode. This feels so good, portrait monitor's good for reading tutorials or for writing code. My coolest setup so far!

Decided to update an old project. Turns out I wasn't stupid 6 years ago and my code still makes sense :)))

Me, when read old code:
if z == true
return true
else
return false
Yeah, why not stupid fucker.

Me trying to understand the code in my old projects.

I'm refactoring some old Java code I did

my goodness I was a short-sighted idiot

me: *submits a PR on our old system*
My teamlead: please mind the code style, there was no need to add the extra whitespace line under that loop.
Me: 🤔 there are style conventions in this project??
-----
NB: this is really old code with tons of long lines, weird spacing and whitespace in random places and functions that span hundreds of lines.
I seriously did not notice a consistent style here.
I wanna go back to working on the new system ☹️

my old code ...

More than 1.5k lines of code within a function, I love the old school php </3

SQL just feels like its screaming at me....

I was checking old code

css:

class name : blue_box
background : #565656

:(

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 :D

Found this gem in some old piece of code:

public static void printStackTrace(Exception e){
e.printStackTrace();
}

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.

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 :)

I don't really drink alcohol, but every time I look at my (old) code, it looks like I was drunk when writing it.

Fuck debugging 20 years old code in fucking assembly !!

Looking thru some old code, i lol'd

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.

Fucking tired of half ass memes of having a sleepless nights because of missed semicolon in the code.

Motherfuck. What are you using fucking notepad? And are you fucking 15 years old. Who the fuck finds such lame meme funny.

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 crying

Apparently, my younger self was a dumbass.

-> everyone at the company uses git
-> asked to change some stuff
-> boss says "don't remove the old code, just comment it in case we need it in the future"
-> ...
-> ???

I was looking through some old robotics code from the team I am on and I found this:

Void ArcadeDrive(xspeed, zrotation){
Drive::ArcadeDrive(zrotation, xspeed);
}

Why?
Why not just pass in variables in the opposite order?

I’m reading through the Apollo 11 source code like a 13 year old that just found out what porn hub is.

I am an atheist but sometimes I thank Jesus when a change to some old messy code actually works

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!!!!

I dont like it when i have to edit an old code made by a previous developer, i dont want to touch that spaghet.

Functions should not be 374 lines.

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!

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.

When you go back and refactor old code

Approaching an old project like...

When I review a code that I wrote 4 months ago

When I revisit old code that's not commented.

Wanted to search something in my old code. Understood why people use comments.. :/

Cleaning up my old code be like..

Reading my old code after a bug report

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"

Any project that started out with "All you have to do is make a copy of the old code. That should take 2-3 hours..." and ends with a huge list of change requests that takes days to fulfill.

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.

3 Years into coding and I still have no fucking clue on what 99% of the lines in a sample code means. And I'm already 18 Years Old... Beginning to think this line of work isn't for me T_T

Found this "new pattern" during refactor old legacy code... I call it "Singlefalse" pattern

When you try to use 6-year old code for your first project as a beginner...

A manager, a mechanical engineer, and software analyst are driving back from convention through the mountains. Suddenly, as they crest a hill, the brakes on the car go out and they fly careening down the mountain. After scraping against numerous guardrails, they come to a stop in the ditch. Everyone gets out of the car to assess the damage.

The manager says, "Let's form a group to collaborate ideas on how we can solve this issue."

The mechanical engineer suggests, "We should disassemble the car and analyze each part for failure."

The software analyst says, "Let's push it back up the hill and see if it does it again."

reading your old code like

Found this in an old project of mine... I think I was fed up with some issues ^^'

Employer asked, whether I could tweak the site's admin template that was made in 2005.
It uses tables to generate new webpages.
It uses php.
UI is a nonsense spaggethi crap.
Whole thing is shit.

Well, for good money I will just write everything from scratch. Took me ~10 hours and I already have the functionality that was in the original crap. Crazy how these 'devs' scam people!

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.

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

Programming commandment: Thou shall, from time to time look at your old code, introspect and improve!

When you're refactoring old code, and find a little note you wrote for yourself:

My first C++ programm which calculates binary numbers to hex numbers.

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 😜

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

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!

Yes!!! Only took one morning.... (changed the Downloader from WebClient to Selenium to get past the bot check, cant find old rant)

Good test for new PC other than games I guess... I can code and compile my projects.

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. 😎

!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 god

Scala reminds me a lot the good old days of Perl. we use to call it "Write Only Language".

Only the one who wrote the code, understand it. As long as he written it no more then a week ago

I just did a code review on an old project of mine. 10k lines altogether. 5.7k TODO's. I can't even.

When you look back at old code and think "Why the hell did I write it like that?"

Reading old code be like: who the fuck made this shit... oh, wait, it's me...

Wrote my first code on a commodore vic 20. I was 7 years old

I've just read my code from project finished 16 month ago. Let's just say that was an eyes opening experience.

Code comments #1: A way to document bad code that wasn't reduced to it's essentials and thus unreadable. Bad.

Code comments #2: A way to explain for non-programmers how the code works. Wrong place.

Code comments #3: Company policy. No one really knows why, but others do that, so we better do it to. The management sucks.

Code comments #4: Because some hip methodology/guru describes how to document code. After a few years, when the methodology has been (unofficially) forgotten, everyone still comments the code the same way. The old management sucked.

Code comments 5#: For insecure programmers who want to convince them self they understand the code they've written. Maybe apply at McDo?

Code comments #6: Some programmers are apparently paid by lines of code. Possibly understandable.

// Comments, anyone?

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.

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..

Sometimes I get so frustrated seeing my old code, I wanna travel back in time and slap myself!

The best beverage for when you're stuck working on an old project with weird code.

How my colleague fixes an error in an old PHP code ... And it works ...

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.

How I feel when im asked to add functionality to a project that was built like 10+ years ago and needs refactored in its entirety but the code base is so terrible that youre honestly better off just starting it from scratch but you are thrown into 5 other million things and there is no time to do it so you just shit out the bare minimum code that will not break the rest of the application.

Trying to integrate old code into a brand new framework... Oh, the pain.

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...

Trying to add features to 15 year-old legacy code..

That feeling of despair when you have to build a feature on top of 2 year old code with no comments

Maintaining old code as comments, coz... you never know when that bug in your commented code turns out to be the next big feature.

When u see old code from 2 years ago

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...

Had to look into some old code today and had the "Is this my code?! This can't be my code!? No one else worked on this code, so it must be mine... But, but, it's so... good! And clean! And logical! And well documented! This can't be mine... Can it!? Hey! It works!" moment.

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.

ffffffukcc you eclipse you god damn old piece of slow fuck, so many missing features after transitioning from intellij to eclipse, i want to fkig code in intellij but college forces us to use the god damn eclipse

Found today in the code of a client's old site: <em style="font-style: italic;">

😫

Reading the code that i wrote years ago, FUCK OLD ME

Past me is a dick.

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.

when you tell someone you code in php and they automatically think you are old school! 😒

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.

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

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.

When you look through two year old code and have to make it conform with your new and shiny code.😀

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! 😕😠😑

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.

If everything goes like the usual, my Valentine date will be a bunch of old code I need to refactor

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"

why on Earth do I find PHP error notices in the _JS_ console when debugging this old project... and those notices are even stopping the code from working. seriously, PHP, why??

"Okay, my query uses wrong date format."

"Why the hell I´ve put that join there? That´s not needed!"

"Why the hell I´ve joined the tables in THAT order?"

Joys of looking at your old code.

When you run your 3 years old project and it works great.
it feels like: The walking dead !

Ahhhh.. the great feeling of starting a new project at work after the stresses and health deterioration of maintaining old code bases.

When you look through your old projects and be like: "wtf thats not how you write code"

Beer or code? The age old question finally answered through personal experience!
.
.
.
Beer

Found an old code... Don't judge me

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

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

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

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. "

🙄

...
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 😂)

*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 better

going over some old code in the project...
thinking what garbage is this?
oh oh it was junior me :(

When someone copy and pastes code, repurposes it and leaves in the old comments that just confuse the hell out of the next dev.

Every time I try to refactor old js code!

Man I'm having coding cancer today. Working on old shit made by previous people. I'll make this example generic as it's from my workplace but..

There's a function that is called isFriend(), you would expect to return true if that is the case or false otherwise right?..

WRONG. There is a tenary statement within it that essentially translates to:
if (jobRole != "friend") return true else return false;

What the fuck.

So how does he rectify this? He flips the output everywhere he used the isFriend statement by putting '!'. No comment to indicate how he patched the fuck up (JUST FIX THE FUCKING PROBLEM YOU FUCKNUT); so when looking at this code I saw:

if (!isFriend()) { do not friend code }

He has wrote:

if (!isFriend()) { do friend code }

Thanks for wasting my time asshole.. many tidbits like this I've found..

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.

Super excited to have gotten the rare opportunity to completely re-write an old VB WinForms application instead of just hacking in functionality. Still has to be WinForms for various reasons, but getting to build it with MVP, separated concerns, testable logic, TDD, and not using in line SQL makes me feel like a pioneer of an old code base 😎
Actually, the biggest challenge is porting over the old functionality so it works the same! Nobody at the company was around when it was built so going from the code up (instead of outlining functionality first then making code) is difficult, but still worth it!
Shout out to all the other times we've had to hack in functionality to SHITTY code bases.... sometimes the re-write comes!!
Now I just need to not fuck it up 😅

Just received a CD that contain < 5gb worth of stuff from my fileshare at my secondary school.
can't wait to find a computer that still has a cd drive so i can find out what coding wonders I have on here...

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

Visiting old code written in vb6

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.

Re-Factoring old code and i find this beauty

$('.modal [name="port"]').attr('name')

Looking at old code i wrote.

That moment when you read your own one month old not-commented code !

What is this?

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!

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 myself

When you are supposed to debug old code, and find these loacl variables

TFW you open a brand new project after working on lines of code for months.

>closes last project
>at least 400 lines of code
>be me: "good bye my old friend."
>opens blank document
>anxiety
>hello darkness my old friend
>Aghhhhhhhhhh

that feel when I am the only one in team who knows at least one framework.. and coworkers refuse to learn and instead copy and paste code parts from old, insecure apps into new apps... 😐

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...

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.

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...)

I think I have figured out a way of making memorable and secure passwords...

Look through your old code and pick the cringiest, the worst snippets of code you can find, and use them as your passwords

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...

Target: Migration of an old system(not developed by us) to a new without touching existing applications.

Todo list:
[✅] Migrating old webservice from VB.NET to C#.
[✅] Decide if we go to the old system or the new based on the document class.
[✅] Start implementing same logic to the new system so the results will be the same.
[✅] Stunble across a search method with fuck up logic.
[✅] Create test cases to foresee all cases.
[✅] Implement logic for new system.
[✅] Stuck in infinite refactoring to fix existing bugs brougth from the old code to the new while mantaining the response the same.
[ ] Become insane during the process. (In Progress)

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.

Refactoring old junk code.

Would there ever be a day when I would look up some old project's code and won't say "WTF was I thinking!"

Looking back on old code is embarrassing... I suppose that's a good sign

!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.

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 .

Reading through old post-it notes and found a TODO that says "fix code" with no indication of a project it refers to lol

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.

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 😐😑

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())`

When I read my 2 years Old code

Old but eternal!

99 bugs in my code
99 bugs in my code
Apply one fix, compile it quick
101 bugs in my code

Guys, I'm a freshman just out from college and I'm arguing with a 30+ so called senior software engineer we should not store our assets in file server. He insisted S3 is not needed. Wtf man, and he say use svn instead of git if I want to use version control!!

When you read some old code you wrote😅

(from "Supermarket" by logic)

Started pushing a few old projects to my GitHub account to populate it a bit.
Found a year-old homework in C++ that was graded 95 or 100.
Run it to check it first aaaand... Fails with 7 errors and 30 warnings.

Fuck.

When you don’t even understand some old code you wrote 🤔😩😂

When I have to update a 10 years old code