What are your worst coding habits?

Is it bad commit messages, getting distracted by social media, commenting out tests?

Let’s hear it all.

Comments

[selbekk]

I write git status at least 4000 times a day, for no reason whatsoever.

[Sundeep]

how about ls and clear

[Huy Duy]

You can use Ctrl + L instead.

[PlayBossWar]

Doing this all day long when I'm working for no reason, I don't know why actually

[José Coelho]

Yep that's me. I even write git status after committing just to make sure 😅

[GlyphCat]

And also git branch after git checkout just to make sure I'm on the right branch… 😂

[kaddkaka]

My prompt reflects which branch I'm on, super helpful!

[Sundeep]

That has actually helped me once, I'd forgotten to git add some files

[Sean Porter]

at least alias it to gst!

also: me too

[Casey Brooks]

With as much as I check git status, I don't have time for a 3-letter alias! gs is all I can afford 😜

[Anton Osenenko]

And gpr for git pull --rebase

[Mahesh Sunuwar]

Most of the time, git log follows git status in my case. :P

[kaddkaka]

tig gives me more information, more concisely. Try it out :)

[Khoa Huỳnh]

Underrated

[Jairo Malanay]

Is it bad ?
Im also guilty of this one + ls and clear

[Bhupesh Varshney 👾]

Been there
😂😭

[Vicente G. Reyes]

This sounds like a good practice😂

[ahmad_haqqer]

me too dude

[Alan Barr]

Never taking the time to learn hotkeys. Not reaching out to a second set of eyes before spending too much time on something. Not doing enough design up front.

[Ben Halpern]

Are you me?

[Sean Porter]

I use vim for basically everything & I can't remember how to do macros without looking it up. I think just generalize this to "not learning your tools effectively" & I totally agree.

[Jonathan Speek]

This is super relatable.

[Alex Antra]

I rewrite other people’s code to my extremely high standard so I can understand it. Such a time waste.

[Dominik]

I know this far too well. There is this strong feeling of „You can’t leave it like it is, when you know it.“ but in the end ... it would most likely run for ages without any issues if we wouldn’t rewrite it. And maybe nobody would ever touch it again. :-)

[Ben Halpern]

I’m sure this thread will contain much worse habits than that! 😂

[Helen Anderson]

Haha! you are far more patient than I am!

[Hugo]

I do not write unit tests 😔

[DIANE GAYDEN]

I knew if I kept reading I'd find my bad habit.

[Jacque Schrag]

Same! I've never written a test. I know that I should, but... ¯_(ツ)_/¯

[Christopher Kade]

Small plug, but I wrote an introduction to unit testing if that could help any of you 😃

dev.to/christopherkade/introductio...

[Jacque Schrag]

This is great, thank you!

[Manda Putra]

Dateline !== No test, or just lrave like this

Agile !== No test

[Yaser Adel Mehraban]

Not reading enough docs, whether it's a framework or API

[aravind_reddy]

Totally relatable

[Vicente G. Reyes]

Stare at my editor -> search for help in duckduckgo -> open social media -> change music on spotify😂

[Bhupesh Varshney 👾]

That's literally me every single day 😂😂

[Carlos Garcia ★]

Same. ❤

[Helen Anderson]

Being too lazy to turn off 'helpful' system settings, like the one that autocompletes a closing bracket. I used to end up adding a closing bracket myself and then having too many so had to hit backspace to get rid of one.

Now that that has become muscle memory, whenever I'm not using that tool I hit backspace on autopilot even though there is no 'helpful' closing bracket to get rid of.

[Ben Sinclair]

I do this all the time!
It's all muscle memory now.

The other way the IDE gets in my way is when I want to add a closing bracket or parenthesis but my cursor is already immediately before one and the editor treats it as if they're the same - so I think I've added enough, but oh no.

[Helen Anderson]

Ugh. Instant rage quit.

There are also some strange moments when the cursor just vanishes completely and I don't know where I am anymore.

[Ben Halpern]

Ah yes, been there.

[Dinesh Pandiyan]

Step 1: Spot a code smell
Step 2: Add a // TODO comment
Step 3: Never get back to it

Repeat.

This is the story of my dev life 😔

[Forest Hoffman]

If you're a VS Code user, checkout the Todo Tree extension.

It's a nice alternative to searching in all files for // TODO or // DEBUG before commiting!

[John Dev]

Good tip 😉

[Brian Kephart]

Not using feature branches.

[Ben Halpern]

This was me until I worked with folks who set great examples. I eventually learned better habits.

[Sean Porter]

Not sure I'd agree with this one, depends on what you're trying to accomplish.

Committing directly to trunk has its benefits, everyone gets the changes immediately but you just need to make sure that the changes are self-contained enough to not break anything.

I used to think this was the way to go too until I read Continuous Delivery
all the way through.

[K]

Trunk based devlopment ftw.

[Phuong Huynh]

haha, you should try to fix it soon

[Stefano Armenes]

You should try git flow :)

[Donna Hogan]

• git push --force on a regular basis
• using VSC to open dot files and not taking the time to learn vim or nano, etc

[selbekk]

My git alias for that command is git fush 😄

[Robert Schaap]

I need that in my life. I'm an obsessive compulsive interactive rebaser.

[Ben Halpern]

I don’t think the second is a bad habit. There’s no special reason one needs to be using bin or nano imo.

Vim won't make you a more productive developer

Mac Siri ・ 1 min read

#healthydebate #vim #editors #productivity

[Eric Curtin]

I think all Unix/Linux developers should know vim. Because vi or vim is almost always installed on these variants. Sure for local development a UI is great, a very useful tool! But for editing files on remote machines, the ability to ssh to a remote machine and make a quick change is very important.