What little things make you happy while coding?

I must say refactoring code to make it look beautiful is my guilty pleasure

Did you find this post useful? Show some love!

Deleting code.

(The context here being: working with problematic legacy code and getting to the point where you have new code (paths) that do(es) the same thing but without the issues, so that the old code, and its issues, can just be discarded)

Agreed!

Also, deleting code you wrote earlier in the project because you've made a more general applicable implementation, hence the old code isn't used any longer.

Yeah I saw that as included in the previous, since I don't see 'legacy code' as inherently being 'code written by somebody else' :-).

When we come up with this kind of comments:

//When I wrote this, only God and I understood what I was doing
//Now, God only knows

I would suggest just comment out codes rather than delete (or have versioning in place).

I see some kind of VCS as a baseline project requirement, and in that case commenting out code is a very big anti-pattern.

And even without it, should an obsolete version of a codepath forever remain in your codebase, even long after it's become sufficiently inconsistent as to be irrelevant?

Or deleting old code that just exists, is no longer used!

If I have momentum on something and I'm locked in with my ideal monitor setup I feel like Batman at his dashboard. So much power at my fingertips.

When things aren't going so smoothly:

It doesn't happen often because there's usually a catch when it does, but when code works the first time, I get really giddy :D

Yes, if all the tests pass immediately, that's a moment to step back and think reaaaaalllll hard.

True. The feeling when you write code and the computer does what you intended.

Ben Halpern DEV.TO FOUNDER

Hey there, we see you aren't signed in. (Yes you, the reader. This is a fake comment.)

Please consider creating an account on dev.to. It literally takes a few seconds and we'd appreciate the support so much. ❤️

Plus, no fake comments when you're signed in. 🙃

I'm a big fan of both having a calm + non-interrupted refactoring session or discussing with colleagues about alternatives of how to implement something or just naming conventions to plan to use.

The pleasure of finally being able to get it or to make something work. Having all those tabs open to just have them closed is some of the best feelings ever... Especially when it looks like this:

True story. Pleasure of clicking on "close tabs to the right" 😁

  • Refactoring code to make it look good
  • When new code works on the first try and passes all the tests
  • Putting into practice knowledge that I've recently acquired
  • When I finally "get" something that I've been using but don't understand in depth
  • Reading good code written by others and getting mindblown by what I've learnt from them

+1 for the last one. I've been working as a junior/front end dev on a freelance project with a C#/asp.net developer who has 12 years of experience. Reading his code and studying it until I understood how all the functions worked was a complete game changer!!

I really like writing code comments, although I don't do it too often. I'm still learning how to make them meaningful first.

I was taught that you should not use comments. To avoid comments your code should be written in a way that can be read like a comment.

I wrote a little article showing the difference of code that needs comments and other that it doesn't.

There are comments and comments. The comments explaining what the code does are usually a symptom that the code is convoluted and difficult to understand even for the person who is writing it.

On the other hand, there are comments like:

# This solves a bug in the library Fubar that prevented the Baz 
# from being executed. See: https://github.com/fu_bar/baz/issues/454

Or:

# Temporalirly removed as per request in Issue #1243

Those make perfect sense to me.

A lot of truth to this, but an exception can and should be made when something merits an explanation of why it is the way it is. Comments should be few and far between in well-written code, but still used when there's an actual need. For me that's usually just when I had to dig to find a way to make something work when a more intuitive solution wouldn't work in that specific case.

Indeed, some business concerns are just impossible to explain by code itself and as you've said, logic that by some black magic doesn't work.
The key is to know if comments are up-to-date with the code as refactors come and go and not everyone updates the comments.

With this I fully agree, that's something I've been trying to improve on myself.

While I agree with not using comments where the code can demonstrate its own purpose and mechanism, I don't like absolutes like "don't use comments". An RFC number or something can be very helpful, or a link to where you found the code you just copy-pasted.

So am i.While i agree with Jose Tomas that try to make your code self-interpretation as possible.I'm trying!

I read Stephen King's book On Writing, he described the development of the story as carving something out of stone. You just start hammering the hell out of the block then it just starts resembling an image (something like that).

My reaction was "Haha, that's what I do when I write code"

Only when I read that book I realised that that might be the reason why I don't look forward to finishing projects - hammering away is fun.

I love working on the heavy parts.

I absolutely love getting to build things from the ground up. Some of my favorite things I've done at my job were things I had to start from scratch. I enjoy most coding tasks, even fixing bugs, but my favorite by far is seeing a feature or product I helped make with no code to start out with.

Refactoring, getting rid of code, Visual Studio Code that sometimes does magical stuff, having tests passing and how easier things are now that I'm using a 24" inch monitor again instead of the Macbook's 13" :D

Coming back to old code after learning something new and applying it there. Feels great and makes me feel like I'm progressing, especially since I want to do this for a living and I only do it as a hobby at the moment.

Fixing up brittle, archaic tests so that they're fast and much easier to follow and iterate on.

In general just getting things to a more maintainable state for the future (probably due to joining teams where the codebase I have to grok is nearly impenetrable).

Lining stuff up vertically. Whether it's the values in key->value literals, wrapped method parameters, class members, or anything else, everything is just so much nicer to look at when it's all lined up vertically.

Any time my commit shows that I've removed more lines than I've added. Best feeling ever.

Really basic but, autocomplete is the little thing that gets me going the most. That breeze you get when you press Tab and the function appears, is something magical.

Context: I've been coding for a little more than a year, being self taught, I discovered autocomplete like two months ago.

It's very useful! Since i have to change languages from time to time it's a challenge to memorize what it will autocomplete and if it will be the same that i want hehe

An office with a door, so I can focus.

My guilty pleasure is I enjoy fixing bugs. Each bug is like a mini-puzzle, and (usually) is apparent whether or not it is fixed or still broken.

Two large monitors. And I'm super particular about keyboards. (IBM Model M forever!)

Clean code makes me happy. I wish there were refactoring tools for C++, like I had JetBrains ReSharper for C#.

The one surprise I had was how much I enjoyed TDD using C#, NUnit, and the awesomely amazing test-runner NCrunch. I really miss that now that I'm back in C++.

Endless supply of Diet Mountain Dew.

Love fixing bugs too!

If it's not a trivial bug you usually learn A LOT chasing a bug. Sometimes you end up with patches to third party libraries, sometimes you end up with more insight about the framework or the language or even parts of your own code you forgot about :D

My two favorite bugs was finding a bug in the compiler (can't remember which compiler anymore, too many years ago - I'm sure it was not GCC), and finding a bug in the gdb debugger.

My guilty pleasure is replacing large external dependencies that were included just to avoid writing a few lines of code oneself with said few lines.

The last codegasm I had was when I replaced the whole of moment.js in an app where it was only used to format the users' time zones for tracking purposes with 4 short lines of script. Boom, 60kb less for the user to download.

Yes, I know there's NIH (not invented here), but sometimes I feel like that's just an excuse for being lazy and using overengineered solutions for simple problems.

No bugs ??? Thats a dream

But working in a peaceful environment , keeps me calm.

Already answered Stack Overflow Questions. If not how will I solve a problem ?

Refactoring code . Sure that helps better understanding.

Comments in code. But who are properly doing it.

Finding someone else has the same, unanswered problem on Stack Overflow and remembering once you've solved it to go back and explain what you did with examples. Doesn't happen to me often enough, but it's a good feeling.

The first time something moves when making a game (especially with a new Lib/Lang/Engine/Framework)

When a complicated VIM-Command/Macro just works as intended

When I write really badly formatted code and Prettier/Gofmt makes it nice after saving.

TFW I realize "oh I can get rid of those 50 lines of CSS" and I type 50-D-D-Esc-:-w
(Delete 50 lines and save the file)

I like testing with silly content, be it inside jokes as a message to see if a component has rendered, or injecting cat pictures as place holders.

My all-time favorite is adding in a marquee tag that scrolls by with "H E L P" in big letters when working with something that's been frustrating me. It never gets old, for some reason, and it helps me feel like I'm in less of a rut.

There are two main things that make happy while coding.

1) Candy and junk food in the workplace.

2) When we have a situation that really needs to be resolved and I can resolve it with a good, reusable code.

I enjoy that moment when working on one language/project and suddenly something in a different language/project becomes clear.

That and when something extremely difficult and frustrating suddenly makes sense and becomes simpler.

Booting up the computer, open up the project I was working on and knowing exactly what I want to do.

Afterwards I'll likely make some refactoring to make sure it is modular and easy to upgrade.

Having a strange idea popping in my mind, immediately starting to code something and having some very basic structure that does the job, a few hours after.

Refactoring tests so that editing or adding tests are not a pain then in the ass anymore. Using stuff like Page object pattern when I need to refactor UI tests.

When another dev discovers your refactoring or implementation and thanks you for making their life easier. That's the best way of making me happy, I think.

Rewriting code that I wrote 10 years ago and realising just how much better I've got at this.

The sound of the stroke keys ... especially when the flow is uninterrupted.

It can be pretty basic but what I love the most is running that heavy, bothering and complicated problem I had working smoothly.

Yeah! Same guilty pleasure there. Even though refactoring will take time, I'll take it. Just to make the code smooth and beautiful. 😌

Well, for me it's a warm cup of tea (or lemon juice in summer) while listening to the right kind of music. That helps me focus on the task at hand.

Coding without refreshing, lol. I would try to go as far as I can on a feature without loading the changes.

I love learning something new, be it a new design pattern, framework, design pattern, programming language...

Code that runs without any errors it feels me happy while coding

Solving real life problems!The only little big thing!

I used to be really concerned with proper indentation, now Prettier handles that for me and that makes me really happy.

Writing some test code quickly without any syntax checking from the IDE and it working like a charm the first time I run it.

Finding a bug after hours of looking up for it.
Finding a big after a really short time of looking for it.
Guessing by a first attempt what a code (not mine) does.

Firstly, no warnings and red squiggly lines. My code compiling. Passing unit tests. And not forgetting a cup of coffee too.

I love when someone hands me a paper document to fill out or for information. Every time I see this as an opportunity to show them how it could be done with web or mobile.

Finding that past-me has already implemented stuff I want to implement.

"So, and for the rest of the day... oh well guess work is done for today!"

When your code runs perfectly in the first time, there is no words to describe the feeling

Continuously seeking ways to lessen load times and memory consumption! Ahh best days!

  1. Quiet and silent environment. I work in an offshore service industry kind of setup and I hate it when people put their overseas call on speaker eventhough only one person is attending.

When I finally solve that one problem that had me stumped.
Or those 'I didn't think that would work' moments lol

Classic DEV Post from May 16

Taking Notes

Using bullet journal techniques to take notes and get things done

READ POST
Follow @monknomo to see more of their posts in your feed.
Jose Tomas Gonzalez
I like working on new projects, having new ideas and trying them out. The worst it could happen is that you learn something new.
Trending on dev.to
What are your programming blogs?
#discuss
Back to basics: Naming
#naming #javascript #programming #discuss
What are the first differences you noticed in GitHub after Microsoft bought it? Post here yours!
#github #microsoft #discuss
What's your approach to fixing a "long-term" hairy bug?
#discuss
Follow Friday!
#discuss
Which contentious opinions in programming actually matter?
#discuss #webdev #programming #grannyrulescomments
Ever feel like you have "Programming Synesthesia"?
#discuss #programming #productivity
How do you make time for your dev/tech projects?
#discuss #productivity