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
Pranav Bakare -
Fazlay Rabbi -
Abdullah Al Mamun Fahim -
Onyedikachi Emmanuel Nnadi -
Top comments (163)
I write
git statusat least 4000 times a day, for no reason whatsoever.how about
lsandclearYou can use Ctrl + L instead.
Doing this all day long when I'm working for no reason, I don't know why actually
Yep that's me. I even write
git statusafter committing just to make sure 😅And also
git branchaftergit checkoutjust to make sure I'm on the right branch… 😂My prompt reflects which branch I'm on, super helpful!
That has actually helped me once, I'd forgotten to
git addsome filesat 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 :)
Underrated
Is it bad ?
Im also guilty of this one +
lsandclearBeen there
😂😭
This sounds like a good practice😂
me too dude
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?
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.
This is super relatable.
I rewrite other people’s code to my extremely high standard so I can understand it. Such a time waste.
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. :-)
I’m sure this thread will contain much worse habits than that! 😂
Haha! you are far more patient than I am!
I do not write unit tests 😔
I knew if I kept reading I'd find my bad habit.
Same! I've never written a test. I know that I should, but... ¯_(ツ)_/¯
Small plug, but I wrote an introduction to unit testing if that could help any of you 😃
dev.to/christopherkade/introductio...
This is great, thank you!
Dateline !== No test, or just lrave like this
Agile !== No test
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. ❤
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.
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.
Ah yes, been there.
Step 1: Spot a code smell
Step 2: Add a
// TODOcommentStep 3: Never get back to it
Repeat.
This is the story of my dev life 😔
If you're a VS Code user, checkout the Todo Tree extension.
It's a nice alternative to searching in all files for
// TODOor// DEBUGbefore commiting!Good tip 😉
Not using feature branches.
This was me until I worked with folks who set great examples. I eventually learned better habits.
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.
Trunk based devlopment ftw.
haha, you should try to fix it soon
You should try git flow :)
git push --forceon a regular basisMy git alias for that command is
git fush😄I need that in my life. I'm an obsessive compulsive interactive rebaser.
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
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.
Sometimes I struggle and go for the longer route instead of just focusing on the quick fix.
I often set a breakpoint and learn how code works from there instead of just looking at the documentation.
A part of me wants to fix everything but I've become much more pragmatic over time 😂
I try to do the right thing first.
Often I fail because of missing information, then I do a bunch of quick fixes second.
Then after the fixes built up too much, I do a rewrite as it should be and everything is good.
The second part often happens because I only find the missing information after I tried enough fixes.
Dumb problem and probably unsolvable 😒
Being too obsessed with code perfection instead of just shipping the feature.
Prettier and refmt helped me so much with this
I still tend to jump in and start coding my first idea. I tell myself it's a proof of concept or that I'm experimenting with different ideas but too often I just end up going with it and not putting the effort in to find a better solution.
I do this even if I have time to plan the project out, because I've worked in tight deadline agencies for so long it's become a habit that's hard to break.
This. I guess sometimes its also a strength. Atleast I tell myself...
Do it with TLA+ instead! 🙃
Not writing (and updating) documentation explaining intent and purpose.
I work in a small team (2 front-end devs), and my co-worker is a bit picky about documenting every function, class, method, etc etc.
But sometimes all he documents is something a function name tells it upfront, I really think there's no purpose in doing something like:
/** This function transforms lower case string to uppper case **/
function lowerCaseToUpper(str...);
If you declare functions and variables with intuitive names, sometimes there's no need to explain them :)
It is called self-documenting functions for a reason right?
yup... unless that function transforms the string using some alien computation, there's no need for that
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 🤔)
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~
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.