I was told during my initial interview that the book "Clean Code" is their Bible here.

And it's true. It's lying, unread in drawers and shelves all over the office.

That rare moment when you write clean beautiful code and you just stare at it for a few minutes

Splitting 5 lines of code to 3 functions

Updated description!
Fuck Wordpress in the ass with a new kind of cms. Make devs happy with clean code. And Laravel

Just want to share some fun 😁

While reading through the Elasticsearch (Java search engine) source code a while ago I found this gem:

return i == -1? -1: i;

I think someone should stop drinking while coding.

Some other nice lines:

int i = 0;
return j + 1000 * i;

Are these guys high?

My brain hurts.

Mark my words.

I like how nano not only shows you unnecessary whitespaces, it throws them in your face and and screams "YOU SEE THAT? WHAT IS THIS SHIT? DELETE THIS DISGRACE TO CLEAN INDENTED CODE!"

One of the coolest good bye message I have ever seen in my company...

The code is so clean with proper comments...

Got my copy 😍

The actual metrics to evaluate the quality of code 😂

When someone asks you to add more comments to your clean code.

a workarround a day keeps the clean code away

I can now die without regret, I came back to a project after leaving it for three months

I WAS ABLE TO UNDERSTAND MY CODE!

I think I reached the point of writing clean code?
Let's hope so :)

I really hate people who prefer this coding style:

if (condition)
{
// something shitty here
}

Instead of this:

if(condition){
// perfectly clean code
}

Refactoring, ain't nobody got time for that 😁

From Robert C. Martin's Clean Code

Currently on an internship, PHP mostly, little bit of Python and the usual web stuff, and I just had the BEST FUCKING DAY EVER.

Wake up and find out I'm out of coffee, oh boy here we go.

Bus leaves 10 minutes late, great gonna miss my train.

Trains just don't wanna ride today, back in a bus I go, what's normally a 10 minute train travel is now a 90 minute bus ride.

Arrive at internship, coffee machine is broke, non problem, I'll just lose it slowly.

NOW HERE COMES THE FUCKING GOOD PART!!

Alright, so I'm working on a CMS that can be used just about on any device you want, mobile or desktop, it's huge, billion's of rows of scientific data. Very specific requirements and low error margins. Now, yesterday I was really enjoying myself here until today, Project manager walks in, comes to my desk and hands me a Samsung Gear S3, an Apple watch and some cheap knockoff. He tells me that before the Friday deploy, THE ENTIRE CMS SHOULD WORK ON THOSE WATCHES!

I mean, don't get me wrong, I like a challenge but it's just not right, I mean, I'm still not sure what the right way to handle tables on phones is, but smart watches, just no. Besides that, I've never worked with any Apple devices, let alone WatchOs, nor have I worked with Android Wear.

Also, Project Manager is a total dickhead, he's the kinda guy that prefers a light theme, doesn't clean up his code, writes 0 documentation for an API, 1 space = tab, pure horror.

So after almost flipping my desk, I just called my school coach to announce I'm leaving this internship. After a brief explanation he decides to come over, and guess what, according to the Project Manager I wasn't supposed to do that, I was supposed to test if it would be possible.

FUCKING ASSFUCKFACE

One of the greatest books I've read so far.

wrote shitload of clean architecture beautiful code and compiled successfully on the first try without crashes or errors

Yesterday I said: "My code was nice and well organized but then I started to do the things the customer wanted. Now it's horrible and ugly."

This guy next to me in the train is coding C#... but his codestyle looks like... no words... I am now reading Clean Code!
I hope he will notice!😂

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

/***********************************
/* a temporary hack, fix it later *
***********************************/

That was 7 years ago. I mean it was last edited 7 years ago when a temporary hack was created. It is now a permanent solution as nobody know what we are supposed to fix

.... Nothing is more permanent than a temporary fix. Not even clean refactored and tested code.

Why not have a custom (500 line) JSON mapper... you know... fuck those auto mapping libraries out there...

Colleagues asking me to write clean code be like...

6 months of internship made me realize that solving other peoples bugs is my biggest distraction.
Apparently I enjoy solving bugs more than writing clean code from scratch. 😐

Oh yes...

I just turned an awful website with with an even worse backend code into something modern and with clean and stripped code ..

Guess what..

I just got thrashed for having a bug in my PHP code ... !!!

I did it! I am now part of a web company as an intern, entirely self-taught. This is so cool, when they looked at my code they were surprised about my skills and how clean my code was. Fuck yeah, I'm happy

I've had this amazing piece of advice as my Desktop wallpaper ever sense it popped up on r/programmerHumor. I mean I still don't write clean code, but now I know to be prepared for the fucker!

Developers coding cycle:

Start of Project - "Right, I am going to make this code clean and structured."

Deadline looming - "F**k it, just throw the code in there and get it finished".

Found this treasure in Clean Code book ))

Dear coworker: oh my god we aren't in highschool algebra; using "x" as the name of a parameter makes me want to cut you.

Picked this up the other day. Hope it's as good as people have been telling me.

If so, then here begins a new journey for me to better code.

My life is a mess but my code is clean.

The proper use of comments is to compensate for our failure to express ourself in code.

Quote of the book "Clean Code" by "Uncle Bob".

#ShotsFired

"Next project, I'll do clean code!"

*Next project*
"Next one for sure..."

My coding-senpai placed this PHP code (before he left) to my org's custom-footer due to a feud that happened months ago

it flooded their cPanel with folders with '.log' as their extension everytime someone visits their website

I LOL'D UNTIL
..They hired me to clean it up :^(

They got over 700,000 of these folders
#feelsbadman

When the code is not working:

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

Then after a while the code works:

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

I write loads of services, tools, programs for myself (unpaid) which I could just as well open source.

Only thing is that the code is usually not that clean and refactoring would take time that I don't have so I'm kinda anxious about putting it out there 😧

There is no reasonable excuse for doing anything less than your best.

- Robert C. Martin, Clean Code

My personal life is in shambles-but goddamn is my code clean.

Me as a programmer 😂

Does anyone else get so self conscious about writing neat, clean and efficient code that you get demotivated because you always think "there's a better way to do this".

The cleanest code is no code at all. 😂

Had a friend who was forced to document his own code. He gave up after an hour of trying to figure out what methods 'somethingsomething()' and 'somethingsomething2()' did...

So happy right now that my new book has arrived

I remember reading a comment on here that as developers, we are really authors. And that has changed how I write (and even read) code. I don't remember who and where it was, but whoever said that: Thank you.

Damn. Scientific code is sure as heck not clean.

Clean Code opened my eyes !!

Read Clean Code and came to the realization that I'm a terrible person to everyone who had to read my work.

That feeling when you refactor that spaghetti mess into clean beautiful code that passes all tests flawlessly

Me trying to clean up my code is like trying to make dirt less dirty.

Was practicing kotlin today.
After finishing a file I ran the clean the code thingy and it removed 137 semicolons.
Its gonna take some time getting used to not ending with ;

I just finish "rebuilding" a page that I have built last year. My Js file (jQuery) went from 1200+ lines to 600..

I rewrite everything, the functionality is the same but the code is mush more cleaner.
Soo bad and redundant code.

Although comments where very helpful.

Feels good.

Maybe this could clean up some of the code I’ve seen... 😂

At my previous job a coworker left positive comments alongside any negative ones on my code. “Nice job here. Very clean”, or “nice use of X design pattern here!” Kinda made me look forward to his code reviews.

DEVS THAT MANUALLY UPDATE AUTOGENERATED CODE ARE THE WORST!!!!

Guess who has to clean up your mess? And be pinged about it later when another dev thinks they wrote the feature??

No, your hack wasn't cool.

Is good code the same as clean code?

Clean code is hard to follow all the way through

When I discovered Clean Code, design patterns, TDD and BDD. It just clicked. Ever since everything build so easy and obviously. I no longer have most of the code problems folks rant here about.

That's when it came to me: it's not enough to know how to write code. To climb off those amateur shoes I must adopt those methodologies, so that the code would be decoupled from me, from my style, and I've got to let tests drive my code rather than vice versa to have a flexible and reliable codebase that is cheap and easy to maintain/extend.

Le me: "my code is awesome! The way I did XY and Z is insanely cool, efficient, and maintainable."

Le Boss: "yeah so let's schedule a code review next week."

Le me : "... fuck, Fuck, FUUUUCK!"

Internal Screaming

Find the root cause

Working code is not a clean code

"As a team, we have the shared responsibility to ___".

(replace with ALL of the following: resolve bugs, do junior's code reviews, clean up dead code, keep the kitchen clean, improve test coverage, write documentation, order coffee beans, etc)

NO. JUST FUCKING STOP RIGHT THERE. Shared responsibilities do not exist. A single person is responsible, and can optionally delegate tasks.

EITHER I DO IT AND I'LL BE FUCKING AWESOME AT IT, OR SOMEONE ELSE DOES — BUT I'LL SLAP SLACKERS IN THE GENITALS WITH MY KEYBOARD.

Fucking startup hipsters with their community driven attitude, this way no shit gets done, ever.

The moment, when you refactor your code and it looks so clean. Priceless.

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.

Every time I have to deal with my boss code and lack of convention and everything that makes a clean code I just want to scream like a bitch and punch him in the face without minding breaking my own hand.

You know it...from the introductory page of "Clean Code" by Robert C. Martin.

Which door represents your code?

Uncle Bob and Martin Fowler. Their books (“Clean code”, “Clean architecture”, “Refactoring”) and Twitter posts have changed the way I look at software development.

Beware of the layers

Sometimes dirty code is more efficient than clean code.

If features get dropped frequently and requirements change every few days, writing best-practices, tested code is wasted time. Learned that in my first job where I thought the other devs were all bad. Until I realized their bad code pays my salary, and my clean code takes more time to develop.

Clean your code till you don't understand what it does anymore

Did someone say "debug the code"?

How to write good clean code

Look at that desktop. Sexy and clean. I wish i could say the same for my code.. :-(

Writing clean and efficient code 101 presented by yours truly, dudeking

Bob Martin. His books Clean Code and the Clean Coder, and all his talks on architecture, SOLID and TDD. I could listen to him talk for days, and he taught me everything i know about writing clean code.

A coworker that is producing incredibly bad code and refuses to learn new stuff was declared "senior developer" by my boss. And me with over 20y experience? I am just a junior.. and have to clean up his mess all the time. I guess it is time to find new job.

Sad. Got a new job. Apparently, readable code is not a priority. My suggestions were being ignored. Does the benefits of condensing an if-else to a simple one-line return statement really that hard to understand? Does making clean and readable code should be an optional thing to consider? It doesn't help that I'm the youngest, they felt like I don't have enough street cred. I'm starting to hate my job.

Visual studio 2017 with Xamarin:

* writing some sweet code, life is good.. build and run.
*change int age to 2, build, build failed, no single message why.
*clean, clean failed, no single message why.
* build rebuild clean all or by project, nothing works, no single message why.
*change nothing, restart VS, build success !
* writing some code, same problem
*restart VS, "this project is not compatible with Visual Studio"

Good bye guys, I'm gonna kill myself

Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best. - Clean Code

You vs The guy she tells you not to worry about...

PM approves all UI and project gets assigned to me. He then makes tons of UI changes that will affect the workflow of the approved UI. To this point, code was clean and well documented. I request a few days to re arrange the code to reflect the new workflow. PM says: I need a minimal product. I don't need it clean. I want speed to ship and start marketing. That's where I stopped caring.. To the next dev, I am terribly sorry..

Yesterday, a very good friend of mine who is a philosopher has given me a present: the book "Clean Code" by Robert C. Martin.

This summer is going to be very good. I'm very greatful.

Fuckwit tried to lecture me on clean code.

Checked his work, it seems like he writes the spaghettiest spaghetti I've ever seen. Who would have guessed it. At least he knows that something called 'clean code' exists.

via "clean code"

I saw this on the first page of a book that discusses techniques for writing clean code... The more I think about it, the more accurate it tests.

I think Clean Code: A Handbook of Agile Software Craftsmanship by Robert Martin should be a must to read.
In school no teacher puts emphasis on code quality.
They should learn how to name variables and functions the right way at an early stage in order to better perfect their craft :)

Be careful when you go down the rabbit hole of creating custom observables (rxJS).

I wasted half a day just to find out that there are hot and cold observables and that the whole time I tried to use the wrong one.

It finally works. 01:00 in the morning.
My boss will be proud when he pulls the changes and the code looks completely fucked up (clean, well structured code, but he doesn't really know observables).

Now something different: Sleep. Cya.

"No matter how slow you are writing clean code, you will always be slower if you make a mess." - Uncle Bob Martin

Some days you write your code and it all goes well.

All your tests pass, you write clean code, you solve your problems nicely.

Other days everything that can go wrong, will go wrong.

...the latter was the case for me today.

Wanted a quiet day at work this Monday so updated my development laptop to Ubuntu 16.04. Ended up spending the whole day fixing it. ¯\_(ツ)_/¯

I rewrote something in clean 20 lines of code, while my coworker had worked hard and ended up with like 80-100 lines. I did not talk to him before I did it, but asked him to review what I did. I still had to learn how to properly work together..

I wish all newbies would read clean code. I feel if you understand the concepts you can more easily join an established team and contribute more quickly with less do overs. I realize writing elegant, testable code is like making good whiskey. It takes time.

I just realize, I can make my Js code shorter by doing this:

for(let i in fruits){
console.log(i + ' ' + fruits[i])
}

instead of this:

for(let i=0; i<fruits.length; i++){
console.log(i + ' ' + fruits[i])
}

Trying to keep my code clean when once again changed requirements arrive

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

There is clean code. There's spaghetti code. And I just discovered there's spaghetti after being thrown up code.

Apparently `a || b` is unreadable to set a default value for a string in JS, but assigning temporary variables and use if statements all over is better somehow.

My code reviewer said use `a ? a : b` except it failed eslint, so he went back on that. (eslint suggested `a || b`, ffs.)

• Plan out everything by taking notes on the rough functionality of the project and how it could be done in a preferably simple way
• Writing code, but documentating it while doing so
• Also trying to write clean code so it can be more easily built upon
• Also keeping everything simple. If I'm using nasty, unreadable one-liners because of efficiency advantages, I'm putting a comment there for what could alternatively be used + explaining it
• Abandon it because side projects never get done

Biggest sin is writing code without taking into account clean coding and just doing what ever is necessary to make the code work

!rant

I got Clean Code for Christmas, it is such a good book. I can't recommend it more.

Im the only who what happened this? 🤔

"The only way to make the deadline - the only way to go fast - is to keep the code as clean as possible at all times."
Uncle Bob

Spread the word.

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!

When it comes to the indentation or look I am fully consistent.
But when it comes to naming I am inconsistent like a crack whore telling she's clean.
Camelcase, underscores inconsistent variable and function names. I use all of them within a single file. On some days I even switch languages.
I truly am miserable in code consistency. Is there any good advice to keep the code consistent?

I think "clean code" won't last.

With the ongoing democratization of coding and the myriad lowest-common-denominator coders flooding the market, the concept that code should simply explain itself and be intuitive to all readers will be more and more difficult to achieve.

Clean code requires the reader be on the same or greater technical skill level with the language than the authors. As developers go back to being generalists from over-specialized this becomes more of a time waster than a time saver.

[...] we should never ignore any part of code. The parts we ignore are where the bugs will hide.
- Uncle Bob

So we had a class that should have 2 states 0 or 1, you think my coworker would be smart enough to represent it with a Boolean? NO!

Represent the state inside the object as an int then when using the object in a function creates a Boolean that determines the state of the object and after the function done it's job THEN call another function that takes the object and the Boolean and change the int state inside the object depending on the Boolean.

Wouldn't it have been whole lot easier to just you know..... Make the state a Boolean from the start.

When I saw this I knew I was witnessing a miracle of the human mind. God bless!

Ps: it wasn't connected to any kind of API nor server and there are never more than 2 states. It's just some local sequential code so don't assume it had a logical reason it's just a fuck up.

Tough realization 😳

Procrastination is weird... Their were a piece of code I wasn't looking forward to work on, so I started cleaning my apartment instead, putting some order in my files, and even tidy up my desk, which I didn't do for months 😐
And it finally took me 10min to actually write the code 😆
It's annoying, but I can't be the only one 🤔
At least I can enjoy a clean setup... Until it become a mess again...

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

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

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

Opened GitHub as usual today, somehow found my old repositories (created when I was a fresher). Opened them and felt why I'm still on this earth, pulled them, restructured all of them, pushed them back and now I can sleep!! 😴

have you ever felt having bad code ocd that you feel like you really need to clean this old project that you got assigned to fix, but cleaning the whole project up would take too much time and it is just not worth it . But you feel like you really need to do it...

copied a code for android from stackoverflow and it worked
edited the code no more works
removed the code and pasted the original code from stackoverflow and still doesnt work
clean and build and now the code starts to work

Told a teacher I finished a week worth of exercises, and asked for the next one
"This code is not yours. It's too clean, redo everything"

... what, is it wk64 already ?

Actually got these tips today:
1. Write code so clean that it won't need commenting.
2. UML and other flow charts and graphs are very important.

The feeling when you realize some people on the project are writing legacy code from scratch. Apparently it seems they've never heard of any coding standards, they think clean code and style guidelines are for the weak and single responsibility means one single method is responsible for a bunch of unbelievably diverse things. They are like the Gumbys of the dev realm but it's my brain that hurts every time I have to deal with their code.

When you're really fuckin proud of that extremely clean, elegant, efficient 30 lines of code. It might not be important, but holy shit it's pretty!!

Our Code everlasting
The all creating One
Coders Almighty

Through Our Holy Lines
Conceiving Algorithms
Konrad Zuse our Savior

I believe in Clean Code
I believe in Free Software
I believe in Open Source
Our Code is three in one
I believe in the bug-free project
That'll be compiled again
For I believe in the name of Alan Turing

Just bought this, hope to get POEAA and Clean Code soon as well

Half fact: Code reviews help to maintain clean codebases.
Full fact: Code reviews are a way to find out who secretly wants you fired.

Java teacher writes code on blackboard in comp lab

He tells us to try it out at our workstations.

We do. The code does work. We tell him.

He says: "There is something wrong with your compiler..."

Question is...we were around 30 students. Can all our compilers not work if we had used the lab before and the code we run worked clean??!?!?!?

We were flabbergasted

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.

Fucken Designers - Have you ever heard of fucken consistency?

Different looks and feels for the same thing in every single page? Wat the fuck man - I am trying to write clean and modular code for components and you guys are making hard -

Bomb Alert:
Fuck Designers *middle finger*

No matter how logically clean and simple your SQL code is, test your data....TEST YOUR DATA.

"Mh, I should just write a short comment instead of writing a novel"

// This is a fucking detailed explaination of this shit, even though you can clearly see what it does because I usually write clean code. Also, it's a one-line comment, so have fun side-scrolling

Reading CleanCode by Robert C. Martin again from time to time.

Tell that to almost all owners of my previous workplaces

Oh gosh... This week a "friend" of mine will have a job interview for a company I am working at. This guy really just can't Code. He has no understanding of clean code, abstraction etc. He just knows the basics. But he loves to brag how good he is and got his bachelor degree. Damn I hate this guy and I hope HR won't hire him.

Writing clean code.
Writing useful comments.
Commit before experimenting.

Just anything to prevent Technical Debt. Just because it works doesn't mean it should be kept as is. Later down the line you'll need to add a new feature and you'll spend 2x more time fixing the things you took for granted.

Refactoring sometimes gives an immense sense of satisfaction. (If it doesn't introduce more bugs)

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

Hope this would help someone

Dev at the start of a project: My code will be effective, clean and well organised!
Dev at the end of a project: console.log("Reverse engineering strictly prohibited.")

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

Nothing is more relaxing then finding some really bad code and clean it up in your free time with music in background. Love this kind of Friday's.

My area of focus has and always will be making sure my code is clean and to the point.

A refactor a day keeps the doctor away!

Recently, I had to make a minor modification to some Node.js code a coworker wrote a year ago which buffers stringified JSON into Kinesis. I just needed to add a new key to the input object, it took minutes to make the change, but hours to make sense out the absolute trash spaghetti code this guy wrote. After spending half a day trying to make his code readable, I just got so pissed off. I replaced his 15 files/+1,500 lines of uncommented code, filled with classes, factory functions, poorly named functions and vars, and so, so many spelling mistakes.

We now have a single, well commented, 300 line file that does the same thing.

Get that shit code out of here.

Found this beautiful piece of code, that I wrote apparently a year ago .... oh my 😂 🤦‍♂ 😅
If I could travel back in time, I would would slap myself for doing this. Although I remember, why I did this, because of many min()/max() operations that I needed. I wanted to keep the code, so that I would know, which code piece belonged to which part, but man ... is that badly written! Nowadays with Clean Code style, I would certainly do it differently.

Anyone have any good book recommendations? They can be language specific or universal. I'm halfway through clean code and love it. Wondering if there're any other world class resources y'all have used.

Yay ...
No more !important in SCSS...
All colors pulled from variables...
Such code ... Very clean 😂

Came into work this morning and my scrum master has decided to take my desk and now I'm working off my laptop screen. I forgot he needed 3 displays for Excel, Outlook and JIRA.

Spent ten plus years professionally coding, used c, go , python, openwhisk ,docker, kubernetes and God know what else. Now I have to convince those team members who coded so far in their free time that write fucking clean code, avoid dependency on distributed and hard coded configuration, how to build a product
Fuck my life

Want to read a book that can help me avoid newb mistakes and can help me write beautiful code ?

Pragmatic programmer(1999)
Or
Clean code
Or
any other book ?
Help me !!?

So true ...

"Many developers on a schedule aren't making efforts to write clean and efficient code, relying on idiot-proof languages (and consequently more RAM and faster processors) to make up for their malaise."

I envy all those developers with clean codebases and consistent coding standards and nice architecture.

I'm fixing bugs and optimize code in someone else written project. which looks like spaghetti. with naming conventions like "a", "bbb", "zA" comments written in unknown language and off course the deadline was yesterday.

I'm going to be that guy .... A lot of these rants are about code compiling first time .. Throwing away code you wrote because you didn't need it... Getting in the zone and writing a billion lines before you compile .... Am I the only freaking person here that does TDD ? My rant is wake up people ! People evangelize about it because it fucking works !

For my school project I made an Django app and after a while I implemented more and more functions, but now the code is unreadable and I began hating working on the project. So I rewrote it and added documentation and now I have a beautiful application with documentation and clean code!

A colleague of mine who doesn't know how to write simple conditions and sends button code from backend in loosely coupled design.

Worst of all she doesn't wants to get updated to the latest programming structure and no signs of learning on how to write clean code!

What's wrong here? (facepalm)

So I'm about to finish The Design of Everyday things by Don Norman and I have Clean Code coming up next.

But what are some good programming books that are tech agnostic?

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.

Today I feel like a coding vampire, let me create a new Xamarin project and boOoOost with the code!!
*Creates a clean project, finds 1492 errors* well... f*ck it

Anyone read the book "clean code "? Want feedbacks! Thanks!

Day of the month

After I read clean code I talked to a fellow developer about some concepts. Later I reviewed some code of him and he clearly got the concept (not)

Java
...
If (isTrue(someValue))...

public boolean isTrue(boolean value){
if(value == true)
return true;
else
return false;
}

I always feel inspired by programming when I create some algorithms or programs which I can use when I need to.

Small utilities and command line programs r what I make at times... and I also enjoy trying to implement them awesome algorithms 😍

However, most inspiration I get is from looking at C code though ( especially the Linux kernel... that code is SO clean 😍😍 )

(PSA: serious replies to this kind of wk tag might be best suited under Random)

"The way you've done this seems much less complicated that what I would've come up with."

"You've been reading Clean Code?"

"I didn't think that was possible, nice."

And finally, the most extreme one:

"Can you print this code for me so I can hang it on my wall of good code?"

Learn early on how to write clean and maintainable code.

Has anyone here read the book "clean code" by Robert C. Martin and can recommend it?

That I should try out some of the functional concepts

That awkward moment your company worker realises you just refactored his code

This year I want to become a better programmer. I ordered the book clean code and want to focus on writing more and better unit tests.

If anyone has any tips on how to improve or how to get tips on your code

Not really in work as a job, these people inspired me rather in lifestyle and thinking: (these are not quotes!!)

Richard Stallman - you can't be sure the program isn't harmful unless you see and understand the code.

Linus Torvalds - doesn't matter if you like the person or not, let the code speak for him/her.

Raymond Hettinger - there are both stupid and smart people. It doesn't matter. What matters is asking the right questions and providing clean and explaining answers.

Unit of code is measured in what the fu**s/minute !!! 😆

Running the selenium tests again to look busy and give me an excuse to spend more time on devRant.

I made 60 lines of modern, clean, multi threaded, optimized python3 code to deliver data from GIT to IBM ClearCase, on old Windows VM, hundreds of files (CC is file-based version control, every file has it's own change)

This calls for sauna today to definitely get rid of this dirt :)

And they said devops is all around docker nowadays :)

You know why i hate JavaScript?

Instead of writing

return x.y.z;

I wrote

return
x
.y
.z;

Just for making the code look clean
and everything broke...

ML Dude: “Hey see what I did with this python code. It is so clean and dope”
Business Boss: “Well Done.”
ML Dude: “It is a nice approach don’t you think.”
Business Boss: “How does this put a money in my business account?”
ML Dude: “Ehmmmm”

OH MAH GAWD, FUCK ECLIPSE.

Just thank you so much Eclipse, for executing the entire build pipeline instead of running the last configuration.

Thank you so so much for considerately forcing me to clean upon every change to the codebase, also obliterating reliable hot code replace.

Special thanks for letting me clean once more, after the pipeline finished.

And thank you for the search bug, where all CTRL+H searches result in an error message, even though the search is being conducted.

Just go fucking die, you tremendous piece of garbage.

Sitting here reading Clean Code and read the heading, "How Would You Build a City" at the beginning of chapter eleven. Damn it now I just have the urge to put the book away and play SimCity.

Start the reading of "clean code".
First thing that i have learn "The only valid measurement of code quality: WTFs/minutes".
What do you think about it ? Agree or not ?

Learning to code is like learning to write when you were younger. It can be sloppy or clean but if you keep at it it'll probably become clean. But, with these sites like code academy that accept only one solution to the problems they present it's as though you're being told that everything you're doing is wrong eventhough you get a solution to the problem in the end. It bugs me that these sites want people to code the exact same way.

I find that open-sourcing my project is a way better motivation to write good, clean code, than pool parties for hitting the gym :)

Let's face it: I am and will always be a tinkerer. Yes, I know my ways around, I can sneak into legacy code bases easily and throw new stuff in there, I've seen software stacks. But scarcely sound design, really modular. Even from the cleverer, experienced ones. They can master more complexity, so they can handle more spaghetti. Some essay from the 80's had this grand idea to organically 'grow' software. That's how it looks like most of the times: cancerous, parasitic super fungi (armillaria). Yeah, we all know have to fight bit-rot and entropy, but it was all lost before already. We'll never get rid of legacy protocols, legacy code.
And even when we go green field, start a fresh. Yeah, take a great design, make everything new, after some months of throwing features and outer constraints at the thing, it's the same old mud again.
But we can still dream on: some day I will design great APIs, I will have great test coverage, documentation, UML design, autometed tests, fuzzing, memchecking, I'll work professionally, clean coder style.
Pfft forget it. Maybe change for consulting, because we'll continue to dream of the 'clean' code, so you can sell the next 'recipe', development method. It's like diets. As effective. For the one selling.

When your mostly done code that you spent time on documenting and keeping clean gets handed over to the sloppiest dev on the team. Because that dev is out of tasks and you got other work that moved up in priority. I really hope he doesn't ruin everything :(

After reading Clean Code principles:

Before you rename your method, remember to use the refractor option
😌

Things just got real

Last Friday night instead of partying, or seeing a movie I stayed home to clean up some code for a potential job interview. Good times! :D

Got this from Robert Martin's book: Clean Code(not my work).... I am guilty of the one on the right

I always do reformatting my code to keep it clean and readable, so I have a reflex of doing it a lot of time.

Even on a file with thousand of lines with several persons working on it

but I hate to see that in my changes, 95% of my changes are random tabs that my auto reformatting erases.

Clean Code philosophy

Goals:
-> Write clean code
-> Never trust the code
-> Never use PHP
-> Stop procastinating
-> Stop ranting

The best dev advice a dev has given me is to write clean and structured code from the very start of every project. Changed my life in general.

"How you do one thing is how you do everything."

Wrote a set of beautiful Swift functions. Runs Xcode, nothing. Checks code...looks good...clean build, delete app, re-install, rebuild...nothing. Checks documentation, watches three videos, re-writes code...nothing. Stares at screen for an hour...realizes I never actually called the functions. Closes laptop, checks self into pysch ward.

Automatically clean up code, removing redundant and duplicate bits, splitting large functions, and formatting it nicely. Especially useful when trying to understand some garbage code someone else wrote which you need to rewrite.

How to write unmaintainable code and keep your job for life, tip #476;

Use A.C.R.O.N.Y.M.S. to keep the code terse. Real men never define acronyms, they understand them genetically

me: i dream of a day where i am given 5 months to re write a certain huge part of our code. where i am free to rethink it, document and write clean code from the ground up.

my company: maybe when ur free, for now, here is 81 tasks that are hacky fixes for bugs regarding that big chunk of unmaintainable code

ha!
from 'clean code' by Robert C. Martin