Is it bad commit messages, getting distracted by social media, commenting out tests?
Let’s hear it all.
For further actions, you may consider blocking this person and/or reporting abuse
Is it bad commit messages, getting distracted by social media, commenting out tests?
Let’s hear it all.
For further actions, you may consider blocking this person and/or reporting abuse
dev.to staff -
Karl Esi -
Rohit -
Dmitry K -
Oldest comments (164)
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.
Are you me?
This is super relatable.
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.
Not using feature branches.
This was me until I worked with folks who set great examples. I eventually learned better habits.
You should try git flow :)
haha, you should try to fix it soon
Trunk based devlopment ftw.
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.
I rewrite other people’s code to my extremely high standard so I can understand it. Such a time waste.
I’m sure this thread will contain much worse habits than that! 😂
Haha! you are far more patient than I am!
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. :-)
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.
Ah yes, been there.
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.
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.
When I need to use search, instead of searching in VIM, I launch sublime and search in there.
ripgrep needs to become your friend 😂
o.0 this is a thing?! That's awesome! Definitely going to grab that as soon as I can.
It's also the tool that Visual Studio Code uses to search :D
Confession:
TFS (Team foundation) lets you commit your code without a message. I sometimes commit without a message...
And I reformat others' code.
The worst offender is always Googling for simple tasks such adding simple HTML elements such as adding CSS link tags and script tags... (I wonder if it's just me not knowing how to add them out of memory 🤔)
No commit message is such an odd thing to me.
I also always good css link tags 😂
gitway of forcing a message should be how all VCS should be IMHO.We moved all our code from TFVC to TFS Git which I can highly recommend. You get the best of both worlds (TFS backlog and project control together with Git version control). And you will never commit without a message again 😉
Wow 😮
Thanks, Jacob.
I wasn't aware it was possible to migrate to TFS Git and keep all the history.
I will check it out~
git push --forceon a regular basisI 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
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.
My git alias for that command is
git fush😄I need that in my life. I'm an obsessive compulsive interactive rebaser.
Not reading enough docs, whether it's a framework or API
Totally relatable
Stare at my editor -> search for help in duckduckgo -> open social media -> change music on spotify😂
That's literally me every single day 😂😂
Same. ❤
Using Facebook's messenger when I'm coding. I can't let go of this one. I think it's because I isolate myself too much. I don't go out. Not at all. I don't use Facebook (I only use messenger, I don't have a Facebook). I use Twitter to see Feed related to coding as well. So I just can't let go of messenger. I need to talk to people. But I consider it a bad habit because I keep it open while coding. It will probably be healthier to just use Messenger when I'm not coding.
I'm feeling this too. I talk to people but I think it's a huge waste of time. Like serious I'm coding 12h a day at a regular base but I'm feeling like I could do the 12h work in 6h if I close social media
Never doing the bandaid solution and always engineering things to a fault. This doesn't sound like too bad of a thing but trust me it's okay to put on the bandaid sometimes. I would have saved many hours if I would have put the bandaid solution on some features that my project owners didn't even want a few weeks / months later.
Hmmm.. using git add wrongly that commit all my ignore files for the project I'm working on.
My git alias,
pf,is just for that,alias.pf push --force-with-lease. More here 😉My Git Aliases
Nick Taylor ・ 5 min read
I write
git statusat least 4000 times a day, for no reason whatsoever.Been there
😂😭
how about
lsandclearDoing this all day long when I'm working for no reason, I don't know why actually
You can use Ctrl + L instead.
Yep that's me. I even write
git statusafter committing just to make sure 😅That has actually helped me once, I'd forgotten to
git addsome filesAnd also
git branchaftergit checkoutjust to make sure I'm on the right branch… 😂My prompt reflects which branch I'm on, super helpful!
This sounds like a good practice😂
Underrated
at least alias it to
gst!also: me too
With as much as I check
git status, I don't have time for a 3-letter alias!gsis all I can afford 😜And gpr for
git pull --rebaseMost of the time,
git logfollowsgit statusin my case. :Ptig gives me more information, more concisely. Try it out :)
Is it bad ?
Im also guilty of this one +
lsandclearme too dude
I get debug/Refactor/develop creep. Often I'm working on one thing and I notice something that can be fixed rewritten or moved somewhere so that it can be reused... Or I suddenly decide to stub out something for later later. Sure, it's stuff that had to be done at some point, but hard to explain or justify when you list hours to tasks for a single component and for some reason a component was finished, plus 2 stubbed, plus one refactored, and a new service was created. 🤪