Spend half an hour finding music to listen to while I code; Pause it after 30 seconds to concentrate on refactoring. Stays paused for rest of day.

Really getting the most out of those expensive new headphones.

Renaming variables is like...

Don't let it be tetris

Dear diary,

Today I sold my soul... I hacked my way around a bug instead of refactoring. It was a moment of weakness... I... I was not given enough time....

I am sorry...

New Project at work.
First commit: 'Initial commit'
Second commit: 'Refactoring'
-.-

An average day:

1. Start working on feature
2. Finish feature
3. Feature doesn't work
4. Spend 7 hours refactoring and fixing imaginary bugs
5. Add the 3 characters that were missing
6. Laugh and cry, laugh and cry...

Sad story about refactoring.
Programmer: I cleaned up the codes, extract reusable methods, reduced repetitive code and improve overall readability and maintainability.
Manager: why the page still display the same.
Programmer: ...

Every single time!

Me 6 months ago: "This is fucking genius. Beauutiful. Look at that code. See how I did this? Wow, I love it. Fuck I'm good"

Me Now: " What. the. ffuck? Wtf is this? What was I thinking? Goddamn. "

*reduces 3 methods and 37 lines to 2 methods and 8 lines*

Well at least it shows I'm still learning.

Refactoring, ain't nobody got time for that 😁

Boss: please refactor this js 2k lines spaghetti code class and use it in our reactive functional app

Me: it will take like 1 week to refactor and plug this

Boss: but it's almost the time I needed to write it!

YOU DON'T SAY? MAYBE FIRST LEARN HOW TO WRITE DECENT CODE. ffs.

I laughed more than I should. 😅

I'm converting some old stylesheets to sass and found this gem. How drunk I must have been to write something like this o.0

Manager: Why are you always refactoring?

Me: Refactoring keeps the codebase's entropy in check :)

Manager: mind blown!!

1. You will write ugly code. Code that is in dire need of refactoring almost immediately.

2. You will write brilliant code. Functions and algorithms that will impress all that use them.

3. 1 & 2 are not mutually exclusive. Good software can be written poorly, beautifully written code can be useless. At the end of the day, just get the job done.

Sounds right...

I was refactoring the most underneath part of our server code and just found 'getUserGender' method. I think for a second:We don't have this info. Look inside:
return name.endsWith('a')?"female":"male";

😑 it's surprising how much it works in Brazil.

Refactoring in a nutshell

I fucking love refactoring and making me and my groups code cleaner 😍

"Can you work on this ticket? It's kind of urgent."

-- "OK"

"And could you please not refactor? Just get this done."

-- "Why? What's the issue?"

"The logic is complex. We should not break it."

-- "Erm, that's what the tests are for. So yes, if the need arises, I'll refactor. The tests are my guidelines if the logic breaks or not."

There's a reason we create tests. So let's not hinder code base improvements by some random fear that stuff might break.

If breaks due to refactoring, we'll fix it by adding a valid test case during and then fixing the bug.

If my refactoring does not break the tests, I'll assume the code base is stable.

If your code is untested, then we have a complete different problem.

When you have to fix and extend some legacy code and somehow nothing breaks

My day in a nutshell:

Fixed the app.
Broke the app.
Fixed the app.
Broke the app.
Reverted all changes from repo.
Fixed app.
Found new bug.
Ugh....

Just coded for ~14h straight. Started doing some super heavy code cleanup and refactoring. Almost cried when I saw my code from the past.

Maybe it's time to call it a day...

Looks like spaghetti code is for dinner tonight

60 additions, 120 deletions and the code runs even better now. I love moments like this.

Me (refactoring bosses code):
Is this worth it?
let me work it...
I'll put this thing down, flip it, and reverse it

Boss:
did you just Missy Eliot my code?

Me:
Ti esrever dna ti pilf nwod gniht ym tup I

when you are refactoring CSS but ....

Refactored a legacy source file and reduced it from 2.8k lines to 300 lines.
Mixed feelings: happy that it is much simpler now and sad that my current project team members never go back to delete unused code.

Testing pending though 😜

Boss: Have you finished that feature?
Me: Almost there, i'm refactoring some classes...
Boss: What? Refactor? But thisnis a new feature, it does not need refactor! We don't have time for this!
Me: 😵🔫

This is what happen when you care about code quality.

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.

So far, this is my inspiration to refactoring the code right after it works as gift to my future self.

Me: *spends 4+ hours refactoring existing spaghetti, ensuring components are modular, easier to test and fault tolerant*

Project manager: ...

Also me: *adds pre-loader image to register and login buttons when user submits form*

Project manager: *All excited* Awesome work. 🙌That's some nice improvement..

Like wtf dude 😳..

My takeaway: These noobs only care about what they can directly interact with

My boss codes, I'm lead Dev:
Boss: "just finished an MVP of the X project. It's 3 files and 1800 lines of code, plus triggers... "
Me: "Shieeet..."
Boss: "yup, your shit, you'll be refactoring it"
Me: *sigh*

Did you ever refactor this much code in 5 hours? I refactored 770 lines of code down to 282 lines.

Refactoring old Js code with Ramda.

Refactoring legacy code when...

if _out == True:
r = True
elif _out == False:
r = False

return r

Refactoring and writing tests for code that was code written by intern and is on production about one year

Me at 11:00
"Ohh I need to split this component into two since too much has been put into this.. Seems like an easy task.. Will take me an hour max to do this.."

Me at 22:00
"Damnnn.. I think I have broken this code.. I am doomed.."
*Replaces all files with HEAD

-Look at super hacky code for 30 minutes
-Ask yourself, how did this ever work, guy must have been an idiot
-Check annotations, you committed it
-"Dear God past self, what have you done..."

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

So, should I refactor this into a .greatGreatGrandParent() method, or should I just go hang myself?
(Thanks former colleague for this gem)

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

Refactoring my 2013 code

I'm refactoring some old Java code I did

my goodness I was a short-sighted idiot

That moment when the you actually think that this huge refactoring isn't worth it, but you do it anyway so you can live with yourself...
Code quality is love. Code quality is life.

When you finally get around to refactoring that inefficient hackjob you implemented months ago

RIP all the code I'll be refactoring 🙏😂

When refactoring your own code makes your past self feel stupid.

Ticket : "I have a blank page when I load this page"
I open the script (php), I see at least 7 nested foreach loop starting with a 2600+ long array. I spot the buggy loop. I mark the ticket "may need refactoring". I go drink a beer with colleagues.

Dear code,
Please get refactored yourself
Thanks

The irony with refactoring is that it is easiest where it's least required.

just wanted to look up something in an old project. saw things i could to better.

Ended up refactoring the whole project. Forgot what i was looking for.

You refactor after there's code. You can't have clean code if there isn't code to be cleaned to begin with. Code first. Think of perfection later.

Just spent 10+ hours refactoring a code, and at the end I've figure it out a one line fix to the problem... just wasted 10 hours of my life.. :)

var { name: x } = person
Day 1 : that's some good ES6 code man, I'm so 2017
Day 5 : Oh yeah I think it works, dont really remember
Day 17 : WTF is that ? Is that even Javascript ?

I hate it when I'm in the middle of a refactor so big I forget why I started it.

That feeling everytime you realize that you could have built something better with less code and repetition after completing a project.

Refactoring nested ifs.
I'm not a pro but I despise working with nested ifs. It's hard to debug and read.

If you cant chunk the if using method, i think you can use ifs like this:
If(){return}
If() {return}

Not like this:
If() {
If() {
If() {
}
}
}
😠😠😤🙅😢

Refactoring a 1000 line God awful js function. Why do people do this?

Every time I look at some code and say "what the hell?!" the code refactors itself before my very eyes.

Before refactor / After refactor

After long hours of brainstorming, refactoring and redesigning, I looked at my boss, placed hand on his shoulder, smiled and said "version 2 boss, version 2" 😂

i am fucking tired of companies that come to me expecting to magically fix their STEAMING PILE OF BULLSHIT AND TRASH CODE. how about when i ask "can i get a project brief", instead of saying "just fix it" or "it just needs to do this", GIVE ME A FUCKING COHERENT AND DESCRIPTIVE WRITEUP OF EXACTLY WHAT YOU NEED. i can't read your minds, let alone read the code the previous cock sucking developer wrote, so guess what? i'm left with no other option but to completely rewrite it. to top it off, instead of giving me god damn excuses as to why you can't get me the api key for your order processing, MAKE A NEW ACCOUNT AND GET IT TO ME. how the fuck do you expect me to test an application when i don't even have access to the fucking api the whole shit pile is based around? i swear to god if these people expect me to have this done by the end of the week but want to be little cunt nuggets they can go eat shit. fuck you, fuck your "contract", fuck your company, FUCK EVERYTHING. greedy, shit faced bastards

Almost 3 weeks back I joined a company as a React developer. For a week I had nothing to work on as they were already working on few projects.
So my senior asked me to take up a project(not yet live) which was developed by 2 interns, as the frontend guy's internship was about to end in 4 days I have to take over the front-end role.

So I talked to that guy for next 2 days regarding all the project scope, codebase and whatnot. But still not entirely convinced. As i got the repo access, I began to check the codes. God !! It was all spaghetti code. I was damn frustrated. And still I am.

This whole week I am trying to do the refactoring as much as I can, I completely lost interest.

I cannot blame the intern guy, he is smart and tried to do the best he could, as he didn't know about the company standards. Maybe I was too the same kind back then. Now he is gone and I am stuck building components over that code.

Bonus: He used some old react boilerplate.
-_-

Cleaning up my old code be like..

When you're asked to extend a functionality on a piece of code and the 2.5k lines in the view are a juicy mix of PHP, HTML, CSS, JavaScript and the functionality relying on jQuery trasversing through the document tree and expecting things to be in their place. Oh did I mention html build with strings in JS? I'm going to love this day! WHY, JUST WHY?! *gasp*

This spaghetti code needs refactoring

I am currently refactoring my code:
1. 200 errors
2. fixed them!!!!
3. build the solution...
4. wait for the build to complete...
5. 300 errors
6. FML

!Rant

Fuckkkkkkkk youuuuuuuu CLIENT :/

Client asked why two weeks for refactoring.?? When you already know the functionality and he gave us two days.

After two days we successfully​ renamed everything!!! 😣

I think I have a programming disease: Premature refactoring. Sometimes I refactor the refactor that I'm doing.

It's only been a few years, might need a little refactoring.... The things you find when cleaning up old directory structures on forgotten hard drives...

I was super unproductive the past two weekends, since I lacked the motivation to code. But today I sat my lazy ass down and did some major refactoring in the engine - seems like nothing had been broken.

Coworker called me up and shouted at me for refactoring code. "It might break!".

But his copy paste addiction is sure to make everything more stable, right?

Course, he still hasn't figured out that I'm the tech lead, so I will completely ignore his useless whining, as I have his boss on board.

Refactoring seems like a great idea until you actually start refactoring

Just saved the company 1 byte, thank me later...

After 20 minutes refactoring code and changing methods, you realize you have been editing the wrong file -.-'

I spent my last 2 months refactoring a crazy panel.
No one understood how that panel was working...I was feeling like the technological version of the chimney sweep.
I could almost breathe frustration.

So... what's your worst experience about refactoring old crazy codes?

Hours of refactoring just to get 0.5 seconds increase in performance per document generation.

Sounds small but makes a big difference when generating 100k documents.

Still not happy with it though...

After finishing a long and arduous refactoring I got to delete some hundreds of lines of really horrible, unmaintainable and broken legacy code. Feels absolutely great.

I love the smell of deleted code in the morning.

That moment when you know your code can be much shorter and cleaner but you just keep typing because you're too lazy to restructure.

When your bitch-ass co-worker inserts something that is plain useless in the program in every degree

First step to refactoring your predecessor's code.... Vent in a comment...

That moment when you have refactored so much shit, then really broken the project, but can't see yourself doing a git revert because you had invested so much time and know ultimately it *needs* these changes...

Thank god I fixed it! 😌

Refactoring 😜

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

I spent 4 hours finding a good way to instanciate golang structures. Came up with a function that returned a value or pointer and I just kept reusing the nomenclature for an entire project. Then my buddy looks over and goes, "Ethan, you're a f****** idiot", and shows me the standard nomenclature. Now I have to refactor my entire project. FML.

(Edit: typo)

Rabbit hole class refactoring.

"I'll just tidy up this method, oh and this one...and..."

Worst code I ever had to touch: a React application, createClass era, before redux was a thing, that had everything in one fucking component.

Every fucking thing.

This was a simple video chat application, but still. The component's code included:

- Views (contact list and video call screen) and logic to switch between them;
- All application state;
- API calls;
- Websocket message handling;
- WebRTC logic (getUserMedia and p2p streaming).

This app was built by one person in one month for a demo. That person left the company after the demo and I had to maintain that mess without zero React knowledge (I was doing angular at that time). On his last day he gave me a crash course and an overview of how the app worked.

Around that time I attended a few meetups and a conference with talks about React. That, my curiosity and ability to learn by refactoring helped me a lot when I had to add new features and fix bugs in that app.

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

When you try refactoring bad code you wrote a long time ago

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.

Tired of reading spaghetti code written by your team mates?

Sit right next to them and ask them to write unit tests for that code.

Smash their head on the keyboard everytime they have to think longer than 10 seconds on how to test a specific logic.

Strangle them with any wire you find nearby till they agree to break up that spaghetti code unless they already started within that 10 second time frame.

When the exercise ends, tell them this is what refactoring is and ask them to pass on the knowledge.

Tried refactoring working legacy code :(

What a difference three lines of code can make. That's the typical case of "that seemed to be a good idea". I don't know how did I think it would work out on the long run. Next step will be reduceing the enourmous CPU usage as well.

Sales guy: I mean, at the end of the day, coding is just typing, right?

Me: You've got to be kidding me.

Other coder: *ignores us because he's three hours into refactoring his vim customizations on a $500 imported dvorak keyboard*

Me: Ok, maybe sometimes.

New task - add new field to a form... After few hours I'm ending up committing changes in 80 files..

*Refactoring craze*

I guess In software development, there are 11 most difficult tasks:

- Naming variables/functions, because the names should be meaningful but not verbose

- Write an appropriate git commit message, because f*ck u....

- Refactoring, because it involves the first two things and more...

Those little moments when you finish writing and refactoring the code and the result is elegant and just works

Love those moments when you’re refactoring legacy code and manage to put logic of 50 loc with bunch of loops and conditions into single sql query.

Refactoring is like kissing a baby.. I like doing that, but to my own.

So this one day I'm at work and the manager peaks into my office and just says "can you check that platform X is building, pretty much done just a basic bug check" (this bloke had negative 1 technical experience)

I'm not sure what he means, the whole thing is built in Java and I know nothing about that...

I log in the platform on dev server, sure enough it seems to work, charts are drawn, no errors, then I try to log out; this button does nothing...

I don't bother telling the manager, I just go to the dev who's a friend of mine and tell him about it.

A week later, manager jumps in the room all excited "we're launching this product tomorrow, mind checking again?"

Sure, I log in, ... There's no log out button, it's gone... I ask the dev.

"Yeah I fixed it, it's gone now!"

When you get back to the office and remember the mess you were tackling on Friday 😅

I wish I had a 💲 for every time my refactoring broke something.

Oh God I love Refactoring!!!
*after 5 minutes*
Oh God I Hate Refactoring!!! ;(

I was looking at some poorly written code today in a project and I was curious to see who wrote it. I blamed it and found I had wrote it 6 months ago! smh Well... at least I know I'm getting better! I ended up refactoring it to use better code patterns.

That awkward feeling when you think you've done a ton of good work but you've really just been stuck in a refactoring loop.

Refactoring someone else's code. I wish I hadn't been born.

Does anybody out there actually really love their job? Because I do. I'm not sure if it's just me or that my job is actually great, but my coworkers are respectful, my boss lets me have control over each project's pace, I get to write tests and invest in refactoring, and I make good money doing it.

Is this just me?

Refactoring you said.
Make your code maintainable you said.

Now, I'm in the middle of refactoring my functions. Detecting redundancies, building new general functions etc.

Then come another jobs.

And when I get back to my half-refactored code, I got really confused.

What did I do last time? And why the hell I wrote "finish this later" as my commit message...

Reaching levels of refactoring not possible before

Just cut 2 seconds off the load time after roughly 2 months of refactoring. The code looks beautiful though.

When you have the amazing refactoring idea you've been waiting for... but it will be hours before your back at a computer.

I'm surprised management allows us to write false positive tests just to have high coverage instead of refactoring it first. Time to abandon ship.

!rant
The moment when your business logic operates significantly faster after refactoring.

Managed to reduce the response time of a logical component from 14s to 4. I am so damn happy right now

Writing

// Refactor this

As I write the code... Never actually refactor it

When u see old code from 2 years ago

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

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

Hmm, let me just refactor this quickly first...

Refactored a lot of code in between meetings today. Feeling accomplished. Haha!

You know you have become geeky when you term restructuring of road as refactoring of road

when a senior dev says your code is messy just after you finished refactoring 😞

i am writing a piece of code that i already feel guilty about,
alternate is refactoring a complete module.

Seems like Big refactoring coming.. 😅😅😅

!rant
That feeling when the refactoring improves the performance

First software refactoring in the company I worked for. No test environnement because "who needs it?", no unit testing, no comments, had to make sql updates and shit, was scared all day long that something would fuck up.
"Fuck fuck fuck, forgot a part of the where !" Had to fix everything quickly so no one would notice, no coffee/smoke pauses. On top of that, got a ton of retarded requests from the PM and other technicians working with me like "hey boi, could you add an icon to every button we made? There's like a thousand, we need it for tonight, our client will come visit us and I want to show him a better interface blablabla"
And since I was an intern, I couldn't refuse, had to work like a prostitute in virgin-land, and for what?

"Oi, you did good, now do other stuff"

!rant this is just a shoutout, how fucking happy I am. Clean code valued over fast but hacky push of features!

Backstory. I work for a startup. Long story short a guy with an idea needed a developer. I've worked for about a year without pay but now since we're live I get paid. Recently a new field of bussiness came up. I told tge guy with the idea (a.k.a. my boss) that we either could just "hack" the current code to just make it "fit" well kind of... Or refactor our main code base, as requirements where changing at least monthly and we just built on top of the monolith.
Don't get me wrong. It still isn't perfect. However I was able to refactor the main business logic for the last few days, as he understood, it's an investment into the future.
Good guy!

P.S. On another note: happiness or happyness? :O

They say 'code drunk, refactor sober' but they fail to mention the sober refactoring dude won't have a CLUE what the drunk coder was even thinking.

Such is my life.

I love refactoring :) just finished going through implementing accrued knowledge from the last 6 months into all my client side code and just doing that opened all kinds of doors for new features and niceties.

I'm rewriting a game from C++ to C just for the purpose of learning and adding more features, however; after I refactored the code, the game broke with a segmentation fault and I have no idea where the memory issue is.

I've been debugging for hours now and I've got nothing. FML

A refactor a day keeps the doctor away!

!rant
That feeling you get after refactoring code!
I feel like I could flyyyyyy!!!

After 2hrs of refactoring

Refactoring some of your messy code into something simple and easy to read is so satisfying. 👍

As a rookie programming, I wrote really bad code and didn't understand why. Now, I've improved to where I know bad code, but I continue writing studios horrible solutions. And in the end up refactoring much until I don't have energy to look at my code anymore. This although knowing what I should/shouldn't do. Shame!

Knowing when to stop refactoring and move on with my life.

It's a Friday and buzzing from refactoring absolute shitty CSS code by reducing it by 2200 lines (and still not complete). Who the Fuck wrote this complete piece of shit!

Refactoring

When you find out you didn't need that if-else statement in your code if you simply made an additional variable with an expression that works for all cases of that if-else statement

Refactored my current portfolio grid :) Decided to remove margins for a cleaner look and removed slideshow functionality because things became too slow and it really doesn't need it.

Spending my saturday night refactoring my js codes <3

That moment when, after you've spent days trying to refactor your code to be clean and readable, you look at what you've made and you honestly feel like you actually made things worse than before.

I don't know what's wrong with me this morning. I started refactoring, and I know I'm overdoing it. I can't stop myself. I'm stuck fiddling over it like a meth head scratching his skin.

Please stop me. I'm hurting the code.

when u feel that u wrote some godlike code. 2 months later client wants to add new features. then u realize ur code needs major refactoring. "what was i thinking, far from godlike"

If you think your legacy code is bad - this is what I came across in a system I'm refactoring this morning... and this isn't even the bug I was looking for.

first off, i think this may be out of scope but either way.

i think along the rants, a tag seperated section for programmer tips could be pretty neat :)

i'll start off, my tip of today would be: if it seems too complex, it probably is.
consider refactoring by splitting into multiple smaller parts or even its own seperate API. :)

!rant

Oh that wonderful feeling of finishing a month long project. Updating all the comments, refactoring things, testing everything out, closing the 50 chrome tabs you have open...

Life is good

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

Working on a project with tests is so nice.
I love tests. Well, I hate making them, but now refactoring is so easy :]

Spent all day refactoring lots of confusing code down to just a few lines. I am satisfied, frustrated and drained all at the same time.

We just found out that refactoring our code -base is no longer optimal for the health of the company because our deadlines are too tight. We'll get back to refactoring in a year.

Spent 2 days refactoring code written by our "offshore team". I've done refactoring on the same code in the past, probably upto about a week in total of refactoring now. The code looked like it was written by someone who had literally just finished their first "Hello World" app - loads of code blocks copied and pasted instead of declaring reusable functions.
The whole thing should have been done by us in the first place.
And yet our money-conscious company wants to employ more of these developers. Cheaper than us? Sure. Quantity over quality though, but I guess money is all that matters to the big cheese

Do not refactor on fridays...

I have to create python parser (3.6) using code provided by client (2.7), that they used in their company, and it is full of crap like:

if a==1:
if not b:
c = [1,2,3]
if a==2:
if not b:
c = [1,2,3]
if b:
c = [1,2,4]

Or:

text = ""
for i in something:
text += "real text " + some_string + " \n"
text += "another line " + some_string + " \n"
text += "and another " + some_string + " \n"
text += "and so on " + some_string + " \n"
... (many lines instead of one appended text block)

Of course above variable names are just for shortening code, but there are variables like oo, ooo, var_ or var__... cause you know, PEP8 does not exist.

Looked up at the clock... 2 AM... Thought about giving up and going to sleep, but something kept me there...

Rewrote my encoder and decoder for my steganography program, which are used to insert and retrieve data respectively from images. Compiled, ran, and output was as expected!

Tried to write actual data, instead of just headers, to the image, and it broke... Of course it wouldn't work first try, it's me writing the code after all.

But then, after debugging for a while and changing a couple lines, the encoder looked like it had done its work properly. Then I decoded it, and voila, data completely recovered! It almost felt too magical to be true, usually I have to modify a lot more to get it working.

So now I'm in bed, after literally decimating the memory usage of the program, amongst other optimizations, and I know that the code works perfectly 😎 best part is I refactored each class down to 100 lines each, so now it's clean and dense 😇

Just had to share, feeling so good right now 😄

Just refactored some crap I wrote 3 years ago. I feel good now.

The boss wants to improve the QA by introducing GUI tests (partially non-automatic) instead of refactoring the legacy blob of application with unit and integration tests.

THIS WONT MAKE IT ANY BETTER

Refactor?
Is it another word for procrastination?

Spent the day refactoring a REST app into graphQL, that feeling when all tests are green and everything is committed and merged 😧🤓

I can't make progress on my private project.
I just started and already refactoring my code.
Yesterday I started to refactor my tests -.-'

I'm sure I will lose the interest in this project because I start a new one I can refactor to death.

When refactoring legacy code and your colleague committed this a week ago... As punishment we made him listen to "You're too fat to fly" all day long.

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.

When you find an awesome, intelligent way to do something after thinking you had already found one and implemented it already.

The moment you realize you've got suboptimal code tattooed onto you forever 😂

Refactoring old junk code.

Pair programming a major refactoring, colleague tries to change _everything_ simultaneously. Spent hours fixing compiler errors, now it's not linking. ¯\_(ツ)_/¯

That awkward decision making process when there's good cases for refactoring, but there's equally as many cases for a full rewrite...

Hmm what do

When your colleagues are doing legacy code refactoring but you know that's not gonna end well 😂

* Start maintaining/upgrading new project at work
* Read book on best practices for the framework
* quickly realise all the "don't do this" parts of the examples in the book is EXACTLY how everything in the project is done
* cry self to sleep

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?

I think my exhaust needs some refactoring too...

"Refactoring is a waste of time"
(inner "what the fuck!!!" ensues)

Refactoring is like dating. You have to remember stuff, maybe you're insecure and you may have to overcome yourself to actually do it.

But when it works out, it's great.

That emotional rollercoaster when you refactor a huge mess and finally there are no more compile errors in it. But there are still endless broken tests to fix :(

Ugh. That may have been a mistake.

I'm deep in a large effort to refactor my project. It's a one man deal and something I've been working on pretty much every day in some fashion for nearly 10 years (five years ago I started a scratch rewrite to move from a fully CGI server rendered application to a browser rendered asynchronous version built around JS) and that took me three years.

I started this refactor about 8 weeks ago. Turns out I've been tackling the largest modules and progress has been decent. So that's good.

But I got to wondering ... Just how much code is there?

So I whipped up a quick script to do some calculations. Read each file and get a line and word count, skipping empty lines.

In JS it turns out I have 83,973 lines and 467,683 words.

On the back end, 86,230 lines and 580,422 words.

Average publishing stats say the are about 250 words/printed page.

That means I'm confronting refactoring 1,870 pages of JS. That's the size of several decent sized novels. (I think I've done the equivalent of Maybe 400 at this point).

Makes me feel like the walls are creeping in to know how much is left to go ...

It the time to play with your code, folks!

You've got the perfect architecture lined up, a great idea about how to transition and you're about to start refactoring. Then it hits you. You've got 10 clients running your code in production and you'll have to migrate their data to the new structures, from the blob to each new microservice datastore. For each release. FML.

INSTANT REFACTORING

code refactoring is the worst fuckin shit that needs to be done

Watching a video on YouTube that shows: Refactoring and Extract Method features in xcode 9 beta brings a tear to my eye, never thought we will get that basic functionality 😢

When you work 2h on a feature and you forgot to commit before merging. Fortunately this also opens a new opportunity: refactoring

How do you eat an elepant?
One small bits at a time.

When you see someone refactoring code without benchmarking it.

And it becomes 10 times slower than the code before...

Seriously, there is a reason why it wasn't perfectly async, because a normal for-loop in nodejs is way faster than a `.forEach()` statement.

Toshiba knows very little about refactoring.

!!rant

Today I wanted to finish a feature in some Python code I. Working on instead I scope creeped myself a bunch times adding "other cool features" and refactoring working and readable code that didn't need refactoring. Oh and learning about random things on SO and finally giving up on making any more progress for the day and reading devrant.

ADHD Self:"Coding is love, coding is life. Plus I'm getting paid."

....

Responsible self: "Wait no, go home sleep, spend time with your wife"

Remembering self:" she's out with friends"

Responsible self: "ah, carry on, she's probably spending more money than you're making"

I discovered the Source Making website a couple weeks ago, it's awesome.

It gives you clear tutorials on the essential design patterns and refactoring techniques complete with example situations and code. Love it!

I promised myself that if I didn't start up a new relationship by September that I would plan to start a new lease in life and move in 2019. The online dating subscription I've used for a few years will cancel at the end of this month.

I used to doubt that fate was real, but times like this make me come close to believing in it. Maybe fate is just one large karmic refactoring.

I have to stop refactoring everything. 4 weeks on one of my private projects and I'm still on the same place. But I have refactored the code like 4-5 times now ...

So I've been back to work for 2 weeks after going on a holiday. Getting back into the flow of things was easy, but seeing the status of the project that I am a part of, and seeing the kind of implementation work that my co-workers has done, it's kind of a no surprise.

So the past 2 weeks I've been completing features that I left my co-workers to finish, but didn't. And rewriting other features that they worked on, but does not meet the specifications.

Will I ever be able to work with reliable/competent developers?

TMW you want to introduce a big feature that will require you to refactor the existing code, but you don't have to worry about breaking the latter since you have tons of unit tests backing you up.

I recently refactored the horrible main.js of one of our clients. I didn't even know you could fit so much shit in "just" 700 lines of code (yes, it's really that big...). After 3 hours full of swearing and grinding teeth about this piece of shit, I was finally done and tested it.
It was so incredibly satisfying to see the page loading twice as fast!

When you finish the sprint

Project almost done! Just gotta clean the code up and maybe iron out some bugs :P
Man cleaning up is boring, but it feels so good to restructure and make it all look pretty 😍
And I'm sorry, tab lovers... but while doing so i realised why people better like to use spaces... as soon as you mix tabs and spaces... it's not pretty ;~;
So yeah, I'm now officially a spaces user...

When your senior says he may as well stops working as I'm always refactoring his code...

Same sentence says I copy what you've done in other places so I don't see why it isn't good enough. By copy he leaves redundant code in there too.

Am I a being a douche is he just being over the top?

- He writes code and expects it to live for a long time.
- I write code and will go home and refactor my own code.

This will enable you to spot any bugs fast. find the cellphone/mobile phone.

Refactoring 2700 files. By hand

Refactoring a long, nauseating piece of code while the mouse died.
Finished the job, about to push, KDE froze.
Good enough excuse for trying a new distro I guess.