Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "habit"
-
I left a company once. Was there with one colleague and we had this kind of code review habit that we looked at each other changes befor merging them to the deploy branch. On my last day I made a dancing cat dance in front of our app as a tiny joke for him. He instead of reviewing just pulled this time and deployed the new version on the companies dev server without a look. So the fist time the cat showed up was appareantly in the first meeting after I left and everyone went completely crazy because they thought they got hacked.
I think they never found the hidden rock roll in the app.4 -
In the darkest of days, I discovered how to remote login to my computer at work through the company vpn. I then proceeded to work overtime at night in secret for a week or so, writing documentation and refactoring code.
I finally woke the fuck up and realized that I shouldn't be obsessing over proprietary codebases that do not belong to me, and I should put this misguided energy into my own projects.
So yeah, as a bad dev habit I'm working on fixing, this fits the bill.3 -
Not really a dev habit, but a habit many devs have.
My beyond fucked up sleep schedule.
SLEEP CAN
SUCK
MY
ASS
I've woken up at 8 and went to sleep at 12 for two days, and I'm beyond happy with the purely accidental progress I've made, really hope to not fuck it up this time like always.3 -
Habit I'm trying to fix?
Doing it all myself. I've been timeboxing my problems and forcing myself to ask instead of forcing myself to just figure it out myself. Communication isn't my strong point.2 -
Bad dev habit…
I am still learning like super fresh —
Second week of class.
But I am also looking at things and getting overwhelmed because I’m like idk wth that is.
But when I end up learning it —
I’m like ohhhh!!
I just overthink everything !!!8 -
Not really trying to, but probably should try to fix this bad, bad habit…
I keep wanting to fix and improve everything - and I keep taking notes, writing action plans et fucking cetera to the point the amount of work that should be done and I want to do is driving me insane. And they should all get done now!
In short, I should really either learn to focus on just one thing at a time for a meaningful period - or just cease to give a fuck. Either could work.3 -
One of my bad dev habits is that I tend to take up too much work because a lot of devs I had to work with seemed not competent enough. It's a bad habit because I get way overworked which influences code quality and deadlines.
I have to learn to trust more in others and give up some responsibility... it's hard though.
I think a big influence on my mindset has been that I never worked in a team bigger than 4 developers and I had way more experience in web dev than the others.
I sometimes may appear as an arrogant prick, but it's not intentional.10 -
not sure if actual bad habit, or just a natural consequence of what i'm writing often being de-facto "exploratory code" so the "bad habit" is actually the right choice, or...
but very often when i finish a functionality and look at the first version of the code, and realize how bad it is, and how it blocks me to implement following features... rather than just fix/improve that code, i just want to nuke all of it and write it from scratch again, and "better this time", because it seems like much less work and effort than trying to gradually fix it "in-place".
it definitely feels like a bad habit though, because it often results in me deleting and implementing to completion the same thing 4 times in a row. -
Showing up to work every day after 25 years of this knowing that I really kind of suck at my job and feeling like I’ll never get to a point where I can say I’m fully caught up to the level of knowledge others I work with have or that I’m expected to have. I suppose this is a bad habit of attitude but it seems to be an actual reality for me with every passing day, week, month, and year. It’s all just too much and my brain just isn’t as agile as it once was (and it wasn’t all that agile to begin with).3
-
I have this habit of whenever I run up against an issue at work programming-wise (a step definition doesn’t behave the way I think it should, I have an error in the console when I attempt to do something and have to work out how to clear the error, etc.), I document the issue and the solution somewhere in the Slack.
This serves two purposes: discoverability for others who might run into that issue later and DISCOVERABILITY FOR MYSELF WHEN I INEVITABLY ENCOUNTER THE SAME ISSUE.1